菜单
Sync skills and dependencies after package updates. Use after running `bun update @cyanheads/mcp-ts-core` to ensure project skills and agent skill directories are up to date, or periodically to check for drift.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | maintenance |
| description | Sync skills and dependencies after package updates. Use after running `bun update @cyanheads/mcp-ts-core` to ensure project skills and agent skill directories are up to date, or periodically to check for drift. |
| metadata | {"author":"cyanheads","version":"1.0","audience":"external","type":"workflow"} |
Skills flow through three tiers:
node_modules/@cyanheads/mcp-ts-core/skills/ (canonical source)skills/ at project root (source of truth for this project).claude/skills/)After bun update @cyanheads/mcp-ts-core, Tier 1 may have newer skills than Tier 2, and Tier 3 may be out of sync with Tier 2 at any time.
node_modules/@cyanheads/mcp-ts-core/skills/metadata.audience: external in its SKILL.md frontmatter:
skills/, copy the full directorymetadata.version — if the package version is newer, replace the full directoryskills/ that don't exist in the package (server-specific)skills/skills/ to your agent directoryskills/ is newerskills/bun outdated to see what's out of datebun update to update dependenciesbun audit to check for vulnerabilities introduced by the updatebun run devcheck to confirm lint, types, and tests still passskills/ (version check)skills/skills/bun update)bun audit passes (no new vulnerabilities)bun run devcheck passesScaffold a new MCP prompt template. Use when the user asks to add a prompt, create a reusable message template, or define a prompt for LLM interactions.
Scaffold a new MCP resource definition. Use when the user asks to add a resource, expose data via URI, or create a readable endpoint.
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a colocated test file.
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
Authentication, authorization, and multi-tenancy patterns for `@cyanheads/mcp-ts-core`. Use when implementing auth scopes on tools/resources, configuring auth modes (none/jwt/oauth), working with JWT/OAuth env vars, or understanding how tenantId flows through ctx.state.