CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

big-pics-little-words

Explain the current subject in HTML with large visuals and minimal text while preserving key details.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/big-pics-little-words/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 body is a compact, well-ordered instruction block that respects token budget and gives a model enough to produce the artifact — format, style, imagery, and audience rules are all concrete. Its weaknesses are minor: slight redundancy, no example or template of the target output, and no self-check that key details survived the 'little words' compression.

Suggestions

Trim the double-hedge "as needed but only selectively when it makes sense" to a single phrase like "use real-world imagery sparingly, only where it clarifies".

Add a compact example or skeleton of the target layout (e.g. a minimal HTML structure with one hero visual and a few terse captions) so the deliverable's shape is unambiguous.

Add a self-check step such as "before finishing, confirm every key detail of the subject is represented visually or in text" to verify the no-withholding constraint.

DimensionReasoningScore

Conciseness

The body is lean with no explanation of concepts Claude already knows, but minor instances could be trimmed: the first two sentences ("Use HTML to help me understand what we're discussing" / "Show me with big pictures and little words") overlap, and "as needed but only selectively when it makes sense" double-hedges a single point. This fits 'efficient; minor instances that could be trimmed' rather than the 'every token earns its place' anchor above.

4 / 5

Actionability

The guidance is concrete and specific for an instruction-only skill — output format (HTML), visual/text balance, imagery selection rule, prose style ("clear, concise/terse, and avoid jargon"), and audience ("as if the viewer is new here"). Minor gaps keep it below fully executable: no example or skeleton of the target layout, and no guidance on sourcing the "real-world pictures/icons/visuals".

4 / 5

Workflow Clarity

As a single-task skill the action is clear (produce an HTML visual explanation of the current subject), but it falls just short of the simple-skill 'unambiguous single action' bar: "without withholding key details" states a constraint with no verification cue, and "only selectively when it makes sense" delegates sequencing judgment without a checkpoint. This is a non-destructive generative task, so the validation cap does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (no references/, scripts/, or assets/ exist in the bundle), and its five lines are coherently ordered (format, style, imagery, prose rules). Per the guidelines, an under-50-line skill with no need for external references scores 5 on organization alone.

5 / 5

Total

17

/

20

Passed

Description

50%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 states a single clear capability in third person without fluff, but it omits any 'when to use' trigger guidance and offers only one composite action rather than concrete coverage of what the skill does. It reads as a mid-tier description: clear what, missing when, moderate trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to explain, visualize, or diagram a topic — especially with phrases like "show me", "help me understand", or "explain it visually".'

Enumerate the concrete actions involved so the scope is comprehensive: identify the subject's key details, then build an HTML page with large visuals, minimal text, and selective real-world imagery/icons.

Sharpen distinctiveness by naming the output form (a single self-contained HTML explainer) to separate it from generic diagramming or dashboard skills.

DimensionReasoningScore

Specificity

The description names the domain ("Explain the current subject in HTML") and one composite action with manner and constraint modifiers ("large visuals and minimal text while preserving key details"), but it does not list several concrete actions — closer to the '1-2 concrete actions, not comprehensive' anchor than the 'several specific actions' anchor above.

3 / 5

Completeness

The 'what' is clear (an HTML visual explanation preserving key details), but there is no 'Use when...' clause or equivalent trigger guidance — 'the current subject' only weakly implies context. Per the guidelines a missing 'when' clause caps completeness at 3, so it cannot reach the both-what-and-when anchors above.

3 / 5

Trigger Term Quality

It contains some relevant keywords ("HTML", "visuals", "minimal text", "Explain") but misses natural phrases and synonyms users would actually say ("diagram", "visualize", "illustration", "show me with pictures") and no trigger guidance exists — matching 'some relevant keywords but missing common variations or synonyms' rather than the 'good keyword coverage' anchor above.

3 / 5

Distinctiveness Conflict Risk

The niche (large-visual, minimal-text HTML explanations) is somewhat specific, but it could overlap with diagramming, visualization, and documentation skills, and without trigger phrases there is nothing to disambiguate invocation — fitting 'somewhat specific but could still overlap' rather than 'mostly distinct with minor overlap risk'.

3 / 5

Total

12

/

20

Passed

Validation

100%

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

plannotator/effective-html

Path

skills/big-pics-little-words/SKILL.md

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.