New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Technical Writing

by sreichholf in sreichholf/dreamDroid

Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages.

GPL-3.0Auto-check passedDevelopment

Install Technical Writing

skills CLI
$ npx skills add sreichholf/dreamDroid --skill technical-writing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sreichholf/dreamDroid technical-writing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sreichholf/dreamDroid.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/technical-writing .claude/skills/technical-writing && rm -rf skills-src

Use ~/.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/

Facts

Skill name
technical-writing
GitHub stars
116
Token cost
~199 tokens
SKILL.md length
80 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
GPL-3.0

At a glance

Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages.

  • Works in 6 steps: Identify the reader and the… → Put prerequisites and outcome before… → Use task-oriented sections for… → …
  • Durable engineering prose
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Technical writing

What it does

Technical Writing is an agent skill from sreichholf/dreamDroid. Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages. Use for durable engineering prose.

Its SKILL.md is about 200 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, Pull requests and Commit messages. The repository describes itself as: DreamDroid is an open-source enigma2 client for android based devices. The licence is GPL-3.0.

When your agent uses it

  • Durable engineering prose
  • Tasks that involve Technical writing
  • Tasks that involve Pull requests

Example prompts

  • “/technical-writing”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify the reader and the action/decision the document should enable.
  2. Put prerequisites and outcome before implementation history.
  3. Use task-oriented sections for procedures, concept-oriented sections for mental models, and reference tables only for lookup material.
  4. Keep terminology stable and sentences concrete. Define unavoidable jargon once.
  5. Examples must be runnable or explicitly illustrative. Never fabricate commands, links, benchmarks, or compatibility claims.
  6. For change documents, include impact, design/behavior, verification, migration/rollback if relevant, and open risks.

What it can do on your machine

Read from SKILL.md and the folder at commit 36f622a. 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 199 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 80 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~199

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

The full file from sreichholf/dreamDroid at commit 36f622a, republished under its GPL-3.0 licence (© sreichholf). 80 words, ~199 tokens.

Download SKILL.mdSave it as .claude/skills/technical-writing/SKILL.md (or your agent's skills folder).
name
technical-writing
description
Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages. Use for durable engineering prose.

Technical Writing

  1. Identify the reader and the action/decision the document should enable.
  2. Put prerequisites and outcome before implementation history.
  3. Use task-oriented sections for procedures, concept-oriented sections for mental models, and reference tables only for lookup material.
  4. Keep terminology stable and sentences concrete. Define unavoidable jargon once.
  5. Examples must be runnable or explicitly illustrative. Never fabricate commands, links, benchmarks, or compatibility claims.
  6. For change documents, include impact, design/behavior, verification, migration/rollback if relevant, and open risks.

© sreichholf, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/technical-writing of sreichholf/dreamDroid.

Open the folder on GitHubat commit 36f622a

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.

Technical Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Technical Writing this skillsreichholf/dreamDroid116—~199Automated safety check: PassGPL-3.0
Technical Writing Standardcursor/plugins10k10 repos~2.4kAutomated safety check: PassNone
Technical Writingfrappe/skills147—~1.1kAutomated safety check: PassNone
No TropesOutThisLife/brooklyn-skills199—~455Automated safety check: PassMIT
Plain Writingdocwriter-org/plain-writing-skill462—~3.6kAutomated safety check: PassMIT
Writing Stylepydantic/monty8.6k—~3.2kAutomated safety check: PassMIT

Similar skills

  • Technical Writing Standard

    cursor/plugins

    Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed

  • Technical Writing

    frappe/skills

    Write prose in "Simplified Technical English". An agent skill from frappe/skills.

    147 GitHub stars~1.1k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

  • No Tropes

    OutThisLife/brooklyn-skills

    Detect and eliminate common AI writing tropes from generated text.

    199 GitHub stars~455 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Plain Writing

    docwriter-org/plain-writing-skill

    Writes and edits prose in a plain and boring style: simple everyday words, complete sentences, no dashes, no jargon, and no analogies.

    462 GitHub stars~3.6k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Writing Style

    pydantic/monty

    Official

    How to write prose that reads like human technical documentation rather than LLM output.

    8.6k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Prose

    static-web-server/static-web-server

    Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…

    2.4k GitHub stars~971 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from sreichholf/dreamDroid

All 12 skills in this repo

  • Verify Dreamdroid

    sreichholf/dreamDroid

    Prove dreamDroid phone UI. An agent skill from sreichholf/dreamDroid.

    116 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Poteto Mode

    sreichholf/dreamDroid

    Lauren Tan-inspired rigorous engineering mode for concise communication, deliberate decomposition, simple code, independent review when available, and runtime verification.

    116 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Principle Never Block On The Human

    sreichholf/dreamDroid

    Run the experiment or make the reversible best-effort change, then show the result.

    116 GitHub stars~235 tokensUpdated today
    Auto-check passed

  • Architect

    sreichholf/dreamDroid

    Settle data shapes, ownership, boundaries, and interfaces before code crosses a function/module boundary.

    116 GitHub stars~224 tokensUpdated today
    Auto-check passed

  • Arena

    sreichholf/dreamDroid

    Spawn parallel candidate implementations for the same task, cross-judge, and graft the best parts into the winning base.

    116 GitHub stars~273 tokensUpdated today
    Auto-check passed

  • Automate Me

    sreichholf/dreamDroid

    Create a personal mode skill from recurring workflow patterns in available history.

    116 GitHub stars~208 tokensUpdated today
    Auto-check passed

Categories

Questions about Technical Writing

What does Technical Writing do?

Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages. Technical Writing is an agent skill from sreichholf/dreamDroid. Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages.

When should I use Technical Writing?

Technical Writing fits situations like: durable engineering prose; tasks that involve Technical writing; tasks that involve Pull requests.

How do I install Technical Writing in Claude Code?

Run `npx skills add sreichholf/dreamDroid --skill technical-writing -a claude-code`. Or copy the skill folder (.agents/skills/technical-writing in sreichholf/dreamDroid) 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 sreichholf/dreamDroid --skill technical-writing -a codex`. Or copy the skill folder (.agents/skills/technical-writing in sreichholf/dreamDroid) 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 sreichholf/dreamDroid --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?

Technical Writing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Technical Writing use?

About 199 tokens (SKILL.md is roughly 796 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 Writing Standard (cursor/plugins, 10k stars), Technical Writing (frappe/skills, 147 stars), No Tropes (OutThisLife/brooklyn-skills, 199 stars) and Plain Writing (docwriter-org/plain-writing-skill, 462 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Technical Writing?

sreichholf (a GitHub user) maintains it in sreichholf/dreamDroid, which has 116 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.

Source: sreichholf/dreamDroid on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.