Technical Writer
curiositech/some_claude_skills
Expert technical documentation specialist for developer docs, API references, and runbooks.
Write prose in "Simplified Technical English". An agent skill from frappe/skills.
Install Technical Writing
$ npx skills add frappe/skills --skill technical-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install frappe/skills technical-writing --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/frappe/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/technical-writing .claude/skills/technical-writing && 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-writing" agent skill from https://github.com/frappe/skills/tree/main/skills/technical-writing into .claude/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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/frappe/skills/tree/main/skills/technical-writingType 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 frappe/skills --skill technical-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install frappe/skills technical-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frappe/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/technical-writing .agents/skills/technical-writing && 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-writing" agent skill from https://github.com/frappe/skills/tree/main/skills/technical-writing into .agents/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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 frappe/skills --skill technical-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install frappe/skills technical-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frappe/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/technical-writing .cursor/skills/technical-writing && 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-writing" agent skill from https://github.com/frappe/skills/tree/main/skills/technical-writing into .cursor/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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/frappe/skills.git --path skills/technical-writing--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 frappe/skills --skill technical-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install frappe/skills technical-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frappe/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/technical-writing .gemini/skills/technical-writing && 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-writing" agent skill from https://github.com/frappe/skills/tree/main/skills/technical-writing into .gemini/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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 frappe/skills technical-writingInstalls 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 frappe/skills --skill technical-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/frappe/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/technical-writing .github/skills/technical-writing && 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-writing" agent skill from https://github.com/frappe/skills/tree/main/skills/technical-writing into .github/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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 frappe/skills --skill technical-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install frappe/skills technical-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frappe/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/technical-writing .opencode/skills/technical-writing && 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-writing" agent skill from https://github.com/frappe/skills/tree/main/skills/technical-writing into .opencode/skills/technical-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-writing", 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-writing- GitHub stars
- 146
- Token cost
- ~1.1k tokens
- SKILL.md length
- 659 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- None found
At a glance
Write prose in "Simplified Technical English". An agent skill from frappe/skills.
- Tasks that involve Technical writing
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Technical documentation
- Tasks that involve Copywriting
What it does
Technical Writing is an agent skill from frappe/skills. Write prose in "Simplified Technical English". This applies to documentation, READMEs, commits, pull request, plans and release notes. It does not apply to code, identifiers, marketing copy, essays, or anything that needs a voice.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Technical writing, Technical documentation and Copywriting. The repository describes itself as: Agent skills for Frappe App development.
When your agent uses it
- Tasks that involve Technical writing
- Tasks that involve Technical documentation
- Tasks that involve Copywriting
Example prompts
- “Simplified Technical English”
- “/technical-writing”
What it can do on your machine
Read from SKILL.md and the folder at commit 0bef982. 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.
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 Writing loads about 1.1k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 659 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 659 words (~1,103 tokens).
- name
- technical-writing
Files
Just SKILL.md in skills/technical-writing of frappe/skills.
Open the folder on GitHubat commit 0bef982
Compare with similar skills
Technical Writing 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 Writing this skillfrappe/skills | 146 | — | ~1.1k | Automated safety check: Pass | None | |
| Technical Writercuriositech/some_claude_skills | 243 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Technical Writingcitypaul/.dotfiles | 739 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Opik Documentation Patternscomet-ml/opik | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Change Documentation Writerjsmastery-pro/skills | 1.4k | — | ~2.4k | Automated safety check: Notes | MIT | |
| Content Modelguardana/guardana | 129 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Technical Writing
citypaul/.dotfiles
Writing developer-facing prose that can be skimmed first and trusted enough to finish — READMEs, guides, tutorials, reference docs, proposals, PR descriptions, release notes.
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
Change Documentation Writer
jsmastery-pro/skills
Writes PR descriptions, changelog entries, release notes and postmortems from the actual commits and diff, and saves each one in the right place.
Content Model
guardana/guardana
Route wording work to GPT (codex CLI) or Gemini (agy CLI) instead of writing it with Claude — landing-page copy, a readability rewrite of a README or docs page, attack and judge prompts for a rule…
Tech Writer
stacklok/mecatl
A skill your agent uses when writing or substantively editing user-facing documentation: drafting a new page, rewriting or restructuring an existing one, adding a major section, or turning…
More from frappe/skills
All 8 skills in this repoFrappe App Dev
frappe/skills
Builds full-stack Frappe Framework applications end-to-end. An agent skill from frappe/skills.
Deep App Audit
frappe/skills
Deep audit of a Frappe app for security, correctness, and customization defects.
Draft Security Advisory
frappe/skills
Turn a vulnerability report into a publication-ready GitHub Security Advisory.
Fix Issue
frappe/skills
Fix a bug reported in a GitHub issue or a markdown file, without letting the report's noise and guesses into the main context.
Frappe Code Review
frappe/skills
Review code for any Frappe application — a checklist distilled from years of engineering practice on correctness, security, performance, concurrency, readability, API design, and testing.
Resolve Backport Conflicts
frappe/skills
Resolve merge conflicts in a Mergify backport pull request. An agent skill from frappe/skills.
Related
Categories
Questions about Technical Writing
What does Technical Writing do?
Write prose in "Simplified Technical English". An agent skill from frappe/skills. Technical Writing is an agent skill from frappe/skills. Write prose in "Simplified Technical English".
When should I use Technical Writing?
Technical Writing fits situations like: tasks that involve Technical writing; tasks that involve Technical documentation; tasks that involve Copywriting.
How do I install Technical Writing in Claude Code?
Run `npx skills add frappe/skills --skill technical-writing -a claude-code`. Or copy the skill folder (skills/technical-writing in frappe/skills) into .claude/skills/technical-writing in your project. Claude Code loads it when a task matches its description.
How do I install Technical Writing in Codex?
Run `npx skills add frappe/skills --skill technical-writing -a codex`. Or copy the skill folder (skills/technical-writing in frappe/skills) into .agents/skills/technical-writing in your project. Codex loads it when a task matches its description.
Can I use Technical Writing 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 frappe/skills --skill technical-writing -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-writing, .gemini/skills/technical-writing, .github/skills/technical-writing and .opencode/skills/technical-writing in your project.
What does Technical Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Writing is instructions for the agent only.
Does Technical Writing 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 Writing 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 Writing use?
No licence was found for Technical Writing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Technical Writing use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Writing?
Skills that share tags, products or a category with Technical Writing: Technical Writer (curiositech/some_claude_skills, 243 stars), Technical Writing (citypaul/.dotfiles, 739 stars), Opik Documentation Patterns (comet-ml/opik, 22k stars) and Change Documentation Writer (jsmastery-pro/skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Writing?
frappe (a GitHub organization) maintains it in frappe/skills, which has 146 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 30, 2026.
Source: frappe/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.