Review documentation for clarity, structure, accuracy, and style issues.
npx skills add https://github.com/stacklok/docs-website --skill docs-review-stacklok
Please help me install this Agent Skill. Skill: docs-review Source: https://github.com/stacklok/docs-website/tree/main/.claude/skills/docs-review Command: npx skills add https://github.com/stacklok/docs-website --skill docs-review-stacklok
This Skill helps teams identify documentation problems that reduce clarity, trust, and usability by applying a technical writing and copyediting review process.
Review this documentation change for clarity, structure, accuracy, and style issues with specific recommendations.
High-intent search queries and answers about installing and using this skill.
Reviewing documentation for clarity and style consistency involves applying a technical writing and copyediting process to evaluate structure, readability, and accuracy. It identifies information architecture issues and provides actionable improvement recommendations for publication readiness.
A technical writing editorial review covers structure, readability, clarity, conciseness, and alignment with style guidelines. It systematically evaluates information architecture, style consistency, accuracy, and readability to identify quality issues like duplicated content and unclear instructions.
Yes, you can review a documentation pull request to find actionable improvements before publication. The editorial analysis identifies clarity, structure, accuracy, and style issues within the proposed changes.
Identifying LLM-generated writing patterns in documentation requires quality checks that detect unnatural phrasing alongside standard editorial analysis. The review specifically flags these patterns while evaluating information architecture, accuracy, and style consistency.
Yes, the editorial review works for multi-page documentation sets requiring editorial analysis. It systematically evaluates information architecture and style consistency across the entire set to identify duplicated content and structural issues.
The best way to check technical documentation for information architecture issues is through a systematic editorial analysis. This process identifies duplicated content, unclear instructions, and inaccurate examples while evaluating overall structure and readability.
jayteealaoReview editorial content against Every's style guide for grammar and punctuation.
sjunglingReview and structure Markdown technical documentation for accuracy and accessibility.
dioerdenReview GitHub pull requests and generate structured reports with security findings.
ahiendzLint and statically analyze Node.js/TypeScript and Python codebases.
