Borrowing it
Nothing to install: this file belongs to compozy/kb. 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/compozy/kb/main/.agents/skills/writing-skills/SKILL.mdgit clone --depth 1 https://github.com/compozy/kbWrote 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/compozy/kb/writing-skills)<a href="https://agentmods.dev/skills/compozy/kb/writing-skills"><img src="https://agentmods.dev/badge/skills/compozy/kb/writing-skills/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/compozy/kb/writing-skills"><img src="https://agentmods.dev/badge/skills/compozy/kb/writing-skills.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.00040 | $0.00729 |
| Opus 5.5 | $0.00016 | $0.00292 |
| Sonnet 5.5 | $0.00008 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
writing-skills 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 25d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Skills
A skill supplies task-specific knowledge or a reliable operation the model would otherwise have to rediscover. Optimize for correct outcomes, useful evidence, and low overhead. Identical process on every run is useful only where ordering is part of the contract.
Choose the Scope
- Follow the user's requested outcome and existing authorization. A skill does not add approval steps or override repository policy.
- Keep a rule only when it changes a relevant decision or prevents an evidenced failure. Delete generic advice, duplicated rules, obsolete model assumptions, and rhetorical pressure.
- Keep descriptions short: put the concrete task, trigger, and main scope boundary in the first sentence so truncation preserves when to use the skill. Add exclusions only to resolve likely overlap. Avoid firing on every code edit, every test, or every completion when the procedure is only needed for a narrower problem.
- Distinguish shared guidance from repository-specific policy. Edit shared sources first; preserve local variants when synchronizing. Check whole-directory differences before an installer overwrites a skill.
Create or Revise
- Identify the outcome, owning files, known failure, and existing instructions. Reuse the current conversation's evidence; recollect only missing or stale material.
- Keep the minimum common contract in
SKILL.md; link branch-specific references with a condition and the section needed. Read a complete schema or tightly coupled procedure when its whole contract is necessary, not every reference by default. - State required order only for dependencies, mutations, authorization, or cleanup. Let independent searches batch and let the agent choose routine implementation details.
- Define completion by the requested deliverable and its applicable checks. Reuse evidence for unchanged inputs. Do not add a mandatory report, subagent round, test suite, or confirmation merely because the skill is installed.
- Check changed triggers, links, metadata, and any affected helper behavior. For a small prose edit, summarize this review; for a new skill or broad rewrite, use
references/checklist.md. Fix material failures at their source.
What ships with it
6 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.
- 25d ago First seen · 39 lines · 40 tokens per session scan A 95c651d32579
writing-skills is a skill published in the GitHub repository compozy/kb (112 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 729 once invoked, about $0.0002 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-26.
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…
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…