Agent skill

Documentation

by EliasOulkadi in EliasOulkadi/shokunin

Generate READMEs, API docs, changelogs, and knowledge base articles.

MITAuto-check passedDevelopment

Install Documentation

skills CLI
$ npx skills add EliasOulkadi/shokunin --skill documentation -a claude-code

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

GitHub CLI
$ gh skill install EliasOulkadi/shokunin documentation --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/EliasOulkadi/shokunin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pack/skills/documentation .claude/skills/documentation && 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
documentation
GitHub stars
114
Token cost
~2k tokens
SKILL.md length
782 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
MIT

At a glance

Generate READMEs, API docs, changelogs, and knowledge base articles.

  • Works in 6 steps: Identify document type — README, API… → Gather source material — for README:… → Apply the template — README: hook →… → …
  • Tasks that involve Technical documentation
  • SKILL.md covers Sub-Commands, README Structure, API Documentation and Changelog Format, plus 9 more sections
  • Calls npx

What it does

Documentation is an agent skill from EliasOulkadi/shokunin. Generate READMEs, API docs, changelogs, and knowledge base articles. Covers README structure with personality, OpenAPI-based API documentation, changelogs from conventional commits, typedoc patterns, and support KB articles.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: opencode

It sits in Development, covering Technical documentation, Changelog and release notes and OpenAPI specifications. It works with OpenAPI. The repository describes itself as: 職人 Shokunin 62 AI agent skills for OpenCode, Claude Code, Cursor, Windsurf. ChromaDB memory, MCP servers, declarative self-updates. Multi-model, open source, zero cost. The licence is MIT.

When your agent uses it

  • Tasks that involve Technical documentation
  • Tasks that involve Changelog and release notes
  • Tasks that involve OpenAPI specifications

Example prompts

  • “/documentation”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): opencode
  • Pre-approved tools (allowed-tools): read, write, edit, glob, grep, bash, webfetch

Workflow steps

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

  1. Identify document type — README, API docs, changelog, or knowledge base article. Each has a distinct structure and rule set.
  2. Gather source material — for README: project files, package.json, build system. For API: OpenAPI spec or route handlers. For changelog…
  3. Apply the template — README: hook → features → quick start → API → examples → config → contributing → license. API: method → path →…
  4. Fill every section with real data — no "TODO", "coming soon", "TBD", placeholder text. Quick start must be copy-paste runnable. API docs…
  5. Verify everything — test quick start from clean environment. Check every link resolves. Confirm license badge matches LICENSE file. KB…
  6. Cut the generic — remove default template comments. Strip "write unit tests" style advice. Every sentence must convey a specific…

What it can do on your machine

Read from SKILL.md and the folder at commit 4c68e5b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • read
    • write
    • edit
    • glob
    • grep
    • bash
    • webfetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    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

    opencode

    From compatibility in the SKILL.md frontmatter.

Context cost

Documentation loads about 2k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 782 words of instructions outside code blocks.

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

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 EliasOulkadi/shokunin at commit 4c68e5b, republished under its MIT licence (© EliasOulkadi). 782 words, ~2,034 tokens.

Download SKILL.mdSave it as .claude/skills/documentation/SKILL.md (or your agent's skills folder).
name
documentation
description
Generate READMEs, API docs, changelogs, and knowledge base articles. Covers README structure with personality, OpenAPI-based API documentation, changelogs from conventional commits, typedoc patterns, and support KB articles.
allowed-tools
read, write, edit, glob, grep, bash, webfetch
compatibility
opencode
triggers
write documentation, write README, API documentation, API docs, changelog, release notes, knowledge base, setup guide, getting started, project docs
negatives
API design, code comments, blog post, technical writing prose
license
MIT
metadata.version
4.0.0
metadata.workflow
documentation
metadata.audience
developers

Documentation

Write docs that developers actually read. Based on Stripe API docs, Standard Readme, Keep a Changelog, and OpenAPI.

Sub-Commands

CommandDescription
readmeGenerate a README from project files
apiGenerate API docs from OpenAPI spec or route handlers
changelogGenerate changelog from conventional commits
kbWrite a knowledge base article

README Structure

# Project Name [Badges]

> One-line description

## Features (3-6 quantified benefits)
## Quick Start — copy-paste runnable (no placeholders, no omitted imports)
## API Reference — every export in table format
## Examples — 2-3 real-world scenarios
## Configuration — env vars, config file, CLI flags
## Contributing — dev setup commands
## License — SPDX identifier
The Hook (first paragraph)

Answers: what (5 words), who, why.

Bad: "A React component library for building modern user interfaces." Good: "Buttons, modals, forms, done right. No design debt. Zero dependencies."

Quick Start Rules

Copy-paste runnable. No omitted imports. No placeholders. No "coming soon". Include expected output.

Badge Requirements
BadgeRequired?
CI (build status)Yes
Package versionYes
LicenseYes
CoverageRecommended

API Documentation

Structure per Endpoint
### [METHOD] [Path]
**Description**: one sentence
**Auth required**: Yes/No [type]
**Request**: Headers, Parameters (path/query/body)
**Response 200**: Body with example
**Error responses**: 400, 401, 404, 500 with descriptions
Rules per Endpoint
  • Request example (curl + one SDK)
  • Response example with ALL fields
  • Error responses for ALL possible status codes
  • Pagination docs (if applicable)
  • Rate limit headers documented

Changelog Format

## [2.1.0] - 2026-05-16

### Added
- New feature (#PR)

### Changed
- Behavior change with migration note (#PR)

### Fixed
- Bug fix (#PR)

### Deprecated / Removed / Security

Rules: Keep a Changelog format. Every entry links to PR. Migration notes for breaking changes. Unreleased section at top. Semantic versioning. Explain WHY not just WHAT.

Knowledge Base

Article Format
Title: as a question user would search for
Context: 1-2 sentences — who, what product/feature
Steps: numbered, one action per step, action verb first
Expected result: after last step
Escalation: if it still doesn't work

Rules: One action per step. Bold UI labels exactly as they appear. Max 15 words per step. No jargon.

Production Checklist

  • All examples tested from clean environment
  • No "TODO", "coming soon", "TBD", placeholder text
  • Consistent tone across all sections
  • Every link resolves
  • License badge matches LICENSE file
  • API docs: curl + SDK example per endpoint
  • Changelog: unreleased section present, versions correct
  • KB: tested by someone unfamiliar with the product

Workflow

  1. Identify document type — README, API docs, changelog, or knowledge base article. Each has a distinct structure and rule set.
  2. Gather source material — for README: project files, package.json, build system. For API: OpenAPI spec or route handlers. For changelog: git log. For KB: product expertise.
  3. Apply the template — README: hook → features → quick start → API → examples → config → contributing → license. API: method → path → description → auth → request → response → errors.
  4. Fill every section with real data — no "TODO", "coming soon", "TBD", placeholder text. Quick start must be copy-paste runnable. API docs need curl + SDK examples.
  5. Verify everything — test quick start from clean environment. Check every link resolves. Confirm license badge matches LICENSE file. KB: test steps as an unfamiliar user.
  6. Cut the generic — remove default template comments. Strip "write unit tests" style advice. Every sentence must convey a specific convention or fact about this project.
Show full SKILL.md (387 more words)Show less

Error Handling

CauseFix
Quick start commands fail from a clean environmentTest every command from scratch. Ensure no omitted imports, no assumed global state, no missing env vars.
API docs missing error response codesDocument all possible status codes for every endpoint: 400 (validation), 401 (auth), 403 (forbidden), 404 (not found), 500 (server error).
Changelog entry lacks migration notes for breaking changesEvery breaking change must include: what changed, why, and the exact migration path. Link to the PR.
KB article steps don't produce expected result when followedHave someone unfamiliar with the product walk through the steps. Fix any ambiguity or missing context.
Links in documentation resolve to 404 or redirectCheck every link. Prefer permalinks. Verify external links haven't moved. Use web archive as fallback for critical references.
README badges show incorrect or outdated statusVerify CI badge matches current pipeline. Version badge matches latest release. Coverage badge matches current report.
API docs example response doesn't match actual API outputGenerate response examples from actual API output, not from spec definitions. Update when the API changes.
Default README template published with unfilled sectionsRemove all template comments and TODO markers before publishing. If a section has no content, omit it rather than leaving a placeholder.

Anti-Patterns

Anti-PatternCorrect
Default README (template unfilled)Remove all template comments. Fill every section.
"Coming soon" featuresShip or hide. Never show unfinished.
Untested install instructionsTest from scratch in clean environment.
API docs without examplesEvery function needs a runnable example.
Changelog without migration notesAlways include migration path for breaking changes.
KB with no expected resultEnd every step with "You should see..."
Example code with secretsUse placeholder env vars. Never real values.

API Documentation Patterns

OpenAPI → Docs
bash
npx @redocly/cli build-docs openapi.yaml -o docs.html
npx @scalar/api-reference openapi.yaml
README Template
  1. Title + one-liner, 2. Quick start (install + first command), 3. Features (bullets), 4. Architecture (diagram), 5. API (link), 6. Contributing (link), 7. License

Changelog Automation

bash
# Generate from conventional commits
npx standard-version
npx changelogen --from v1.0.0 --to HEAD

# Keep a Changelog format
## [version] - YYYY-MM-DD
### Added | Changed | Deprecated | Removed | Fixed | Security

Sources

  • Standard Readme specification
  • Stripe API documentation standards
  • Keep a Changelog (keepachangelog.com)
  • Conventional Commits (conventionalcommits.org)
  • OpenAPI Specification (openapis.org)
  • Zendesk / Intercom — KB standards

Checklist

  • Skill loads without errors in the AI agent
  • YAML frontmatter is valid (description, compatibility, audience)
  • Workflow section provides clear step-by-step instructions
  • Error handling section covers common failure modes
  • All referenced files (references/, scripts/, assets/) exist
  • Skill triggers correctly for intended use cases
  • No broken links or missing resources

© EliasOulkadi, MIT. 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 .pack/skills/documentation of EliasOulkadi/shokunin.

Open the folder on GitHubat commit 4c68e5b

Compare with similar skills

Documentation 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.

Documentation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Documentation this skillEliasOulkadi/shokunin114—~2kAutomated safety check: PassMIT
Documentationaiskillstore/marketplace4331 repos~2.7kAutomated safety check: PassNone
Documentation Patternsyonatangross/orchestkit292—~830Automated safety check: PassMIT
Docs Interfacesjh941213/my-cc-harness125—~863Automated safety check: NotesNone
Nacos API Doc Updatenacos-group/nacos-group.github.io115—~3.3kAutomated safety check: PassApache-2.0
Generate Dochyochan/react-native-nitro-sound961—~824Automated safety check: PassMIT

Similar skills

  • Documentation

    aiskillstore/marketplace

    Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation.

    433 GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed
  • Documentation Patterns

    yonatangross/orchestkit

    Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides.

    292 GitHub stars~830 tokensUpdated today
    DevelopmentAuto-check passed
  • Docs Interfaces

    jh941213/my-cc-harness

    Generate interface/API docs — OpenAPI 3.1/AsyncAPI 3.0 specs, API topology diagrams, interface flow (sequence) diagrams, API changelog.

    125 GitHub stars~863 tokensUpdated 2 mo ago
    Backend & APIsAuto-check: notes
  • Nacos API Doc Update

    nacos-group/nacos-group.github.io

    Updates Nacos API documentation from Swagger api.json. An agent skill from nacos-group/nacos-group.github.io.

    115 GitHub stars~3.3k tokensUpdated 16 days ago
    DevelopmentAuto-check passed
  • Generate Doc

    hyochan/react-native-nitro-sound

    Create or update react-native-nitro-sound API documentation, examples, migration notes, FAQ entries, changelog or release notes, and compiled AI context.

    961 GitHub stars~824 tokensUpdated 10 days ago
    DevelopmentAuto-check passed
  • API Documentation Generator

    luongnv89/claude-howto

    Generate comprehensive, accurate API documentation from source code. Use when creating or updating API documentation, generating OpenAPI specs, or when users…

    42k GitHub stars~429 tokensUpdated 9 days ago
    DevelopmentAuto-check passed

More from EliasOulkadi/shokunin

All 49 skills in this repo
  • CI CD

    EliasOulkadi/shokunin

    Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…

    114 GitHub stars~3.4k tokensUpdated 5 days ago
    Auto-check: notes
  • Component Forge

    EliasOulkadi/shokunin

    Build production-grade components for React, Vue 3, and Svelte 5 with all states (loading, empty, error, success, idle), TypeScript strict, WCAG 2.2 accessibility, server components (RSC), and…

    114 GitHub stars~3.6k tokensUpdated 5 days ago
    Auto-check: notes
  • DB Admin

    EliasOulkadi/shokunin

    PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…

    114 GitHub stars~2k tokensUpdated 5 days ago
    Auto-check: notes
  • DB Sculptor

    EliasOulkadi/shokunin

    Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and…

    114 GitHub stars~3.1k tokensUpdated 5 days ago
    Auto-check: notes
  • Docker

    EliasOulkadi/shokunin

    Optimize Docker images with multi-stage builds, distroless bases, BuildKit cache mounts, multi-arch builds, compose watch, security hardening (non-root, seccomp, capabilities drop), and…

    114 GitHub stars~3.8k tokensUpdated 5 days ago
    Auto-check: notes
  • Error Handler

    EliasOulkadi/shokunin

    Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…

    114 GitHub stars~3.6k tokensUpdated 5 days ago
    Auto-check: notes

Works with

Categories

Questions about Documentation

What does Documentation do?

Generate READMEs, API docs, changelogs, and knowledge base articles. Documentation is an agent skill from EliasOulkadi/shokunin. Generate READMEs, API docs, changelogs, and knowledge base articles.

When should I use Documentation?

Documentation fits situations like: tasks that involve Technical documentation; tasks that involve Changelog and release notes; tasks that involve OpenAPI specifications.

How do I install Documentation in Claude Code?

Run `npx skills add EliasOulkadi/shokunin --skill documentation -a claude-code`. Or copy the skill folder (.pack/skills/documentation in EliasOulkadi/shokunin) into .claude/skills/documentation in your project. Claude Code loads it when a task matches its description.

How do I install Documentation in Codex?

Run `npx skills add EliasOulkadi/shokunin --skill documentation -a codex`. Or copy the skill folder (.pack/skills/documentation in EliasOulkadi/shokunin) into .agents/skills/documentation in your project. Codex loads it when a task matches its description.

Can I use Documentation 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 EliasOulkadi/shokunin --skill documentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation, .gemini/skills/documentation, .github/skills/documentation and .opencode/skills/documentation in your project.

What does Documentation need to run?

Going by SKILL.md and its folder, Documentation needs the command-line tools its instructions call (npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: read, write, edit, glob, grep, bash, webfetch. Compatibility (from SKILL.md): opencode.

Does Documentation access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Documentation 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 Documentation use?

Documentation 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 Documentation use?

About 2k tokens (SKILL.md is roughly 8.1k 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 Documentation?

Skills that share tags, products or a category with Documentation: Documentation (aiskillstore/marketplace, 433 stars), Documentation Patterns (yonatangross/orchestkit, 292 stars), Docs Interfaces (jh941213/my-cc-harness, 125 stars) and Nacos API Doc Update (nacos-group/nacos-group.github.io, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Documentation?

EliasOulkadi (a GitHub user) maintains it in EliasOulkadi/shokunin, which has 114 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 5, 2026.

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