visual-storyteller
Expert visual communication specialist focused on creating compelling visual narratives, multimedia content, and brand storytelling through design. Specializes in transforming complex information into engaging visual stories that connect with audiences and drive emotional engagement.
19
0%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./design-visual-storyteller/skills/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is almost entirely composed of marketing buzzwords and abstract language without any concrete actions, specific deliverables, or explicit trigger conditions. It fails to tell Claude what the skill actually does in practical terms and when to select it, making it nearly useless for skill selection among a pool of available skills.
Suggestions
Replace abstract phrases like 'compelling visual narratives' and 'emotional engagement' with concrete actions such as 'create infographics, design social media graphics, build presentation slides, produce brand style guides.'
Add an explicit 'Use when...' clause with natural trigger terms users would actually say, e.g., 'Use when the user asks to design infographics, create visual content, make diagrams, or build branded graphics.'
Narrow the scope to a clear niche to reduce conflict risk — specify the exact output formats or tools involved (e.g., SVG diagrams, HTML/CSS layouts, slide decks) rather than covering all of 'visual communication.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'compelling visual narratives,' 'multimedia content,' and 'brand storytelling through design' without listing any concrete actions. There are no specific operations like 'create infographics,' 'design slide decks,' or 'produce social media graphics.' | 1 / 3 |
Completeness | The description vaguely addresses 'what' with abstract language but never answers 'when' — there is no 'Use when...' clause or any explicit trigger guidance. Both the what and when are very weak. | 1 / 3 |
Trigger Term Quality | The description is filled with buzzwords ('visual narratives,' 'emotional engagement,' 'brand storytelling') that users would rarely use in natural requests. Users would more likely say things like 'make an infographic,' 'design a poster,' or 'create a presentation' — none of which appear here. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic and could overlap with branding skills, presentation skills, design skills, content creation skills, or data visualization skills. There is no clear niche or distinct trigger to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a persona definition rather than an actionable skill document. It is extremely verbose, repeating similar concepts across multiple sections (mission, capabilities, advanced capabilities) without providing any concrete, executable guidance. The content describes what a 'Visual Storyteller' is rather than instructing Claude on how to perform specific visual storytelling tasks, and the arbitrary success metrics and personality traits waste significant token budget.
Suggestions
Replace the persona/identity sections with concrete, actionable instructions: specific templates for storyboards, example outputs for visual narrative plans, and executable code for generating visual assets.
Eliminate redundant sections (Core Mission, Core Capabilities, and Advanced Capabilities heavily overlap) and consolidate into a single concise workflow with clear steps and validation checkpoints.
Add concrete examples of inputs and expected outputs, such as a sample brief transformed into a storyboard outline or a data set transformed into a visualization specification.
Remove arbitrary success metrics (50% engagement increase, 35% brand recognition) and personality descriptions that don't help Claude execute tasks, and use that space for actionable reference material or links to detailed guides.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive sections that explain concepts Claude already knows (what a story arc is, what narrative structure means, basic platform descriptions). The 'success metrics' with arbitrary percentages, personality descriptions, and identity sections are padding that consume tokens without adding actionable value. | 1 / 3 |
Actionability | Almost entirely abstract and descriptive rather than instructive. The bash commands in the workflow are generic file reads with no real executable guidance. There are no concrete examples of actual visual storytelling outputs, no templates, no specific code or commands for creating anything. Bullet points describe capabilities rather than providing actionable instructions. | 1 / 3 |
Workflow Clarity | The 4-step workflow is vague and lacks any validation checkpoints or feedback loops. Steps like 'Define story arc and emotional journey' and 'Develop storyboards and visual concepts' are abstract descriptions with no concrete actions, no verification steps, and no error recovery guidance. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files for detailed content. Everything is inline in one massive document with repetitive sections (Core Capabilities, Advanced Capabilities, and Core Mission all overlap significantly). The self-reference at the end ('Your detailed methodology is in this agent definition') is circular. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- Reviewed
Table of Contents
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.