Good docs audit
SkillFiles & storageLets your agent check documentation against a style guide and report violations with suggested rewrites.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Good docs audit skill
About this capability
Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations. Use when the user asks to review, critique, lint, or check the voice and tone of documentation or text. Produces a structured findings report (file:line, rule violated, offending text, sugg
What this skill tells your AI
The instructions your AI receives, as published by composiohq/composio in .agents/skills/good-docs-audit/SKILL.md and read by ahel’s review.
Review target documentation against the good-docs-writing rules and report where the writing drifts from that voice. Default behavior is report only: produce findings, do not edit. Only modify files if the user explicitly says to fix, rewrite, or apply.
Read references/audit-process.md for the procedure, the prioritized violation checklist, the report format, and the reporting rules.
Non-negotiables:
- Read
good-docs-writing(and itsreferences/style-guide.md) first. Those rules are the rubric; this skill is the process. - Cite
file:linefor every finding and quote the exact offending text. - Give a real rewrite in the target voice, not "consider revising."
- Don't invent violations. A short report is a good outcome.
Signals
- GitHub stars
- 30k
- Forks
- 5k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
good-docs-audit- Source
- github.com/composiohq/composio