- Skills
- 212
- 仓库
- 2
- 职业覆盖
- 6
- 场景覆盖
- 7
- Stars
- ★ 14
Sandra Schipal 的 Skills 212
robotics-mcp
Robotics control via MCP
mcp-server-architect
Comprehensive MCP server development guide covering FastMCP 2.14.3 features, Anthropic standards, ecosystem integration, and production deployment across all agentic IDEs
full-stack-developer
Complete fullstack development mastery covering modern web architectures, automation tools, AI integration, and production deployment practices
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.
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).
nsis-build
Build and smoke-test the Windows NSIS installer for a Tauri-based fleet MCP server repo under D:\Dev\repos. Trigger this whenever the user says "nsis build" followed by a repo name, asks to build the native installer, package the desktop app, or run the CUA smoke test on a repo that has a native/ Tauri directory. Not for MCPB/dxt packaging of a plain (non-Tauri) MCP server -- that is a different artifact, see the assfix skill Phase 5 for that path instead.
mcp-standards-manager-skill
暂无简介
mcp-builder
暂无简介
gapfind
Read-only audit of which backend capabilities (REST routes, MCP tools) a repo's webapp never surfaces, plus webapp calls to routes that do not exist. Trigger when the user says "gapfind" followed by a repo name, or asks "are there api endpoints or mcp tools in the backend that are not surfaced / used in webapp pages", or what the backend can do that the UI does not show. Report and propose only, never auto-fix. Do NOT trigger for mock data / dead buttons (that is fakefind), fleet-standard compliance (drift-scan / assfix), or coverage against the wrapped software's API (wrappee-drift).
fleet-expert
暂无简介
fleet-doctor
暂无简介
fakefind
Read-only audit of a repo's webapp for hardcoded mock data, dead buttons, fake stats, placeholder content, and UI that pretends to work but does not. Trigger when the user says "fakefind" followed by a repo name, "find fakes" followed by a repo name, or asks whether a UI is real, whether buttons actually do anything, or to hunt for gaslighting/mock data in a frontend. Report only, never auto-fix. Do NOT trigger for strategic worth ("is this repo worth keeping") -- that is quality-check -- or for SOTA compliance and packaging -- that is assfix.
drift-scan
Read-only fleet-wide gap analysis across every repo under D:\Dev\repos. Trigger whenever the user says "drift", "drift scan", "which repos need fixing", "fleet triage", or asks how badly repos deviate from current fleet standards. This is the fleet-wide TRIAGE tool that decides which repos to assfix; it is not itself a fix. Do NOT trigger for single-repo work ("assess and fix X", "lint this repo") -- that is the assfix skill.