# API Documentation Question

> Customer asks questions about API usage, code implementation, or technical documentation.

- Skill: `majiayu000/api-documentation-question` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/api-documentation-question`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/api-documentation-question/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/api-documentation-question

---


# 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