technical-writing

technical-writing is a skill for Claude Code, Codex from i9wa4/dotfiles. It costs 79 tokens per session (500 once invoked), scanned A, original, MIT.

A collection of guidance for reviewing and improving technical writing, including English and Japanese text. It covers terminology, clarity, rhythm, translation, and checks for generic or unclear prose.

In plain words
What is it for?
Use it to edit documentation, check terminology, improve English prose, translate English into Japanese, or review Japanese technical writing.
Why use it?
It helps make technical text easier to understand while preserving its original meaning, names, commands, links, and other exact details.

Skill for Claude CodeCodex

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

Good fit Use it to edit documentation, check terminology, improve English prose, translate English into Japanese, or review Japanese technical writing.

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

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/i9wa4/dotfiles/technical-writing/github.svg)](https://agentmods.dev/skills/i9wa4/dotfiles/technical-writing)
Your own site
<a href="https://agentmods.dev/skills/i9wa4/dotfiles/technical-writing"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/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/i9wa4/dotfiles/technical-writing"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/technical-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 500 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.00079 $0.00500
Opus 5.5 $0.00032 $0.00200
Sonnet 5.5 $0.00016 $0.00100
Haiku 4.5 $0.00008 $0.00050

Measured 2mo ago against content hash d4a095eac930, 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 2mo 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.

skills/technical-writing/SKILL.md · 55 lines

What it actually says

Technical Writing

Owns meaning-preserving editing, translation, terminology, rhythm, and QA.

1. Workflow

  1. Identify surface: English, Japanese, translation, skill text, or QA.
  2. Preserve meaning. Do not rewrite commands, identifiers, product names, paths, code, links, versions, or APIs for style.
  3. Keep glossary/terminology polish here when meanings are stable; use clarify-concepts first when they are not.
  4. For generic/AI-like prose, read Prose Review.
  5. For English checks, read Vale And Harper.
  6. For English-to-Japanese, clean English first, then read English-to-Japanese Workflow and Japanese Writing Style.
  7. For Japanese editorial review, read Japanese Writing Style.
  8. For flat explanatory prose, read Cognitive Rhythm. Build rhythm from source material.
  9. Apply only clarity changes; preserve facts and intent.

2. Boundaries

Issue 225/226 boundaries: no automation, model/cost/privacy, external-sharing approval, derivative publication approval, or chunking.

Do not add direct polished-Japanese drafting from scratch. Repair English first, then translate or QA Japanese.

3. References

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. 2mo ago First seen · 55 lines · 79 tokens per session scan A d4a095eac930

Subscribe to this mod's changes

technical-writing is a skill published in the GitHub repository i9wa4/dotfiles (12 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 500 once invoked, about $0.0003 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

sync-translated-docs

Keep a document and its translated counterpart (README.md and READMEJP.md, docs in two languages) saying the same thing. Use whenever you edit one file of a translated pair, and when asked to check or merge the differences between them. Does not apply to a document that has no counterpart -- a repository with only a…

aiya000/dotfiles · 85 tokens

forensic-transcript-translator

A multi-stage workflow for translating a long English earnings-call transcript into Traditional Chinese used in Taiwan. It records the transcript structure and uses separate checks to compare the original and translation for missing or altered content.

fredchu/claude-dotfiles · 234 tokens

taiwan-earnings-translator

A Traditional Chinese translator for complete U.S. stock earnings-call transcripts, including transcripts supplied as text or English PDFs. Earnings calls are company presentations and question sessions about financial results.

fredchu/claude-dotfiles · 153 tokens

validate__japanese

A Japanese-language review for Markdown documents, such as READMEs, manuals, and blog drafts. It checks writing style, spacing, line breaks, and links to real code symbols.

shunsock/dotfiles · 200 tokens

edit-site

Plans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA Power Pages sites created from Microsoft templates or manually in Design Studio. Use for requests involving pages, localized content, navigation, assets, snippets, site markers, Liquid/web templates, page layouts, or styling.…

microsoft/power-platform-skills · 104 tokens

asc-subscription-localization

Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.

rorkai/app-store-connect-cli-skills · 60 tokens