# Skillforge

Use when creating, improving, finding, or auditing agent skills - the user says 'create...

- Repository: https://github.com/tripleyak/SkillForge (915 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-07-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add tripleyak/SkillForge --skill skillforge -g -a claude-code -y`
Codex: `npx skills add tripleyak/SkillForge --skill skillforge -g -a codex -y`
Cursor: `npx skills add tripleyak/SkillForge --skill skillforge -g -a cursor -y`
Gemini CLI: `npx skills add tripleyak/SkillForge --skill skillforge -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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:

```bash
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](references/testing-and-evals.md).

The rest: https://github.com/tripleyak/SkillForge/blob/HEAD//SKILL.md