with one click
with one click
Add comprehensive CI workflows to a target repo - lint, test, build, security scanning, dependabot, scorecard, action pinning
Bootstrap orchestrate skills into a target repo - making it self-sufficient for orchestrating its own related repos
Add security governance to a target repo - CODEOWNERS, SECURITY.md, CONTRIBUTING.md, LICENSE, .gitignore audit
Scan a repository to bootstrap new skills or audit and update existing ones
Validate skill files meet the standard format and naming conventions
Create or edit skills with proper structure, task tracking, and naming conventions
| name | skills |
| description | Skill management - create, validate, and improve Claude Code skills |
flowchart TD
START(["/skills"]) --> NEED{"What do you need?"}
NEED -->|New skill| WORKTREE["git:worktree"]:::git
NEED -->|Edit skill| WORKTREE
NEED -->|Audit all| SCAN["skills:scan"]:::skills
WORKTREE --> WRITE["skills:write"]:::skills
WRITE --> VALIDATE["skills:validate"]:::skills
VALIDATE -->|Issues| WRITE
VALIDATE -->|Pass| PR["Create PR"]:::git
SCAN -->|Gaps found| WORKTREE
classDef skills fill:#607D8B,stroke:#333,color:white
classDef git fill:#FF9800,stroke:#333,color:white
Follow this diagram as the workflow.
Skills for managing the skill system itself. All skill development starts in a worktree — never edit skills directly on main.
Before creating or editing any skill, create a worktree:
git fetch upstream main
git worktree add .worktrees/skills-<topic> -b docs/skills-<topic> upstream/main
Then work in the worktree, validate, and create a PR.
| Skill | Purpose |
|---|---|
skills:write | Create new skills or edit existing ones following the standard template |
skills:validate | Validate skill format, naming, and structure |
skills:scan | Audit repository skills — gaps, quality, connections, diagrams |
orchestrate - Orchestrate related repositories using these skills