skill-forgelisted
Install: claude install-skill titouannwtt/claude-tools
# skill-forge
Objective: accumulate reusable skills, one by one, without creating any wrongly. A skill is not justified for a one-off
task; it is for a capability that will be useful in other projects.
## 1. Check what exists
List `~/.claude/skills/` and `skills/` of the `claude-tools` repository. If a skill covers the request, use it and stop there.
## 2. Propose, do not create
If nothing covers the request, write:
"We have no skill for this. It looks useful for later. Do you want me to create it?"
Wait for the answer. Without agreement, create nothing.
## 3. Plan (after agreement)
Present a short plan, to be validated before any implementation:
- **Name** (kebab-case, generic, no personal name or hard-coded path).
- **Scope**: what the skill does, and what it does not do.
- **Inputs and outputs**: arguments, output format (text, JSON).
- **Script**: language, justification (see section 4), planned tests.
- **Research**: sources to explore (GitHub repositories, crates.io, PyPI, official documentation).
- **Configuration**: local values (paths, identifiers) in `local.env`, ignored by git.
## 4. Choose the language
Rust feasibility checklist, to fill in before writing the script:
1. Is the work compute-bound (heavy loops, parsing large volumes)? Yes/no.
2. Does a single dependency-free binary need to be distributed? Yes/no.
3. Will the script be called very often (dozens of times a day)? Yes/no.
- At least one "yes" and a measured or estimated gain: Rust.
- Otherwise