storytelling

Narrative-driven design using visuals, copy, and interaction to guide users through engaging, emotionally resonant journeys.

Quality

71%

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/storytelling/SKILL.md

Quality

Content

92%

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

The body is a well-structured, lean, and actionable guideline-authoring skill with a clear workflow and validation gates. Its main weakness is that everything lives inline in one file with no progressive disclosure.

Suggestions

Split the detailed style tokens, component rule expectations, and QA checklist into a referenced file (e.g., references/tokens.md or references/component-rules.md) so SKILL.md stays an overview.

Add clearly signaled one-level-deep links for the larger sections to keep the entry file navigable.

Fix the grammatically broken Brand sentence ('a narrative techniques to create...') so it reads cleanly as a concise brand statement.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet lists and concrete tokens (hex colors, font weights, spacing scale) with no explanation of concepts Claude already knows; only the awkward Brand sentence is mildly padded.	3 / 3
Actionability	It gives concrete, specific guidance — design tokens, required states, a required output structure, and explicit constraint language ('must'/'should') — which is actionable for an instruction-only skill.	3 / 3
Workflow Clarity	A numbered 6-step Guideline Authoring Workflow is paired with Quality Gates and a QA checklist, providing a clear sequence with validation checkpoints.	3 / 3
Progressive Disclosure	The sections are well-organized, but the skill is monolithic with no bundle files or one-level-deep references, and content like detailed tokens and component rules is all inline.	2 / 3
	Total	11 / 12 Passed

Description

50%

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 clear and third-person, naming a coherent domain and medium, but it stops short of listing concrete actions or providing an explicit use-when trigger. It is solid but not comprehensive.

Suggestions

Add a 'Use when...' clause naming the situations users would mention (e.g., 'Use when authoring storytelling-driven UI, brand narrative, or emotionally resonant onboarding flows').

Replace the abstract 'guide users through engaging, emotionally resonant journeys' with concrete actions (e.g., 'structure narrative flows, sequence onboarding steps, and pair copy with visuals').

Include natural trigger variations such as 'storytelling', 'narrative design', 'brand story', and 'emotional UX' to improve discovery and distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain and some elements ("visuals, copy, and interaction") plus an action ("guide users through...journeys"), but does not list multiple concrete actions like the anchor-3 example does.	2 / 3
Completeness	The "what" is stated clearly, but there is no "Use when..." or equivalent explicit trigger clause, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	"Narrative-driven design" is a natural term, but coverage lacks common variations (e.g., "storytelling", "brand narrative") and "emotionally resonant journeys" reads as buzzwordy rather than user-spoken.	2 / 3
Distinctiveness Conflict Risk	"Narrative-driven design" carves out a niche but, without explicit triggers, it could still overlap with general design or branding skills.	2 / 3
	Total	8 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/storytelling/SKILL.md
Commit: f631a09

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.