Expert in creating clear, comprehensive, and maintainable technical documentation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondocumentation-engineerExecute the skills CLI command in your project's root directory to begin installation:
Fetches documentation-engineer from charon-fan/agent-playbook and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate documentation-engineer. Access via /documentation-engineer in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
27
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
27
stars
Expert in creating clear, comprehensive, and maintainable technical documentation.
Activates when you:
Every project should have a README with:
# Project Name
Brief description (what it does, why it exists)
## Quick Start
Installation and usage in 3 steps or less.
## Installation
Detailed installation instructions.
## Usage
Examples of common usage patterns.
## Configuration
Environment variables and configuration options.
## Development
How to run tests, build, and develop locally.
## Contributing
Guidelines for contributors.
## License
License information.
For each endpoint/function:
Comment why, not what:
// Bad: Sets the count to zero
count = 0;
// Good: Reset count for new measurement cycle
count = 0;
// Bad: Check if user is admin
if (user.role === 'admin') {
// Good: Only admins can bypass approval workflow
if (user.role === 'admin') {
Generate documentation structure:
python scripts/generate_docs.py
Validate documentation:
python scripts/validate_docs.py
references/readme-template.md - README templatereferences/api-template.md - API documentation templatereferences/style-guide.md - Documentation style guidePrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sammcj/agentic-coding
404kidwiz/claude-supercode-skills
jeffallan/claude-skills
jeffallan/claude-skills
davila7/claude-code-templates
sickn33/antigravity-awesome-skills
documentation-engineer reduced setup friction for our internal harness; good balance of opinion and flexibility.
documentation-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for documentation-engineer matched our evaluation — installs cleanly and behaves as described in the markdown.
documentation-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend documentation-engineer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
documentation-engineer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in documentation-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
documentation-engineer has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: documentation-engineer is focused, and the summary matches what you get after install.
Useful defaults in documentation-engineer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 56