project-infographic
Generate a visually beautiful HTML infographic showing high-level project overview for sprint demos. Use when preparing presentations, stakeholder updates, or visual project summaries.
70
54%
Does it follow best practices?
Impact
99%
1.57xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/project-infographic/SKILL.mdQuality
Discovery
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 functional and covers both what and when, earning strong marks for completeness. However, it lacks specificity about what the infographic contains (metrics, charts, timelines, team progress?) and could include more natural trigger terms users might use. The distinctiveness is moderate—it could conflict with general presentation or dashboard-generation skills.
Suggestions
Add specific concrete actions or elements the infographic includes, e.g., 'showing milestones, team velocity, completion metrics, and key deliverables'.
Expand trigger terms to include common variations like 'dashboard', 'sprint review', 'progress report', 'project status', 'visual report', or 'demo prep'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (HTML infographic for project overview) and one main action (generate), but doesn't list multiple concrete actions like what specific elements are included (charts, timelines, metrics, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (generate a visually beautiful HTML infographic showing high-level project overview for sprint demos) and 'when' (use when preparing presentations, stakeholder updates, or visual project summaries) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'infographic', 'sprint demos', 'presentations', 'stakeholder updates', and 'project summaries', but misses common variations users might say such as 'dashboard', 'project status', 'sprint review', 'progress report', or 'visual report'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'HTML infographic' and 'sprint demos' provides some distinctiveness, but terms like 'presentations' and 'stakeholder updates' could overlap with general presentation or reporting skills. The 'project overview' framing is somewhat broad. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable and concrete guidance for generating HTML infographics, with specific code examples, design tokens, and clear section requirements. However, it is severely over-engineered in length — the extensive CSS and HTML template code bloats the skill far beyond what Claude needs, and the lack of any progressive disclosure or external file references means all this detail competes for context window space. Adding validation steps and splitting templates into referenced files would significantly improve this skill.
Suggestions
Extract the CSS design tokens, example HTML architecture structure, and CSS patterns into separate referenced files (e.g., `templates/design-tokens.css`, `templates/architecture-example.html`) and reference them from the main skill.
Remove or drastically condense the CSS/HTML examples — Claude knows how to write CSS hover effects, flexbox layouts, and gradient backgrounds. Focus on the unique constraints (section order, audience, visual density) rather than implementation details.
Add a validation step after generating the HTML, such as verifying the file was created, checking that all required sections are present, and confirming that referenced project information actually exists in the codebase.
Condense the 'Architectural Diagram Style' section to a brief description of the desired visual outcome (system boundary, flow nodes, branch visualization) without providing full CSS implementations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It includes extensive CSS code examples, HTML structure examples, and detailed design system tokens that Claude could generate on its own. The architectural diagram section alone is massive and largely unnecessary — Claude knows how to write CSS and HTML. Much of this could be condensed to a brief template description with key constraints. | 1 / 3 |
Actionability | The skill provides fully concrete, executable guidance: specific file paths to scan, exact CSS design tokens, complete HTML structure examples, specific output file locations, and clear section requirements. Everything is copy-paste ready and leaves no ambiguity about what to produce. | 3 / 3 |
Workflow Clarity | The scan process (steps 1-4) is clearly sequenced, and the output sections are well-defined. However, there are no validation checkpoints — no step to verify the generated HTML renders correctly, no feedback loop for checking accuracy against actual codebase, and no verification that the output file was saved successfully. For a skill that generates artifacts from codebase scanning, validation of accuracy is important. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The extensive CSS examples, HTML structure templates, and architectural diagram patterns could easily be split into separate reference files (e.g., DESIGN_TOKENS.md, ARCHITECTURE_TEMPLATE.html). Everything is inlined, making the skill unnecessarily long and hard to navigate. | 1 / 3 |
Total | 7 / 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
- 0xrabbidfly/eric-cartman
- Commit
a5309ae
- 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.