Cassiiopeia/projectops / skills/pro-skill-creator
pro-skill-creator
VerifiedCreate, review or improve a standard skill. Classifies intent as create/review/improve, then runs the matching phases. Use for 'make a skill', 'review this skill', 'improve this skill'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| references/anti_patterns.md | markdown | 4.4 KB |
| references/meta_principles.md | markdown | 5.1 KB |
| references/phase0_brainstorming.md | markdown | 8.6 KB |
| references/phase1_slots.md | markdown | 3.4 KB |
| references/phase2_question_format.md | markdown | 1.8 KB |
| references/phase4_checklist.md | markdown | 3.1 KB |
| references/phase6_report_format.md | markdown | 2.2 KB |
| references/review_improve.md | markdown | 4.0 KB |
| references/trigger_optimization.md | markdown | 2.6 KB |
| templates/config.json.example | other | 495 B |
| templates/python_cli_script.py | script | 3.9 KB |
references/trigger_optimization.md
View on GitHub# Trigger utterance optimization (optional)
Use when the quick check in CREATE mode Phase 5 passed but the skill still does not seem to get invoked well. In most cases the quick check (5 samples) is enough.
## Why the description matters
The `description` in the SKILL.md frontmatter is almost the only signal Claude uses to decide "should I invoke this skill?". However good the body is, a vague description means the skill never gets invoked.
## Quick check (Phase 5 default)
1. **3 should-trigger**: utterances that should invoke it. Natural phrasing that does not name the skill directly.
2. **2 should-not-trigger**: nearby topics that must not invoke it.
3. The agent asks itself "Would I think of this skill from the description alone?"
5/5 is OK. If even one misses, fix the description and check again.
## Quantitative optimization with the official `run_loop.py` (advanced)
The official skill-creator has a loop that improves the description automatically. Requirements:
- the `claude` CLI is available (Claude Code environment)
- about 20 eval queries prepared (a mix of should-trigger / should-not-trigger)
### Run
```bash
python -m scripts.run_loop \
--eval-set <trigger-eval.json> \
--skill-path <skill-dir> \
--model <model-id> \
--max-iterations 5 \
--verbose
```
- 60% train / 40% test split
- each query runs 3 times for a stable trigger rate
- extended thinking proposes description improvements → re-evaluate → repeat (up to 5 times)
- best_description is picked by test score (prevents overfitting to train)
### Tips for writing eval queries
- **Bad**: "Format this data", "Extract text from PDF" — too abstract
- **Good**: utterances a real user would type, with context: file paths, work background, a bit of small talk
Example:
> "I just want to see the changed files in MR !347 of the api-server repo on our team's gitlab.example.com"
### In-house network limits
If `claude -p` is blocked on the in-house network, this loop does not run. Use the quick check (Phase 5 default) instead.
## Description writing tips (without quantitative optimization)
1. **Quote example trigger utterances directly** — "show me the MR changed files", "make a skill"
2. **Write in English by default, and add the users' own language** — e.g. a Korean team types mostly Korean but uses English technical terms, so include both
3. **Include concrete topics/project aliases** — CM, query server, systemdashboard, etc.
4. **Use "pushy" wording** — "always invoke", "when the user mentions X, Y, or Z". Too modest and it never gets invoked.
5. **Not too long** — ~200~300 characters. Too long lowers the signal-to-noise ratio.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |