Mfs Find
zilliztech/mfs
Search, grep, browse, and read across registered MFS data sources via the mfs CLI — codebases, docs, PDFs, web crawls, databases (postgres/mysql/mongo/snowflake/bigquery), issue trackers…
Official agent skill
by github in github/awesome-copilot
Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-master-migration-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creating-oracle-to-postgres-master-migration-plan .claude/skills/creating-oracle-to-postgres-master-migration-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "creating-oracle-to-postgres-master-migration-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-plan into .claude/skills/creating-oracle-to-postgres-master-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-master-migration-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-master-migration-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/creating-oracle-to-postgres-master-migration-plan .agents/skills/creating-oracle-to-postgres-master-migration-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "creating-oracle-to-postgres-master-migration-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-plan into .agents/skills/creating-oracle-to-postgres-master-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-master-migration-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-master-migration-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/creating-oracle-to-postgres-master-migration-plan .cursor/skills/creating-oracle-to-postgres-master-migration-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "creating-oracle-to-postgres-master-migration-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-plan into .cursor/skills/creating-oracle-to-postgres-master-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-master-migration-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/creating-oracle-to-postgres-master-migration-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-master-migration-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/creating-oracle-to-postgres-master-migration-plan .gemini/skills/creating-oracle-to-postgres-master-migration-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "creating-oracle-to-postgres-master-migration-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-plan into .gemini/skills/creating-oracle-to-postgres-master-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-master-migration-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-master-migration-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/creating-oracle-to-postgres-master-migration-plan .github/skills/creating-oracle-to-postgres-master-migration-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "creating-oracle-to-postgres-master-migration-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-plan into .github/skills/creating-oracle-to-postgres-master-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-master-migration-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot creating-oracle-to-postgres-master-migration-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/creating-oracle-to-postgres-master-migration-plan .opencode/skills/creating-oracle-to-postgres-master-migration-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "creating-oracle-to-postgres-master-migration-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/creating-oracle-to-postgres-master-migration-plan into .opencode/skills/creating-oracle-to-postgres-master-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-oracle-to-postgres-master-migration-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
creating-oracle-to-postgres-master-migration-planDiscovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan.
Creating Oracle To Postgres Master Migration Plan is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases. It works with PostgreSQL, .NET and GitHub. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Creating Oracle To Postgres Master Migration Plan loads about 862 tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 207 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 207 words, ~862 tokens.
.claude/skills/creating-oracle-to-postgres-master-migration-plan/SKILL.md (or your agent's skills folder).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 fileStep 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/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.
© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/creating-oracle-to-postgres-master-migration-plan of github/awesome-copilot.
Open the folder on GitHubat commit 727ff2e
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.
Creating Oracle To Postgres Master Migration Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Creating Oracle To Postgres Master Migration Plan this skillgithub/awesome-copilot | 40k | 1 repos | ~862 | Automated safety check: Pass | MIT | |
| Mfs Findzilliztech/mfs | 150 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Releaserogerpadilla/uql | 125 | — | ~842 | Automated safety check: Pass | MIT | |
| Mfs Ingestzilliztech/mfs | 150 | — | ~4.7k | Automated safety check: Pass | Apache-2.0 | |
| Meta Issue Creationcipherstash/stack | 157 | — | ~1k | Automated safety check: Pass | MIT | |
| Aspire DevchainNethereum/Nethereum | 2.3k | — | ~1k | Automated safety check: Pass | MIT |
zilliztech/mfs
Search, grep, browse, and read across registered MFS data sources via the mfs CLI — codebases, docs, PDFs, web crawls, databases (postgres/mysql/mongo/snowflake/bigquery), issue trackers…
rogerpadilla/uql
Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site.
zilliztech/mfs
Register, update, or re-sync data sources for MFS so they become searchable — postgres / mysql / mongo / snowflake / bigquery, github / jira / linear / notion / hubspot / zendesk, slack / discord /…
cipherstash/stack
How an agent files a GitHub issue on cipherstash repos — required structure (Background / Problem / Proposal), dumbed-down wording rules, and pre-filing checks.
Nethereum/Nethereum
Help users create and run a local Ethereum development environment with .NET Aspire — DevChain node, blockchain indexer, Blazor explorer, and PostgreSQL.
digoal/blog
抓取并汇总"数据库、AI、GitHub、AI 论文"近 1 周新闻,输出图文并茂(含 mermaid 图)的 markdown 周报到当前项目的 markdown/ 目录。覆盖 10 个数据源:postgresweekly.com/issues(自动解析最新 issue…
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Works with
Categories
Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Creating Oracle To Postgres Master Migration Plan is an agent skill from github/awesome-copilot, published by the product's own GitHub organization.NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan.
Creating Oracle To Postgres Master Migration Plan fits situations like: starting a multi-project Oracle-to-PostgreSQL migration; creating a migration inventory; assessing which .NET projects contain Oracle dependencies.
Run `npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a claude-code`. Or copy the skill folder (skills/creating-oracle-to-postgres-master-migration-plan in github/awesome-copilot) into .claude/skills/creating-oracle-to-postgres-master-migration-plan in your project. Claude Code loads it when a task matches its description.
Run `npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a codex`. Or copy the skill folder (skills/creating-oracle-to-postgres-master-migration-plan in github/awesome-copilot) into .agents/skills/creating-oracle-to-postgres-master-migration-plan in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-oracle-to-postgres-master-migration-plan, .gemini/skills/creating-oracle-to-postgres-master-migration-plan, .github/skills/creating-oracle-to-postgres-master-migration-plan and .opencode/skills/creating-oracle-to-postgres-master-migration-plan in your project.
SKILL.md names no scripts, command-line tools or credentials: Creating Oracle To Postgres Master Migration Plan is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Creating Oracle To Postgres Master Migration Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 862 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Creating Oracle To Postgres Master Migration Plan: Mfs Find (zilliztech/mfs, 150 stars), Release (rogerpadilla/uql, 125 stars), Mfs Ingest (zilliztech/mfs, 150 stars) and Meta Issue Creation (cipherstash/stack, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.