write-skill

write-skill is a command for Claude Code from iliaal/whetstone. It costs 41 tokens per session (3,144 once invoked), scanned A, original, MIT.

A guided process for creating a new coding-agent skill from the ground up, including its activation examples and checks that it follows the required format.

In plain words
What is it for?
It helps scaffold a new skill, collect its required details, register when it should activate, and run checks before it is added.
Why use it?
It helps avoid missing files, naming rules, trigger patterns, or validation steps when adding a skill to a project.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions .claude-plugin; mentions CLAUDE.md; names the AskUserQuestion tool.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 distillery/scripts/distiller.py eval-triggers <name> \.

Good fit It helps scaffold a new skill, collect its required details, register when it should activate, and run checks before it is added.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/iliaal/whetstone
agentmods
npx agentmods add commands/iliaal/whetstone/write-skill

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-skill

README.md
[![agentmods](https://agentmods.dev/badge/commands/iliaal/whetstone/write-skill/github.svg)](https://agentmods.dev/commands/iliaal/whetstone/write-skill)
Your own site
<a href="https://agentmods.dev/commands/iliaal/whetstone/write-skill"><img src="https://agentmods.dev/badge/commands/iliaal/whetstone/write-skill/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-skill

Your own site · 80×15
<a href="https://agentmods.dev/commands/iliaal/whetstone/write-skill"><img src="https://agentmods.dev/badge/commands/iliaal/whetstone/write-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,144 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.03144
Opus 5.5 $0.00016 $0.01258
Sonnet 5.5 $0.00008 $0.00629
Haiku 4.5 $0.00004 $0.00314

Measured 24d ago against content hash e2f179aec067, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 24d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/write-skill.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write Skill

Skill name: $ARGUMENTS

Scaffold a new plugin skill from scratch, generate paired trigger fixtures, register the regex pattern, and run all gates. For distilling a skill from skills.sh sources, use the skill-distiller skill instead — /write-skill is for skills with no external upstream.

Phase 1: Resolve target

  1. If $ARGUMENTS is empty or doesn't start with ia-, ask for the skill name.
  2. Validate format: must match ^ia-[a-z0-9][a-z0-9-]*$, no consecutive hyphens, no banned tokens (anthropic, claude).
  3. Confirm the skill doesn't already exist:
    • plugins/whetstone/skills/<name>/SKILL.md must NOT exist.
    • distillery/tests/fixtures/triggers/<name>.jsonl must NOT exist.
    • No matching SKILL_PATTERNS[<name>]= line in plugins/whetstone/hooks/skill-patterns.sh.
  4. Read CLAUDE.md "Skill compliance checklist" section to refresh the gates this skill must pass.

Phase 2: Batch up-front interview

Use AskUserQuestion once to collect everything needed before scaffolding. Do not drip-feed questions across turns.

Ask:

  1. Class — one of the five values from CLAUDE.md "Skill class taxonomy": language, discipline, workflow, meta, tool. Read that section before asking so the option descriptions match what the validator will accept.
  2. Scope summary — one or two sentences: what this skill is for, when it fires.
  3. Primary trigger vocabulary — 3-6 distinctive phrases users would type.
  4. Existing skills it should not overlap with — names of any close-in-scope ia-* skills the user already has in mind.

Phase 3: Inspect prior art

Read the SKILL.md of every skill the user named in question 4 (and any others that look similar by class). Goals:

  • Match house style (frontmatter shape, body voice, references/ patterns).
  • Identify trigger overlap risk — validate-plugin will flag descriptions with >70% word overlap.
  • Find a close structural template to model the new skill after.

Phase 4: Scaffold

Read the full file on GitHub · 226 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 24d ago Changed e2f179aec067
  2. 1mo ago First seen · 226 lines · 41 tokens per session scan A 4a8b97b20fc5

Subscribe to this mod's changes

write-skill is a command published in the GitHub repository iliaal/whetstone (35 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 3,144 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.