storyboard

Create a six-frame storyboard that shows a user's journey from problem to solution. Use when you need a fast narrative for alignment, concept reviews, or demos.

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/storyboard/SKILL.md

Quality

Content

56%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 and well-sequenced with a validation loop, but it is held back by noticeable redundancy (a verbatim Purpose restatement and the Sarah example worked multiple times) and dangling references to non-existent bundle files.

Suggestions

Deduplicate the Sarah/invoices example: keep one full worked version (or move it to examples/sample.md) and reference it rather than repeating it across Steps 3-4, Examples, and Pitfalls.

Remove the verbatim restatement of the frontmatter intent in the Purpose section, or replace it with only the non-obvious 'not a UI mockup' framing.

Either create the referenced template.md and examples/sample.md files or remove the references so navigation is not broken.

Dimension	Reasoning	Score
Conciseness	The Purpose section restates the frontmatter intent verbatim and the same Sarah/invoices example is fully worked twice (Step 3 narrative and Step 4 visuals), re-excerpted in Examples, and reused across Pitfalls, plus a 'Why This Works' benefits list — several padded or redundant sections rather than just minor tightening.	2 / 5
Actionability	Concrete, actionable guidance throughout — a named 6-frame structure, 7 specific questions, a fill-in template with a fully worked example, per-frame visual guidance, and a test checklist — with only the minor gap of dangling template.md/examples/sample.md references.	4 / 5
Workflow Clarity	A clear 5-step sequence with an explicit validation checklist in Step 5 ("If any answer is 'no,' revise") and a Step-1 'don't fabricate' checkpoint; validation is concentrated at the end rather than per-step, leaving minor checkpoint gaps.	4 / 5
Progressive Disclosure	Headers and section organization are clear, but the body references template.md and examples/sample.md that do not exist as bundle files (dangling references) and inlines a full worked example that the skill itself says belongs in a separate file.	3 / 5
	Total	13 / 20 Passed

Description

73%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 strong description that clearly states both capability and an explicit 'Use when' trigger with concrete contexts, though the second-person phrasing and single-action specificity slightly limit its score.

Suggestions

Rewrite the trigger clause in third person (e.g., 'Use when the user needs a fast narrative...') to avoid the second-person specificity penalty.

Add 1-2 more concrete actions or synonyms (e.g., 'pitch a feature,' 'communicate vision') to broaden specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the storyboard domain and one concrete action ("Create a six-frame storyboard that shows a user's journey from problem to solution"), matching the anchor-3 base of '1-2 concrete actions'; the trigger clause's second-person voice ("Use when you need...") triggers the rubric's mandatory -1 specificity penalty, bringing it to 2.	2 / 5
Completeness	It explicitly answers both what ("Create a six-frame storyboard...") and when ("Use when you need a fast narrative for alignment, concept reviews, or demos") with concrete trigger phrases, matching the score-5 anchor and avoiding the missing-trigger cap of 3.	5 / 5
Trigger Term Quality	The trigger clause surfaces several natural terms a user would say ("fast narrative," "alignment," "concept reviews," "demos"), giving good keyword coverage, though synonyms like "pitch" or "stakeholder alignment" are missing.	4 / 5
Distinctiveness Conflict Risk	The six-frame problem-to-solution storyboard is a distinct niche with mostly-distinct triggers, but terms like 'alignment' and 'demos' overlap with sibling PM-artifact skills, leaving minor conflict risk.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/storyboard/SKILL.md
Commit: a03af68

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