Individual skill
skill-creator
Use when authoring a brand-new skill from scratch - turning a capability idea or a "make me a skill that…" request into a complete SKILL.md with a trigger-precise description and the full paid-quality anatomy: procedure, elicitation, thresholds, worked artifact, deliverable, Do NOT, quality bar. Triggers on "write a new SKILL.md from scratch", "turn this capability idea into a complete skill". Do NOT use to review or grade an existing skill (use skill-auditor), to convert an existing prompt (use prompt-to-skill), or for writing unrelated to skills.
skills/skill-creator/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- marketing Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,965 bytes
Read excerpt
# Skill Creator
Turn a capability idea into a committable SKILL.md that meets the paid-quality bar. The costly mistake this prevents: writing a competent essay about the topic instead of an operating procedure - a skill that reads well and changes nothing about the model's output.
## The bar
The skill you write ships only if all of these hold:
- It **fires on exactly the right requests and never on the wrong ones.** The description front-loads concrete triggers a router can act on with no ambiguity.
- It **does not collide** with any existing skill. Before writing, check the catalog for trigger overlap and carve clean boundaries into both descriptions.
- Its body carries the **full anatomy** (skill-author is the canonical standard): framing, ordered procedure, input elicitation, concrete thresholds, at least one worked artifact, an explicit deliverable, a Do NOT section, and a quality bar.
- It is **token-disciplined.** The description loads every session; the body loads on trigger. Every line is paid for by every installer, every session.
- It is **correct and self-contained** - real tools, real paths, real practitioner numbers; no hallucinated capabilities; no context it hasn't established.