Borrowing it
Nothing to install: this file belongs to calf-ai/calfkit-sdk. 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/calf-ai/calfkit-sdk/main/.agents/skills/diataxis-docs-writer/SKILL.mdgit clone --depth 1 https://github.com/calf-ai/calfkit-sdkWrote 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/calf-ai/calfkit-sdk/diataxis-docs-writer)<a href="https://agentmods.dev/skills/calf-ai/calfkit-sdk/diataxis-docs-writer"><img src="https://agentmods.dev/badge/skills/calf-ai/calfkit-sdk/diataxis-docs-writer/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/calf-ai/calfkit-sdk/diataxis-docs-writer"><img src="https://agentmods.dev/badge/skills/calf-ai/calfkit-sdk/diataxis-docs-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector 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.00218 | $0.02700 |
| Opus 5 | $0.00109 | $0.01350 |
| Sonnet 5 | $0.00044 | $0.00540 |
| Haiku 4.5 | $0.00022 | $0.00270 |
Grade A, and why
diataxis-docs-writer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- diataxis-docs-writer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diátaxis documentation
Good documentation is not one thing. It is four things, each answering a different question a user has, each written in a different way. Most bad documentation is bad not because the writing is poor but because two of these four got mixed together — a tutorial clogged with explanation, a reference page that wanders into opinion, a "how-to" that's really a half-finished lesson.
Your job with this skill is to keep them separate. Decide which kind you're writing, commit to its discipline, and link out to the others rather than bleeding into them.
Diátaxis is a guide, not a plan. You don't start by building four empty sections and filling them in. You write each piece well, in its proper mode, and good structure emerges from that.
The two axes (why there are exactly four)
Every craft involves two distinctions. Documentation must serve both sides of each:
- Action ↔ Cognition — is the content about doing (practical steps) or about knowing (theoretical facts and ideas)?
- Acquisition ↔ Application — does it serve the user at study (learning the craft) or at work (applying it to get something done)?
Cross those two axes and you get four quadrants — the four documentation types. There can't be three or five; the two axes define the whole territory.
Step 1 — Classify before you write (the compass)
Before writing a sentence, decide which type you're producing. Ask just two questions:
- Action or cognition? (Is this about what the user does, or what they know?)
- Acquisition or application? (Is the user studying, or working?)
| If the content informs… | …and serves the user's… | …then it is a… | It answers | Its form is |
|---|---|---|---|---|
| action | acquisition (study) | Tutorial | "Can you teach me to…?" | a lesson |
| action | application (work) | How-to guide | "How do I…?" | a recipe |
| cognition | application (work) | Reference | "What is…? / What are the options?" | dry description |
| cognition | acquisition (study) | Explanation | "Why…? / Tell me about…" | a discursive article |
What ships with it
7 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 · 196 lines · 218 tokens per session scan A 67190e949979
diataxis-docs-writer is a skill published in the GitHub repository calf-ai/calfkit-sdk (146 stars, last pushed 9d ago), licensed Apache-2.0. It adds 218 tokens to every session and 2,700 once invoked, about $0.0011 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-30.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
junjo-evaluation
Turn a developer's product-quality objective into a complete Junjo Studio-backed evaluation workflow. Use when a coding agent needs to establish a baseline, design or generate typed cases, run or resume application-owned Node, Workflow, or Agent targets, inspect outcomes and exact trace evidence, compare a candidate…
junjo-openai-agents
Add Junjo's optional OpenAI Agents SDK integration to an application. Use when a coding agent needs to install junjo[openai-agents], expose a native Junjo Workflow or Agent as an OpenAI function tool, send standard OpenAI Agent and nested Junjo spans through one application-owned OpenTelemetry provider, declare an…
writing-workspace-jobs
Author FSM workspace jobs. Use when creating, editing, or debugging jobs, signals, or FSM workflows in workspace.yml.
workspace-api
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL. Use when the user asks to create, edit, delete, or list workspaces, spaces, projects, or environments; add or patch signals / agents / jobs / memory / skills; convert a workspace.yml into a live workspace; wire up triggers…
core
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple…