skill-creator2
Skill0 starsChanged 3 months agoMITView on GitHub
Create, improve, and evaluate Claude skills with a QA-first workflow. Use when users ask to build a skill, improve this skill, refine this one, make this better, run benchmark-only validation, or optimize a skill description for reliable triggering.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dipaulavs/ClaudeCode-Workspace-2025their own version, first seen Nov 5, 2025
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dipaulavs/ClaudeCode-Workspace-2025★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- corporate-espionageSkill
- dispatching-parallel-agentsSkill
- epub-readerSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- github-raw-readerSkill
- magisk-moduleSkill
- notepadpp-plugin-skillSkill
- planningSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- technical-writerSkill
- test-driven-developmentSkill
- text-humanizerSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- windows-diagnosticsSkill
- writing-plansSkill
- zed-extensionSkill
- zed-themeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
41 rules. About 0 are common, 22 are distinctive, and 19 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈22
Distinctive · estimate
This author's own choices. Worth a look.
19
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When the user gives a vague refinement request (for example: "use skill-creator to refine this skill", "make this better"), do not start …
- Very specific: line 16
Ensure QA.txt exists in the target skill root.
- Very specific: line 17
Run a comprehensive QA pass against that QA.txt.
- Distinctive: line 20
If the user gives minimal direction, proceed with the recommended option.
- Distinctive: line 22
Use this fast path as the default for underspecified improvement requests.
- Distinctive: line 26
Use triage first, then follow the matching workflow.
- Distinctive: line 39
If the conversation already includes requirements, extract them before asking new questions.
- Distinctive: line 43
Every major feature must be reachable from a concrete user cue.
- Very specific: line 59
Before writing or revising prompt text for any skill, read references/prompt-engineering-best-practices.md.
- Distinctive: line 68
Use reasoning guidance only when the task benefits from multi-step thinking.
- Distinctive: line 69
Add a self-check pattern for evaluative outputs.
- Distinctive: line 70
Use XML-style tags or clear delimiters when mixing instructions, examples, context, and dynamic input.
- Very specific: line 78
Read references/intake-and-triage.md before drafting or editing.
- Very specific: line 89
When writing SKILL.md for the target skill:
- Distinctive: line 92
Keep frontmatter valid and description specific enough to trigger reliably.
- Distinctive: line 93
Keep instructions imperative and deterministic.
- Very specific: line 94
Keep SKILL.md lean and router-like.
- Very specific: line 105
Read references/eval-loop.md and execute it as one continuous sequence.
- Very specific: line 109
Run python -m scripts.quick_validate .
- Very specific: line 111
Treat QA as passing only when every question in the created or edited skill root QA.txt is answered yes.
- Distinctive: line 113
Run a negative-trigger smoke test with an obviously unrelated prompt to confirm the skill does not load.
- Very specific: line 114
Create realistic eval prompts and save evals/evals.json.
- Distinctive: line 115
Run with-skill and baseline runs in parallel where supported.
- Very specific: line 117
Use all agents/*.md workflows as part of testing: agents/grader.md for grading, agents/comparator.md for paired blind comparisons, and …
- Very specific: line 126
After each edit cycle, run the loop in references/eval-loop.md.
- Very specific: line 130
Ensure QA bootstrap was completed before any create/edit/evaluate action: QA.txt exists and missing assets/QA.txt questions were appended …
- Very specific: line 132
After each edit, run Comprehensive QA pass #1 against current QA.txt.
- Very specific: line 134
Run Comprehensive QA pass #2 against the expanded QA.txt to confirm improvement, no regressions, and preserved objective fit.
- Very specific: line 136
Do not treat the QA stage as complete unless every question in the target skill root QA.txt is answered yes.
- Very specific: line 139
Keep the target skill's SKILL.md within practical router size limits.
- Distinctive: line 146
When the user confirms satisfaction, explicitly ask them for recommendations to improve the skill-creator itself.
- Distinctive: line 155
Use this when the user asks whether the new version is actually better.
- Distinctive: line 159
After creation or improvement, offer to optimize skill triggering.
- Distinctive: line 168
Prefer test-score-selected descriptions over train-only wins to reduce overfitting.
- Distinctive: line 172
After every skill creation or edit cycle that the user confirms as complete, packaging is mandatory.
- Very specific: line 181
Always call present_files with that path so the user receives a downloadable zip regardless of environment.
- Very specific: line 188
Read references/environment-adapters.md for environment-specific behavior:
- Distinctive: line 223
Avoid AI fluff and ambiguous language.
- Distinctive: line 224
Prefer deterministic steps over vague guidance.
- Distinctive: line 225
Use the highest available reasoning effort by default for design-critical work that reduces future user effort.
- Distinctive: line 227
Never skip QA just because a request is underspecified.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Creator
A skill for creating new skills and iteratively improving existing skills.
Fast Path: "Improve this skill" with no specs
When the user gives a vague refinement request (for example: "use skill-creator to refine this skill", "make this better"), do not start with broad spec questions. Run this QA-first intake path first.
- Identify the target skill path and current name.
- Snapshot the current skill before editing.
- Ensure
QA.txtexists in the target skill root. Append missing baseline checks fromassets/QA.txt. - Run a comprehensive QA pass against that
QA.txt. - Produce an improvement brief with prioritized issues, expected impact, and risk.
- Present 2-3 concrete improvement options and recommend one.
- If the user gives minimal direction, proceed with the recommended option.
Use this fast path as the default for underspecified improvement requests.
Workflow Map
Use triage first, then follow the matching workflow.
| Situation | Path |
| Brand new skill | Capture Intent -> Write -> Test -> Iterate |
| Improving an existing skill with clear specs | Capture Intent -> Edit -> Test -> Iterate |
| Improving an existing skill, specs not provided | Run QA-first fast path, then continue with scoped improvements |
| QA or benchmarking only (mature skill) | Skip writing. Evaluate as-is first, then propose improvements |
| User wants to review outputs/results before more edits | Jump to eval loop review step and launch user review view first |
| User asks "is the new version actually better?" | Run blind comparison workflow |
| User asks to optimize triggering | Run description optimization workflow |
| User asks to package/install the skill | Run packaging workflow |
If the conversation already includes requirements, extract them before asking new questions.
Feature Entry Points
Every major feature must be reachable from a concrete user cue.
| User cue | Feature | Entry action |
| "create a skill for X" | Skill creation | Start capture-intent flow |
| "improve this skill" (vague) | QA-first improvement intake | Run fast path before broad interviews |
| "edit this part of the skill" | Scoped refinement | Start existing-skill edit flow |
| "test/benchmark/QA this skill" | QA/benchmark-only mode | Evaluate as-is first |
| "show me outputs to review" or iteration eval in progress | User review workflow | Generate review viewer before more edits unless user opts out |
| "is new version better?" | Blind comparison | Run comparator + analyzer |
| "improve triggering" | Description optimization | Run trigger-eval optimization loop |
| "package it" / "I want the .skill file" | Packaging | Run package script and provide artifact path |
| Environment constraints (no subagents/headless) | Environment adapter | Switch to environment-specific reference workflow |
Prompt Engineering Reference
Before writing or revising prompt text for any skill, read
references/prompt-engineering-best-practices.md.
This is required guidance. All prompt blocks should follow this default shape:
role -> context -> task -> constraints -> output format
Apply with judgment:
- Use reasoning guidance only when the task benefits from multi-step thinking.
- Add a self-check pattern for evaluative outputs.
- Use XML-style tags or clear delimiters when mixing instructions, examples, context, and dynamic input.
- For long-context tasks, ground outputs in quoted or clearly identified evidence.
- Surface hidden assumptions and ask for clarification when requirements are underspecified.
Core Workflow
1) Capture Intent and Research
Read references/intake-and-triage.md before drafting or editing.
You must:
- Clarify the user goal, trigger conditions, output format, constraints, and success criteria.
- Research professional standards and official documentation relevant to the target domain before writing logic.
- For skills targeting hobbyist or practitioner communities, research the social platforms where that community is active (forums, subreddits, GitHub topic searches) to surface real pain points and ecosystem gaps that official docs omit. See
references/intake-and-triage.md§5 for the platform lookup table and recording requirements. - For each new or refined skill, draft 3 candidate core prompt formulations, pick the best, and record rationale in
references/design-log.md.
2) Write or Edit the Skill
When writing SKILL.md for the target skill:
- Preserve skill name and directory when refining an existing skill.
- Keep frontmatter valid and description specific enough to trigger reliably.
- Keep instructions imperative and deterministic.
- Keep
SKILL.mdlean and router-like. Move heavy implementation details toreferences/. - For every file placed in
scripts/, add an entry inSKILL.mdthat states when to run it, the exact command, how to interpret its output, and what to do if it fails.
Progressive disclosure standard:
- Metadata (
name,description) should define what and when. SKILL.mdshould route to the right reference files.- Scripts and references should hold heavy details and repeatable procedures.
3) Test and Evaluate
Read references/eval-loop.md and execute it as one continuous sequence.
The test/eval workflow includes:
- Run
python -m scripts.quick_validate .from the target skill root. - Immediately run mandatory QA against that skill's
QA.txt. - Treat QA as passing only when every question in the created or edited skill
root
QA.txtis answeredyes. - Run a negative-trigger smoke test with an obviously unrelated prompt to confirm the skill does not load; record the prompt and outcome in the workspace.
- Create realistic eval prompts and save
evals/evals.json. - Run with-skill and baseline runs in parallel where supported.
- Draft and refine assertions while runs execute.
- Use all
agents/*.mdworkflows as part of testing:agents/grader.mdfor grading,agents/comparator.mdfor paired blind comparisons, andagents/analyzer.mdfor benchmark and post-comparison analysis. - Grade outputs, aggregate benchmark data, and generate the review viewer.
- Trigger user review with eval-viewer auto-submit mode and wait for completion before additional edits.
- Collect user feedback and continue iteration.
4) Improve and Iterate
After each edit cycle, run the loop in references/eval-loop.md.
Required quality gates before presenting changes:
- Ensure QA bootstrap was completed before any create/edit/evaluate action:
QA.txtexists and missingassets/QA.txtquestions were appended as-is. - After each edit, run Comprehensive QA pass #1 against current
QA.txt. - Then review description quality and append missing skill-specific QA checks.
- Run Comprehensive QA pass #2 against the expanded
QA.txtto confirm improvement, no regressions, and preserved objective fit. - Do not treat the QA stage as complete unless every question in the target
skill root
QA.txtis answeredyes. - Feature discoverability and integration checks for new phases.
- Keep the target skill's
SKILL.mdwithin practical router size limits.
Stop when:
- The user confirms satisfaction, or
- Feedback is consistently empty, or
- Additional iterations stop producing meaningful gains.
- When the user confirms satisfaction, explicitly ask them for recommendations to improve the skill-creator itself.
Advanced: Blind Comparison
For rigorous A/B evaluation between two skill versions, use:
agents/comparator.mdfor blind output comparisonagents/analyzer.mdfor post-hoc winner/loser analysis
Use this when the user asks whether the new version is actually better.
Description Optimization
After creation or improvement, offer to optimize skill triggering.
Read references/description-optimization.md.
Important rules:
- Description must describe concrete situations, not just capabilities.
- Include at least one realistic example trigger phrase.
- Evaluate both should-trigger and should-not-trigger cases.
- Prefer test-score-selected descriptions over train-only wins to reduce overfitting.
Packaging and Delivery
After every skill creation or edit cycle that the user confirms as complete, packaging is mandatory. Run:
python -m scripts.package_skill <path/to/skill-folder> /mnt/user-data/outputsThis produces a .zip file at /mnt/user-data/outputs/<skill-name>.zip.
Always call present_files with that path so the user receives a downloadable
zip regardless of environment. Do not skip this step or leave it as an offer
the user must accept. If the packager returns an error, report it and fix the
underlying validation failure before re-running.
Environment Adapters
Read references/environment-adapters.md for environment-specific behavior:
- Claude Code (subagents and full loop)
- Claude.ai (no subagents)
- Cowork/headless environments
The high-level workflow remains the same; only execution mechanics differ.
Reference Index
Core references
references/intake-and-triage.md- triage, QA-first vague-improvement intake, interview flow, design-log requirementsreferences/eval-loop.md- test execution, grading, benchmark aggregation, review viewer, feedback loop, iteration gatesreferences/description-optimization.md- trigger eval set design and optimization loopreferences/environment-adapters.md- Claude.ai and Cowork execution differencesreferences/file-routing-index.md- complete non-root file routing map for discoverability/QAreferences/schemas.md- JSON schemas for eval and benchmark artifactsreferences/prompt-engineering-best-practices.md- required prompt construction rulesreferences/prompt-research-notes.md- supporting research notes
Subagent references
agents/grader.md- grading assertions against outputsagents/comparator.md- blind A/B comparisonagents/analyzer.md- benchmark and post-hoc analysis
QA baseline
assets/QA.txt- baseline QA checklist to merge into target skillQA.txt
Operating Principles
- Be flexible with user preference while preserving evaluation rigor.
- Never use emojis.
- Avoid AI fluff and ambiguous language.
- Prefer deterministic steps over vague guidance.
- Use the highest available reasoning effort by default for design-critical work that reduces future user effort. Only trade down when the user explicitly prefers speed.
- Preserve existing features unless the user requests removal.
- Never skip QA just because a request is underspecified.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

