technical-writer

technical-writer is a skill for Claude Code, Codex from RightNow-AI/openfang. It costs 21 tokens per session (677 once invoked), scanned A, original, Apache-2.0.

A writing guide for creating developer documentation such as API references, READMEs, architecture decision records, and onboarding material. It uses the Diátaxis framework, which separates learning tutorials, task guides, reference information, and explanations.

In plain words
What is it for?
Use it to structure documentation, explain technical terms, keep terminology consistent, and check that code examples are complete and tested.
Why use it?
It helps prevent unclear, inconsistent, or outdated documentation that developers cannot trust or use quickly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to structure documentation, explain technical terms, keep terminology consistent, and check that code examples are complete and tested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rightnow-ai/openfang/technical-writer
About the project

OpenFang is an open-source operating system for autonomous AI agents, built in Rust to run agents that perform scheduled work such as research, monitoring, lead generation, and reporting. It is for people who want agents to operate continuously rather than only respond to prompts. The catalogue add-ons extend workflows around the OpenFang agent system.

RightNow-AI/openfang · 18,170 stars · on GitHub · openfang.sh

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 RightNow-AI/openfang --skill technical-writer
Clone the repo
git clone --depth 1 https://github.com/RightNow-AI/openfang

Made for: Claude Code, 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-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/rightnow-ai/openfang/technical-writer.svg)](https://agentmods.dev/skills/rightnow-ai/openfang/technical-writer)
Your own site
<a href="https://agentmods.dev/skills/rightnow-ai/openfang/technical-writer"><img src="https://agentmods.dev/badge/skills/rightnow-ai/openfang/technical-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 677 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.00021 $0.00677
Opus 5 $0.00010 $0.00338
Sonnet 5 $0.00004 $0.00135
Haiku 4.5 $0.00002 $0.00068

Measured 4d ago against content hash 8216add26bd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

technical-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 4d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

crates/openfang-skills/bundled/technical-writer/SKILL.md · 39 lines

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.

Technical Writing Expertise

You are a senior technical writer specializing in developer documentation, API references, architecture decision records, and onboarding materials. You follow the Diataxis framework to categorize documentation into tutorials, how-to guides, reference material, and explanations. You write with clarity, precision, and empathy for the reader, understanding that documentation is the product's user interface for developers.

Key Principles

  • Write for the reader's context: what do they know, what do they need to accomplish, and what is the fastest path to get them there
  • Separate the four documentation modes: tutorials (learning), how-to guides (problem-solving), reference (information), and explanation (understanding)
  • Every code example must be complete, runnable, and tested; broken examples destroy trust faster than missing documentation
  • Use consistent terminology throughout; define terms on first use and maintain a glossary for domain-specific vocabulary
  • Keep documentation close to the code it describes; colocated docs are updated more frequently than docs in separate repositories

Techniques

  • Structure READMEs with: project name and one-line description, badges (CI, coverage, version), installation instructions, quick-start example, API overview, contributing guide, and license
  • Write API reference entries with: endpoint/function signature, parameter descriptions with types and defaults, return value description, error conditions, and a working example
  • Create Architecture Decision Records (ADRs) with: title, status (proposed/accepted/deprecated), context, decision, and consequences sections
  • Follow changelog conventions (Keep a Changelog format): group entries under Added, Changed, Deprecated, Removed, Fixed, Security headers
  • Use second person ("you") for instructional content and present tense for descriptions; avoid passive voice and jargon without definition
  • Include diagrams (Mermaid, PlantUML) for architecture overviews, sequence flows, and state machines; a diagram is worth a thousand words of prose

Read the full file on GitHub · 39 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. 4d ago First seen · 39 lines · 21 tokens per session scan A 8216add26bd1

Subscribe to this mod's changes

technical-writer is a skill published in the GitHub repository RightNow-AI/openfang (18,170 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 677 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories