Agent skill
readme-sync
Synchronizes the list of Agent Skills in the root README.md with the actual skills present in the codebase.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/readme-sync-yu-iskw-coding-agent-skills
SKILL.md
README Sync
Purpose
Ensures that the ## Agent Skills section in the root README.md accurately reflects all available skills in skills/.
Workflow
- Identify Skills: Use
Globorfindto locate allSKILL.mdfiles inskills/and.cursor/skills/. - Extract Information: For each skill found, use
uv run skills-ref read-properties <skill-directory>to get thenameanddescription. - Generate Markdown: Format the collected information as a sorted list of markdown items:
- Format:
- **[name](relative/path/to/skill/)**: description
- Format:
- Update README.md: Replace the content between
<!-- START-SKILLS -->and<!-- END-SKILLS -->markers in the rootREADME.mdwith the newly generated list.
Implementation Notes
- The
skills-reftool is part of the project dependencies and can be run viauv run. - Always maintain alphabetical order of the skills in the
README.mdlist. - Ensure the relative paths in the markdown links correctly point to the skill directories from the root.
Examples
Scenario: Updating README.md after adding a new skill
- Find all skills in the directory
skills/. - Get properties for each skill:
uv run skills-ref read-properties skills/claude-code-cli. - Update
README.mdwithin the<!-- START-SKILLS -->block.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?