SkillAgentSearch skills...

creating-oracle-to-postgres-master-migration-plan

Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan

Install / Use

npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

91/100

Supported Platforms

Universal

Our assessment of creating-oracle-to-postgres-master-migration-plan

creating-oracle-to-postgres-master-migration-plan scores 91/100 on our quality scale, 183rd of 606 Data & Analytics skills we index (top 31%).

Its SKILL.md is 3.4 KB long, split into 7 sections with 2 code examples: a solid amount of guidance for an agent.

With 39,348 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
16/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so creating-oracle-to-postgres-master-migration-plan is actively maintained.
  • Our last check on 2026-10-28 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

creating-oracle-to-postgres-master-migration-plan compared with similar skills

All 4 of these similar skills score higher than creating-oracle-to-postgres-master-migration-plan; compare them before choosing.

SkillScoreStarsUpdatedFormat
creating-oracle-to-postgres-master-migration-plan (this skill)by github9139.3k53d agoSKILL.md
claude-memby thedotmack100117.6ktodayCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install creating-oracle-to-postgres-master-migration-plan?
Run npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan. The install tabs above show the steps for each supported agent.
Which AI agents does creating-oracle-to-postgres-master-migration-plan work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is creating-oracle-to-postgres-master-migration-plan safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is creating-oracle-to-postgres-master-migration-plan still maintained?
The repository was last updated about 2 months ago, so creating-oracle-to-postgres-master-migration-plan is actively maintained.

name: creating-oracle-to-postgres-master-migration-plan description: 'Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.'

Creating an Oracle-to-PostgreSQL Master Migration Plan

Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.

Workflow

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:

  • NuGet references: Oracle.ManagedDataAccess, Oracle.EntityFrameworkCore (check .csproj and packages.config)
  • Config entries: Oracle connection strings in appsettings.json, web.config, app.config
  • Code usage: OracleConnection, OracleCommand, OracleDataReader
  • DDL cross-references under .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/MasterMigrationPlan.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}

## DDL Artifacts

**Location:** {path to DDL artifacts, e.g., `.github/oracle-to-postgres-migration/DDL/`}
**External tool used:** {Yes / No} β€” {If Yes, name the tool (e.g., `ora2pg`) and note that Phase 4 (Schema & DDL Migration) can be skipped; PostgreSQL DDL artifacts already exist.}

## 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.

Related Skills

View on GitHub
GitHub Stars39.3k
CategoryData
Updated1mo ago
Forks5.0k

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
creating-oracle-to-postgres-master-migration-plan β€” Universal Skill: Install & Safety Check | SkillAgent