pythia-skill-authorlisted
Install: claude install-skill thaildhe172591/pythia
# Authoring a New Skill
**Announce at start:** "Using pythia-skill-author — let's capture how you actually work."
**Phase:** Learn → Ask → Do — interview, mine the schema, verify triggering
A skill is a decision captured so it never has to be re-argued. Capture what
the team *actually does* — with evidence from the database — not what anyone
remembers about it.
## Step 1 — Interview, one question at a time
Ask, in order, waiting for each answer:
1. **What task is this for?» One skill per concern — "our report procedure
ritual" is one skill; "everything about our team" is not.
2. **When should it trigger?** Collect the developer's *own words* — the
phrases they would type ("làm báo cáo", "clone the export proc", an error
code, a file pattern). These go into the description verbatim; triggering
lives or dies on them.
3. **Which parts are law, which are taste?** Hard rules get an Iron Law and
a red-flags table; preferences get a "default unless told otherwise".
4. **What does *wrong* look like?** Past incidents make the best red-flag
rows.
## Step 2 — Mine the evidence
Memory lies; the schema does not. Before writing a line:
- `pythia similar <TYPICAL_NAME>` → which family of programs embodies this
workflow; open the top hits with `pythia src` and extract the *actual*
naming, parameter and structure conventions.
- `pythia args` / `pythia cols` for the signatures and types the skill will
tell people to use.
- Save two or three short **verbatim** s