[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADCSSSDMHAT5E5CVS4D790":3,"skill-same:01M6ADCSSSDMHAT5E5CVS4D790":69},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6ADCSSSDMHAT5E5CVS4D790","create-agentsmd",null,"Prompt for generating an AGENTS.md file for a repository","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41028,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-agentsmd\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29],"create","create agentsmd","file","repository","prompt","for","2026-11-10 10:12:30",false,"---\nname: create-agentsmd\ndescription: 'Prompt for generating an AGENTS.md file for a repository'\n---\n\n# Create high‑quality AGENTS.md file\n\nYou are a code agent. Your task is to create a complete, accurate AGENTS.md at the root of this repository that follows the public guidance at https:\u002F\u002Fagents.md\u002F.\n\nAGENTS.md is an open format designed to provide coding agents with the context and instructions they need to work effectively on a project.\n\n## What is AGENTS.md?\n\nAGENTS.md is a Markdown file that serves as a \"README for agents\" - a dedicated, predictable place to provide context and instructions to help AI coding agents work on your project. It complements README.md by containing detailed technical context that coding agents need but might clutter a human-focused README.\n\n## Key Principles\n\n- **Agent-focused**: Contains detailed technical instructions for automated tools\n- **Complements README.md**: Doesn't replace human documentation but adds agent-specific context\n- **Standardized location**: Placed at repository root (or subproject roots for monorepos)\n- **Open format**: Uses standard Markdown with flexible structure\n- **Ecosystem compatibility**: Works across 20+ different AI coding tools and agents\n\n## File Structure and Content Guidelines\n\n### 1. Required Setup\n\n- Create the file as `AGENTS.md` in the repository root\n- Use standard Markdown formatting\n- No required fields - flexible structure based on project needs\n\n### 2. Essential Sections to Include\n\n#### Project Overview\n\n- Brief description of what the project does\n- Architecture overview if complex\n- Key technologies and frameworks used\n\n#### Setup Commands\n\n- Installation instructions\n- Environment setup steps\n- Dependency management commands\n- Database setup if applicable\n\n#### Development Workflow\n\n- How to start development server\n- Build commands\n- Watch\u002Fhot-reload setup\n- Package manager specifics (npm, pnpm, yarn, etc.)\n\n#### Testing Instructions\n\n- How to run tests (unit, integration, e2e)\n- Test file locations and naming conventions\n- Coverage requirements\n- Specific test patterns or frameworks used\n- How to run subset of tests or focus on specific areas\n\n#### Code Style Guidelines\n\n- Language-specific conventions\n- Linting and formatting rules\n- File organization patterns\n- Naming conventions\n- Import\u002Fexport patterns\n\n#### Build and Deployment\n\n- Build commands and outputs\n- Environment configurations\n- Deployment steps and requirements\n- CI\u002FCD pipeline information\n\n### 3. Optional but Recommended Sections\n\n#### Security Considerations\n\n- Security testing requirements\n- Secrets management\n- Authentication patterns\n- Permission models\n\n#### Monorepo Instructions (if applicable)\n\n- How to work with multiple packages\n- Cross-package dependencies\n- Selective building\u002Ftesting\n- Package-specific commands\n\n#### Pull Request Guidelines\n\n- Title format requirements\n- Required checks before submission\n- Review process\n- Commit message conventions\n\n#### Debugging and Troubleshooting\n\n- Common issues and solutions\n- Logging patterns\n- Debug configuration\n- Performance considerations\n\n## Example Template\n\nUse this as a starting template and customize based on the specific project:\n\n```markdown\n# AGENTS.md\n\n## Project Overview\n\n[Brief description of the project, its purpose, and key technologies]\n\n## Setup Commands\n\n- Install dependencies: `[package manager] install`\n- Start development server: `[command]`\n- Build for production: `[command]`\n\n## Development Workflow\n\n- [Development server startup instructions]\n- [Hot reload\u002Fwatch mode information]\n- [Environment variable setup]\n\n## Testing Instructions\n\n- Run all tests: `[command]`\n- Run unit tests: `[command]`\n- Run integration tests: `[command]`\n- Test coverage: `[command]`\n- [Specific testing patterns or requirements]\n\n## Code Style\n\n- [Language and framework conventions]\n- [Linting rules and commands]\n- [Formatting requirements]\n- [File organization patterns]\n\n## Build and Deployment\n\n- [Build process details]\n- [Output directories]\n- [Environment-specific builds]\n- [Deployment commands]\n\n## Pull Request Guidelines\n\n- Title format: [component] Brief description\n- Required checks: `[lint command]`, `[test command]`\n- [Review requirements]\n\n## Additional Notes\n\n- [Any project-specific context]\n- [Common gotchas or troubleshooting tips]\n- [Performance considerations]\n```\n\n## Working Example from agents.md\n\nHere's a real example from the agents.md website:\n\n```markdown\n# Sample AGENTS.md file\n\n## Dev environment tips\n\n- Use `pnpm dlx turbo run where \u003Cproject_name>` to jump to a package instead of scanning with `ls`.\n- Run `pnpm install --filter \u003Cproject_name>` to add the package to your workspace so Vite, ESLint, and TypeScript can see it.\n- Use `pnpm create vite@latest \u003Cproject_name> -- --template react-ts` to spin up a new React + Vite package with TypeScript checks ready.\n- Check the name field inside each package's package.json to confirm the right name—skip the top-level one.\n\n## Testing instructions\n\n- Find the CI plan in the .github\u002Fworkflows folder.\n- Run `pnpm turbo run test --filter \u003Cproject_name>` to run every check defined for that package.\n- From the package root you can just call `pnpm test`. The commit should pass all tests before you merge.\n- To focus on one step, add the Vitest pattern: `pnpm vitest run -t \"\u003Ctest name>\"`.\n- Fix any test or type errors until the whole suite is green.\n- After moving files or changing imports, run `pnpm lint --filter \u003Cproject_name>` to be sure ESLint and TypeScript rules still pass.\n- Add or update tests for the code you change, even if nobody asked.\n\n## PR instructions\n\n- Title format: [\u003Cproject_name>] \u003CTitle>\n- Always run `pnpm lint` and `pnpm test` before committing.\n```\n\n## Implementation Steps\n\n1. **Analyze the project structure** to understand:\n\n   - Programming languages and frameworks used\n   - Package managers and build tools\n   - Testing frameworks\n   - Project architecture (monorepo, single package, etc.)\n\n2. **Identify key workflows** by examining:\n\n   - package.json scripts\n   - Makefile or other build files\n   - CI\u002FCD configuration files\n   - Documentation files\n\n3. **Create comprehensive sections** covering:\n\n   - All essential setup and development commands\n   - Testing strategies and commands\n   - Code style and conventions\n   - Build and deployment processes\n\n4. **Include specific, actionable commands** that agents can execute directly\n\n5. **Test the instructions** by ensuring all commands work as documented\n\n6. **Keep it focused** on what agents need to know, not general project information\n\n## Best Practices\n\n- **Be specific**: Include exact commands, not vague descriptions\n- **Use code blocks**: Wrap commands in backticks for clarity\n- **Include context**: Explain why certain steps are needed\n- **Stay current**: Update as the project evolves\n- **Test commands**: Ensure all listed commands actually work\n- **Consider nested files**: For monorepos, create AGENTS.md files in subprojects as needed\n\n## Monorepo Considerations\n\nFor large monorepos:\n\n- Place a main AGENTS.md at the repository root\n- Create additional AGENTS.md files in subproject directories\n- The closest AGENTS.md file takes precedence for any given location\n- Include navigation tips between packages\u002Fprojects\n\n## Final Notes\n\n- AGENTS.md works with 20+ AI coding tools including Cursor, Aider, Gemini CLI, and many others\n- The format is intentionally flexible - adapt it to your project's needs\n- Focus on actionable instructions that help agents understand and work with your codebase\n- This is living documentation - update it as your project evolves\n\nWhen creating the AGENTS.md file, prioritize clarity, completeness, and actionability. The goal is to give any coding agent enough context to effectively contribute to the project without requiring additional human guidance.\n","# Create high‑quality AGENTS.md file\n\nYou are a code agent. Your task is to create a complete, accurate AGENTS.md at the root of this repository that follows the public guidance at https:\u002F\u002Fagents.md\u002F.\n\nAGENTS.md is an open format designed to provide coding agents with the context and instructions they need to work effectively on a project.\n\n## What is AGENTS.md?\n\nAGENTS.md is a Markdown file that serves as a \"README for agents\" - a dedicated, predictable place to provide context and instructions to help AI coding agents work on your project. It complements README.md by containing detailed technical context that coding agents need but might clutter a human-focused README.\n\n## Key Principles\n\n- **Agent-focused**: Contains detailed technical instructions for automated tools\n- **Complements README.md**: Doesn't replace human documentation but adds agent-specific context\n- **Standardized location**: Placed at repository root (or subproject roots for monorepos)\n- **Open format**: Uses standard Markdown with flexible structure\n- **Ecosystem compatibility**: Works across 20+ different AI coding tools and agents\n\n## File Structure and Content Guidelines\n\n### 1. Required Setup\n\n- Create the file as `AGENTS.md` in the repository root\n- Use standard Markdown formatting\n- No required fields - flexible structure based on project needs\n\n### 2. Essential Sections to Include\n\n#### Project Overview\n\n- Brief description of what the project does\n- Architecture overview if complex\n- Key technologies and frameworks used\n\n#### Setup Commands\n\n- Installation instructions\n- Environment setup steps\n- Dependency management commands\n- Database setup if applicable\n\n#### Development Workflow\n\n- How to start development server\n- Build commands\n- Watch\u002Fhot-reload setup\n- Package manager specifics (npm, pnpm, yarn, etc.)\n\n#### Testing Instructions\n\n- How to run tests (unit, integration, e2e)\n- Test file locations and naming conventions\n- Coverage requirements\n- Specific test patterns or frameworks used\n- How to run subset of tests or focus on specific areas\n\n#### Code Style Guidelines\n\n- Language-specific conventions\n- Linting and formatting rules\n- File organization patterns\n- Naming conventions\n- Import\u002Fexport patterns\n\n#### Build and Deployment\n\n- Build commands and outputs\n- Environment configurations\n- Deployment steps and requirements\n- CI\u002FCD pipeline information\n\n### 3. Optional but Recommended Sections\n\n#### Security Considerations\n\n- Security testing requirements\n- Secrets management\n- Authentication patterns\n- Permission models\n\n#### Monorepo Instructions (if applicable)\n\n- How to work with multiple packages\n- Cross-package dependencies\n- Selective building\u002Ftesting\n- Package-specific commands\n\n#### Pull Request Guidelines\n\n- Title format requirements\n- Required checks before submission\n- Review process\n- Commit message conventions\n\n#### Debugging and Troubleshooting\n\n- Common issues and solutions\n- Logging patterns\n- Debug configuration\n- Performance considerations\n\n## Example Template\n\nUse this as a starting template and customize based on the specific project:\n\n```markdown\n# AGENTS.md\n\n## Project Overview\n\n[Brief description of the project, its purpose, and key technologies]\n\n## Setup Commands\n\n- Install dependencies: `[package manager] install`\n- Start development server: `[command]`\n- Build for production: `[command]`\n\n## Development Workflow\n\n- [Development server startup instructions]\n- [Hot reload\u002Fwatch mode information]\n- [Environment variable setup]\n\n## Testing Instructions\n\n- Run all tests: `[command]`\n- Run unit tests: `[command]`\n- Run integration tests: `[command]`\n- Test coverage: `[command]`\n- [Specific testing patterns or requirements]\n\n## Code Style\n\n- [Language and framework conventions]\n- [Linting rules and commands]\n- [Formatting requirements]\n- [File organization patterns]\n\n## Build and Deployment\n\n- [Build process details]\n- [Output directories]\n- [Environment-specific builds]\n- [Deployment commands]\n\n## Pull Request Guidelines\n\n- Title format: [component] Brief description\n- Required checks: `[lint command]`, `[test command]`\n- [Review requirements]\n\n## Additional Notes\n\n- [Any project-specific context]\n- [Common gotchas or troubleshooting tips]\n- [Performance considerations]\n```\n\n## Working Example from agents.md\n\nHere's a real example from the agents.md website:\n\n```markdown\n# Sample AGENTS.md file\n\n## Dev environment tips\n\n- Use `pnpm dlx turbo run where \u003Cproject_name>` to jump to a package instead of scanning with `ls`.\n- Run `pnpm install --filter \u003Cproject_name>` to add the package to your workspace so Vite, ESLint, and TypeScript can see it.\n- Use `pnpm create vite@latest \u003Cproject_name> -- --template react-ts` to spin up a new React + Vite package with TypeScript checks ready.\n- Check the name field inside each package's package.json to confirm the right name—skip the top-level one.\n\n## Testing instructions\n\n- Find the CI plan in the .github\u002Fworkflows folder.\n- Run `pnpm turbo run test --filter \u003Cproject_name>` to run every check defined for that package.\n- From the package root you can just call `pnpm test`. The commit should pass all tests before you merge.\n- To focus on one step, add the Vitest pattern: `pnpm vitest run -t \"\u003Ctest name>\"`.\n- Fix any test or type errors until the whole suite is green.\n- After moving files or changing imports, run `pnpm lint --filter \u003Cproject_name>` to be sure ESLint and TypeScript rules still pass.\n- Add or update tests for the code you change, even if nobody asked.\n\n## PR instructions\n\n- Title format: [\u003Cproject_name>] \u003CTitle>\n- Always run `pnpm lint` and `pnpm test` before committing.\n```\n\n## Implementation Steps\n\n1. **Analyze the project structure** to understand:\n\n   - Programming languages and frameworks used\n   - Package managers and build tools\n   - Testing frameworks\n   - Project architecture (monorepo, single package, etc.)\n\n2. **Identify key workflows** by examining:\n\n   - package.json scripts\n   - Makefile or other build files\n   - CI\u002FCD configuration files\n   - Documentation files\n\n3. **Create comprehensive sections** covering:\n\n   - All essential setup and development commands\n   - Testing strategies and commands\n   - Code style and conventions\n   - Build and deployment processes\n\n4. **Include specific, actionable commands** that agents can execute directly\n\n5. **Test the instructions** by ensuring all commands work as documented\n\n6. **Keep it focused** on what agents need to know, not general project information\n\n## Best Practices\n\n- **Be specific**: Include exact commands, not vague descriptions\n- **Use code blocks**: Wrap commands in backticks for clarity\n- **Include context**: Explain why certain steps are needed\n- **Stay current**: Update as the project evolves\n- **Test commands**: Ensure all listed commands actually work\n- **Consider nested files**: For monorepos, create AGENTS.md files in subprojects as needed\n\n## Monorepo Considerations\n\nFor large monorepos:\n\n- Place a main AGENTS.md at the repository root\n- Create additional AGENTS.md files in subproject directories\n- The closest AGENTS.md file takes precedence for any given location\n- Include navigation tips between packages\u002Fprojects\n\n## Final Notes\n\n- AGENTS.md works with 20+ AI coding tools including Cursor, Aider, Gemini CLI, and many others\n- The format is intentionally flexible - adapt it to your project's needs\n- Focus on actionable instructions that help agents understand and work with your codebase\n- This is living documentation - update it as your project evolves\n\nWhen creating the AGENTS.md file, prioritize clarity, completeness, and actionability. The goal is to give any coding agent enough context to effectively contribute to the project without requiring additional human guidance.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fcreate-agentsmd",5335,"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-11 11:59:04",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add github\u002Fawesome-copilot --skill create-agentsmd",{"tool":51,"command":52},"bunx","bunx skills add github\u002Fawesome-copilot --skill create-agentsmd",{"tool":54,"command":55},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill create-agentsmd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-agentsmd\u002FSKILL.md",true,[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",166,"https:\u002F\u002Fgithub.com\u002Ftdortman\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fimprove-codebase-architecture\u002Fagents\u002Fopenai.yaml",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"HTML-REPORT.md",6641,"https:\u002F\u002Fgithub.com\u002Ftdortman\u002Fdotfiles\u002Fblob\u002Fmain\u002Fhome\u002Fdot_agents\u002Fskills\u002Fimprove-codebase-architecture\u002FHTML-REPORT.md",[70,101,128,158,191,208],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":80,"publishedAt":30},"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",[76,79],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":30},"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",[107],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,113,114,29,115,116,117,118,119,120,121,122,123,124,125,126,127],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":140,"publishedAt":30},"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",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[141,142,143,144,145,146,29,85,147,148,149,150,151,152,153,97,154,155,156,157],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":169,"publishedAt":30},"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",[165,168],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},[170,171,172,173,174,175,176,177,178,26,179,180,181,182,183,86,184,185,186,187,188,29,189,190],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":195,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":204,"publishedAt":30},"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",[199,200,203],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":201,"categoryName":202,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[205,112,26,206,207],"resemble detect","https","identity",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":195,"licenseFileUrl":212,"sourceHtmlUrl":213,"categories":214,"keywords":219,"publishedAt":30},"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",[215,218],{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[220,221,222,223,142,87,9,111,224,225,206,226,227,228,229,230,231,232,233,234,235,236,95,237,238,239,240],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]