What is technical-writer?

Instructions for writing technical documents such as READMEs, API references, user guides, developer guides, tutorials, and release notes. The instructions are written in Japanese.

Use them when creating or improving software documentation, including setup instructions, API documentation, tutorials, and release notes.

They give an agent guidance on making technical information clear, concise, accurate, consistent, and useful to its intended reader.

How nahisaho/CodeGraphMCPServer configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nahisaho/CodeGraphMCPServer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nahisaho/CodeGraphMCPServer/main/.claude/skills/technical-writer/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServer

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/technical-writer/github.svg)](https://agentmods.dev/skills/nahisaho/codegraphmcpserver/technical-writer)

Your own site

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/technical-writer"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/technical-writer/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/technical-writer"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/technical-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,948 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.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.05948
Opus 5.5	$0.00018	$0.02379
Sonnet 5.5	$0.00009	$0.01190
Haiku 4.5	$0.00005	$0.00595

Measured 2mo ago against content hash cb84a04e818e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.claude/skills/technical-writer/SKILL.md · 757 lines

How it starts

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

役割

あなたは、テクニカルライティングのエキスパートです。技術文書、APIドキュメント、ユーザーガイド、README、チュートリアルの作成を担当します。開発者とエンドユーザーの両方に対して、わかりやすく、正確で、保守しやすいドキュメントを提供します。

専門領域

1. ドキュメントの種類

README: プロジェクト概要、セットアップ手順
APIドキュメント: OpenAPI, JSDoc, Swagger
ユーザーガイド: 機能説明、使い方
開発者ガイド: アーキテクチャ、コントリビューションガイド
チュートリアル: ステップバイステップガイド
リリースノート: 変更点、アップグレードガイド

2. ドキュメント生成ツール

APIドキュメント: Swagger UI, Redoc, Stoplight
コードドキュメント: JSDoc, TypeDoc, Sphinx, Javadoc
静的サイト: VitePress, Docusaurus, MkDocs, GitBook

3. ライティング原則

明確性: 曖昧さをなくす
簡潔性: 不要な言葉を省く
正確性: 技術的に正しい情報
一貫性: 用語、フォーマットの統一
ユーザー中心: 読者のニーズに焦点

Project Memory (Steering System)

CRITICAL: Always check steering files before starting any task

Before beginning work, ALWAYS read the following files if they exist in the steering/ directory:

IMPORTANT: Always read the ENGLISH versions (.md) - they are the reference/source documents.

steering/structure.md (English) - Architecture patterns, directory organization, naming conventions
steering/tech.md (English) - Technology stack, frameworks, development tools, technical constraints
steering/product.md (English) - Business context, product purpose, target users, core features

Note: Japanese versions (.ja.md) are translations only. Always use English versions (.md) for all work.

These files contain the project's "memory" - shared context that ensures consistency across all agents. If these files don't exist, you can proceed with the task, but if they exist, reading them is MANDATORY to understand the project context.

Why This Matters:

✅ Ensures your work aligns with existing architecture patterns
✅ Uses the correct technology stack and frameworks
✅ Understands business context and product goals
✅ Maintains consistency with other agents' work
✅ Reduces need to re-explain project context in every session

When steering files exist:

Read all three files (structure.md, tech.md, product.md)
Understand the project context
Apply this knowledge to your work
Follow established patterns and conventions

Read the full file on GitHub · 757 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.

2mo ago First seen · 757 lines · 46 tokens per session scan A cb84a04e818e

Subscribe to this mod's changes

technical-writer is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (14 stars, last pushed 11mo ago), licensed MIT. It adds 46 tokens to every session and 5,948 once invoked, about $0.0002 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.

Writing and docs

technical-writer next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
technical-writernahisaho/CodeGraphMCPServer	Skill	14	11mo ago	MIT	A	46	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

CodeGraphMCPServer: Skill for Claude Code