Infographic Outline Creator - Auto-activating skill for Visual Content. Triggers on: infographic outline creator, infographic outline creator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/infographic-outline-creator/SKILL.mdQuality
Discovery
7%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 is a very weak description that essentially just restates the skill name and category without providing any meaningful detail about capabilities, actions, or usage triggers. The trigger terms are duplicated and lack natural language variations. It reads as an auto-generated placeholder rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates structured infographic outlines with sections, data points, visual hierarchy suggestions, and layout recommendations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to plan an infographic, create a visual summary, outline data for a poster, or structure information for visual presentation.'
Remove the duplicated trigger term and expand with natural variations users might say, such as 'infographic', 'visual outline', 'data visualization plan', 'infographic structure', 'poster layout'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Infographic Outline Creator') and its category ('Visual Content') but does not describe any concrete actions like creating layouts, structuring sections, selecting data points, or organizing visual hierarchies. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' guidance. The 'Triggers on' line is just a duplicated skill name, not meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('infographic outline creator, infographic outline creator'). It lacks natural user phrases like 'infographic', 'visual summary', 'data visualization outline', 'infographic layout', or 'design outline'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'infographic outline' is somewhat specific and wouldn't overlap heavily with most other skills, but the lack of detail about what it actually does and the broad 'Visual Content' category label could cause confusion with other visual/design skills. | 2 / 3 |
Total | 5 / 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 an empty placeholder with no substantive content. It consists entirely of generic boilerplate descriptions that could apply to any skill, with no actual guidance on creating infographic outlines—no templates, examples, steps, or concrete instructions of any kind.
Suggestions
Add a concrete infographic outline template or structure (e.g., sections like Title, Key Statistics, Flow/Process, Call to Action) with specific examples of each section.
Provide actionable step-by-step workflow: e.g., 1. Define the topic and audience, 2. Identify 3-5 key data points, 3. Choose a layout type (timeline, comparison, process), 4. Draft section content, 5. Validate data accuracy.
Include at least one complete example showing an input topic and the resulting infographic outline output.
Remove all generic boilerplate ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual domain-specific instructions that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and boilerplate. It explains what the skill does in vague, repetitive terms without providing any actual actionable content. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of infographic outlines, no templates, no specific steps. The skill describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely claims it 'provides step-by-step guidance' without actually containing any steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of overview from detailed content. There are no bundle files to reference either. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
3a2d27d
Table of Contents
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.