create-workflow-diagram

Create FigJam/Miro-style workflow diagrams as high-quality PNG images from plain-text workflow descriptions. Renders beautiful HTML diagrams with connected nodes, arrows, and labels, then screenshots them for sharing.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/design/capabilities/create-workflow-diagram/SKILL.md

Quality

Content

63%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 body is highly actionable with a complete HTML template, explicit layout algorithms, and concrete screenshot commands, organized into a clear five-phase workflow. Its weaknesses are redundant narrative sections that pad token usage, missing output validation, and references to bundle files (STYLE_PRESETS.md, screenshot-diagram.js) that are not actually present.

Suggestions

Actually provide STYLE_PRESETS.md and the screenshot script (or inline their content), since the body instructs Claude to use files that do not exist in the bundle.

Cut redundant sections — 'Core Philosophy', 'Workflow Overview', and 'Example Session Flow' all restate the phases — and move the full HTML template and style presets into reference files.

Add an explicit validation step after screenshotting, e.g. verify the PNG exists in exports/ and is under the 5MB spec before delivering.

Dimension	Reasoning	Score
Conciseness	The HTML template, layout formulas, and icon heuristics earn their place, but sections like 'Core Philosophy', the 'Workflow Overview' block, and the 'Example Session Flow' restate the same phases, and the delivery message template is padded — mostly efficient but could be tightened.	3 / 5
Actionability	The skill provides a copy-paste-ready HTML template, concrete layout math, arrow-coordinate code, and explicit commands ('node screenshot-diagram.js <diagram-name>', 'npm install'), but the referenced screenshot script is not provided and its behavior is only described — mostly executable with minor gaps.	4 / 5
Workflow Clarity	Five clearly numbered phases (Discovery, Style, Generate, Screenshot, Delivery) plus a Troubleshooting section give a clear sequence with feedback loops for known failure modes, but there is no explicit output-validation checkpoint (e.g., verify the PNG exists and is under 5MB), keeping it below anchor 5.	4 / 5
Progressive Disclosure	The body is well-sectioned and signals references clearly ('See STYLE_PRESETS.md for full details on each style'), but those referenced files do not exist in the bundle and the ~215-line HTML template and style presets are inlined rather than split out — structure is present but organization and real reference files are incomplete.	3 / 5
	Total	14 / 20 Passed

Description

71%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.

A specific, action-oriented description that clearly states what the skill does across the full create-render-screenshot pipeline. Its main weaknesses are the complete absence of 'when to use' trigger guidance, which caps completeness, and missing common synonyms like 'flowchart' or 'process map'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user describes a workflow, process, or pipeline in plain text and wants a shareable diagram.'

Include natural synonyms users would say, such as 'flowchart', 'process map', or 'process diagram', to broaden trigger coverage.

Trim evaluative fluff like 'high-quality' and 'beautiful' in favor of concrete output details (e.g., '1920x1080 PNG').

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions covering the full pipeline — 'Create FigJam/Miro-style workflow diagrams as high-quality PNG images from plain-text workflow descriptions' and 'Renders beautiful HTML diagrams with connected nodes, arrows, and labels, then screenshots them' — matching the comprehensive-coverage anchor despite minor fluff like 'high-quality' and 'beautiful'.	5 / 5
Completeness	The 'what' is explicit (create, render, screenshot workflow diagrams), but there is no 'Use when...' clause or any trigger guidance, so per the rubric completeness is capped at 3; it is not 2 because the 'what' is clear and concrete.	3 / 5
Trigger Term Quality	Natural phrases such as 'workflow diagrams', 'workflow descriptions', 'PNG images', and 'sharing' are present, but common synonyms users would say — 'flowchart', 'process map', 'process diagram' — are missing, matching the good-but-not-comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	'FigJam/Miro-style workflow diagrams from plain-text workflow descriptions' carves a distinct niche, with only minor overlap risk against general diagramming or dataviz skills — an anchor-4 match rather than 5 since 'diagram' triggers are still somewhat shared.	4 / 5
	Total	16 / 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
skill_md_line_count	SKILL.md is long (619 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/design/capabilities/create-workflow-diagram/SKILL.md
Commit: cc3e518

Reviewed: 7 days 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.