Name: testland/print-stylesheet-tests
Rating: 70.39999999999999 (1 reviews)
Author: testland

testland/print-stylesheet-tests

Test CSS print-media output via Playwright `page.emulateMedia({ media: 'print' })` + `page.pdf()` - `@page` rule (size, margin, orphans, widows), `@page :first / :left / :right` pseudo-classes, `break-before/after/inside`, `@media print` selector activation, page-break suppression on headings. Use when an app exposes a Print button or a print stylesheet exists but is untested, and users report the printed or PDF copy breaking in the wrong places while the on-screen page looks fine.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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.

A well-structured, actionable, and clearly sequenced skill body with strong validation and a genuine feedback loop in the worked example. Its weak spots are repeated explanations of known behavior and assertions that rely on undefined helper utilities.

Suggestions

Replace or define the placeholder helper functions (getPdfPageCount, extractTextPerPage, renderPdfPage, getPdfMargins, etc.) with concrete implementations or point to the specific PDF-inspector library that provides them, so examples are copy-paste ready.

Trim the repeated explanations of printBackground's default and the CSS-vs-API precedence rule to a single authoritative mention, removing the conceptual MDN lead-in that Claude already knows.

Resolve the references/cross-engine-regression.md citation: either add the file to this skill's references/ bundle or reword the pointer to make clear it lives in the pdf-snapshot-tester sister skill.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and code-forward, but it restates known behaviors (printBackground default, CSS-vs-API precedence) across the intro, per-step notes, and anti-patterns, plus a conceptual MDN lead-in — minor over-explanation that could be trimmed.	4 / 5
Actionability	Real, executable Playwright calls and CSS snippets are provided, but the assertions depend on undefined helper utilities (getPdfPageCount, extractTextPerPage, renderPdfPage, hasLetterhead, etc.) that are not built-ins, so the code is mostly but not fully copy-paste ready.	4 / 5
Workflow Clarity	A clear 7-step 'How to use' sequence pairs with per-step assertion-based validation, and the 'Worked example' gives an explicit fail -> diagnose -> fix -> re-run feedback loop, matching the anchor for explicit validation and error-recovery loops.	5 / 5
Progressive Disclosure	Content is well-sectioned and one level deep, correctly offloading @page pseudo-classes/margins to references/page-geometry.md (which exists), but references/cross-engine-regression.md is cited yet not present in this skill's bundle, a minor navigation gap.	4 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong, specific, third-person description that clearly states both what the skill does and when to use it, with concrete trigger phrasing tied to real symptoms. Keyword/synonym enumeration is the only minor gap.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete, specific actions/areas (emulateMedia, page.pdf, @page size/margin/orphans/widows, @page pseudo-classes, break-before/after/inside, @media print activation, page-break suppression), matching the comprehensive-coverage anchor.	5 / 5
Completeness	It explicitly answers both 'what' (test CSS print-media output via specific Playwright + @page features) and 'when' (app exposes a Print button, untested print stylesheet, printed/PDF copy breaks while the on-screen page looks fine) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'Print button', 'print stylesheet exists but is untested', and 'printed or PDF copy breaking in the wrong places' are present and well-chosen, but synonyms and file extensions (e.g. .pdf, 'PDF generation', 'page breaks') are not enumerated, so it stops just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	It carves a clear, narrow niche (Playwright-based print/PDF stylesheet testing) with distinctive symptom-based triggers unlikely to fire for unrelated skills, so conflict risk is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Reviewed

19 days ago

Table of Contents

Discovery Implementation Validation