[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PFAN4DAENMY574Q7Q3CB3H":3,"skill-same:01M6PFAN4DAENMY574Q7Q3CB3H":65},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6PFAN4DAENMY574Q7Q3CB3H","wrappee-drift",null,"Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.","sandraschi\u002Fdocumentation-mcp","sandraschi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34750307?v=4","01M6C42H9WE5EC9CK3N5RGZP8S","Sandra Schipal","01M6PE1X2FZP8KR5GANPPFTHA8",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"wrappee drift","drift","never","repo audit","features","fleet","now","software","tool list","only","memory","coverage","list","read","competitors","api","data","audit","capabilities","training","2026-11-10 10:12:30",false,"---\nname: wrappee-drift\ndescription: Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.\n---\n\n# wrappee drift\n\nSingle-repo, read-only capability-gap audit. Answers \"has the software we wrap moved,\nor has a competing wrapper covered ground we haven't, since this repo's tool list was\nlast touched\" -- a question `drift-scan` never asks, because passing every internal\nfleet-standard check says nothing about whether the wrapped software itself moved.\n\n## Canonical procedure\n\nThe authoritative SOP is:\n\n    D:\\Dev\\repos\\mcp-central-docs\\patterns\\WRAPPEE_CAPABILITY_DRIFT_SOP.md\n\nRead that file first and follow its four phases. Do not reconstruct the checks from\nmemory and do not invent additional ones. If the SOP and this skill ever disagree, the\nSOP wins.\n\nRelated macro definition: `mcp-central-docs\\standards\\rules\\agentic_macros.md` ->\n`wrappee drift` (alias `capability audit`).\n\n## Hard rules\n\n- **Always scoped to one named repo.** Never run this across the fleet on your own\n  initiative -- unlike `drift-scan`'s cheap file-existence probes, this requires real\n  external research per repo (current docs of the wrapped software, current listings\n  of comparable wrappers), which is expensive and only worth doing when asked.\n- **Never build what you find in the same pass.** This produces a gap report. Building\n  a found capability is a separate, explicitly-scoped follow-up task the user decides\n  on after reading the report.\n- **Check the wrapped software's current real docs\u002FAPI, not training-data memory of it.**\n  The entire point is catching drift since this repo was last touched. An answer drawn\n  from memory of \"what Blender can do\" is exactly as stale as the repo's tool list --\n  possibly staler. Fetch or introspect the current version.\n\n## Reporting\n\nStructure per `WRAPPEE_CAPABILITY_DRIFT_SOP.md` Phase 4: gaps because the wrapped\nsoftware moved, gaps because a comparable wrapper covers something this repo doesn't,\nwhat this repo already has that comparables don't (for completeness, not action), and\nanything found but explicitly not recommended to build, with why.\n\nPersist to `reports\u002Fwrappee-drift-{repo}-{date}.md` (gitignored, same convention as\n`drift-scan`'s reports).\n","# wrappee drift\n\nSingle-repo, read-only capability-gap audit. Answers \"has the software we wrap moved,\nor has a competing wrapper covered ground we haven't, since this repo's tool list was\nlast touched\" -- a question `drift-scan` never asks, because passing every internal\nfleet-standard check says nothing about whether the wrapped software itself moved.\n\n## Canonical procedure\n\nThe authoritative SOP is:\n\n    D:\\Dev\\repos\\mcp-central-docs\\patterns\\WRAPPEE_CAPABILITY_DRIFT_SOP.md\n\nRead that file first and follow its four phases. Do not reconstruct the checks from\nmemory and do not invent additional ones. If the SOP and this skill ever disagree, the\nSOP wins.\n\nRelated macro definition: `mcp-central-docs\\standards\\rules\\agentic_macros.md` ->\n`wrappee drift` (alias `capability audit`).\n\n## Hard rules\n\n- **Always scoped to one named repo.** Never run this across the fleet on your own\n  initiative -- unlike `drift-scan`'s cheap file-existence probes, this requires real\n  external research per repo (current docs of the wrapped software, current listings\n  of comparable wrappers), which is expensive and only worth doing when asked.\n- **Never build what you find in the same pass.** This produces a gap report. Building\n  a found capability is a separate, explicitly-scoped follow-up task the user decides\n  on after reading the report.\n- **Check the wrapped software's current real docs\u002FAPI, not training-data memory of it.**\n  The entire point is catching drift since this repo was last touched. An answer drawn\n  from memory of \"what Blender can do\" is exactly as stale as the repo's tool list --\n  possibly staler. Fetch or introspect the current version.\n\n## Reporting\n\nStructure per `WRAPPEE_CAPABILITY_DRIFT_SOP.md` Phase 4: gaps because the wrapped\nsoftware moved, gaps because a comparable wrapper covers something this repo doesn't,\nwhat this repo already has that comparables don't (for completeness, not action), and\nanything found but explicitly not recommended to build, with why.\n\nPersist to `reports\u002Fwrappee-drift-{repo}-{date}.md` (gitignored, same convention as\n`drift-scan`'s reports).\n",{"name":5,"description":7},"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fskills\u002Fwrappee-drift",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-12 11:03:54",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill wrappee-drift",{"tool":57,"command":58},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill wrappee-drift",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill wrappee-drift","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",true,[],[66,93,103,129,155,175],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":80,"publishedAt":39},"01M6PFAWAHEJJCKKVNXEWNK87W","Docs Research","Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fsrc\u002Fdocs_mcp\u002Fskills\u002Fdocs-research\u002FSKILL.md",[72,77],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":78,"categoryName":79,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发",[81,82,83,84,85,86,87,88,89,90,91,92],"docs research","docs","research","packaging","use","ask","standards","fastmcp","MCP","search","server","documentation",{"skillNo":94,"name":95,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":102,"publishedAt":39},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[98,101],{"categoryNo":99,"categoryName":100,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":78,"categoryName":79,"taxonomyType":75,"taxonomyTypeDesc":76},[95],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":113,"publishedAt":39},"01M6PFA8YA029N68TW0X31FB1W","mcp-standards","Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI\u002FCD workflows.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002FSKILL.md",[109,112],{"categoryNo":110,"categoryName":111,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":78,"categoryName":79,"taxonomyType":75,"taxonomyTypeDesc":76},[89,87,114,115,116,92,117,118,119,120,121,122,123,124,125,126,85,84,127,128],"mcp standards","mcp servers","error handling","workflows","testing","scaffolding","servers","for","CI\u002FCD","error","cd","monitoring","sampling","access","ci",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":137,"publishedAt":39},"01M6PFA1XX344WX57B0DJZY94Q","webapp-cua-test","Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR \"Connected\" wait, sidebar nav walk) for a fleet MCP server repo under D:\\Dev\\repos. Trigger when the user says \"cua webapp test\" or \"webapp clickthrough\" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill \u002F cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwebapp-cua-test\u002FSKILL.md",[135,136],{"categoryNo":110,"categoryName":111,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":78,"categoryName":79,"taxonomyType":75,"taxonomyTypeDesc":76},[138,139,140,141,142,121,143,144,145,146,91,147,148,149,150,151,152,153,89,154],"webapp","test","webapp cua test","dom","assertions","trigger","click","app","tauri","repo","e2e","ocr","browser","dev","playwright","mcp server","stack",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":39},"01M6PF9WYF6NWJR7WVN38TT0WH","ship","Final release gate for a fleet MCP server repo under D:\\Dev\\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says \"ship it\", \"ship\" followed by a repo name, \"release\" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix\u002Fnsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fship\u002FSKILL.md",[161],{"categoryNo":78,"categoryName":79,"taxonomyType":75,"taxonomyTypeDesc":76},[157,163,164,153,165,89,166,167,121,143,168,169,170,171,147,172,173,91,174,151],"quality gates","commit","github","shipping","gates","ship it","artifact","done","say","work","publish","push",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":39},"01M6PF9QZ56VY2X22YVWQKA2YJ","quality-check","Strategic, qualitative assessment of whether a fleet MCP server repo is worth having -- its originality, difficulty, wrappee, competition, tool surface, fleet integration, and whether to promote, archive, or deprecate it. Trigger when the user says \"qualitycheck\" followed by a repo name, \"is this repo worth it\", \"should I archive X\", or asks for a strategic rather than mechanical review. Do NOT trigger for SOTA compliance, linting, or packaging (that is assfix), nor for auditing a webapp for mock data and dead buttons (that is fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fquality-check\u002FSKILL.md",[181],{"categoryNo":78,"categoryName":79,"taxonomyType":75,"taxonomyTypeDesc":76},[183,184,185,186,121,187,188,189,143,190,138,84,147,191,192,193,194,153,195,89],"quality check","check","quality","mechanical","mock data","strategic","mock","do","archive","tool","promote","assessment","review"]