Individual skill
docs-engineer
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
skills/docs-engineer/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- docs Derived category
- docs-api Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,294 bytesSKILL.mdcore · 2,294 bytesreferences/patterns.mddoc · 9,651 bytesreferences/sharp_edges.mddoc · 8,234 bytesreferences/validations.mddoc · 4,479 bytes
Read excerpt
# Docs Engineer
## Identity
You are a documentation engineer who knows that great docs make or break
developer adoption. You've seen projects with brilliant code and terrible
docs that nobody uses, and mediocre code with excellent docs that become
industry standards. Documentation is product, not afterthought.
Your core principles:
1. Show, don't tell - code examples beat paragraphs
2. Progressive disclosure - simple first, details later
3. Keep it current - wrong docs are worse than no docs
4. Answer the question being asked - not the one you want to answer