Review target documentation for style, readability, tone, completeness, and factual accuracy.
npx skills add https://github.com/tldraw/tldraw --skill review-docs
Please help me install this Agent Skill. Skill: review-docs Source: https://github.com/tldraw/tldraw/tree/main/.claude/skills/review-docs Command: npx skills add https://github.com/tldraw/tldraw --skill review-docs
This Skill helps teams review and improve project documentation through a structured evaluation loop, employing parallel evaluation to surface issues and provide actionable improvements, with state tracking across rounds.
Run the review-docs skill on a target document path to initiate an evaluation and improvement cycle.
High-intent search queries and answers about installing and using this skill.
To review documentation for style and accuracy issues, you can run a structured evaluation loop on a specified document path. This process employs parallel evaluation to surface readability, tone, completeness, and factual correctness problems.
State tracking in iterative document improvement is the process of maintaining a state file to log identified issues and guide verification across multiple rounds. It ensures that style and accuracy problems are addressed systematically rather than lost between reviews.
You can improve developer guide readability and tone by initiating an iterative improvement cycle guided by user feedback. The evaluation operates on your target document to assess style and provide actionable improvements with clear acceptance criteria.
Yes, you can use parallel evaluation for README and API docs review. The system evaluates documentation by operating on a specified document path, targeting these specific file types to surface clarity, correctness, and completeness issues.
The best way to ensure accuracy in project documentation is through a structured evaluation loop with state tracking across rounds. This verifies that factual correctness issues are identified by parallel agents and resolved to meet clear acceptance criteria.
A limitation of iterative documentation review loops is that they require user feedback to guide the improvement cycle and clear acceptance criteria to conclude. The process evaluates a specified document path and relies on a state file to track issues across rounds.
GeneralJerelDraft structured PRDs from problem statements for product teams.
TeddyBennettExecutes iterative Ralph loop plans with validation and progress tracking in PRP projects.
hainamchungProvides Anthropic's official brand identity and style resources for documents and presentations.
causify-aiDetect factual and stylistic issues in written text files.
