Borrowing it
Nothing to install: this file belongs to dboeckli/ai-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dboeckli/ai-agent-skills/master/.claude/skills/skill-best-practices/SKILL.mdgit clone --depth 1 https://github.com/dboeckli/ai-agent-skillsWrote 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.
[](https://agentmods.dev/skills/dboeckli/ai-agent-skills/skill-best-practices)<a href="https://agentmods.dev/skills/dboeckli/ai-agent-skills/skill-best-practices"><img src="https://agentmods.dev/badge/skills/dboeckli/ai-agent-skills/skill-best-practices/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.
<a href="https://agentmods.dev/skills/dboeckli/ai-agent-skills/skill-best-practices"><img src="https://agentmods.dev/badge/skills/dboeckli/ai-agent-skills/skill-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.03280 |
| Opus 5 | $0.00057 | $0.01640 |
| Sonnet 5 | $0.00023 | $0.00656 |
| Haiku 4.5 | $0.00011 | $0.00328 |
Grade A, and why
skill-best-practices 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Best Practices
Reference: https://resources.anthropic.com/hubfs/The-Complete-Guide-to-Building-Skill-for-Claude.pdf
Instructions
Step 1: Identify your use case category
Determine which type of skill you're building:
- Document & Asset Creation — consistent output (docs, designs, code)
- Workflow Automation — multi-step processes with consistent methodology
- MCP Enhancement — workflow guidance on top of MCP tool access
Define 2–3 concrete use cases before writing anything (see Planning section below).
Step 2: Create the folder and SKILL.md
- Name the folder in kebab-case (e.g.
my-skill-name) - Create exactly
SKILL.md(case-sensitive) inside it - Write YAML frontmatter with
nameanddescription(see Technical requirements)
Step 3: Write the description — this is the most critical part
The description controls when Claude loads your skill. It must include:
- WHAT the skill does
- WHEN to use it (specific trigger phrases)
- Optional: negative triggers ("Do NOT use for...")
See "Writing effective descriptions" for good/bad examples.
Step 4: Write the body instructions
Follow the recommended template: ## Instructions → numbered steps → ## Examples → ## Troubleshooting.
Be specific and actionable. Move detailed docs to references/ and link to them.
Step 5: Update CLAUDE.md and README.md
After creating or modifying any skill in this repository, always update the skill tables in both files:
CLAUDE.md— skill table under "Included Skills" (Trigger column: one-line description of when it fires)README.md— skill table under "Enthaltene Skills" (Beschreibung column: German one-liner)
Both files must stay in sync. This step is mandatory and must not be skipped.
Also invoke the cc-best-practices skill when working on skills in this repository to ensure context and session management follow project standards.
Step 6: Validate YAML and skills CLI compatibility
Run the validation script from the repository root before testing or committing:
What ships with it
2 files 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.
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.
- 10d ago First seen · 457 lines · 114 tokens per session scan A a724766d42f2
skill-best-practices is a skill published in the GitHub repository dboeckli/ai-agent-skills (0 stars, last pushed 16d ago), licensed MIT. It adds 114 tokens to every session and 3,280 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…