Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. 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/loerei/chronicle-mcp/main/.agents/skills/write-a-skill/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/write-a-skill)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/write-a-skill"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/write-a-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.
<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/write-a-skill"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/write-a-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00019 | $0.00759 |
| Opus 5.5 | $0.00008 | $0.00304 |
| Sonnet 5.5 | $0.00004 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
write-a-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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a Skill
Create and distribute agent skills with proper structure, progressive disclosure, and execution predictability.
Directives
- Description Rule ("Use When Only"): MUST use format
Use when [specific triggers]in 10–14 words. NEVER summarize internal features (What), explain benefits (Why), or include slash commands. - Plain English: State direct instructions; NEVER use self-important titles or marketing fluff (
orchestrate,robust,comprehensive pipeline). - Progressive Disclosure: Keep
SKILL.mdlean. Disclose heavy tables, checklists, or domain guides into sub-documents (REFERENCE.mdor<DOMAIN>.md) per HEURISTICS.md. - Mermaid Decision Trees: Use flowcharts ONLY for workflows with 3+ branching paths or error recovery loops. Do NOT use for flat linear steps.
- Mindset Over Micro-Format: Directives MUST state the thinking principle the agent should adopt. Do NOT prescribe specific response structures (e.g. "step 1: flat bullet list, step 2: separate paragraph for caveats"). Structural micro-rules get replayed literally regardless of context. This applies to response-formatting rules, not operational workflow steps (spawning subagents, calling MCP tools, reading files) which legitimately require precise sequencing. See REFERENCE.md § Case Study for a before/after example.
- Prerequisite:
write-for-ai: MUST readwrite-for-ai/SKILL.mdbefore drafting or editing any skill. Skill content is AI-facing text; all prose quality rules apply.
| Bad (Bloated Fluff) | Good (Plain English) |
|---|---|
Comprehensive Execution Architecture |
Workflow |
Verify optimal state convergence across targets |
Verify all tests pass |
Forensic behavioral telemetry capture on anomalies |
Save error logs to a file on failure |
SKILL.md Template
---
name: <skill-name>
description: Use when [specific triggers].
---
# <Skill Title>
<1-sentence description of purpose and produced artifacts>.
## Directives
1. **<Rule 1>**: MUST/NEVER [Actionable constraint].
---
## Template / Output Format
<Clean markdown template or code block with placeholders>
---
## Workflow
1. <Step 1: Inspect/Audit>
2. <Step 2: Execute/Draft>
3. <Step 3: Verify & Sync via agents distribute>
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.
- 1mo ago Changed · +2 lines a84da134d040
- 1mo ago First seen · 74 lines · 19 tokens per session scan A e901131ce6de
write-a-skill is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 759 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…