create-skill

create-skill is a skill for Claude Code, Codex from XMZF-vAI/clerkbox. It costs 56 tokens per session (3,535 once invoked), scanned A, original, Apache-2.0.

A guide for creating Agent Skills in ClerkBox, where a skill is a set of instructions that teaches an agent how to handle a specialised task. It covers skill files, task matching, and how skills can lead to follow-up skills.

In plain words
What is it for?
Use it to plan and write new skills, choose their routing details, and structure their `SKILL.md` files in the `.clerkbox/skills` directory.
Why use it?
It helps turn repeated team procedures into skills that agents can discover and load when relevant. It also explains how descriptions and trigger keywords affect whether a skill is selected.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit Use it to plan and write new skills, choose their routing details, and structure their SKILL.md files in the .clerkbox/skills directory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xmzf-vai/clerkbox/create-skill
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 XMZF-vAI/clerkbox --skill create-skill
Clone the repo
git clone --depth 1 https://github.com/XMZF-vAI/clerkbox

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/xmzf-vai/clerkbox/create-skill"><img src="https://agentmods.dev/badge/skills/xmzf-vai/clerkbox/create-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,535 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00056 $0.03535
Opus 5 $0.00028 $0.01767
Sonnet 5 $0.00011 $0.00707
Haiku 4.5 $0.00006 $0.00353

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

Security

Grade A, and why

create-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 8d 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.

resources/preset-skills/create-skill/SKILL.md · 379 lines

How it starts

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

Creating Skills in ClerkBox

This skill guides you through creating effective Agent Skills for ClerkBox. Skills are markdown files that teach the agent how to perform specific tasks: reviewing PRs using team standards, generating commit messages in a preferred format, querying database schemas, or any specialized workflow.

How ClerkBox Uses Skills (read this first)

ClerkBox uses progressive loading: the system prompt only contains a lightweight skill index (slug, name, description, trigger_keywords, path). The agent reads a skill's SKILL.md via read_file only when it matches the current task. Therefore:

  1. description + trigger_keywords are the routing signal — they decide whether your skill ever gets read. Make them specific.
  2. The user can also activate a skill explicitly by typing /<skill-slug> at the start of a message.
  3. chains_to can chain a skill to successor skills (advisory) — after the main action completes, the agent may load a listed successor whose description matches the new state.

Before You Begin: Gather Requirements

Before creating a skill, gather essential information from the user (ask conversationally, one short round):

  1. Purpose and scope: What specific task or workflow should this skill help with?
  2. Trigger scenarios: When should the agent automatically apply this skill?
  3. Key domain knowledge: What specialized information does the agent need that it wouldn't already know?
  4. Output format preferences: Are there specific templates, formats, or styles required?
  5. Existing patterns: Are there existing examples or conventions to follow?

Inferring from Context

If you have previous conversation context, infer the skill from what was discussed. You can create skills based on workflows, patterns, or domain knowledge that emerged in the conversation.


Skill File Structure

Directory Layout

Skills are stored as directories containing a SKILL.md file:

skill-name/
├── SKILL.md              # Required - main instructions
├── reference.md          # Optional - detailed documentation
├── examples.md           # Optional - usage examples
└── scripts/              # Optional - utility scripts
    ├── validate.py
    └── helper.sh

Read the full file on GitHub · 379 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 379 lines · 56 tokens per session scan A 716367e1218b

Subscribe to this mod's changes

create-skill is a skill published in the GitHub repository XMZF-vAI/clerkbox (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 3,535 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

add-community-extension

Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…

github/spec-kit · 63 tokens

agent-harness-fault-injection

Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.

sickn33/agentic-awesome-skills · 34 tokens

api-rate-limit-handler

Implement bounded, idempotency-aware API throttling, backoff, and retry handling for 429 and transient 5xx responses.

sickn33/agentic-awesome-skills · 32 tokens

agenttrace-session-audit

Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.

sickn33/agentic-awesome-skills · 34 tokens

Developmental Gene Panel Design Workflow

Panel design for DEVELOPING / dynamic systems (embryonic organs, differentiation, regeneration). The target experiment is usually a LATE / terminal stage, but the biology is a trajectory: terminal cell types are end-products of earlier lineage programs. A panel built from the target stage alone resolves terminal…

aristoteleo/PantheonOS · 129 tokens

development-workflow

Detailed development workflow with modular patterns for git, review, testing, and deployment.

athola/claude-night-market · 20 tokens