skill-writer

skill-writer is a skill for Claude Code, Codex from clutchpbcfo/hermes-skills. It costs 57 tokens per session (954 once invoked), scanned A, original, MIT.

A guide for creating a saved Hermes skill: a Markdown file that tells an agent when and how to perform a repeatable workflow. It follows the agentskills.io format and includes setup details, steps, and a way to check the result.

In plain words
What is it for?
Creating a new skill, improving an existing one, or documenting a recurring task with its trigger, inputs, procedure, and verification check.
Why use it?
It turns a workflow that someone repeatedly performs by hand into a consistent, reusable instruction file.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Creating a new skill, improving an existing one, or documenting a recurring task with its trigger, inputs, procedure, and verification check.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/clutchpbcfo/hermes-skills/skill-writer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add clutchpbcfo/hermes-skills --skill skill-writer
Clone the repo
git clone --depth 1 https://github.com/clutchpbcfo/hermes-skills

Made for: Claude Code, Codex.

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 skill-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/clutchpbcfo/hermes-skills/skill-writer/github.svg)](https://agentmods.dev/skills/clutchpbcfo/hermes-skills/skill-writer)
Your own site
<a href="https://agentmods.dev/skills/clutchpbcfo/hermes-skills/skill-writer"><img src="https://agentmods.dev/badge/skills/clutchpbcfo/hermes-skills/skill-writer/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 skill-writer

Your own site · 80×15
<a href="https://agentmods.dev/skills/clutchpbcfo/hermes-skills/skill-writer"><img src="https://agentmods.dev/badge/skills/clutchpbcfo/hermes-skills/skill-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 954 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.00057 $0.00954
Opus 5 $0.00028 $0.00477
Sonnet 5 $0.00011 $0.00191
Haiku 4.5 $0.00006 $0.00095

Measured 11d ago against content hash a1d92901c0db, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

skill-writer 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 11d 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.

skill-writer/SKILL.md · 41 lines

How it starts

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

Skill Writer

When to Use

Use this when the user wants to create a new Hermes skill, clean up one they have, or turn a repeatable workflow they keep doing by hand into a saved skill. Triggers include "help me write a skill for...", "turn this workflow into a skill", "make a SKILL.md", or "I keep doing X manually, can we save it." The output is a complete, installable SKILL.md, not advice about writing one.

Background

A skill is an on-demand knowledge document the agent loads only when a task needs it (progressive disclosure). Skills follow the agentskills.io open standard: a Markdown file with YAML frontmatter, stored at ~/.hermes/skills//SKILL.md. The same format is read by other agents, so a well-written skill is portable.

Procedure

  1. Extract the workflow. Ask the user to describe the task they do repeatably. Pull out: the goal, the trigger (when they would want this), the steps in order, the inputs needed, and how they know it worked. If they describe it vaguely, ask for one concrete recent example.
  2. Name it. Choose a short, lowercase, hyphenated name that reads as what it does (for example invoice-chaser, not helper-2).
  3. Write the description. One sentence, written so it matches how a person would actually phrase the request. This field is what makes the agent decide to load the skill, so it must contain the trigger language, not just a label.
  4. Write the frontmatter. Produce valid YAML: name, description, version (start at 1.0.0), optional platforms only if the skill is OS-specific, and metadata.hermes with tags and a category.
  5. Write "When to Use." Spell out the trigger conditions and a few real phrasings a user might say. Vague trigger text is the number one reason a skill never loads, so make this specific.
  6. Write "Procedure." Numbered, ordered steps. Each step is one clear action. Define what "done" looks like. Where the order matters, say so.
  7. Write "Pitfalls." List the real failure modes for this workflow and how to avoid them. Skip generic warnings; name the ones that actually bite.
  8. Write "Verification." Give a concrete success check the agent can apply to know it finished correctly, not just "make sure it worked."
  9. Assemble and deliver. Output the full SKILL.md in one block, ready to save to ~/.hermes/skills//SKILL.md. Then tell the user how to test it (see Verification).

Read the full file on GitHub · 41 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. 11d ago First seen · 41 lines · 57 tokens per session scan A a1d92901c0db

Subscribe to this mod's changes

skill-writer is a skill published in the GitHub repository clutchpbcfo/hermes-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 954 once invoked, about $0.0003 per session on Opus 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-31.

Related

Other skills, from other repositories