technical-writing-workflow

technical-writing-workflow is a skill for Codex from tokenbender/agent-guides. It costs 97 tokens per session (1,113 once invoked), scanned A, original, Apache-2.0.

A structured process for creating and checking technical writing, from the initial reader need through research, drafting, revision, and publication. It applies to documents such as reports, textbooks, READMEs, papers, and research notes.

In plain words
What is it for?
It helps define scope and readers, organize research, build outlines, resolve conflicting sources, draft explanations, and perform final fact and structure checks.
Why use it?
It prevents important claims from being vague, unsupported, or outside their evidence. It also helps keep terminology, structure, and cross-references consistent.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit It helps define scope and readers, organize research, build outlines, resolve conflicting sources, draft explanations, and perform final fact and structure checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tokenbender/agent-guides/technical-writing-workflow
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 tokenbender/agent-guides --skill technical-writing-workflow
Clone the repo
git clone --depth 1 https://github.com/tokenbender/agent-guides

Made for: Codex.

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-workflow

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tokenbender/agent-guides/technical-writing-workflow"><img src="https://agentmods.dev/badge/skills/tokenbender/agent-guides/technical-writing-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,113 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00097 $0.01113
Opus 5.5 $0.00039 $0.00445
Sonnet 5.5 $0.00019 $0.00223
Haiku 4.5 $0.00010 $0.00111

Measured 1mo ago against content hash 3aef810accf3, 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-workflow 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.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/anti_llm_pattern_audit.py, scripts/citation_audit.py, scripts/heading_audit.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

claude-skills/technical-writing-workflow/SKILL.md · 188 lines

How it starts

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

Technical writing workflow

Use this skill when the user asks to write, rewrite, improve, audit, explain, teach, document, or publish technical material. Treat it as a workflow with checks, not as a prose vibe.

Core rule

Open the subject up without making it shallow.

Every important explanation must name:

  1. the object or behavior being described
  2. the method, mechanism, or actor that changes it
  3. the evidence that supports the claim
  4. the boundary the claim is allowed to cover

Serial before parallel

Serialize meaning. Parallelize collection.

Do these serially before drafting:

  1. Define the reader and use case.
  2. Define scope and exclusions.
  3. Build the ontology table.
  4. Decide the argument order.
  5. Write chapter or section contracts.
  6. Resolve source contradictions.

Then parallelize:

  • source packets
  • paper cards
  • glossary entries
  • examples
  • diagrams
  • exercises
  • tables
  • reference checks
  • local fact checks
  • counterexamples and failure modes

Return to serial work for:

  • synthesis
  • final claim strength
  • voice and terminology
  • cross-references
  • final layout or render inspection

The workflow

1. Intake

Write a short brief before drafting:

  • audience
  • task the reader should perform after reading
  • source surface
  • deliverable format
  • deadline or depth target
  • claim-risk level

If any of these are unknown, make a conservative assumption and state it briefly.

2. Source audit

Separate sources into evidence classes:

  • primary paper or official documentation
  • benchmark or measurement artifact
  • code or reproducibility artifact
  • technical blog or explainer
  • social post or pointer
  • local note or capture

Do not let a pointer carry a claim that belongs to a paper, code artifact, or measurement.

3. Ontology table

For each major topic, create this table before drafting:

Topic:
Object:
Method:
Resource or behavior changed:
Evidence:
Boundary:
Common beginner mistake:
Best example:

This table is the backbone. If it is confused, the prose will be confused.

Read the full file on GitHub · 188 lines

Files

What ships with it

5 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. 1mo ago First seen · 188 lines · 97 tokens per session scan A 3aef810accf3

Subscribe to this mod's changes

technical-writing-workflow is a skill published in the GitHub repository tokenbender/agent-guides (367 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,113 once invoked, about $0.0004 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-08-30.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens