Skm sync agent skills
Agent Skill Manager — discover, install, link, and upgrade skills for Claude Code & Codex.
npx -y skills add weiox/skm --skill skm-sync-agent-skillsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the declared skill layout under `~/.skm` and the live entrypoints in `~/.agents/skills` or `~/.claude/skills` may be out of sync, and you want to rebuild missing links while removing stale or unmanaged symlinks.
SKILL.md
2.7 KB, as published. Nobody here has run it
Sync Agent Skills
Overview
This skill forces the runtime entrypoints back into alignment with the skm source of truth.
Use it when the current state is messy but you already trust the managed source tree.
When to Use
Use this skill when:
- stale entrypoint links keep reappearing
CodexorClaude Codeare exposing the wrong set of skills- unmanaged symlinks exist in
~/.agents/skillsor~/.claude/skills - you want to reconcile the current runtime state to the declared layout
- you created a new skill under
~/.skm/personaland the runtime layer has not picked it up yet
Do not use this skill to discover new external packages. Use skm-install-linked-agent-skills for that.
Do not use this skill to force through duplicate skill-name conflicts. Resolve those with skm-doctor-agent-skills or skm-organize-agent-skills first.
Core Rule
Sync means:
- remove symlink entries not declared by
skm - rebuild the expected entrypoints
- verify the rebuilt state
Run:
bash ~/.skm/skills/skm-sync-agent-skills/scripts/skm-sync-agent-skills.sh
Important Reminder
Sync repairs the runtime entrypoints. It does not hot-reload the skill inventory of an already-running Codex session.
If a newly created skill still does not appear after sync:
- verify
check.shpasses - start a new
Codexsession
Workflow
1. Diagnose if needed
If you are not sure what is wrong, run skm-doctor-agent-skills first.
If doctor reports CONFLICT, stop there. Sync should not proceed until the duplicate declared sources are resolved.
2. Run sync
bash ~/.skm/skills/skm-sync-agent-skills/scripts/skm-sync-agent-skills.sh
3. Read the diff-style output
The script reports:
ADDED <layer> <name>REMOVED <layer> <name>
Then it runs:
bootstrap.sh --forcecheck.sh
If duplicate skill names exist across declared sources, sync now aborts instead of silently choosing one source.
If the script succeeds but the current session still cannot see a new skill, that is a session-refresh issue rather than a sync failure.
Common Mistakes
- Running sync when the source tree itself is wrong
- Running sync when
doctorhas already reportedCONFLICT - Expecting unmanaged symlinks to survive a sync
- Treating entrypoint directories as editable source directories
Completion Checklist
- stale links are removed
- expected links are present again
check.shpasses