CtrlK
BlogDocsLog inGet started
Tessl Logo

css-print

Use when reviewing stylesheets, component styles, and responsive behavior related to Include a print stylesheet. Check the rendered layout across breakpoints and interaction states before proposing a fix.

55

Quality

62%

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/css-print/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The content is well-structured with a clean progressive-disclosure reference to a real bundle file, but it leans descriptive rather than instructive: it explains concepts Claude already knows and lacks an executable CSS example or an explicit validation checkpoint. Adding a concrete @media print example and a sharper check-fix loop would raise the weaker dimensions.

Suggestions

Replace the conceptual intro and the 'Explain' section (which restate what Claude already knows) with lean, actionable guidance.

Add an executable @media print CSS example block so the Fix section is copy-paste ready instead of prose-only bullets.

Turn the Check→Fix sequence into an explicit checklist with a validation checkpoint, e.g. 'Print-preview the page and confirm nav/ads are hidden before finishing.'

DimensionReasoningScore

Conciseness

The body is mostly lean with concise Quick Reference bullets, but the conceptual intro ('saves ink and improves accessibility') and the 'Explain' section restate knowledge Claude already has and could be tightened away.

2 / 3

Actionability

The Quick Reference gives concrete techniques ('Use @media print', '.no-print', 'serif fonts at 12pt'), but the body contains no executable CSS code block and the Fix section is prose ('Create a print stylesheet that removes unnecessary elements...') rather than copy-paste-ready guidance.

2 / 3

Workflow Clarity

The Check then Fix sequence is present with a verification flavor, but 'Check' reads as a description rather than an explicit checkpoint and there is no feedback loop, so it sits at the 'steps listed but checkpoints implicit' anchor.

2 / 3

Progressive Disclosure

The body is a well-organized overview with clearly labeled sections and a single, well-signaled one-level-deep reference ('For full implementation details... see references/rule.md'), and that file exists in the bundle.

3 / 3

Total

9

/

12

Passed

Description

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 covers both what and when with an explicit 'Use when' trigger, but its quality is dragged down by a garbled embedded rule title, second-person imperative voice, and broad framing that blurs its print-stylesheet niche. Rewriting in third person with cleaner, more natural print triggers would lift the weaker dimensions.

Suggestions

Rewrite in third person and lead with what the skill does ('Reviews print stylesheets and responsive behavior...') instead of the imperative 'Check the rendered layout...' to avoid the voice penalty.

Fix the garbled phrase 'responsive behavior related to Include a print stylesheet' and surface natural print triggers such as 'print CSS', 'print styles', and 'printing the page'.

Sharpen the niche so the description is clearly about print stylesheets rather than broad CSS/responsive review, reducing overlap with general CSS-review skills.

DimensionReasoningScore

Specificity

It names the domain and several concrete actions ('reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states before proposing a fix'), but the imperative 'Check the rendered layout...' is second-person voice, so the specificity score is reduced by one per the rubric guideline.

2 / 3

Completeness

It explicitly answers both what (review/check/fix print-stylesheet behavior) and when via an explicit 'Use when reviewing stylesheets...' trigger clause, matching the anchor that requires both with explicit triggers.

3 / 3

Trigger Term Quality

Relevant keywords are present ('stylesheets', 'responsive behavior', 'breakpoints', 'interaction states', 'print stylesheet'), but the core print trigger is awkwardly embedded in the garbled phrase 'related to Include a print stylesheet' and common variations like 'print CSS' or 'printing the page' are missing.

2 / 3

Distinctiveness Conflict Risk

The print-stylesheet niche is somewhat specific, but the broad 'reviewing stylesheets, component styles, and responsive behavior' framing overlaps with general CSS/responsive-review skills and could trigger for the wrong skill.

2 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.