agentsclimarketplace

Guide review

Skill adobe/ai-repo-harness-guide/.agents/skills/guide-review

Review a multi-chapter guide, series, or book from six specialist perspectives. Orchestrates Series Editor, Non-Technical Proxy, Practitioner Proxy, Consistency Auditor, Diagram Reviewer, and Claims Auditor. Use for single-chapter review, full-series audit, consistency checks, diagram audits, and claims audits.From its SKILL.md

Install
npx -y skills add adobe/ai-repo-harness-guide --skill guide-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, as published. Nobody here has run it

Guide Review — Multi-Perspective Review Panel

Configure for your work

Before running any workflow, read the work's README or table of contents to establish:

  • All chapters, their titles, and reading order
  • Which chapters target non-technical readers vs. practitioners
  • Diagram format in use (Mermaid, PlantUML, images, etc.)
  • Any stated style rules, invariants, or editorial constraints

Agent roster

AgentPersonaActivate for
Series EditorNarrative ArchitectArc, voice, flow, and bloat across all chapters
Non-Technical ProxySkeptical decision-makerNon-technical chapters — accessibility, business clarity, engagement
Practitioner ProxyImpatient senior engineerTechnical chapters — actionability, depth, implementability
Consistency AuditorCross-chapter editorTerminology drift, duplication, model consistency, link integrity
Diagram ReviewerVisual clarity judgeDiagram quality, placement, accuracy, and format compliance
Claims AuditorSkeptical copy editorUnsupported claims, overstatements, weasel words, false precision

Workflows

Single-chapter review (quick)

  1. Identify whether the chapter targets a non-technical or practitioner audience.
  2. Relevant Proxy reviews for engagement and actionability.
  3. Series Editor checks voice consistency and transition into the next chapter.
  4. Claims Auditor flags any unsupported assertions.
  5. Surface findings to author.

Full series audit (thorough)

  1. Series Editor reads all chapters for arc, flow, and bloat.
  2. Non-Technical Proxy reviews non-technical chapters.
  3. Practitioner Proxy reviews practitioner chapters.
  4. Consistency Auditor runs a cross-chapter pass.
  5. Diagram Reviewer audits all visuals.
  6. Claims Auditor audits all chapters.
  7. Series Editor synthesizes findings into a prioritized revision list.
  8. Surface to author for approval.

Consistency check (targeted)

  1. Consistency Auditor scans for terminology drift, duplication, and broken links.
  2. Series Editor reviews findings for impact on arc and voice.
  3. Surface to author.

Diagram audit (targeted)

  1. Diagram Reviewer scans all chapters for visual opportunities and format issues.
  2. Series Editor reviews visual density and cross-chapter consistency.
  3. Surface to author.

Claims audit (targeted)

  1. Claims Auditor reads all chapters and produces structured report.
  2. Surface flagged claims to author for resolution.

Quality gates

Every chapter must pass before the author approves:

  • Series Editor: voice consistent, no bloat, transition to next chapter present
  • Relevant Proxy: engagement and actionability confirmed
  • Claims Auditor: all claims verified, qualified, or flagged for removal
  • Diagram Reviewer: visuals present where needed, accurate, format-compliant
  • Author approval

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.