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.

Install with Tessl CLI

npx tessl i github:0xrabbidfly/eric-cartman --skill project-infographic

What are skills?

1.57x

Quality

72%

Does it follow best practices?

Impact

99%

1.57x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./.github/skills/project-infographic/SKILL.md

SKILL.md

Review

Evals

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.

This description has good structure with explicit 'Use when' guidance, making the completeness strong. However, it lacks specificity in concrete actions beyond 'generate' and could benefit from more natural trigger terms users would actually say. The distinctiveness is moderate due to overlap potential with general presentation tools.

Suggestions

Add specific concrete actions like 'displays sprint metrics, team velocity, milestone progress, and deliverable status'

Expand trigger terms to include variations like 'sprint review', 'project status', 'demo prep', 'progress report', 'project dashboard'

Dimension	Reasoning	Score
Specificity	Names the domain (HTML infographic, project overview) and one action (generate), but lacks comprehensive concrete actions like 'display metrics', 'show timeline', 'visualize dependencies'. The phrase 'visually beautiful' is somewhat vague.	2 / 3
Completeness	Clearly answers both what ('Generate a visually beautiful HTML infographic showing high-level project overview') and when ('Use when preparing presentations, stakeholder updates, or visual project summaries') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'sprint demos', 'presentations', 'stakeholder updates', 'project summaries', but misses common variations users might say like 'project status', 'demo prep', 'sprint review', 'project dashboard', or 'progress report'.	2 / 3
Distinctiveness Conflict Risk	The 'sprint demos' and 'project overview' focus provides some distinction, but 'presentations' and 'visual summaries' are broad enough to potentially conflict with general presentation or visualization skills.	2 / 3
	Total	9 / 12 Passed

Implementation

77%

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

This is a well-structured, highly actionable skill for generating stakeholder-friendly infographics. Its strengths are concrete code examples and clear workflow steps. However, it's verbose for a skill file—the extensive CSS/HTML templates inflate token usage and could be externalized for better progressive disclosure.

Suggestions

Extract the CSS design tokens and HTML architecture examples into a separate `INFOGRAPHIC_TEMPLATES.md` file and reference it from the main skill

Remove the 'Sample Invocation Phrases' section—Claude doesn't need trigger phrase examples

Condense the 'Target Audience' section to a single line; Claude understands stakeholder communication needs

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some unnecessary explanation (e.g., explaining what stakeholders want, listing sample invocation phrases). The extensive CSS examples and HTML templates, while useful, could be more condensed or referenced externally.	2 / 3
Actionability	Provides fully executable CSS and HTML code examples that are copy-paste ready. Clear scan locations, specific file paths, and concrete design tokens make this highly actionable for generating infographics.	3 / 3
Workflow Clarity	Clear 4-step scan process (Purpose → Flow → Status → Tech Stack) followed by structured output sections. The workflow is well-sequenced with explicit locations to scan and a defined output structure with required sections.	3 / 3
Progressive Disclosure	Content is reasonably organized with clear section headers, but the skill is monolithic at ~300 lines. The extensive CSS/HTML examples could be split into a separate reference file, with SKILL.md providing just the overview and linking to detailed templates.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 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

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.