Technical Writer
finos/morphir
Assists with writing and maintaining Morphir technical documentation.
[production-grade internal] Generates documentation when you need to explain code — API references, developer guides, READMEs, architecture overviews.
Install Technical Writer
$ npx skills add nagisanzenin/production-grade --skill technical-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nagisanzenin/production-grade technical-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nagisanzenin/production-grade.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/technical-writer .claude/skills/technical-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "technical-writer" agent skill from https://github.com/nagisanzenin/production-grade/tree/main/skills/technical-writer into .claude/skills/technical-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nagisanzenin/production-grade/tree/main/skills/technical-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nagisanzenin/production-grade --skill technical-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nagisanzenin/production-grade technical-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nagisanzenin/production-grade.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/technical-writer .agents/skills/technical-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-writer" agent skill from https://github.com/nagisanzenin/production-grade/tree/main/skills/technical-writer into .agents/skills/technical-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nagisanzenin/production-grade --skill technical-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nagisanzenin/production-grade technical-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nagisanzenin/production-grade.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/technical-writer .cursor/skills/technical-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-writer" agent skill from https://github.com/nagisanzenin/production-grade/tree/main/skills/technical-writer into .cursor/skills/technical-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nagisanzenin/production-grade.git --path skills/technical-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nagisanzenin/production-grade --skill technical-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nagisanzenin/production-grade technical-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nagisanzenin/production-grade.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/technical-writer .gemini/skills/technical-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-writer" agent skill from https://github.com/nagisanzenin/production-grade/tree/main/skills/technical-writer into .gemini/skills/technical-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nagisanzenin/production-grade technical-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nagisanzenin/production-grade --skill technical-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nagisanzenin/production-grade.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/technical-writer .github/skills/technical-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-writer" agent skill from https://github.com/nagisanzenin/production-grade/tree/main/skills/technical-writer into .github/skills/technical-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nagisanzenin/production-grade --skill technical-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nagisanzenin/production-grade technical-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nagisanzenin/production-grade.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/technical-writer .opencode/skills/technical-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-writer" agent skill from https://github.com/nagisanzenin/production-grade/tree/main/skills/technical-writer into .opencode/skills/technical-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
technical-writer- GitHub stars
- 181
- Token cost
- ~3k tokens
- SKILL.md length
- 1,121 words
- Files
- 5
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- None found
At a glance
[production-grade internal] Generates documentation when you need to explain code — API references, developer guides, READMEs, architecture overviews.
- Works in 3 steps: Phase 1: Content Audit (sequential —… → Phases 2-3: API Reference + Developer… → Phase 4: Docusaurus Scaffold (sequential…
- Tasks that involve Technical documentation
- SKILL.md covers Preprocessing, Brownfield Awareness, Engagement Mode and Progress Output, plus 10 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Technical Writer is an agent skill from nagisanzenin/production-grade. [production-grade internal] Generates documentation when you need to explain code — API references, developer guides, READMEs, architecture overviews. Routed via the production-grade orchestrator.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `phases/01-content-audit.md`, `phases/02-api-reference.md` and `phases/03-developer-guides.md`).
It sits in Development, covering Technical documentation and Technical writing. The repository describes itself as: Claude Code Plugin: Fully autonomous production-grade SaaS pipeline — 14 bundled skills, CEO/CTO command-driven, single install.
When your agent uses it
- Tasks that involve Technical documentation
- Tasks that involve Technical writing
Example prompts
- “/technical-writer”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Phase 1: Content Audit (sequential — establishes doc sitemap)
- Phases 2-3: API Reference + Developer Guides (PARALLEL)
- Phase 4: Docusaurus Scaffold (sequential — needs all docs)
What it can do on your machine
Read from SKILL.md and the folder at commit 4b2f13f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Technical Writer loads about 3k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 1,121 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,121 words (~3,001 tokens).
“!cat Claude-Production-Grade-Suite/.protocols/ux-protocol.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/input-validation.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/tool-efficiency.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/visual-identity.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/freshness-protocol.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/receipt-protocol.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/boundary-safety.md 2>/dev/null || true !cat Claude-Production-Grade-Suite/.protocols/loop-protocol.md 2>/dev/null || true…”
- name
- technical-writer
Files
SKILL.md and 4 other files in skills/technical-writer of nagisanzenin/production-grade.
- SKILL.md
- phases/01-content-audit.md
- phases/02-api-reference.md
- phases/03-developer-guides.md
- phases/04-docusaurus-scaffold.md
Open the folder on GitHubat commit 4b2f13f
Compare with similar skills
Technical Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Writer this skillnagisanzenin/production-grade | 181 | — | ~3k | Automated safety check: Pass | None | |
| Technical Writerfinos/morphir | 213 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Doc Writerpretend1111/claude-desktop-app | 496 | 1 repos | ~375 | Automated safety check: Pass | Custom licence | |
| Diataxis Docspmndrs/glyph | 395 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Tabler Docs Writertabler/tabler | 42k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Document Generatorgarrytan/gstack | 136k | — | ~11k | Automated safety check: Notes | MIT |
Similar skills
Doc Writer
pretend1111/claude-desktop-app
Generate README, API docs, or user guides for code and projects.
Diataxis Docs
pmndrs/glyph
Design, classify, write, audit, or restructure technical documentation with the Diátaxis framework.
Tabler Docs Writer
tabler/tabler
Writes and updates Tabler documentation pages in simple English following the repository's page schema, and flags new components that have no docs yet.
Document Generator
garrytan/gstack
Writes missing documentation from scratch for a feature, a module or a whole project, organized as tutorial, how-to, reference and explanation pages.
RFC Creator
tech-leads-club/agent-skills
Drafts Request for Comments documents that lay out a proposal, the options weighed and the decision needed, so approvers can align before a major change.
More from nagisanzenin/production-grade
All 13 skills in this repoProduction Grade
nagisanzenin/production-grade
A skill your agent uses when the user wants to build, create, or develop anything — websites, apps, APIs, services, platforms.
Data Scientist
nagisanzenin/production-grade
[production-grade internal] Optimizes AI/ML/LLM usage when you need model selection, prompt engineering, cost reduction, or experiment design.
Product Manager
nagisanzenin/production-grade
[production-grade internal] Turns product ideas and business goals into formal requirements — BRD, user stories, acceptance criteria, prioritization.
Skill Maker
nagisanzenin/production-grade
[production-grade internal] Creates reusable Claude Code skills and plugins when you want to automate repeatable workflows into shareable tools.
Software Engineer
nagisanzenin/production-grade
[production-grade internal] Implements backend services, APIs, and business logic — builds features, fixes bugs, refactors code from specs.
Sre
nagisanzenin/production-grade
[production-grade internal] Makes systems reliable in production — SLOs, monitoring, alerting, chaos engineering, incident runbooks, capacity planning.
Related
Categories
Questions about Technical Writer
What does Technical Writer do?
[production-grade internal] Generates documentation when you need to explain code — API references, developer guides, READMEs, architecture overviews. Technical Writer is an agent skill from nagisanzenin/production-grade. [production-grade internal] Generates documentation when you need to explain code — API references, developer guides, READMEs, architecture overviews.
When should I use Technical Writer?
Technical Writer fits situations like: tasks that involve Technical documentation; tasks that involve Technical writing.
How do I install Technical Writer in Claude Code?
Run `npx skills add nagisanzenin/production-grade --skill technical-writer -a claude-code`. Or copy the skill folder (skills/technical-writer in nagisanzenin/production-grade) into .claude/skills/technical-writer in your project. Claude Code loads it when a task matches its description.
How do I install Technical Writer in Codex?
Run `npx skills add nagisanzenin/production-grade --skill technical-writer -a codex`. Or copy the skill folder (skills/technical-writer in nagisanzenin/production-grade) into .agents/skills/technical-writer in your project. Codex loads it when a task matches its description.
Can I use Technical Writer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nagisanzenin/production-grade --skill technical-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-writer, .gemini/skills/technical-writer, .github/skills/technical-writer and .opencode/skills/technical-writer in your project.
What does Technical Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Writer is instructions for the agent only. Our summary lists: Python 3.
Does Technical Writer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Technical Writer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Technical Writer use?
No licence was found for Technical Writer or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Technical Writer use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Technical Writer?
Skills that share tags, products or a category with Technical Writer: Technical Writer (finos/morphir, 213 stars), Doc Writer (pretend1111/claude-desktop-app, 496 stars), Diataxis Docs (pmndrs/glyph, 395 stars) and Tabler Docs Writer (tabler/tabler, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Writer?
nagisanzenin (a GitHub user) maintains it in nagisanzenin/production-grade, which has 181 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 19, 2026.
Source: nagisanzenin/production-grade on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.