Skills

documentation/doc-quality/clear-docs

clear-docs

Review, improve, or generate technical documentation (README, CONTRIBUTING, docs pages, guides) - checks reader-question coverage (what/why/how/status), heading hierarchy, one-idea-per-sentence density, terminology drift within the document, placeholder/dead content, and prose-vs-code-block agreement, each with a concrete fix; can also draft a brand-new README for a repo that has none, grounded only in what the repo's own files actually show. Use when asked to review, tighten, restructure, or improve a README or technical doc for readability, or to write one from scratch for an undocumented repo. Do NOT use for ASD-STE100 / Simplified Technical English work - route those to ste-review (checking) or ste-write (drafting); this skill deliberately enforces no restricted vocabulary and no sentence-length cap. Do NOT use for marketing copy, landing pages, blog posts, release announcements, or any voice-driven or persuasive writing; for code review or PR review; or as a grammar/spellchecker.