CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

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

63%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 lean, well-sectioned overview that correctly delegates ~1000 lines of implementation detail to a single clearly-signaled reference file, achieving exemplary progressive disclosure. Its weaknesses are redundancy — Check, Fix, and Explain paraphrase the same guidance — and the absence of any executable code or concrete violation example in the body itself.

Suggestions

Collapse the Check, Fix, and Explain sections, which paraphrase the same "optimize typography / ensure readability" guidance three times, into one concrete checklist plus one fix step.

Inline one minimal executable example (e.g., a short @media print block using .no-print and 12pt serif) so the body is self-sufficient for the common case instead of deferring all code to the reference.

Add a concrete flagged-violation example in the Code Review section — a selector, why it violates the rule, and the exact change — to make the review instruction executable.

DimensionReasoningScore

Conciseness

The intro sentence ("Print stylesheets ensure content is readable when printed—removing digital clutter and optimizing for paper saves ink and improves accessibility") explains a concept Claude already knows, and the Check, Fix, and Explain sections each paraphrase the same "optimizes typography / ensures readability" idea. Mostly efficient but with noticeable repetition — anchor 3, not 4, since the redundancy across three sections is more than minor.

3 / 5

Actionability

The Quick Reference gives concrete techniques ("Use @media print", "Hide navigation, ads, and interactive elements with .no-print", "Use serif fonts at 12pt and optimize page breaks"), but the Check and Fix sections are abstract direction ("Verify that a print stylesheet is provided and properly optimized...") and the body contains no executable CSS snippet. Anchor 3 — concrete guidance present but incomplete; not 4 because nothing in the body is copy-paste executable.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review forms a clear sequence for this single-purpose review skill, with a concrete checking step ("Flag exact selectors, declarations, or breakpoints that violate the rule in the rendered UI"). Minor gap: no verification of a proposed fix, and the relationship between Check, Code Review, and Fix is not crisply ordered — anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body is a lean, well-sectioned overview that defers bulk detail via a clearly signaled, one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), and that file actually exists with the 996 lines of detail. This matches anchor 5: clear overview, appropriate split, easy navigation.

5 / 5

Total

15

/

20

Passed

Description

75%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 answers both what and when with several concrete actions and natural CSS-review vocabulary, but the mid-sentence embedding of the rule title ("related to Include a print stylesheet") makes the phrasing garbled, and it omits print-specific trigger terms like "@media print" or "print styles". All dimensions land just below the top anchor.

Suggestions

Rewrite to remove the embedded rule title, e.g.: "Review stylesheets for print-specific rules (@media print blocks, .no-print handling, page breaks, print typography). Use when reviewing CSS print styles, print stylesheets, or @media print rules."

Add natural trigger synonyms such as "@media print", "print styles", "print CSS", and "when printing" so users' phrasing matches the description.

State the what and the when as separate, crisp clauses so the trigger condition is unambiguous rather than tangled into one sentence.

DimensionReasoningScore

Specificity

Names several concrete actions — "reviewing stylesheets, component styles, and responsive behavior" and "Check the rendered layout across breakpoints and interaction states before proposing a fix" — but coverage stays generic rather than naming print-specific techniques, matching anchor 4 rather than 5; above anchor 3 because more than 1-2 actions are listed.

4 / 5

Completeness

Both parts are explicit: "Use when reviewing stylesheets... related to Include a print stylesheet" (when) and "Check the rendered layout across breakpoints and interaction states before proposing a fix" (what). The embedded rule title garbles the trigger phrasing, keeping it below anchor 5's crisp concrete triggers; it is above anchor 3 because the "when" is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Natural review vocabulary is present ("stylesheets", "print stylesheet", "responsive behavior", "breakpoints", "component styles"), but common variations users would say — "@media print", "print styles", "when printing" — are absent, fitting anchor 4 (good coverage, a few natural terms missing) rather than 5.

4 / 5

Distinctiveness Conflict Risk

Print-stylesheet review is a fairly distinct niche, but broad phrases like "component styles, and responsive behavior" and "breakpoints" create minor overlap risk with general CSS or responsive-design review skills — anchor 4, not 5 since non-print CSS review tasks could also match.

4 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/css-print/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.