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

66%

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

65%

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 complete executable HTML/CSS, JS, and bash examples plus concrete layout math, but it is verbose and monolithic. Workflow clarity and progressive disclosure are held back by missing validation/feedback around the screenshot step and dangling references to a non-existent STYLE_PRESETS.md.

Suggestions

Add an explicit validation/feedback loop after the screenshot step: confirm the PNG exists, dimensions match the chosen size, and file size is under 5MB, and instruct retry on failure.

Provide the referenced STYLE_PRESETS.md (or move the full style presets, HTML scaffold, and icon table into separate reference files) so progressive-disclosure references resolve to real files.

Trim redundant tables (the Style Quick Reference and Node Sizing Rules overlap the inline presets and CSS variables) to reduce token cost without losing guidance.

Dimension	Reasoning	Score
Conciseness	The 619-line body is mostly action-oriented with code rather than concept-explanation fluff, but it carries redundancy (overlapping icon, node-sizing, and style-reference tables) and inlines a full CSS/HTML scaffold that could be tightened or referenced out, landing in the 'mostly efficient but could be tighter' anchor rather than the lean anchor at 3.	2 / 3
Actionability	Provides fully executable HTML/CSS markup, JavaScript arrow-coordinate functions, concrete bash screenshot commands, and explicit layout formulas — copy-paste ready guidance matching the anchor at 3 and clearly above the pseudocode anchor at 2.	3 / 3
Workflow Clarity	A clear five-phase sequence is present, but the fragile render-then-screenshot step lacks validation checkpoints (no confirmation that the PNG meets the stated <5MB or dimension specs, and no feedback loop for failed captures), which caps workflow clarity at 2 per the destructive/fragile-operation guideline.	2 / 3
Progressive Disclosure	STYLE_PRESETS.md is referenced twice with clear signaling, but no bundle file or directory exists, so the references are dangling; combined with most detail inlined in a single monolithic file this fits the 'some structure but could be better organized' anchor rather than the clean one-level-deep reference anchor at 3.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 and occupies a clear niche, naming several concrete actions and a recognizable output format. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves trigger-term coverage implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating workflow or process diagrams, flowcharts, or step-by-step pipelines to share as images.'

Include natural user-facing synonyms such as 'flowchart', 'process diagram', or 'pipeline diagram' alongside 'workflow diagram' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Create...workflow diagrams as high-quality PNG images', 'Renders beautiful HTML diagrams with connected nodes, arrows, and labels', 'screenshots them for sharing' — clearly above the 'names domain and some actions' anchor at 2.	3 / 3
Completeness	Clearly answers 'what does this do' but provides no explicit 'Use when...' trigger clause, so per the guidelines completeness is capped at 2 rather than reaching the explicit-trigger anchor at 3.	2 / 3
Trigger Term Quality	Contains relevant terms like 'workflow diagrams', 'HTML diagrams', 'nodes, arrows, and labels', 'screenshots', and 'PNG', but lacks the natural user-spoken trigger phrasing and common variations (e.g., 'flowchart', 'process diagram') that would warrant a 3.	2 / 3
Distinctiveness Conflict Risk	The 'FigJam/Miro-style workflow diagrams as high-quality PNG images' niche is distinct and unlikely to trigger for unrelated skills, matching the clear-niche anchor at 3 rather than the overlap-prone anchor at 2.	3 / 3
	Total	10 / 12 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: 8866b2a

Reviewed: 1 day 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.