Documentation

Use when writing README, CHANGELOG, runbooks, onboarding guides, API docs, architecture docs, or any technical documentation

9 stars 1 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add PanPanFR/oh-my-openkilo --skill documentation
Manual install
git clone --depth 1 https://github.com/PanPanFR/oh-my-openkilo.git /tmp/oh-my-openkilo
mkdir -p ~/.claude/skills
cp -r /tmp/oh-my-openkilo/skills/documentation ~/.claude/skills/documentation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Technical Documentation

## Principles

1. **Clarity** - simple, unambiguous language
2. **Accuracy** - code snippets and technical details correct and current
3. **User-centricity** - every doc helps a specific user achieve a specific task
4. **Consistency** - same tone, terminology, style across docs
5. Write for the reader; start with the most useful info (don't bury the lede)
6. Show, don't tell - examples, commands, screenshots
7. Keep it current - outdated docs are worse than none
8. Link, don't duplicate

## Document Types

| Type | Contains |
|------|----------|
| **README** | What/why, quick start (<5 min to first success), config/usage, GFM + admonitions. NO license/contributing/changelog sections (dedicated files) |
| **API docs** | Endpoint reference with request/response examples, auth, error codes, rate limits, pagination, SDK examples |
| **Runbook** | When to use, prerequisites/access, step-by-step procedure, rollback steps, escalation path |
| **Architecture** | Context/goals, high-level design with diagrams, key decisions/trade-offs, data flow |
| **Onboarding** | Environment setup, key systems and connections, common task walkthroughs, who to ask |

### Diátaxis Quadrants (when structured docs needed)

- **Tutorials:** learning-oriented; guide newcomer to successful outcome
- **How-to Guides:** problem-oriented; recipe for specific problem
- **Reference:** information-oriented; technical description of machinery
Read the full skill on GitHub

Details

Skill name
documentation
Path
skills/documentation/SKILL.md
License
MIT
Repo updated
2 November 2026

FAQ

What does the Documentation skill do?

Use when writing README, CHANGELOG, runbooks, onboarding guides, API docs, architecture docs, or any technical documentation

How do I install the Documentation skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add PanPanFR/oh-my-openkilo --skill documentation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Documentation popular?

It lives in PanPanFR/oh-my-openkilo, which has 9 GitHub stars and 1 forks.

Related skills

Adaptive

9

PanPanFR/oh-my-openkilo

Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto, and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API, and how to preserve UI, navigation, scroll, and media playback state across configuration changes (such as folding/unfolding a foldable, rotating a device, or resizing a window). It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as button

Mobile Development

Agentmemory

9

PanPanFR/oh-my-openkilo

Index for agentmemory internals: how it is wired into a host agent, its architecture and ports, configuration flags, capture hooks, MCP tool surface, and REST fallback. Use when installing or debugging agentmemory itself, when a memory tool name or parameter is unclear, or when capture is not recording. For normal recall and save work, use agentmemory-ops instead.

AI, LLMs & Agents

Agentmemory History

9

PanPanFR/oh-my-openkilo

Read past work: resume the last session, recap recent sessions, list agent-linked commits, trace a line back to the session that wrote it, or compact the current conversation for handoff. Use when the user says "where were we", "resume", "recap", "session history", "what did we do", "why is this code here", "who wrote this", or "handoff".

AI, LLMs & Agents

Confluence

9

flurdy/agent-skills

Read Confluence pages and comments. Use to fetch design docs, ADRs, runbooks, or any wiki content for context when working on tasks.

Writing & Content

Caveman Commit

9

PanPanFR/oh-my-openkilo

Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

Writing & Content

Plan to Backlog

9

flurdy/agent-skills

Materialize an approved cited plan into proportionate Beads tracking when the user asks for durable ownership. Recommends no item, one item, or a bounded epic; checks owners and duplicates; previews every write; applies only after exact confirmation.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.