[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE9YHHQ63YFFXK98NH5VE6":3,"skill-same:01M6AE9YHHQ63YFFXK98NH5VE6":72},{"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":26,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6AE9YHHQ63YFFXK98NH5VE6","typescript-mcp-server-generator",null,"Generate a complete MCP server project in TypeScript using the MCP TypeScript SDK v2 (@modelcontextprotocol\u002Fserver) with tools, resources, and proper configuration","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41128,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-mcp-server-generator\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"MCP","typescript","mcp server","server","typescript mcp server generator","generator","typescript mcp","sdk","generate","Tools","configuration","project","complete","resources","with","with tools","2026-11-10 10:12:30",false,"---\nname: typescript-mcp-server-generator\ndescription: 'Generate a complete MCP server project in TypeScript using the MCP TypeScript SDK v2 (@modelcontextprotocol\u002Fserver) with tools, resources, and proper configuration'\n---\n\n# Generate TypeScript MCP Server\n\nCreate a complete Model Context Protocol (MCP) server in TypeScript using the **MCP TypeScript SDK v2** with the following specifications:\n\n## Requirements\n\n1. **Project Structure**: Create a new TypeScript\u002FNode.js project with proper directory structure\n2. **NPM Packages**: The v1 monolithic `@modelcontextprotocol\u002Fsdk` package is retired. Use the focused v2 packages:\n   - `@modelcontextprotocol\u002Fserver` — server implementation (stdio transport via the `@modelcontextprotocol\u002Fserver\u002Fstdio` subpath)\n   - `@modelcontextprotocol\u002Fnode` — Node HTTP transport (`NodeStreamableHTTPServerTransport`), or a framework adapter: `@modelcontextprotocol\u002Fexpress`, `@modelcontextprotocol\u002Fhono`, `@modelcontextprotocol\u002Ffastify` — each adapter requires its peer framework to be installed alongside it (e.g. `@modelcontextprotocol\u002Fexpress` + `express`)\n   - `@modelcontextprotocol\u002Fcore` — shared protocol schemas (import `*Schema` constants from here, not from `sdk\u002Ftypes.js`)\n   - `zod@^4.2` — v2 requires Zod 4.2+; do not use zod@3\n3. **Runtime**: Node.js 20+ (v2 minimum); ESM-first with `\"type\": \"module\"` (a CommonJS build is also shipped, so `require()` works if needed)\n4. **Server Type**: Choose between HTTP (Streamable HTTP transport) or stdio-based server. SSE and WebSocket transports were removed in v2 — do not generate them.\n5. **Tools**: Create at least one useful tool with proper schema validation\n6. **Error Handling**: Include comprehensive error handling and validation\n\n## Implementation Details\n\n### Project Setup\n- Initialize with `npm init` and create package.json\n- Install dependencies: `@modelcontextprotocol\u002Fserver`, `zod@^4.2`, and the transport package — `@modelcontextprotocol\u002Fnode` for plain Node HTTP, or a framework adapter together with its peer framework (e.g. `npm install @modelcontextprotocol\u002Fexpress express`)\n- Configure TypeScript with ES modules: `\"type\": \"module\"` in package.json\n- Add dev dependencies: `tsx` or `ts-node` for development\n- Create proper .gitignore file\n\n### Server Configuration\n- Use `McpServer` class from `@modelcontextprotocol\u002Fserver` for high-level implementation\n- Set server name and version\n- Choose the appropriate transport:\n  - HTTP (Node): `NodeStreamableHTTPServerTransport` from `@modelcontextprotocol\u002Fnode`\n  - HTTP (Web Standard runtimes): `WebStandardStreamableHTTPServerTransport` from `@modelcontextprotocol\u002Fserver`\n  - stdio: `StdioServerTransport` from `@modelcontextprotocol\u002Fserver\u002Fstdio`\n- For HTTP: prefer a framework adapter (`@modelcontextprotocol\u002Fexpress`, etc.) with proper middleware and error handling\n- Note that v2 uses Web Standard `Headers`\u002F`Request` types; read headers with `ctx.http?.req?.headers.get('x-custom')`\n\n### Tool Implementation\n- Use `registerTool()` with a config object — v1 variadic `.tool()` signatures are gone:\n  ```typescript\n  server.registerTool('greet', {\n    description: 'Greet user',\n    inputSchema: z.object({ name: z.string() })\n  }, async ({ name }, ctx) => {\n    return { content: [{ type: 'text', text: `Hello, ${name}!` }] };\n  });\n  ```\n- Schemas must be full Zod objects (`z.object({...})`) — raw shape objects (`{ name: z.string() }`) are deprecated\n- Provide clear `title` and `description` fields\n- Return both `content` and `structuredContent` in results\n- The handler's second parameter is a structured `ctx` object (replaces v1 `extra`): `ctx.mcpReq.signal`, `ctx.mcpReq.id`, `ctx.mcpReq.send(...)`, `ctx.mcpReq.notify(...)`\n- Implement proper error handling with try-catch blocks; use the v2 error hierarchy (`ProtocolError`, `SdkError`, `SdkHttpError` with `.status`) instead of v1 `McpError`\u002F`StreamableHTTPError`\n- Support async operations where appropriate\n\n### Resource\u002FPrompt Setup (Optional)\n- Add resources using `registerResource()` with ResourceTemplate for dynamic URIs\n- Add prompts using `registerPrompt()` with argument schemas (same config-object style as `registerTool()`)\n- Consider adding completion support for better UX; note the v2 `completable()` wrapper order: `completable(z.string(), callback).optional()` (optional applied outside)\n\n### Code Quality\n- Use TypeScript for type safety\n- Follow async\u002Fawait patterns consistently\n- Implement proper cleanup on transport close events\n- Use environment variables for configuration\n- Add inline comments for complex logic\n- Structure code with clear separation of concerns\n\n## Example Tool Types to Consider\n- Data processing and transformation\n- External API integrations\n- File system operations (read, search, analyze)\n- Database queries\n- Text analysis or summarization (LLM-assisted via the multi-round `input_required` pattern)\n- System information retrieval\n\n## Configuration Options\n- **For HTTP Servers**: \n  - Port configuration via environment variables\n  - CORS setup for browser clients\n  - Session management (stateless vs stateful)\n  - DNS rebinding protection for local servers\n  - Strict `Content-Type` handling: v2 rejects non-`application\u002Fjson` POST bodies\n  \n- **For stdio Servers**:\n  - Proper stdin\u002Fstdout handling\n  - Environment-based configuration\n  - Process lifecycle management\n\n## Migrating an Existing v1 Server\n- Run the official codemod first: `npx @modelcontextprotocol\u002Fcodemod@latest v1-to-v2 .`\n- Then search for `@mcp-codemod-error` markers for the parts requiring manual judgment (transport choice, header reads, error classification)\n- Swap `McpError + ErrorCode` checks for the new error classes; HTTP status now lives on `error.status`, not `error.code`\n- `Server.createMessage()`, `listRoots()`, `sendLoggingMessage()` and the `roots`\u002F`sampling`\u002F`logging` capability fields are deprecated in v2 — avoid them in new code\n\n## Testing Guidance\n- Explain how to run the server (`npm start` or `npx tsx server.ts`)\n- Provide MCP Inspector command: `npx @modelcontextprotocol\u002Finspector`\n- For HTTP servers, include connection URL: `http:\u002F\u002Flocalhost:PORT\u002Fmcp`\n- Include example tool invocations\n- Add troubleshooting tips for common issues\n\n## Additional Features to Consider\n- LLM-powered tools using the multi-round `input_required` pattern (the v2 replacement for the deprecated sampling subsystem)\n- User input elicitation for interactive workflows\n- Dynamic tool registration with enable\u002Fdisable capabilities\n- Notification debouncing for bulk updates\n- Resource links for efficient data references\n\nGenerate a complete, production-ready MCP server with comprehensive documentation, type safety, and error handling.\n","# Generate TypeScript MCP Server\n\nCreate a complete Model Context Protocol (MCP) server in TypeScript using the **MCP TypeScript SDK v2** with the following specifications:\n\n## Requirements\n\n1. **Project Structure**: Create a new TypeScript\u002FNode.js project with proper directory structure\n2. **NPM Packages**: The v1 monolithic `@modelcontextprotocol\u002Fsdk` package is retired. Use the focused v2 packages:\n   - `@modelcontextprotocol\u002Fserver` — server implementation (stdio transport via the `@modelcontextprotocol\u002Fserver\u002Fstdio` subpath)\n   - `@modelcontextprotocol\u002Fnode` — Node HTTP transport (`NodeStreamableHTTPServerTransport`), or a framework adapter: `@modelcontextprotocol\u002Fexpress`, `@modelcontextprotocol\u002Fhono`, `@modelcontextprotocol\u002Ffastify` — each adapter requires its peer framework to be installed alongside it (e.g. `@modelcontextprotocol\u002Fexpress` + `express`)\n   - `@modelcontextprotocol\u002Fcore` — shared protocol schemas (import `*Schema` constants from here, not from `sdk\u002Ftypes.js`)\n   - `zod@^4.2` — v2 requires Zod 4.2+; do not use zod@3\n3. **Runtime**: Node.js 20+ (v2 minimum); ESM-first with `\"type\": \"module\"` (a CommonJS build is also shipped, so `require()` works if needed)\n4. **Server Type**: Choose between HTTP (Streamable HTTP transport) or stdio-based server. SSE and WebSocket transports were removed in v2 — do not generate them.\n5. **Tools**: Create at least one useful tool with proper schema validation\n6. **Error Handling**: Include comprehensive error handling and validation\n\n## Implementation Details\n\n### Project Setup\n- Initialize with `npm init` and create package.json\n- Install dependencies: `@modelcontextprotocol\u002Fserver`, `zod@^4.2`, and the transport package — `@modelcontextprotocol\u002Fnode` for plain Node HTTP, or a framework adapter together with its peer framework (e.g. `npm install @modelcontextprotocol\u002Fexpress express`)\n- Configure TypeScript with ES modules: `\"type\": \"module\"` in package.json\n- Add dev dependencies: `tsx` or `ts-node` for development\n- Create proper .gitignore file\n\n### Server Configuration\n- Use `McpServer` class from `@modelcontextprotocol\u002Fserver` for high-level implementation\n- Set server name and version\n- Choose the appropriate transport:\n  - HTTP (Node): `NodeStreamableHTTPServerTransport` from `@modelcontextprotocol\u002Fnode`\n  - HTTP (Web Standard runtimes): `WebStandardStreamableHTTPServerTransport` from `@modelcontextprotocol\u002Fserver`\n  - stdio: `StdioServerTransport` from `@modelcontextprotocol\u002Fserver\u002Fstdio`\n- For HTTP: prefer a framework adapter (`@modelcontextprotocol\u002Fexpress`, etc.) with proper middleware and error handling\n- Note that v2 uses Web Standard `Headers`\u002F`Request` types; read headers with `ctx.http?.req?.headers.get('x-custom')`\n\n### Tool Implementation\n- Use `registerTool()` with a config object — v1 variadic `.tool()` signatures are gone:\n  ```typescript\n  server.registerTool('greet', {\n    description: 'Greet user',\n    inputSchema: z.object({ name: z.string() })\n  }, async ({ name }, ctx) => {\n    return { content: [{ type: 'text', text: `Hello, ${name}!` }] };\n  });\n  ```\n- Schemas must be full Zod objects (`z.object({...})`) — raw shape objects (`{ name: z.string() }`) are deprecated\n- Provide clear `title` and `description` fields\n- Return both `content` and `structuredContent` in results\n- The handler's second parameter is a structured `ctx` object (replaces v1 `extra`): `ctx.mcpReq.signal`, `ctx.mcpReq.id`, `ctx.mcpReq.send(...)`, `ctx.mcpReq.notify(...)`\n- Implement proper error handling with try-catch blocks; use the v2 error hierarchy (`ProtocolError`, `SdkError`, `SdkHttpError` with `.status`) instead of v1 `McpError`\u002F`StreamableHTTPError`\n- Support async operations where appropriate\n\n### Resource\u002FPrompt Setup (Optional)\n- Add resources using `registerResource()` with ResourceTemplate for dynamic URIs\n- Add prompts using `registerPrompt()` with argument schemas (same config-object style as `registerTool()`)\n- Consider adding completion support for better UX; note the v2 `completable()` wrapper order: `completable(z.string(), callback).optional()` (optional applied outside)\n\n### Code Quality\n- Use TypeScript for type safety\n- Follow async\u002Fawait patterns consistently\n- Implement proper cleanup on transport close events\n- Use environment variables for configuration\n- Add inline comments for complex logic\n- Structure code with clear separation of concerns\n\n## Example Tool Types to Consider\n- Data processing and transformation\n- External API integrations\n- File system operations (read, search, analyze)\n- Database queries\n- Text analysis or summarization (LLM-assisted via the multi-round `input_required` pattern)\n- System information retrieval\n\n## Configuration Options\n- **For HTTP Servers**: \n  - Port configuration via environment variables\n  - CORS setup for browser clients\n  - Session management (stateless vs stateful)\n  - DNS rebinding protection for local servers\n  - Strict `Content-Type` handling: v2 rejects non-`application\u002Fjson` POST bodies\n  \n- **For stdio Servers**:\n  - Proper stdin\u002Fstdout handling\n  - Environment-based configuration\n  - Process lifecycle management\n\n## Migrating an Existing v1 Server\n- Run the official codemod first: `npx @modelcontextprotocol\u002Fcodemod@latest v1-to-v2 .`\n- Then search for `@mcp-codemod-error` markers for the parts requiring manual judgment (transport choice, header reads, error classification)\n- Swap `McpError + ErrorCode` checks for the new error classes; HTTP status now lives on `error.status`, not `error.code`\n- `Server.createMessage()`, `listRoots()`, `sendLoggingMessage()` and the `roots`\u002F`sampling`\u002F`logging` capability fields are deprecated in v2 — avoid them in new code\n\n## Testing Guidance\n- Explain how to run the server (`npm start` or `npx tsx server.ts`)\n- Provide MCP Inspector command: `npx @modelcontextprotocol\u002Finspector`\n- For HTTP servers, include connection URL: `http:\u002F\u002Flocalhost:PORT\u002Fmcp`\n- Include example tool invocations\n- Add troubleshooting tips for common issues\n\n## Additional Features to Consider\n- LLM-powered tools using the multi-round `input_required` pattern (the v2 replacement for the deprecated sampling subsystem)\n- User input elicitation for interactive workflows\n- Dynamic tool registration with enable\u002Fdisable capabilities\n- Notification debouncing for bulk updates\n- Resource links for efficient data references\n\nGenerate a complete, production-ready MCP server with comprehensive documentation, type safety, and error handling.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Ftypescript-mcp-server-generator",5353,"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 11:40:39",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add github\u002Fawesome-copilot --skill typescript-mcp-server-generator",{"tool":64,"command":65},"bunx","bunx skills add github\u002Fawesome-copilot --skill typescript-mcp-server-generator",{"tool":67,"command":68},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill typescript-mcp-server-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-mcp-server-generator\u002FSKILL.md",true,[],[73,102,130,160,192,209],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":83,"publishedAt":43},"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",[79,82],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[84,85,86,87,38,88,89,90,91,92,93,94,95,96,97,98,99,100,101,41],"supabase","rls","supabase rls","supabase rls policies","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":43},"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",[108],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":142,"publishedAt":43},"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",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[143,144,145,146,147,148,116,38,149,150,151,152,153,154,155,99,156,157,158,159],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":169,"publishedAt":43},"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",[167,168],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},[170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,88,185,186,187,188,189,116,190,191],"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":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":196,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":205,"publishedAt":43},"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",[200,201,204],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[206,113,179,207,208],"resemble detect","https","identity",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":196,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":220,"publishedAt":43},"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",[216,219],{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[221,222,223,224,144,89,9,112,225,226,207,227,228,229,230,231,232,233,234,235,236,237,97,238,239,240,241],"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"]