| 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"} |
Context
Skills flow through three tiers:
- Package —
node_modules/@cyanheads/mcp-ts-core/skills/ (canonical source)
- Project —
skills/ at project root (source of truth for this project)
- Agent — your agent skill directory (e.g.,
.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.
Steps
Sync project skills (Tier 1 → Tier 2)
- List all skill directories in
node_modules/@cyanheads/mcp-ts-core/skills/
- For each skill with
metadata.audience: external in its SKILL.md frontmatter:
- If the skill does not exist in project
skills/, copy the full directory
- If it exists, compare
metadata.version — if the package version is newer, replace the full directory
- If the local version is equal or newer, skip (local override)
- Do not touch skills in
skills/ that don't exist in the package (server-specific)
Sync agent skills (Tier 2 → Tier 3)
- Compare your agent skill directory against project
skills/
- Copy any missing skills from
skills/ to your agent directory
- For existing skills, compare file contents — update if
skills/ is newer
- Do not remove skills from your agent directory that aren't in
skills/
Dependency updates
- Run
bun outdated to see what's out of date
- Review changelogs for any major version bumps before proceeding
- Run
bun update to update dependencies
- Run
bun audit to check for vulnerabilities introduced by the update
- Run
bun run devcheck to confirm lint, types, and tests still pass
Checklist
