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.

63

Quality

75%

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

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 well-organized, token-efficient overview that delegates detail to a single clearly-signaled reference file, with concrete actionable directives in the Quick Reference and a sensible review workflow.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows, but the Check/Fix/Explain sections restate near-identical ideas in a templated way that could be tightened further.

4 / 5

Actionability

Quick Reference gives concrete directives ('.no-print', 'serif fonts at 12pt', 'optimize page breaks', 'Show full URLs for external links'); executable code lives in the reference file, leaving only minor gaps inline.

4 / 5

Workflow Clarity

Clear sectioned structure (Check/Fix/Explain/Code Review) for a simple, non-destructive review skill; no explicit validation checkpoints, but none are required for this single-purpose task.

4 / 5

Progressive Disclosure

A concise overview with a single clearly-signaled one-level-deep reference ('see references/rule.md') for full implementation details, code examples, and framework-specific guidance.

5 / 5

Total

17

/

20

Passed

Description

71%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 clearly answers both what and when with an explicit 'Use when' clause and several concrete actions, but the trigger phrasing is templated around the rule title and the leading scope is broad enough to risk overlap with sibling CSS review skills.

Suggestions

Lead the trigger with natural print-specific phrasing (e.g., 'Use when the user mentions printing web pages, print stylesheets, or @media print') instead of embedding the rule title.

Narrow the opening scope so the skill is clearly about print stylesheets rather than general stylesheet/responsive review.

Add print-specific trigger synonyms ('print CSS', '@media print', 'print-friendly') to improve keyword coverage and distinctiveness.

DimensionReasoningScore

Specificity

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'), with only minor coverage gaps.

4 / 5

Completeness

Both what (review/check rendered layout across breakpoints and states, propose a fix) and when (explicit 'Use when reviewing stylesheets...') are present, but the 'when' is templated around the rule title rather than concrete user trigger phrases.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('stylesheets', 'responsive behavior', 'breakpoints', 'interaction states'), though it awkwardly embeds the rule title 'Include a print stylesheet' instead of using natural print-related phrasings.

4 / 5

Distinctiveness Conflict Risk

The print-stylesheet niche is distinct, but the description leads with broad 'reviewing stylesheets, component styles, and responsive behavior' language that could overlap with general CSS/responsive review skills.

3 / 5

Total

15

/

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.

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.