Skill

diagram-review

Use when the user has saved diagrams in the project library and asks for review-style help — phrases like "look over my architecture", "any issues with this diagram?", "review what I have", "what would you change?". Triggers on review/critique intent against existing saved content.

npx claudepluginhub michaeldancurtis/prixmaviz --plugin prixmaviz

Tool Access

This skill uses the workspace's default tool permissions.

Preview

When the user wants you to review a saved diagram:

SKILL.md

Similar Skills

cache-components

139.4k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

pdf

131.6k

Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.

11 files

document-skills

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMay 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Diagram Review

When the user wants you to review a saved diagram:

Call list_diagrams() to see what's saved.

If a diagram is currently focused, prefer that one. Otherwise ask the user which to review.

Call load_diagram(slug) to read the IR/DSL.

Call get_annotations(diagramId) to see the user's existing marks.

Walk the structure and identify common issues:

Orphan nodes (nodes with no edges in/out of them — usually a mistake)
Missing edges (groups of nodes that obviously belong together but aren't connected)
Ambiguous labels (nodes named "Service" or "DB1" without disambiguation)
Unbalanced detail (one subgraph deeply detailed, others stubbed)
Annotation conflicts (user marked something as wrong but didn't say what should change)

Suggest 1-3 concrete patches that fix specific issues. Use apply_patch to apply on user confirmation.

Don't lecture. Diagrams are working tools, not artwork. Suggest changes that make the diagram more useful for the user's evident purpose.

Diagram Review

When the user wants you to review a saved diagram:

Call list_diagrams() to see what's saved.
If a diagram is currently focused, prefer that one. Otherwise ask the user which to review.
Call load_diagram(slug) to read the IR/DSL.
Call get_annotations(diagramId) to see the user's existing marks.
Walk the structure and identify common issues:
- Orphan nodes (nodes with no edges in/out of them — usually a mistake)
- Missing edges (groups of nodes that obviously belong together but aren't connected)
- Ambiguous labels (nodes named "Service" or "DB1" without disambiguation)
- Unbalanced detail (one subgraph deeply detailed, others stubbed)
- Annotation conflicts (user marked something as wrong but didn't say what should change)
Suggest 1-3 concrete patches that fix specific issues. Use apply_patch to apply on user confirmation.

Don't lecture. Diagrams are working tools, not artwork. Suggest changes that make the diagram more useful for the user's evident purpose.