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.

1.57x

Quality

70%

Does it follow best practices?

Impact

99%

1.57x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/project-infographic/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

The content is highly actionable with concrete templates and a clear scan-to-output workflow, but it is verbose and monolithic — large code templates and restated rules are inlined rather than split into reference files. No bundle files are present to support progressive disclosure.

Suggestions

Move the large architectural-diagram CSS and HTML templates into a reference file (e.g. references/architecture-template.html) and link to it from SKILL.md to improve both conciseness and progressive_disclosure.

Remove the 'Sample Invocation Phrases' section and the restated 'Important Rules' list, since both duplicate guidance already given in 'When to Use This Skill' and the section specifications.

Trim the soft over-claim wording ('visually beautiful', 'premium') and consolidate the duplicated design-token and node-styling CSS into a single block to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sectioning, but it inlines ~100 lines of CSS and a large HTML template, restates guidance in 'Important Rules', and duplicates triggers in 'Sample Invocation Phrases' — several padded sections could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready, fully executable guidance: concrete CSS design tokens, a complete HTML structure template, a required-sections checklist, and explicit output file locations covering the common case.	5 / 5
Workflow Clarity	A clear sequenced scan process (Understand Purpose → Map Flow → Gather Status → Identify Tech Stack → Output) with an 'ACCURATE: cross-reference with actual code/docs' checkpoint; minor validation gaps but no destructive/batch operation requiring a validate-fix-retry loop.	4 / 5
Progressive Disclosure	Good header/numbered-step structure exists, but the large architecture CSS/HTML templates that clearly belong in separate reference files are inlined and no bundle files or one-level-deep references are used at all.	3 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%Scale 1-5

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, uses appropriate imperative/third-person voice, and answers both what and when with natural trigger terms. It is held back by a single concrete action, mild over-claim wording, and trigger terms that are slightly generic.

Dimension	Reasoning	Score
Specificity	Names the domain ('HTML infographic', 'high-level project overview') and one concrete action ('Generate a visually beautiful HTML infographic'), but coverage is a single action rather than comprehensive; 'visually beautiful' is mild over-claim fluff.	3 / 5
Completeness	Explicitly answers both 'what' (generate HTML infographic showing project overview) and 'when' (Use when preparing presentations, stakeholder updates, or visual project summaries); the 'when' is explicit but the trigger phrasing is somewhat generic rather than sharply concrete.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('preparing presentations', 'stakeholder updates', 'visual project summaries', 'sprint demos') with good keyword coverage; a few synonyms (e.g. 'demo slide', 'executive summary') are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (project-overview infographics for sprint demos) with distinct triggers, but broad terms like 'presentations' and 'visual project summaries' create minor overlap risk with general presentation/summary skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: 0xrabbidfly/eric-cartman
Path: .github/skills/project-infographic/SKILL.md
Commit: 0b8453f

Reviewed: 5 days 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.