general
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 0
02 资源文件 12
- 参考文档3p-updates.md3.4 KB
- 参考文档arctic-frost.md708 B
- 参考文档botanical-garden.md687 B
- 参考文档company-newsletter.md3.4 KB
- 参考文档desert-rose.md659 B
- 参考文档faq-answers.md2.5 KB
- 参考文档forest-canopy.md671 B
- 参考文档general-comms.md770 B
- 参考文档golden-hour.md691 B
- 参考文档modern-minimalist.md718 B
- 参考文档ocean-depths.md719 B
- 参考文档tech-innovation.md714 B
03 SKILL.md 正文
<!-- SOURCE: https://github.com/anthropics/skills ORIGINAL_PATH: template-skill\SKILL.md AUTHOR: Anthropic LICENSE: Apache-2.0 COPIED: 2025-10-28 -->
name: template-skill description: Replace with description of the skill and when Claude should use it.
Insert instructions below
04 同仓库更多 Skills
Docs Research
Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).
wrappee-drift
Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing 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/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.
modules
暂无简介
mcp-standards
Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.
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 / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).
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/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.