Name: render-diagram
Rating: 72 (1 reviews)
Author: AndreJorgeLopes

render-diagram

Create and render an Excalidraw diagram from a description or codebase analysis — exports to PNG via a pure-node pipeline (no browser/MCP), shows it inline via the Read tool, and embeds it in docs. Use when asked to diagram, visualize, or draw an architecture/flow, or when another skill needs a rendered diagram.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is render-diagram in AndreJorgeLopes/devflow

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, validated workflow and well-structured one-level-deep references. Conciseness is the main weakness: Step 4 and the Maintenance notes carry rationale and dated detail that pad the token budget.

Suggestions

Tighten Step 4 by trimming the empirically-tested show_widget rationale into a one-line 'avoid mcp__visualize__show_widget; use the standalone PNG Read' note.

Move dated version/version-pinning detail (e.g. the '2026-06' test note and node-25/canvas@3 pinning) into a dedicated 'Maintenance / known-good versions' subsection rather than inlining it in the operational steps.

Condense the Maintenance notes' bound-text and export-pipeline internals, keeping only the action-relevant gotchas (fontFamily:2, don't grow boxes, NODE_PATH/CommonJS).

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational content (commands, JSON essentials, color hexes) but Step 4 and the Maintenance notes run long with empirically-tested rationale and dated material ('2026-06') that could be tightened or moved aside.	3 / 5
Actionability	Fully executable guidance — exact commands ('devflow visualizations render <file>.excalidraw', 'DEVFLOW_RENDER_ASSUME_YES=1'), concrete JSON schema essentials, and specific color hexes — copy-paste ready.	5 / 5
Workflow Clarity	Five sequenced steps plus a Preflight dependency check with explicit validation checkpoints (deps check, capturing 'PNG <abspath>', mandatory SHOW step) and feedback loops (missing dep → STOP/report; declined install → report).	5 / 5
Progressive Disclosure	Body is a concise overview pointing to five real one-level-deep reference files (json-format.md, arrows.md, colors.md, examples.md, validation.md) with brief inline essentials and SOURCE.md attribution — easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive, naming concrete actions and an explicit 'Use when' trigger clause. Trigger-term coverage is strong but could add a few more natural synonyms.

Suggestions

Add common synonyms like 'flowchart' or 'schema diagram' and the '.excalidraw' extension to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create and render an Excalidraw diagram', 'exports to PNG via a pure-node pipeline', 'shows it inline via the Read tool', and 'embeds it in docs' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (create/render/export/show/embed) and when ('Use when asked to diagram, visualize, or draw an architecture/flow, or when another skill needs a rendered diagram').	5 / 5
Trigger Term Quality	Strong natural terms ('diagram', 'visualize', 'draw', 'architecture/flow', 'rendered diagram') but missing common synonyms like 'flowchart' and file extensions; good coverage, a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche — rendered Excalidraw via a pure-node pipeline shown inline via the Read tool — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: AndreJorgeLopes/devflow
Path: devflow-plugin/flows/diagrams/skills/render-diagram/SKILL.md
Commit: bd4b70c

Reviewed: 9 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.