pr-screenshots

Capture Playwright screenshots and embed them in GitHub PR descriptions

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/pr-screenshots/SKILL.md

Quality

Content

76%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 highly actionable and well-structured with copy-paste-ready guidance, but its workflow involving destructive git operations lacks the validation/feedback checkpoints the rubric requires for such operations.

Suggestions

Add explicit validation checkpoints between destructive steps, e.g. verify the orphan branch pushed the expected PNGs (list remote files), confirm `git branch --show-current` returns the original branch after `git checkout -f`, and verify the rendered images appear in the PR before cleanup.

Add a feedback loop for the force-push step: if `git push --force screenshots-temp` fails or the branch already exists with different content, abort and re-create rather than silently proceeding.

Consider moving the large PR body markdown template into a `references/pr-body-template.md` file (progressive disclosure) once a bundle is permitted, to keep SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	Lean, opinionated content with executable code and no padding explaining what Playwright or PR descriptions are; only minor sections (the Anti-Patterns list, the Context trigger list) could be trimmed slightly.	4 / 5
Actionability	Provides fully executable, copy-paste-ready code and commands end to end: a Playwright capture script, the orphan-branch git workflow, the `gh pr edit` body template, cleanup, and gitignore snippets.	5 / 5
Workflow Clarity	Patterns 1-5 form a clear sequence with an explicit cleanup step, but the workflow involves destructive/batch operations (`git push --force`, `git checkout -f`, branch deletion) with no validation checkpoints, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear sections and no nested references; no bundle files are present, and the content is appropriately self-contained, though the full PR body template and examples make the file longer than ideal for a single SKILL.md.	4 / 5
	Total	16 / 20 Passed

Description

65%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 is specific and distinctive with a clear niche, but it lacks an explicit 'Use when' trigger clause, which caps its completeness and leaves trigger coverage slightly incomplete.

Suggestions

Add an explicit 'Use when' clause listing concrete triggers, e.g. 'Use when a PR changes docs site pages, UI components, or other visual artifacts and reviewers need to see the result without checking out the branch.'

Expand trigger terms with synonyms users might say, such as 'pull request', 'visual review', and 'preview images'.

Optionally name one or two additional concrete actions (e.g. 'host on a temporary branch', 'clean up the branch after merge') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names two concrete actions ('Capture Playwright screenshots', 'embed them in GitHub PR descriptions') with a specific tool and target, but does not enumerate a comprehensive set of actions.	3 / 5
Completeness	Clearly states the 'what' (capture and embed screenshots), but provides no explicit 'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('screenshots', 'PR', 'Playwright', 'embed'), but omits common variations such as 'pull request' and 'visual review'.	4 / 5
Distinctiveness Conflict Risk	The 'Playwright screenshots in GitHub PR descriptions' niche is narrow with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: bradygaster/squad
Path: .squad/skills/pr-screenshots/SKILL.md
Commit: a0d2563

Reviewed: about 15 hours ago

Table of Contents

Discovery Implementation Validation

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.