[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NC1MPH3QM11MNTPVTNA8E":3,"skill-same:01M71NC1MPH3QM11MNTPVTNA8E":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":56,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M71NC1MPH3QM11MNTPVTNA8E","mcp-builder",null,"Org role guidance for an MCP builder: design and build Model Context Protocol servers whose tools, resources and prompts agents can reliably pick and use. Short practices on naming, schemas, errors and agent smoke tests; for a full build guide see mcp-server-builder.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmcp-builder\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"MCP","mcp builder","builder","guide","full","Tools","org","monomind","mcp-server","server","model context protocol","query","impact","design","errors","pick","short","model","resources","build guide","2026-11-10 10:56:23",false,"---\nname: mcp-builder\ndescription: \"Org role guidance for an MCP builder: design and build Model Context Protocol servers whose tools, resources and prompts agents can reliably pick and use. Short practices on naming, schemas, errors and agent smoke tests; for a full build guide see mcp-server-builder.\"\ntags: [\"engineering\",\"mcp\",\"agents\"]\ntools: [\"monograph_query\",\"monograph_context\",\"monograph_impact\"]\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# MCP Builder — Best Practices\n\n## Focus\nDesigns and builds Model Context Protocol servers — custom tools, resources, and prompts that extend what an AI agent can actually do.\n\n## Best practices\n- Give tools descriptive, unambiguous names (`search_users`, not `query1`) — agents select tools by name and description alone.\n- Type every parameter with a schema (e.g., Zod\u002FJSON Schema) and provide sane defaults for optional fields.\n- Write tool descriptions for the *agent*, not a human developer — state exactly when to use it and what it returns.\n- Return structured, parseable output (JSON for data, concise markdown for human-readable summaries) — never raw dumps.\n- Design tools to be stateless and independent; don't assume a particular call order between tools.\n- Fail gracefully: return actionable error content in the tool response rather than crashing the server or throwing unhandled exceptions.\n- Validate and sanitize all inputs — MCP tools are still a trust boundary, especially for file paths and shell commands.\n- Test tools with an actual agent driving them, not just unit tests — a tool that \"looks right\" can still confuse a model.\n\n## Common pitfalls\n- Vague tool descriptions that cause the agent to pick the wrong tool or misuse parameters.\n- Overloading a single tool with too many responsibilities instead of a few focused ones.\n- Returning huge unstructured payloads that blow up the agent's context.\n- Assuming the agent will call tools in a specific sequence and breaking silently when it doesn't.\n- Skipping rate limiting\u002Fauth on tools that wrap sensitive or costly external APIs.\n\n## Tools & techniques\n- MCP TypeScript\u002FPython SDKs with schema validation (Zod, Pydantic) baked into every tool definition.\n- Stdio transport for local\u002Fdev servers; HTTP+SSE for remote\u002Fshared servers.\n- Manual \"agent smoke test\": have an agent attempt the target task end-to-end using only the new tools.\n- Version the server (`name`, `version` in server metadata) so breaking tool changes are traceable.\n","# MCP Builder — Best Practices\n\n## Focus\nDesigns and builds Model Context Protocol servers — custom tools, resources, and prompts that extend what an AI agent can actually do.\n\n## Best practices\n- Give tools descriptive, unambiguous names (`search_users`, not `query1`) — agents select tools by name and description alone.\n- Type every parameter with a schema (e.g., Zod\u002FJSON Schema) and provide sane defaults for optional fields.\n- Write tool descriptions for the *agent*, not a human developer — state exactly when to use it and what it returns.\n- Return structured, parseable output (JSON for data, concise markdown for human-readable summaries) — never raw dumps.\n- Design tools to be stateless and independent; don't assume a particular call order between tools.\n- Fail gracefully: return actionable error content in the tool response rather than crashing the server or throwing unhandled exceptions.\n- Validate and sanitize all inputs — MCP tools are still a trust boundary, especially for file paths and shell commands.\n- Test tools with an actual agent driving them, not just unit tests — a tool that \"looks right\" can still confuse a model.\n\n## Common pitfalls\n- Vague tool descriptions that cause the agent to pick the wrong tool or misuse parameters.\n- Overloading a single tool with too many responsibilities instead of a few focused ones.\n- Returning huge unstructured payloads that blow up the agent's context.\n- Assuming the agent will call tools in a specific sequence and breaking silently when it doesn't.\n- Skipping rate limiting\u002Fauth on tools that wrap sensitive or costly external APIs.\n\n## Tools & techniques\n- MCP TypeScript\u002FPython SDKs with schema validation (Zod, Pydantic) baked into every tool definition.\n- Stdio transport for local\u002Fdev servers; HTTP+SSE for remote\u002Fshared servers.\n- Manual \"agent smoke test\": have an agent attempt the target task end-to-end using only the new tools.\n- Version the server (`name`, `version` in server metadata) so breaking tool changes are traceable.\n",{"name":5,"tags":48,"tools":52,"source":56,"license":14,"description":7},[49,50,51],"engineering","mcp","agents",[53,54,55],"monograph_query","monograph_context","monograph_impact","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmcp-builder",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add monoes\u002Fmonomind --skill mcp-builder",{"tool":71,"command":72},"bunx","bunx skills add monoes\u002Fmonomind --skill mcp-builder",{"tool":74,"command":75},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill mcp-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmcp-builder\u002FSKILL.md",true,[],[80,103,138,165,190,215],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":102},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[87,88,89,90,91,92,36,93,35,34,94,95,30,96,97,98,99,100,29,101],"zk","zk steward","steward","zero-knowledge","engineer","choice","knowledge","snark","review","security review","stark","zettelkasten","cryptography","security","blockchain","2026-11-10 13:02:02",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":119,"publishedAt":102},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[120,121,122,91,123,124,125,126,34,127,128,129,130,131,132,133,134,135,136,137],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":148,"publishedAt":102},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000031","产品经理",[131,149,150,151,152,93,153,125,154,155,156,130,157,158,159,160,161,162,163,164],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":102},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000033","数据分析师",[34,131,176,177,178,179,93,163,125,180,181,182,183,156,184,185,186,187,188,189],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"publishedAt":102},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[201,202,203,204,178,205,206,207,208,35,209,210,211,34,30,184,212,213,214,186],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":102},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[221],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[203,223,224,225,226,227,228,178,229,230,127,231,232,233,30,184,234,235,186,236],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]