api-documentation-question
Answer API and technical documentation questions. Use when a customer asks about API usage, code implementation, or integration details.
Best use case
api-documentation-question is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Answer API and technical documentation questions. Use when a customer asks about API usage, code implementation, or integration details.
Teams using api-documentation-question should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/api-documentation-question/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How api-documentation-question Compares
| Feature / Agent | api-documentation-question | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Answer API and technical documentation questions. Use when a customer asks about API usage, code implementation, or integration details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# API or Technical Documentation Question ## Response Patterns (from samples) Common openings: - "Hi," - "Hey," - "Hey there," Common core lines: - "Best," - "I hope this helps!" - "Hi," Common closings: - "Best," - "Best wishes," - "Thanks!" ## Phrases That Work (4-gram frequency) - "insights can help others" — 13 (39.4%) - "can help others too" — 13 (39.4%) - "plus your questions and" — 12 (36.4%) - "your questions and insights" — 12 (36.4%) - "questions and insights can" — 12 (36.4%) - "and insights can help" — 12 (36.4%) - "help others too i" — 9 (27.3%) - "others too i hope" — 9 (27.3%) - "too i hope this" — 9 (27.3%) - "i hope this helps" — 9 (27.3%) ## Tone Guidance (observed) - Openings trend toward: "Hi," - Closings often include: "Best," ## What NOT To Do - Don't introduce policy details that are not present in the verified response lines above. - Don't paraphrase or reframe the customer's question in a way that changes meaning. - Don't add refund/discount promises unless they appear in the extracted responses for this topic. ## Validation Draft must: - [ ] Include at least one of the required phrases from the validation block - [ ] Stay consistent with the observed response patterns above - [ ] NOT introduce policy details that are not present in the verified response lines above.
Related Skills
code-documentation-code-explain
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...
asking-questions
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
api-reference-documentation
Creates professional API documentation using OpenAPI specifications with endpoints, authentication, and interactive examples. Use when documenting REST APIs, creating SDK references, or building developer portals.
api-documentation
API documentation standards and patterns
api-documentation-writer
Expert guide for writing comprehensive API documentation including OpenAPI specs, endpoint references, authentication guides, and code examples. Use when documenting APIs, creating developer portals, or improving API discoverability.
api-documentation-generator
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
Answering Research Questions
Main orchestration workflow for systematic literature research - search, evaluate, traverse, synthesize
ask-question
Draft a technical research question and send to ChatGPT for investigation
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
obsidian-daily
Manage Obsidian Daily Notes via obsidian-cli. Create and open daily notes, append entries (journals, logs, tasks, links), read past notes by date, and search vault content. Handles relative dates like "yesterday", "last Friday", "3 days ago".
obsidian-additions
Create supplementary materials attached to existing notes: experiments, meetings, reports, logs, conspectuses, practice sessions, annotations, AI outputs, links collections. Two-step process: (1) create aggregator space, (2) create concrete addition in base/additions/. INVOKE when user wants to attach any supplementary material to an existing note. Triggers: "addition", "create addition", "experiment", "meeting notes", "report", "conspectus", "log", "practice", "annotations", "links", "link collection", "аддишн", "конспект", "встреча", "отчёт", "эксперимент", "практика", "аннотации", "ссылки", "добавь к заметке".
observe
Query and manage Observe using the Observe CLI. Use when the user wants to run OPAL queries, list datasets, manage objects, or interact with their Observe tenant from the command line.