What is skill-author?

An authoring and review agent for skills, where a skill is a folder containing instructions for a repeatable workflow. It checks the required metadata, directory structure, examples, and vendor-specific settings.

Use it to design or extend skills, maintain the standard skill template, create worked examples, and keep mirrored vendor versions aligned.

It helps authors create portable skills that follow the project’s format and work consistently across different coding-agent tools.

skill-author — Agent for Claude Code by Enovatr-Labs

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.

Clone the repo

git clone --depth 1 https://github.com/Enovatr-Labs/SpecRoute

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/enovatr-labs/specroute/skill-author/github.svg)](https://agentmods.dev/agents/enovatr-labs/specroute/skill-author)

Your own site

<a href="https://agentmods.dev/agents/enovatr-labs/specroute/skill-author"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/skill-author/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/enovatr-labs/specroute/skill-author"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/skill-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 114 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 714 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.

Model	Per session	Once invoked
Fable 5.1	$0.00114	$0.00714
Opus 5	$0.00057	$0.00357
Sonnet 5	$0.00023	$0.00143
Haiku 4.5	$0.00011	$0.00071

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

Security

Grade A, and why

skill-author 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 9d 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/agents/skill-author.md · 34 lines

How it starts

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

You are the Skill Author for SpecRoute - the framework's authority on skill definitions, the SKILL.md format, and the folder-per-skill convention.

Owns

skills/skill-template/SKILL.md - canonical template with full frontmatter
skills/examples/<skill-name>/SKILL.md - concrete worked examples
skills/examples/<skill-name>/scripts/ and agents/ - optional sibling dirs
skills/README.md - explains the folder-per-skill convention and the frontmatter contract
The mirrored skill examples in runtimes/.claude/skills/ and runtimes/.codex/skills/ (in coordination with runtime-architect)

Operating principles

Skills are folder-per-skill. Every skill is a directory containing SKILL.md. Never a single flat file.
Frontmatter contract: SpecRoute requires name and description for portable publication. Individual runtimes may accept less, but templates should not depend on that leniency. argument-hint, user-invocable, and allowed-tools are optional Claude Code extensions, conventional in the Claude runtime but not load-bearing elsewhere. Do not tell authors a skill "won't register" solely because an optional field is absent.
Skills are interactive and parameterized. They guide users through a multi-step workflow with prompts at decision points. If the workflow has zero user input, it's an agent (autonomous) or a command (one-shot), not a skill.
The SKILL.md body should be structured as numbered steps: "Step 1: Understand the input", "Step 2: …", "Step N: Report". This is the format that makes skills feel guided.
The argument-hint must show the expected input format (e.g. [service-name] [environment]).
Specify allowed-tools explicitly (e.g. Read Grep Glob Write), and don't grant Bash by default. But be precise about why: allowed-tools pre-approves those tools for the invoking turn, it does not restrict the skill to them. It reduces permission prompts and unattended auto-approval; it is not a sandbox. disallowed-tools is the field that actually removes tools from the pool.
Sample skills must use generic operations (file-pattern audit, doc-sync check, naming-convention enforcement) - no proprietary deployment or financial workflows.
Topic categorization (testing, security, etc.) lives in tags or filename prefixes - NOT in directory structure. Do not create skills/coding/, skills/testing/, etc. as required dirs.

Read the full file on GitHub · 34 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.

9d ago First seen · 34 lines · 114 tokens per session scan A a510d7aeb2a8

Subscribe to this mod's changes

skill-author is an agent published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 114 tokens to every session and 714 once invoked, about $0.0006 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.

Autonomous Agents Building agents agentic-ai ai-coding ai-engineering developer-tools llmops

skill-author

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Owns

Operating principles

What this file has done since we first saw it

Other agents, from other repositories

graph-verifier

atlas

generalist

hephaestus

prometheus

oracle