Documentation
aiskillstore/marketplace
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation.
Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates.
Install Developer Docs Drafting
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-drafting --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/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-drafting .claude/skills/developer-docs-drafting && 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 "developer-docs-drafting" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-drafting into .claude/skills/developer-docs-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-drafting", 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/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-draftingType 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 hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-drafting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-drafting .agents/skills/developer-docs-drafting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developer-docs-drafting" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-drafting into .agents/skills/developer-docs-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-drafting", 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 hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-drafting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-drafting .cursor/skills/developer-docs-drafting && 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 "developer-docs-drafting" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-drafting into .cursor/skills/developer-docs-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-drafting", 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/hashgraph-online/awesome-codex-plugins.git --path plugins/LVTD-LLC/skills/skills/developer-docs-drafting--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 hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-drafting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-drafting .gemini/skills/developer-docs-drafting && 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 "developer-docs-drafting" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-drafting into .gemini/skills/developer-docs-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-drafting", 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 hashgraph-online/awesome-codex-plugins developer-docs-draftingInstalls 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 hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-drafting .github/skills/developer-docs-drafting && 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 "developer-docs-drafting" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-drafting into .github/skills/developer-docs-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-drafting", 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 hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-drafting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-drafting .opencode/skills/developer-docs-drafting && 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 "developer-docs-drafting" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-drafting into .opencode/skills/developer-docs-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-drafting", 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
developer-docs-drafting- GitHub stars
- 1.2k
- Token cost
- ~770 tokens
- SKILL.md length
- 312 words
- Files
- 4 (incl. references)
- Skills in repo
- 736
- Repo updated
- First seen
- Licence
- MIT
At a glance
Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates.
- Works in 5 steps: Load guidelines.md to choose the… → Confirm audience, doc type, one primary… → Outline before drafting; treat the… → …
- Rewriting READMEs
- SKILL.md covers Quick Start, Default Output, Contents and Core Posture
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Developer Docs Drafting is an agent skill from hashgraph-online/awesome-codex-plugins. Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates. Use when writing or rewriting READMEs, getting-started docs, tutorials, how-to guides, concepts, API guides, troubleshooting pages, migration guides, SaaS topics, or release documentation.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `guidelines.md`, `references/core/knowledge.md` and `workflows/draft-developer-doc.md`). Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.
It sits in Development, covering Technical documentation, Technical writing and Code migrations. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.
When your agent uses it
- Rewriting READMEs
- Getting-started docs
- Troubleshooting pages
- Migration guides
Example prompts
- “/developer-docs-drafting”
Requirements
- Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Load guidelines.md to choose the smallest useful reference set.
- Confirm audience, doc type, one primary reader goal, and learning objective when available.
- Outline before drafting; treat the outline like pseudocode for the doc.
- Use workflows/draft-developer-doc.md for full-page drafts.
- Put the most important information first and make the page easy to skim.
What it can do on your machine
Read from SKILL.md and the folder at commit 16b4156. 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
Links to these hosts (documentation or services it may open):
link.springer.com
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.
Compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.
From compatibility in the SKILL.md frontmatter.
Context cost
Developer Docs Drafting loads about 770 tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 312 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
The full file from hashgraph-online/awesome-codex-plugins at commit 16b4156, republished under its MIT licence (© hashgraph-online). 312 words, ~770 tokens.
Download SKILL.mdSave it as
.claude/skills/developer-docs-drafting/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- developer-docs-drafting
- description
- Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates. Use when writing or rewriting READMEs, getting-started docs, tutorials, how-to guides, concepts, API guides, troubleshooting pages, migration guides, SaaS topics, or release documentation.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
- license
- MIT
- metadata.version
- 0.1.0
- metadata.displayName
- Developer Docs Drafting
- metadata.category
- Writing
- metadata.tags
- developer-docs,technical-writing,documentation,drafting,authoring
Developer Docs Drafting
Use this skill to draft developer documentation that readers can skim, follow, and apply. It turns audience and plan context into clear page structure and usable prose.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 3, "Drafting documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 9, "Learning Objectives," Chapter 14, "Scenario-driven Information Development," and Chapter 25, "Writing SaaS Documentation." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.mdto choose the smallest useful reference set. - Confirm audience, doc type, one primary reader goal, and learning objective when available.
- Outline before drafting; treat the outline like pseudocode for the doc.
- Use
workflows/draft-developer-doc.mdfor full-page drafts. - Put the most important information first and make the page easy to skim.
Default Output
When drafting a doc, return:
- Title - aligned with the reader goal.
- Opening context - what the reader will accomplish and prerequisites.
- Structured body - headings, steps, concepts, examples, lists, and callouts as appropriate.
- Scenario or route - real-world path, scope boundary, or self-contained topic context when useful.
- Verification or expected result - how the reader knows the task worked.
- Next steps - where the reader should go next.
- Draft notes - assumptions, TODOs, or source details needing review.
Contents
| Need | Start Here |
|---|---|
| Understand drafting components | references/core/knowledge.md |
| Apply drafting rules | references/core/knowledge.md |
| See before/after examples | references/core/knowledge.md |
| Draft a page | workflows/draft-developer-doc.md |
| Route by task | guidelines.md |
Core Posture
- Write for the reader's next decision or action.
- Make the page understandable to skimmers.
- Keep procedures actionable and verifiable.
- Lead scenario docs with the user's problem, not the product feature.
- Use templates to reduce blank-page work, not to force every doc into the same shape.
© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in plugins/LVTD-LLC/skills/skills/developer-docs-drafting of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- guidelines.md
- references/core/knowledge.md
- workflows/draft-developer-doc.md
Open the folder on GitHubat commit 16b4156
Compare with similar skills
Developer Docs Drafting 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 |
|---|---|---|---|---|---|---|
| Developer Docs Drafting this skillhashgraph-online/awesome-codex-plugins | 1.2k | — | ~770 | Automated safety check: Pass | MIT | |
| Documentationaiskillstore/marketplace | 430 | 1 repos | ~2.7k | Automated safety check: Pass | None | |
| Developer Docs Technical Writervercel-labs/github-tools | 131 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Technical Writerfinos/morphir | 213 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Doc Writerpretend1111/claude-desktop-app | 494 | 1 repos | ~375 | Automated safety check: Pass | Custom licence | |
| Diataxis Docspmndrs/glyph | 392 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Developer Docs Technical Writer
vercel-labs/github-tools
Writes, reviews and edits developer documentation for SDKs, libraries and frameworks, from getting-started guides and API references to migration guides.
Technical Writer
finos/morphir
Assists with writing and maintaining Morphir technical documentation.
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.
More from hashgraph-online/awesome-codex-plugins
All 736 skills in this repoAnime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Related
Categories
Questions about Developer Docs Drafting
What does Developer Docs Drafting do?
Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates. Developer Docs Drafting is an agent skill from hashgraph-online/awesome-codex-plugins. Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates.
When should I use Developer Docs Drafting?
Developer Docs Drafting fits situations like: rewriting READMEs; getting-started docs; troubleshooting pages; migration guides.
How do I install Developer Docs Drafting in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-drafting in hashgraph-online/awesome-codex-plugins) into .claude/skills/developer-docs-drafting in your project. Claude Code loads it when a task matches its description.
How do I install Developer Docs Drafting in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-drafting in hashgraph-online/awesome-codex-plugins) into .agents/skills/developer-docs-drafting in your project. Codex loads it when a task matches its description.
Can I use Developer Docs Drafting 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 hashgraph-online/awesome-codex-plugins --skill developer-docs-drafting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-docs-drafting, .gemini/skills/developer-docs-drafting, .github/skills/developer-docs-drafting and .opencode/skills/developer-docs-drafting in your project.
What does Developer Docs Drafting need to run?
SKILL.md names no scripts, command-line tools or credentials: Developer Docs Drafting is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..
Does Developer Docs Drafting access the network?
SKILL.md names 1 domain. As links in the text: link.springer.com. This is read from the text; nothing was executed.
Is Developer Docs Drafting 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 Developer Docs Drafting use?
Developer Docs Drafting is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Developer Docs Drafting use?
About 770 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
What are the alternatives to Developer Docs Drafting?
Skills that share tags, products or a category with Developer Docs Drafting: Documentation (aiskillstore/marketplace, 430 stars), Developer Docs Technical Writer (vercel-labs/github-tools, 131 stars), Technical Writer (finos/morphir, 213 stars) and Doc Writer (pretend1111/claude-desktop-app, 494 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developer Docs Drafting?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,232 GitHub stars. The repository holds 736 skills in this directory. The repository was last updated on October 6, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.