absolute-docs

A documentation workflow based on Diátaxis, a method that separates tutorials, how-to guides, reference material, and explanations by reader need. It writes or audits developer documentation after checking the project’s actual code and documentation setup.

In plain words
What is it for?
Use it to create, improve, or review READMEs, contribution guides, architecture decisions, tutorials, how-to guides, and developer reference pages.
Why use it?
It prevents documentation from mixing different purposes or describing behavior that the code does not support. It also requires an outline to be approved before a full document is written.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/maddhruv/absolute/absolute-docs
Any agent
npx skills add maddhruv/absolute --skill absolute-docs
Clone the repo
git clone --depth 1 https://github.com/maddhruv/absolute

Made for: Claude Code, Codex.

Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00102 $0.03769
Opus 5 $0.00051 $0.01885
Sonnet 5 $0.00020 $0.00754
Haiku 4.5 $0.00010 $0.00377

Measured yesterday against content hash fbf62766c887, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

absolute-docs 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 yesterday.

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.

skills/absolute-docs/SKILL.md · 346 lines

How it starts

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

Start your first response with the 📚 emoji.

Absolute Documentations: Diátaxis-Driven Documentation

Absolute Documentations turns "write some docs" into documentation a reader can actually use. Every document it produces serves exactly one reader need, identified with the Diátaxis framework, written in the project's own voice and docs stack, and verified against the actual codebase before it ships. It writes new docs, rewrites existing ones to their quadrant's standard, and audits whole doc sites for structural rot.

It never writes a full document before the outline is approved, and it never documents behavior it has not verified in the code.


The Diátaxis Compass

Every piece of documentation answers exactly one kind of reader need. Classify before writing — a page that mixes quadrants serves nobody.

Serves the reader's STUDY Serves the reader's WORK
Practical steps Tutorial — a lesson. Guides a newcomer through a guaranteed-success experience. How-to guide — a recipe. Helps a competent user accomplish a specific goal.
Theoretical knowledge Explanation — a discussion. Deepens understanding of a topic, gives context and reasons. Reference — a dictionary. States facts about the machinery, completely and neutrally.

To classify, ask two questions:

  1. Is the reader studying (acquiring skill) or working (applying skill)?
  2. Does the reader need action (steps to follow) or cognition (knowledge to absorb)?
Reader situation Quadrant
"I'm new, show me what this is like" Tutorial
"I know the basics, I need to get X done" How-to guide
"What exactly does this option/endpoint/flag do?" Reference
"Why does it work this way? What's the bigger picture?" Explanation

The cardinal sin is mixing. A tutorial that stops to explain architecture loses the learner. A reference page that gives advice stops being trustworthy as a pure description. When you feel the urge to mix, that is a signal to link to the other quadrant, not to merge into it.

Read the full file on GitHub · 346 lines

Files

What ships with it

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

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. yesterday First seen · 346 lines · 102 tokens per session scan A fbf62766c887

Subscribe to this mod's changes

absolute-docs is a skill published in the GitHub repository maddhruv/absolute (208 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 3,769 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

openspec-onboard

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

fengshao1227/ccg-workflow · 26 tokens

code-to-content

Use when transforming a codebase into developer content. Activates for: Blog posts, tutorials, or technical documentation about code README, changelog, release notes, or API docs generation Twitter/X threads, LinkedIn posts about technical work Conference talk proposals (CFP) or newsletter content Build-in-public…

arome3/code-to-content · 109 tokens

pitchdocs

Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.

littlebearapps/pitchdocs · 58 tokens

documentation

Technical writing, API docs, and documentation best practices.

miles990/claude-software-skills · 12 tokens

diataxis-docs-framework

Enterprise technical documentation best practices, patterns, and frameworks for developer and partner adoption. Covers content architecture (Diataxis four quadrants), 14 content types (tutorials, how-to guides, API reference, SDK docs, migration guides, changelogs, runbooks, integration guides, troubleshooting…

anivar/developer-docs-framework · 259 tokens

offers

When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,'…

coreyhaines31/marketingskills · 233 tokens