How do I install the LLM Doc Writer skill?

Run npx skillmds@latest add aiskillstore/llm-doc-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is LLM Doc Writer safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with LLM Doc Writer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is LLM Doc Writer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published LLM Doc Writer?

aiskillstore (@aiskillstore) published this skill. Their other Agent Skills are listed on their SkillMD profile.

LLM Doc Writer by aiskillstore — Agent Skill

Name: LLM Doc Writer
Rating: 4.2 (5 reviews)
Author: aiskillstore

File contents

LLM-Optimized Documentation

Core Principles

Principle	Rule
Density	Max info, min tokens
Format	Tables > prose, bullets > paragraphs
No fluff	Ban filler words (see list below)
Show don't tell	Code examples > explanations
Progressive disclosure	TOC + separate files for details

Banned Patterns

# Filler words - NEVER use
simplement, il suffit de, en fait, basically, just, simply,
it's important to note, as mentioned, obviously, of course,
please note that, keep in mind, remember that

# Redundant structures - NEVER use
"This file contains..." (obvious from filename)
"In this section we will..." (just do it)
"The following example shows..." (just show it)

Format Rules

Tables over Prose

# BAD - 45 tokens
The system supports three modes: development mode which
enables hot reload, production mode which optimizes for
performance, and test mode which mocks external services.

# GOOD - 20 tokens
| Mode | Behavior |
|------|----------|
| dev | Hot reload |
| prod | Optimized |
| test | Mocked services |

Bullets over Paragraphs

# BAD - Narrative
To run the project, first ensure Node.js is installed,
then install dependencies with npm install, and finally
start the dev server with npm run dev.

# GOOD - Scannable
## Run
1. Requires: Node.js 18+
2. `npm install`
3. `npm run dev`

Code over Explanation

# BAD - Explaining
To create a new user, call the createUser function
with an object containing name and email properties.

# GOOD - Showing
```ts
createUser({ name: "Jo", email: "jo@x.com" })


## Structure Template

For CLAUDE.md / agent docs:

```markdown
# Project Name

## Stack
- Frontend: React/Vite
- Backend: FastAPI
- DB: PostgreSQL

## Commands
| Action | Command |
|--------|---------|
| Dev | `npm run dev` |
| Test | `npm test` |
| Build | `npm run build` |

## Architecture
[Brief description, link to detailed docs if needed]

## Conventions
- [Rule 1]
- [Rule 2]

Progressive Disclosure

For long docs (>200 lines):

# Main Doc

## Quick Reference
[Essential info here]

## Details
See [ARCHITECTURE.md](ARCHITECTURE.md)
See [API.md](API.md)

Self-Check

Before finalizing, verify:

No filler words?
Tables used where possible?
Bullet points, not paragraphs?
Examples over explanations?
< 500 lines (or split)?
No redundant info?

Examples

See patterns.md for before/after examples.

---name: llm-doc-writerdescription: Write token-efficient documentation for LLM context. Use when creating CLAUDE.md, README, technical docs, agent instructions, or any documentation consumed by AI assistants.---# LLM-Optimized Documentation## Core Principles| Principle | Rule ||-----------|------|| **Density** | Max info, min tokens || **Format** | Tables > prose, bullets > paragraphs || **No fluff** | Ban filler words (see list below) || **Show don't tell** | Code examples > explanations || **Progressive disclosure** | TOC + separate files for details |## Banned Patterns```# Filler words - NEVER usesimplement, il suffit de, en fait, basically, just, simply,it's important to note, as mentioned, obviously, of course,please note that, keep in mind, remember that# Redundant structures - NEVER use"This file contains..." (obvious from filename)"In this section we will..." (just do it)"The following example shows..." (just show it)```## Format Rules### Tables over Prose```markdown# BAD - 45 tokensThe system supports three modes: development mode whichenables hot reload, production mode which optimizes forperformance, and test mode which mocks external services.# GOOD - 20 tokens| Mode | Behavior ||------|----------|| dev | Hot reload || prod | Optimized || test | Mocked services |```### Bullets over Paragraphs```markdown# BAD - NarrativeTo run the project, first ensure Node.js is installed,then install dependencies with npm install, and finallystart the dev server with npm run dev.# GOOD - Scannable## Run1. Requires: Node.js 18+2. `npm install`3. `npm run dev````### Code over Explanation```markdown# BAD - ExplainingTo create a new user, call the createUser functionwith an object containing name and email properties.# GOOD - Showing```tscreateUser({ name: "Jo", email: "jo@x.com" })``````## Structure TemplateFor CLAUDE.md / agent docs:```markdown# Project Name## Stack- Frontend: React/Vite- Backend: FastAPI- DB: PostgreSQL## Commands| Action | Command ||--------|---------|| Dev | `npm run dev` || Test | `npm test` || Build | `npm run build` |## Architecture[Brief description, link to detailed docs if needed]## Conventions- [Rule 1]- [Rule 2]```## Progressive DisclosureFor long docs (>200 lines):```markdown# Main Doc## Quick Reference[Essential info here]## DetailsSee [ARCHITECTURE.md](ARCHITECTURE.md)See [API.md](API.md)```## Self-CheckBefore finalizing, verify:- [ ] No filler words?- [ ] Tables used where possible?- [ ] Bullet points, not paragraphs?- [ ] Examples over explanations?- [ ] < 500 lines (or split)?- [ ] No redundant info?## ExamplesSee [patterns.md](patterns.md) for before/after examples.

Frequently asked questions

LLM Doc Writer