[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD460VR0XNKGSEYWS7XK8Y":3,"skill-same:01M6AD460VR0XNKGSEYWS7XK8Y":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6AD460VR0XNKGSEYWS7XK8Y","acreadiness-generate-instructions",null,"Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github\u002Fcopilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running \u002Facreadiness-assess to close gaps in the AI Tooling pillar.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Facreadiness-generate-instructions\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,9,38,39,40,41,42,43,44],"generate","acreadiness generate instructions","instructions","ai tooling","running","gaps","apply","for","claude-md","with","output","assess","dry","default","files","use","strategy","code","run","copilot","ai agent","2026-11-10 10:12:30",false,"---\nname: acreadiness-generate-instructions\ndescription: 'Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github\u002Fcopilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running \u002Facreadiness-assess to close gaps in the AI Tooling pillar.'\nargument-hint: \"[--output .github\u002Fcopilot-instructions.md|AGENTS.md] [--strategy flat|nested] [--areas | --area \u003Cname>] [--apply-to \u003Cglob>] [--claude-md] [--dry-run]\"\n---\n\n# \u002Facreadiness-generate-instructions — write AI agent instructions\n\nUse this skill whenever the user wants to **create**, **regenerate**, or **refresh** their custom instructions for AI coding agents (Copilot, Claude, etc.). This is the *Generate* step in AgentRC's **Measure → Generate → Maintain** loop and the single highest-leverage action for the **AI Tooling** pillar.\n\n## Output options\n\nVS Code recognises several instruction file types — AgentRC generates the most common ones:\n\n| File | Scope | When to use |\n|---|---|---|\n| `.github\u002Fcopilot-instructions.md` | Always-on, whole workspace | **Default** — VS Code Copilot's native instruction file |\n| `AGENTS.md` | Always-on, whole workspace | Multi-agent repos (Copilot + Claude + others) |\n| `.github\u002Finstructions\u002F*.instructions.md` | Scoped by `applyTo` glob | Per-area \u002F per-language rules in monorepos |\n| `CLAUDE.md` | Claude-specific | Add via `--claude-md` (nested only) |\n\n## Strategies\n\n- **`flat`** *(default)* — single `.github\u002Fcopilot-instructions.md` at the chosen path. Simple, easy to review.\n- **`nested`** — hub at `.github\u002Fcopilot-instructions.md` + per-topic detail files at `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`, each with an `applyTo` glob so VS Code only loads the topic when it's relevant. Better for large or multi-stack repos.\n\n> **Why `.github\u002Finstructions\u002F` and not `.agents\u002F`?** AgentRC's default nested layout writes to `.agents\u002F`, which is the right home for *agent-agnostic* repos (Copilot + Claude + Cursor reading `AGENTS.md`). For VS Code Copilot specifically, the native location is `.github\u002Finstructions\u002F` with `applyTo` frontmatter — that's what Copilot auto-discovers. This skill rewrites AgentRC's nested output to the VS Code-native location whenever the main output is `.github\u002Fcopilot-instructions.md`. If you instead chose `--output AGENTS.md`, nested keeps AgentRC's default `.agents\u002F` layout.\n\nFor monorepos, generate **area-scoped** instructions with `--areas`, `--area \u003Cname>`, or `--areas-only`. Areas are defined in `agentrc.config.json`. Per-area output is written as VS Code `.instructions.md` files with an `applyTo` glob (see below).\n\n### Topic vs area `.instructions.md` files\n\nBoth end up in `.github\u002Finstructions\u002F` but they answer different questions:\n\n| Kind | Filename example | `applyTo` example | Where it comes from |\n|---|---|---|---|\n| **Topic** (nested) | `testing.instructions.md` | `**\u002F*.{test,spec}.{ts,tsx,js}` | AgentRC `--strategy nested` topic split |\n| **Area** (monorepo) | `frontend.instructions.md` | `apps\u002Ffrontend\u002F**` | `agentrc.config.json` areas + `--areas` |\n\nYou can have both at once: a nested set of topic files plus per-area files for a monorepo.\n\n## Per-area files with `applyTo`\n\nWhen the user opts into areas, emit one VS Code-native `.instructions.md` file per area at `.github\u002Finstructions\u002F\u003Carea>.instructions.md`. Each file MUST start with frontmatter declaring the glob the rules apply to:\n\n```markdown\n---\napplyTo: \"apps\u002Ffrontend\u002F**\"\n---\n\n# Frontend area instructions\n\n…AgentRC-generated content for this area…\n```\n\nWorkflow:\n\n1. **Read `agentrc.config.json`** to discover declared areas and their `paths` \u002F globs. If `paths` is missing, ask the user for the glob (e.g. `src\u002Fapi\u002F**`).\n2. **Run `agentrc instructions --areas`** (or `--area \u003Cname>`) to produce the per-area body content.\n3. **Wrap each area's content** in `.github\u002Finstructions\u002F\u003Carea>.instructions.md` with the `applyTo` frontmatter taken from the area's `paths`. If the user passed `--apply-to \u003Cglob>` on a single-area call, use that glob verbatim.\n4. **Leave the main file alone** — the root `.github\u002Fcopilot-instructions.md` stays as the always-on instructions; `.instructions.md` files only kick in for matching paths.\n\nNaming: lowercase, kebab-case area name. Examples: `.github\u002Finstructions\u002Ffrontend.instructions.md`, `.github\u002Finstructions\u002Fapi.instructions.md`, `.github\u002Finstructions\u002Finfra.instructions.md`.\n\n## Steps\n\n1. **Pick the target file**. **Default to `.github\u002Fcopilot-instructions.md`.** Switch to `AGENTS.md` only if the user mentions multi-agent \u002F Claude \u002F Cursor support.\n2. **Always ask which strategy to use** — `flat` or `nested` — unless the user already specified one in their message or via `--strategy`. Present the trade-off briefly:\n   - **Flat** *(default)* — one `.github\u002Fcopilot-instructions.md`. Simple, easy to review in a single PR. Best for small\u002Fmedium repos with one stack.\n   - **Nested** — hub `.github\u002Fcopilot-instructions.md` + per-topic `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md` files (each with an `applyTo` glob so VS Code only loads them when relevant). Best for large or multi-stack repos. Add `--claude-md` to also emit `CLAUDE.md`.\n   Recommend `nested` proactively when the repo has > 5 top-level directories, multiple stacks, or already uses a monorepo tool (turbo\u002Fnx\u002Fpnpm workspaces).\n3. **Detect monorepo areas** by reading `agentrc.config.json`. If areas exist, ask the user whether they want **per-area `.instructions.md` files with `applyTo`** in addition to the root file. Default to \"yes\" when `agentrc.config.json` declares areas.\n4. **Run dry-run first** so the user can preview:\n   ```bash\n   npx -y github:microsoft\u002Fagentrc instructions --output \u003Cfile> --strategy \u003Cflat|nested> [--areas|--area \u003Cname>] [--claude-md] --dry-run\n   ```\n5. **Show a short summary** of what would change — files that would be created or overwritten, area count + their `applyTo` globs, model used (default `claude-sonnet-4.6`).\n6. **On confirmation, run the same command without `--dry-run`** (and optionally `--force` if files already exist).\n7. **Post-process layout for Copilot output**:\n   - **If `--output` ends in `copilot-instructions.md` and strategy is `nested`**: move\u002Frewrite AgentRC's `.agents\u002F\u003Ctopic>.md` files to `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`. Add frontmatter to each file with an appropriate `applyTo` glob (see \"Topic applyTo defaults\" below). Delete the now-empty `.agents\u002F` directory.\n   - **If `--areas` was used**: also write `.github\u002Finstructions\u002F\u003Carea>.instructions.md` for every area, using each area's `paths` from `agentrc.config.json` as the `applyTo` glob (override with `--apply-to` for single-area calls).\n   - **If `--output AGENTS.md`** was chosen: keep AgentRC's native `.agents\u002F` layout for nested — agent-agnostic readers expect it there.\n   Create the `.github\u002Finstructions\u002F` directory if missing.\n\n### Topic `applyTo` defaults\n\nWhen promoting AgentRC's nested topic files to `.instructions.md`, use these defaults unless the user specifies otherwise:\n\n| Topic | Default `applyTo` |\n|---|---|\n| `testing` | `**\u002F*.{test,spec}.{ts,tsx,js,jsx,mjs,cjs}` |\n| `style` \u002F `code-quality` \u002F `formatting` | `**\u002F*.{ts,tsx,js,jsx,mjs,cjs,py,go,rs,java,kt,cs}` |\n| `build` \u002F `ci` | `**\u002F{package.json,turbo.json,nx.json,.github\u002Fworkflows\u002F**}` |\n| `docs` | `**\u002F*.md` |\n| `security` | `**` |\n| anything else \u002F hub-level | `**` |\n8. **Verify** by reading the generated file(s) back and showing the user a 1-paragraph synopsis: stack detected, conventions captured, length, list of `.instructions.md` files with their globs.\n9. **Suggest next steps**:\n   - Re-run the `assess` skill to confirm the AI Tooling pillar score improved.\n   - If the user already has both `copilot-instructions.md` and `AGENTS.md`, recommend consolidating to a single source of truth (AgentRC flags this at maturity Level 2+).\n\n## Notes\n\n- AgentRC reads your **actual code** — no templates. Output reflects detected languages, frameworks, and conventions.\n- `--claude-md` (nested strategy only) also emits `CLAUDE.md`.\n- VS Code applies `.instructions.md` files automatically when the active file matches `applyTo`. The root `.github\u002Fcopilot-instructions.md` always loads.\n- Never run this skill non-interactively in CI; instructions are part of the repo and should land via PR.\n","# \u002Facreadiness-generate-instructions — write AI agent instructions\n\nUse this skill whenever the user wants to **create**, **regenerate**, or **refresh** their custom instructions for AI coding agents (Copilot, Claude, etc.). This is the *Generate* step in AgentRC's **Measure → Generate → Maintain** loop and the single highest-leverage action for the **AI Tooling** pillar.\n\n## Output options\n\nVS Code recognises several instruction file types — AgentRC generates the most common ones:\n\n| File | Scope | When to use |\n|---|---|---|\n| `.github\u002Fcopilot-instructions.md` | Always-on, whole workspace | **Default** — VS Code Copilot's native instruction file |\n| `AGENTS.md` | Always-on, whole workspace | Multi-agent repos (Copilot + Claude + others) |\n| `.github\u002Finstructions\u002F*.instructions.md` | Scoped by `applyTo` glob | Per-area \u002F per-language rules in monorepos |\n| `CLAUDE.md` | Claude-specific | Add via `--claude-md` (nested only) |\n\n## Strategies\n\n- **`flat`** *(default)* — single `.github\u002Fcopilot-instructions.md` at the chosen path. Simple, easy to review.\n- **`nested`** — hub at `.github\u002Fcopilot-instructions.md` + per-topic detail files at `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`, each with an `applyTo` glob so VS Code only loads the topic when it's relevant. Better for large or multi-stack repos.\n\n> **Why `.github\u002Finstructions\u002F` and not `.agents\u002F`?** AgentRC's default nested layout writes to `.agents\u002F`, which is the right home for *agent-agnostic* repos (Copilot + Claude + Cursor reading `AGENTS.md`). For VS Code Copilot specifically, the native location is `.github\u002Finstructions\u002F` with `applyTo` frontmatter — that's what Copilot auto-discovers. This skill rewrites AgentRC's nested output to the VS Code-native location whenever the main output is `.github\u002Fcopilot-instructions.md`. If you instead chose `--output AGENTS.md`, nested keeps AgentRC's default `.agents\u002F` layout.\n\nFor monorepos, generate **area-scoped** instructions with `--areas`, `--area \u003Cname>`, or `--areas-only`. Areas are defined in `agentrc.config.json`. Per-area output is written as VS Code `.instructions.md` files with an `applyTo` glob (see below).\n\n### Topic vs area `.instructions.md` files\n\nBoth end up in `.github\u002Finstructions\u002F` but they answer different questions:\n\n| Kind | Filename example | `applyTo` example | Where it comes from |\n|---|---|---|---|\n| **Topic** (nested) | `testing.instructions.md` | `**\u002F*.{test,spec}.{ts,tsx,js}` | AgentRC `--strategy nested` topic split |\n| **Area** (monorepo) | `frontend.instructions.md` | `apps\u002Ffrontend\u002F**` | `agentrc.config.json` areas + `--areas` |\n\nYou can have both at once: a nested set of topic files plus per-area files for a monorepo.\n\n## Per-area files with `applyTo`\n\nWhen the user opts into areas, emit one VS Code-native `.instructions.md` file per area at `.github\u002Finstructions\u002F\u003Carea>.instructions.md`. Each file MUST start with frontmatter declaring the glob the rules apply to:\n\n```markdown\n---\napplyTo: \"apps\u002Ffrontend\u002F**\"\n---\n\n# Frontend area instructions\n\n…AgentRC-generated content for this area…\n```\n\nWorkflow:\n\n1. **Read `agentrc.config.json`** to discover declared areas and their `paths` \u002F globs. If `paths` is missing, ask the user for the glob (e.g. `src\u002Fapi\u002F**`).\n2. **Run `agentrc instructions --areas`** (or `--area \u003Cname>`) to produce the per-area body content.\n3. **Wrap each area's content** in `.github\u002Finstructions\u002F\u003Carea>.instructions.md` with the `applyTo` frontmatter taken from the area's `paths`. If the user passed `--apply-to \u003Cglob>` on a single-area call, use that glob verbatim.\n4. **Leave the main file alone** — the root `.github\u002Fcopilot-instructions.md` stays as the always-on instructions; `.instructions.md` files only kick in for matching paths.\n\nNaming: lowercase, kebab-case area name. Examples: `.github\u002Finstructions\u002Ffrontend.instructions.md`, `.github\u002Finstructions\u002Fapi.instructions.md`, `.github\u002Finstructions\u002Finfra.instructions.md`.\n\n## Steps\n\n1. **Pick the target file**. **Default to `.github\u002Fcopilot-instructions.md`.** Switch to `AGENTS.md` only if the user mentions multi-agent \u002F Claude \u002F Cursor support.\n2. **Always ask which strategy to use** — `flat` or `nested` — unless the user already specified one in their message or via `--strategy`. Present the trade-off briefly:\n   - **Flat** *(default)* — one `.github\u002Fcopilot-instructions.md`. Simple, easy to review in a single PR. Best for small\u002Fmedium repos with one stack.\n   - **Nested** — hub `.github\u002Fcopilot-instructions.md` + per-topic `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md` files (each with an `applyTo` glob so VS Code only loads them when relevant). Best for large or multi-stack repos. Add `--claude-md` to also emit `CLAUDE.md`.\n   Recommend `nested` proactively when the repo has > 5 top-level directories, multiple stacks, or already uses a monorepo tool (turbo\u002Fnx\u002Fpnpm workspaces).\n3. **Detect monorepo areas** by reading `agentrc.config.json`. If areas exist, ask the user whether they want **per-area `.instructions.md` files with `applyTo`** in addition to the root file. Default to \"yes\" when `agentrc.config.json` declares areas.\n4. **Run dry-run first** so the user can preview:\n   ```bash\n   npx -y github:microsoft\u002Fagentrc instructions --output \u003Cfile> --strategy \u003Cflat|nested> [--areas|--area \u003Cname>] [--claude-md] --dry-run\n   ```\n5. **Show a short summary** of what would change — files that would be created or overwritten, area count + their `applyTo` globs, model used (default `claude-sonnet-4.6`).\n6. **On confirmation, run the same command without `--dry-run`** (and optionally `--force` if files already exist).\n7. **Post-process layout for Copilot output**:\n   - **If `--output` ends in `copilot-instructions.md` and strategy is `nested`**: move\u002Frewrite AgentRC's `.agents\u002F\u003Ctopic>.md` files to `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`. Add frontmatter to each file with an appropriate `applyTo` glob (see \"Topic applyTo defaults\" below). Delete the now-empty `.agents\u002F` directory.\n   - **If `--areas` was used**: also write `.github\u002Finstructions\u002F\u003Carea>.instructions.md` for every area, using each area's `paths` from `agentrc.config.json` as the `applyTo` glob (override with `--apply-to` for single-area calls).\n   - **If `--output AGENTS.md`** was chosen: keep AgentRC's native `.agents\u002F` layout for nested — agent-agnostic readers expect it there.\n   Create the `.github\u002Finstructions\u002F` directory if missing.\n\n### Topic `applyTo` defaults\n\nWhen promoting AgentRC's nested topic files to `.instructions.md`, use these defaults unless the user specifies otherwise:\n\n| Topic | Default `applyTo` |\n|---|---|\n| `testing` | `**\u002F*.{test,spec}.{ts,tsx,js,jsx,mjs,cjs}` |\n| `style` \u002F `code-quality` \u002F `formatting` | `**\u002F*.{ts,tsx,js,jsx,mjs,cjs,py,go,rs,java,kt,cs}` |\n| `build` \u002F `ci` | `**\u002F{package.json,turbo.json,nx.json,.github\u002Fworkflows\u002F**}` |\n| `docs` | `**\u002F*.md` |\n| `security` | `**` |\n| anything else \u002F hub-level | `**` |\n8. **Verify** by reading the generated file(s) back and showing the user a 1-paragraph synopsis: stack detected, conventions captured, length, list of `.instructions.md` files with their globs.\n9. **Suggest next steps**:\n   - Re-run the `assess` skill to confirm the AI Tooling pillar score improved.\n   - If the user already has both `copilot-instructions.md` and `AGENTS.md`, recommend consolidating to a single source of truth (AgentRC flags this at maturity Level 2+).\n\n## Notes\n\n- AgentRC reads your **actual code** — no templates. Output reflects detected languages, frameworks, and conventions.\n- `--claude-md` (nested strategy only) also emits `CLAUDE.md`.\n- VS Code applies `.instructions.md` files automatically when the active file matches `applyTo`. The root `.github\u002Fcopilot-instructions.md` always loads.\n- Never run this skill non-interactively in CI; instructions are part of the repo and should land via PR.\n",{"name":5,"description":7,"argument-hint":50},"[--output .github\u002Fcopilot-instructions.md|AGENTS.md] [--strategy flat|nested] [--areas | --area \u003Cname>] [--apply-to \u003Cglob>] [--claude-md] [--dry-run]","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Facreadiness-generate-instructions",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add github\u002Fawesome-copilot --skill acreadiness-generate-instructions",{"tool":67,"command":68},"bunx","bunx skills add github\u002Fawesome-copilot --skill acreadiness-generate-instructions",{"tool":70,"command":71},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill acreadiness-generate-instructions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Facreadiness-generate-instructions\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"agents\u002Fopenai.yaml","REFERENCE","参考文档",251,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-knowledge\u002Fagents\u002Fopenai.yaml",[82,111,137,166,200,217],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":92,"publishedAt":45},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[88,91],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,39,109,110,33],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":45},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[117],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[119,120,121,122,123,124,31,125,126,127,128,129,130,131,34,132,133,134,135,136],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","investigate","duplicate","template","release","reconcile",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":149,"publishedAt":45},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[150,41,151,152,153,154,31,97,155,156,157,158,159,160,161,39,162,163,164,165],"custom","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":177,"publishedAt":45},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},[178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,98,193,194,195,196,197,31,198,199],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":213,"publishedAt":45},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[208,209,212],{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[214,122,187,215,216],"resemble detect","https","identity",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":204,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":228,"publishedAt":45},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[224,227],{"categoryNo":225,"categoryName":226,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[229,230,231,232,41,99,9,121,233,42,215,234,235,236,237,238,239,240,241,242,243,244,107,245,246,247,248],"playbook","quality playbook","quality","code review","tdd","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]