docs-review

Score technical documentation files against a 100-point rubric and return prioritized audits.

18|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/nexus-substrate/nexus-agents --skill docs-review-nexus-substrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-review
Source: https://github.com/nexus-substrate/nexus-agents/tree/main/skills/docs-review
Command: npx skills add https://github.com/nexus-substrate/nexus-agents --skill docs-review-nexus-substrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly evaluate the quality and technical soundness of a document so you can fix the most important issues before publishing or shipping.

Core Features & Use Cases

  • 100-point technical-doc rubric scoring: Scores technical structure, evidence, and argument clarity using the rubric in .rules/docs-rubric.md.
  • Read-only audit with a prioritized punch list: Produces a top-10 set of issues bucketed by severity (Critical to Low) with file/line locations and recommendations.
  • Defer-to user-level quality lenses: Reuses existing blog-* skills for prose-quality dimensions and fact-checking rather than duplicating logic.

Quick Start

Ask the skill to review an existing doc at a given path, for example: review the file docs/architecture/ADR-012.md and return a score with the top issues.

Frequently Asked Questions about docs-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I score a technical RFC against a structured rubric?▼

You can score a technical RFC by applying a 5-category 100-point rubric that evaluates technical structure, evidence, and argument clarity, returning a numeric score alongside a prioritized top-10 issue list.

Can I batch review multiple ADRs and READMEs in a directory?▼

Yes, you can batch review multiple ADRs and READMEs by pointing the skill at a directory or URL, which processes each technical document individually and outputs scores with prioritized issue recommendations.

What is the best way to audit technical documentation for argument strength?▼

The best way to audit argument strength is using a read-only review that mechanically extracts evidence signals to score technical structure and argument clarity, producing a prioritized punch list of actionable issues.

Does the docs-review rubric check prose quality and fact-check content?▼

No, the docs-review rubric does not check prose quality or fact-check content directly. It defers those prose and evidence lenses to existing blog-* skills to avoid duplicating quality-checking logic.

Can I review a CLAUDE.md file for technical soundness before shipping?▼

Yes, you can review a CLAUDE.md file for technical soundness before shipping. The skill accepts single-doc or batch directory/URL inputs to evaluate structure and argument clarity across various technical posts.