Skillforge
Use when creating, improving, finding, or auditing agent skills - the user says 'create...
Install
npx skills add tripleyak/SkillForge --skill skillforge -g -a claude-code -y- Repository
- tripleyak/SkillForge915
- Category
- Testing
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Mediumabout 2,117 tokens
- Runs scripts
- No, instructions only
What it does
Use when creating, improving, finding, or auditing agent skills - the user says 'create a skill', 'do I have a skill for X', 'improve the X skill', 'which skill should I use', asks whether a skill exists for a task, or wants to validate, test, evaluate, package, or health-check skills. Also use for skill ecosystem maintenance (duplicate detection, stale skills, trigger collisions) and advisor checkpoints.
SkillForge 6 - Skill Router, Creator & Ecosystem Maintainer
Routes any skill-related request to the right action (use, improve, create, compose), creates new skills through an evidence-driven pipeline, and maintains the health of the whole skill ecosystem. Core principle: skill quality is a property of behavior, not documents - a skill is done when a fresh agent demonstrably does better with it than without it.
Routing (Phase 0)
Always triage before creating anything:
python3 scripts/discover_skills.py # refresh index (auto-refreshes if >24h old)
python3 scripts/triage_skill_request.py "<the user's request>" --json
| Triage result | Action |
|---|---|
| Strong match (existing skill) | Recommend it; do not create a duplicate |
| Moderate match | Offer IMPROVE_EXISTING on the matched skill |
| Weak/no match + create intent | Proceed to creation pipeline |
| Multi-domain | Suggest composing existing skills |
| Ambiguous | Ask one clarifying question |
Match bands are keyword-evidence heuristics, not calibrated probabilities - report them as "strong/moderate/weak match", never as percent confidence.
Creation pipeline
Run phases in order. Each phase's detailed procedure lives in its reference - read the reference when you reach the phase, not before.
0. Baseline gate (RED). Before designing anything, dispatch a fresh subagent (Task tool) on 1-2 representative target tasks WITHOUT the skill. Capture verbatim what it does wrong. If the baseline does not fail, stop - the skill is unnecessary. The failures become the skill's test cases and its description keywords. See references/testing-and-evals.md.
