technical-writing

technical-writing is a skill for Claude Code from saajunaid/caddis-plugin. It costs 34 tokens per session (1,961 once invoked), scanned A, original, MIT.

A set of practices for writing developer documentation, including READMEs, API references, architecture documents, runbooks, and guides.

In plain words
What is it for?
Writing or reviewing documentation, creating onboarding material, and setting documentation standards.
Why use it?
It helps make technical information easier to follow and more consistent for developers who need to use, operate, or maintain a system.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter.

Good fit Writing or reviewing documentation, creating onboarding material, and setting documentation standards.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/saajunaid/caddis-plugin/technical-writing
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.

Any agent
npx skills add saajunaid/caddis-plugin --skill technical-writing
Clone the repo
git clone --depth 1 https://github.com/saajunaid/caddis-plugin

Made for: Claude Code.

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

agentmods badge for technical-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/technical-writing/github.svg)](https://agentmods.dev/skills/saajunaid/caddis-plugin/technical-writing)
Your own site
<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/technical-writing"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/technical-writing/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.

agentmods 80×15 button for technical-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/technical-writing"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/technical-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,961 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00034 $0.01961
Opus 5.5 $0.00014 $0.00784
Sonnet 5.5 $0.00007 $0.00392
Haiku 4.5 $0.00003 $0.00196

Measured 19d ago against content hash 93224ff840bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

technical-writing 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 19d 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.

.github/skills/docs/technical-writing/SKILL.md · 287 lines

How it starts

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

Technical Writing Skill

Good documentation is the difference between a project that scales and one that stalls. Write for the reader who has zero context.

1. When to Apply This Skill

Trigger conditions:

  • Writing or updating a README
  • Creating API documentation
  • Writing architecture decision records (ADRs)
  • Building runbooks or incident playbooks
  • Creating onboarding/developer guides
  • Reviewing documentation for clarity

2. Document Types and Templates

Document Provenance Frontmatter

All descriptive Markdown docs must follow .github/instructions/document-frontmatter.instructions.md.

  • New docs: include Original Author, Creation Date, and Creating Model in YAML frontmatter.
  • Updated docs: preserve those original fields and add or update Last Author, Last Updated, and Last Model Used.
  • Use full ISO 8601 UTC timestamps for Creation Date and Last Updated values.
  • Merge these fields into existing frontmatter instead of replacing document-specific metadata.

README Structure

Every project README follows this order:

# Project Name
One-sentence description of what this does and who it's for.

## Quick Start
Minimum steps to run the project locally (≤5 commands).

## Prerequisites
- Runtime versions (Python 3.12+, Node 22+)
- Required tools (Docker, pnpm)
- Required accounts/access

## Installation
Step-by-step setup with copy-pasteable commands.

## Usage
Common tasks with examples.

## Architecture
Brief overview with a diagram (link to detailed docs).

## Contributing
How to submit changes, run tests, and follow conventions.

## License

Rules:

  • Quick Start must work on a fresh machine in under 5 minutes
  • Every command must be copy-pasteable (no <placeholder> without explanation)
  • Test the README by following it literally on a clean environment

Architecture Decision Record (ADR)

# ADR-{NNN}: {Decision Title}

## Status
Accepted | Superseded by ADR-{NNN} | Deprecated

## Context
What problem are we solving? What constraints exist?

## Decision
What did we decide and why?

## Alternatives Considered
| Option | Pros | Cons | Why Not |
|--------|------|------|---------|

## Consequences
What changes as a result? What new constraints are introduced?

Read the full file on GitHub · 287 lines

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. 19d ago Changed · -7 tokens per session 93224ff840bf
  2. 1mo ago First seen · 287 lines · 41 tokens per session scan A 14da28a68be6

Subscribe to this mod's changes

technical-writing is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,961 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.

Related

Other skills, from other repositories

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…

eigent-ai/eigent · 168 tokens

pptx

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying…

eigent-ai/eigent · 152 tokens

xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…

eigent-ai/eigent · 201 tokens

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…

eigent-ai/eigent · 92 tokens

document-processor

Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.

vixues/LeAgent · 44 tokens

attendance-signin-sheet

A spreadsheet generator for printable attendance or meeting sign-in sheets. It turns a list of names into rows with columns such as signatures, dates, departments, or employee IDs.

vixues/LeAgent · 51 tokens