Diagram Design
cathrynlavery/diagram-design
Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.
Create clear, comprehensive API documentation with examples and error handling.
Install API Documentation Writer
$ npx skills add captainflasmr/ollama-buddy --skill api-documentation-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install captainflasmr/ollama-buddy api-documentation-writer --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/captainflasmr/ollama-buddy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/api-documentation-writer .claude/skills/api-documentation-writer && 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 "api-documentation-writer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/api-documentation-writer into .claude/skills/api-documentation-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-documentation-writer", 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/captainflasmr/ollama-buddy/tree/main/.agents/skills/api-documentation-writerType 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 captainflasmr/ollama-buddy --skill api-documentation-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install captainflasmr/ollama-buddy api-documentation-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/api-documentation-writer .agents/skills/api-documentation-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-documentation-writer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/api-documentation-writer into .agents/skills/api-documentation-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-documentation-writer", 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 captainflasmr/ollama-buddy --skill api-documentation-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install captainflasmr/ollama-buddy api-documentation-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/api-documentation-writer .cursor/skills/api-documentation-writer && 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 "api-documentation-writer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/api-documentation-writer into .cursor/skills/api-documentation-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-documentation-writer", 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/captainflasmr/ollama-buddy.git --path .agents/skills/api-documentation-writer--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 captainflasmr/ollama-buddy --skill api-documentation-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install captainflasmr/ollama-buddy api-documentation-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/api-documentation-writer .gemini/skills/api-documentation-writer && 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 "api-documentation-writer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/api-documentation-writer into .gemini/skills/api-documentation-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-documentation-writer", 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 captainflasmr/ollama-buddy api-documentation-writerInstalls 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 captainflasmr/ollama-buddy --skill api-documentation-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/api-documentation-writer .github/skills/api-documentation-writer && 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 "api-documentation-writer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/api-documentation-writer into .github/skills/api-documentation-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-documentation-writer", 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 captainflasmr/ollama-buddy --skill api-documentation-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install captainflasmr/ollama-buddy api-documentation-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/api-documentation-writer .opencode/skills/api-documentation-writer && 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 "api-documentation-writer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/api-documentation-writer into .opencode/skills/api-documentation-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-documentation-writer", 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
api-documentation-writer- GitHub stars
- 103
- Token cost
- ~326 tokens
- SKILL.md length
- 134 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Create clear, comprehensive API documentation with examples and error handling.
- Works in 5 steps: Provide concise overviews of… → Include complete, accurate details about… → Show practical examples of common use… → …
- Phrases like api documentation
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Document this api
What it does
API Documentation Writer is an agent skill from captainflasmr/ollama-buddy. Create clear, comprehensive API documentation with examples and error handling. Trigger on phrases like "api documentation", "document this api", "write api docs", "api reference", "api endpoint documentation".
Its SKILL.md is about 330 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 documentation. The repository describes itself as: A friendly Emacs interface for interacting with Ollama models. The licence is GPL-3.0.
When your agent uses it
- Phrases like api documentation
- Document this api
- Api endpoint documentation
Example prompts
- “api documentation”
- “document this api”
- “write api docs”
- “/api-documentation-writer”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Provide concise overviews of functionality and purpose
- Include complete, accurate details about endpoints, parameters, and return values
- Show practical examples of common use cases
- Address error handling and edge cases
- Use consistent terminology and formatting
What it can do on your machine
Read from SKILL.md and the folder at commit 12eaf7f. 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
API Documentation Writer loads about 326 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 134 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 captainflasmr/ollama-buddy at commit 12eaf7f, republished under its GPL-3.0 licence (© captainflasmr). 134 words, ~326 tokens.
Download SKILL.mdSave it as
.claude/skills/api-documentation-writer/SKILL.md (or your agent's skills folder).- name
- api-documentation-writer
- description
- Create clear, comprehensive API documentation with examples and error handling. Trigger on phrases like "api documentation", "document this api", "write api docs", "api reference", "api endpoint documentation".
API Documentation Writer
You are an API documentation specialist who creates clear, comprehensive documentation for software interfaces. Your documentation should:
- Provide concise overviews of functionality and purpose
- Include complete, accurate details about endpoints, parameters, and return values
- Show practical examples of common use cases
- Address error handling and edge cases
- Use consistent terminology and formatting
When creating API documentation:
- Structure content logically with clear navigation
- Include both quick reference and detailed explanations
- Provide example requests and responses in multiple languages
- Document authentication requirements and security considerations
- Include status codes and error messages with their meanings
Balance technical completeness with readability, ensuring that documentation serves both new users who need guidance and experienced users who need quick reference. Use tables, code blocks, and other formatting to enhance clarity and scanability.
© captainflasmr, 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/api-documentation-writer of captainflasmr/ollama-buddy.
Open the folder on GitHubat commit 12eaf7f
Compare with similar skills
API Documentation Writer 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 |
|---|---|---|---|---|---|---|
| API Documentation Writer this skillcaptainflasmr/ollama-buddy | 103 | — | ~326 | Automated safety check: Pass | GPL-3.0 | |
| Diagram Designcathrynlavery/diagram-design | 44k | 1 repos | ~7.5k | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Get API Docs with chubandrewyng/context-hub | 14k | 2 repos | ~775 | Automated safety check: Pass | MIT | |
| Doc SyncJetBrains/ideavim | 10k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Mailspring App ScreenshotsFoundry376/Mailspring | 18k | — | ~1.4k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Get API Docs with chub
andrewyng/context-hub
Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
Mailspring App Screenshots
Foundry376/Mailspring
Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.
Draw.io Diagram Studio
Agents365-ai/drawio-skill
Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.
More from captainflasmr/ollama-buddy
All 12 skills in this repoBlog Writer
captainflasmr/ollama-buddy
Write an Emacs blog post in James Dyer's voice for www.emacs.dyerdwelling.family.
Elisp Dev
captainflasmr/ollama-buddy
Assist with Emacs Lisp (elisp) development, debugging, and parenthesis matching.
Elisp Review
captainflasmr/ollama-buddy
Review Emacs Lisp (elisp) packages for bugs, style/convention violations, and optimisation opportunities.
Annotate Project
captainflasmr/ollama-buddy
Analyse a project's source code and generate a simply-annotate database file with LLM-created annotations categorised by tag: defun for functions and large syntactical blocks, line for smaller…
Reddit Post Writer
captainflasmr/ollama-buddy
Write an r/emacs Reddit post in James Dyer's voice for announcing or discussing an Emacs package.
Code Refactoring
captainflasmr/ollama-buddy
Expert code refactoring and optimization with analysis, improvements, and documentation.
Related
Categories
Questions about API Documentation Writer
What does API Documentation Writer do?
Create clear, comprehensive API documentation with examples and error handling. API Documentation Writer is an agent skill from captainflasmr/ollama-buddy. Create clear, comprehensive API documentation with examples and error handling.
When should I use API Documentation Writer?
API Documentation Writer fits situations like: phrases like api documentation; document this api; api endpoint documentation.
How do I install API Documentation Writer in Claude Code?
Run `npx skills add captainflasmr/ollama-buddy --skill api-documentation-writer -a claude-code`. Or copy the skill folder (.agents/skills/api-documentation-writer in captainflasmr/ollama-buddy) into .claude/skills/api-documentation-writer in your project. Claude Code loads it when a task matches its description.
How do I install API Documentation Writer in Codex?
Run `npx skills add captainflasmr/ollama-buddy --skill api-documentation-writer -a codex`. Or copy the skill folder (.agents/skills/api-documentation-writer in captainflasmr/ollama-buddy) into .agents/skills/api-documentation-writer in your project. Codex loads it when a task matches its description.
Can I use API Documentation Writer 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 captainflasmr/ollama-buddy --skill api-documentation-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-documentation-writer, .gemini/skills/api-documentation-writer, .github/skills/api-documentation-writer and .opencode/skills/api-documentation-writer in your project.
What does API Documentation Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: API Documentation Writer is instructions for the agent only.
Does API Documentation Writer 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 API Documentation Writer 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 API Documentation Writer use?
API Documentation Writer 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 API Documentation Writer use?
About 326 tokens (SKILL.md is roughly 1.3k 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 API Documentation Writer?
Skills that share tags, products or a category with API Documentation Writer: Diagram Design (cathrynlavery/diagram-design, 44k stars), Simple English (moeru-ai/airi, 50k stars), Get API Docs with chub (andrewyng/context-hub, 14k stars) and Doc Sync (JetBrains/ideavim, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Documentation Writer?
captainflasmr (a GitHub user) maintains it in captainflasmr/ollama-buddy, which has 103 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 10, 2026.
Source: captainflasmr/ollama-buddy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.