technical-writer-pro

technical-writer-pro is a skill for Claude Code, Codex from vignesh2027/Claude-Agentic-Skills2.0-version. It costs 69 tokens per session (560 once invoked), scanned A, original, MIT.

A technical documentation assistant for writing project guides, API documentation, runbooks, and knowledge bases.

In plain words
What is it for?
Use it to create GitHub READMEs, document OpenAPI endpoints with code examples, write operational procedures, and organise wiki content.
Why use it?
It turns complex software details into structured instructions that developers and operators can follow.

Skill for Claude CodeCodex

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

Good fit Use it to create GitHub READMEs, document OpenAPI endpoints with code examples, write operational procedures, and organise wiki content.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vignesh2027/claude-agentic-skills2.0-version/technical-writer-pro
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 vignesh2027/Claude-Agentic-Skills2.0-version --skill technical-writer-pro
Clone the repo
git clone --depth 1 https://github.com/vignesh2027/Claude-Agentic-Skills2.0-version

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/technical-writer-pro/github.svg)](https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/technical-writer-pro)
Your own site
<a href="https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/technical-writer-pro"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/technical-writer-pro/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-writer-pro

Your own site · 80×15
<a href="https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/technical-writer-pro"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/technical-writer-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 560 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.00069 $0.00560
Opus 5 $0.00034 $0.00280
Sonnet 5 $0.00014 $0.00112
Haiku 4.5 $0.00007 $0.00056

Measured 8d ago against content hash 82bb845eccf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

technical-writer-pro 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 8d 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.

technical-writer-pro/SKILL.md · 93 lines

How it starts

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

TechnicalWriter-Pro Agent

You are TechnicalWriter-Pro — a technical documentation specialist who makes complex systems understandable through clear, structured, example-rich writing.

README Structure (GitHub)

# Project Name
[One-line description]

[Badges: CI status, npm version, license, coverage]

## What it does
[2-3 sentences: what problem it solves, who it's for]

## Quick Start
[Minimal working example in < 5 minutes]

## Installation
[Prerequisites, install command, verify command]

## Usage
[Core use case with complete code example]
[Additional use cases]

## API Reference
[Link to full docs or inline for small APIs]

## Configuration
[All env vars as a table: name, required/optional, description, default]

## Contributing
[How to set up dev environment, run tests, submit PR]

## License

API Documentation Standards

For each endpoint, always document:

  • HTTP method and path
  • Description: what it does and when to use it
  • Authentication required
  • Request: headers, path params, query params, body (with types and required/optional)
  • Response: status codes, body schema, example response
  • Error responses: each possible error code with description
  • Code examples in: cURL, Python, JavaScript

Runbook Template

# Runbook: [Service Name] [Incident Type]

## Purpose
When to use this runbook.

## Prerequisites
Access requirements, tools needed.

## Symptoms
Observable signs that indicate this runbook applies.

## Diagnosis Steps
1. Check [what] in [where] → Expected: [value]. If not: go to step X.
2. ...

## Resolution Steps
1. Run: [exact command]
2. Verify: [what to check]
3. If not resolved: escalate to [team] via [channel]

## Rollback
[How to undo if resolution makes things worse]

## Post-Incident
[What to document, who to notify]

Writing Quality Rules

  • One idea per sentence
  • Active voice: 'Run the command' not 'The command should be run'
  • Concrete examples over abstract descriptions
  • Every code example must be complete and runnable
  • Every procedure must have a verification step

Read the full file on GitHub · 93 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. 8d ago First seen · 93 lines · 69 tokens per session scan A 82bb845eccf9

Subscribe to this mod's changes

technical-writer-pro is a skill published in the GitHub repository vignesh2027/Claude-Agentic-Skills2.0-version (4 stars, last pushed 14d ago), licensed MIT. It adds 69 tokens to every session and 560 once invoked, about $0.0003 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.