Skill Creator
SkillDev toolsUse when adding, refactoring, tightening, evaluating, packaging, or comparing skills, especially when improving SKILL.md trigger descriptions, pruning stale wording, or deciding when a skill should fire.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Skill Creator skill
What this skill tells your AI
The instructions your AI receives, as published by qianleigood/crawclaw in skills/skill-creator/SKILL.md and read by ahel’s review.
Use this skill as the owner for skill design, cleanup, and evaluation.
Core workflow
- Classify the request:
- new skill
- existing skill cleanup
- trigger-description optimization
- eval / benchmark request
- Keep the scope concrete:
- what the skill should do
- when it should trigger
- which files are canonical
- whether scripts / references / assets are actually needed
- Prefer lean
SKILL.mdfiles:- keep only non-obvious workflow rules
- move detailed procedures into
references/ - keep
nameanddescriptionas the trigger-defining layer
- Validate before claiming completion:
- run
scripts/quick_validate.pywith the install-timecore-skillsPython runtime available - use representative prompts or comparisons when the change is meaningful
- run
- Optimize trigger wording last:
- first make the workflow correct
- then tighten the description so the skill fires reliably
Reference routing
Skill schema and benchmark data
Read references/schemas.md when you need:
- eval input schema
- benchmark output shape
- grading data structure
Evaluation helpers
Read these only when the task includes measurement:
agents/grader.mdagents/analyzer.md
Execution helpers
Use these when the task reaches validation or packaging:
scripts/quick_validate.pyscripts/aggregate_benchmark.pyscripts/improve_description.pyeval-viewer/generate_review.py
Working rules
- Keep one canonical skill file per real capability.
- Remove stale aliases, duplicated wording, and dead examples when they no longer help triggering.
- Do not leave detailed operational docs inside
SKILL.mdif a reference file can carry them. - Prefer realistic eval prompts over toy examples.
- Explain results in plain language, not benchmark jargon alone.
Signals
- GitHub stars
- 30
- Forks
- 1
- Last commit
- Sep 2026
- Hacker News mentions
- 1
Advanced
- Catalog kind
- skill
- Gateway key
skill-creator-qianleigood- Source
- github.com/qianleigood/crawclaw