Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncreating-oracle-to-postgres-master-migration-planExecute the skills CLI command in your project's root directory to begin installation:
Fetches creating-oracle-to-postgres-master-migration-plan from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate creating-oracle-to-postgres-master-migration-plan. Access via /creating-oracle-to-postgres-master-migration-plan in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.
Progress:
- [ ] Step 1: Discover projects in the solution
- [ ] Step 2: Classify each project
- [ ] Step 3: Confirm with user
- [ ] Step 4: Write the plan file
Step 1: Discover projects
Find the Solution File (it has a .sln or .slnx extension) in the workspace root (ask the user if multiple exist). Parse it to extract all .csproj project references. For each project, note the name, path, and type (class library, web API, console, test, etc.).
Step 2: Classify each project
Scan every non-test project for Oracle indicators:
Oracle.ManagedDataAccess, Oracle.EntityFrameworkCore (check .csproj and packages.config)appsettings.json, web.config, app.configOracleConnection, OracleCommand, OracleDataReader.github/oracle-to-postgres-migration/DDL/Oracle/ (if present)Assign one classification per project:
| Classification | Meaning |
|---|---|
| MIGRATE | Has Oracle interactions requiring conversion |
| SKIP | No Oracle indicators (UI-only, shared utility, etc.) |
| ALREADY_MIGRATED | A -postgres or .Postgres duplicate exists and appears processed |
| TEST_PROJECT | Test project; handled by the testing workflow |
Step 3: Confirm with user
Present the classified list. Let the user adjust classifications or migration ordering before finalizing.
Step 4: Write the plan file
Save to: .github/oracle-to-postgres-migration/Reports/Master Migration Plan.md
Use this exact template — downstream consumers depend on the structure:
# Master Migration Plan
**Solution:** {solution file name}
**Solution Root:** {REPOSITORY_ROOT}
**Created:** {timestamp}
**Last Updated:** {timestamp}
## Solution Summary
| Metric | Count |
|--------|-------|
| Total projects in solution | {n} |
| Projects requiring migration | {n} |
| Projects already migrated | {n} |
| Projects skipped (no Oracle usage) | {n} |
| Test projects (handled separately) | {n} |
## Project Inventory
| # | Project Name | Path | Classification | Notes |
|---|---|---|---|---|
| 1 | {name} | {relative path} | MIGRATE | {notes} |
| 2 | {name} | {relative path} | SKIP | No Oracle dependencies |
## Migration Order
1. **{ProjectName}** — {rationale, e.g., "Core data access library; other projects depend on it."}
2. **{ProjectName}** — {rationale}
Order projects so that shared/foundational libraries are migrated before their dependents.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
creating-oracle-to-postgres-master-migration-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend creating-oracle-to-postgres-master-migration-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
creating-oracle-to-postgres-master-migration-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
creating-oracle-to-postgres-master-migration-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for creating-oracle-to-postgres-master-migration-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in creating-oracle-to-postgres-master-migration-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: creating-oracle-to-postgres-master-migration-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.
creating-oracle-to-postgres-master-migration-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added creating-oracle-to-postgres-master-migration-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend creating-oracle-to-postgres-master-migration-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 55