take-doc-screenshots

Take screenshots of the running pgconsole app for documentation. Use when updating docs with screenshots or adding images to .mdx files.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

87%

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

A well-written, concise, highly actionable skill body with concrete commands and selectors throughout. The main gap is the absence of explicit validation/verification checkpoints in a multi-step screenshot automation that involves login and batch capture.

Suggestions

Add an explicit verification checkpoint after capture (e.g., confirm each PNG is non-empty / shows the expected element before converting to WebP), and a reachability check for the dev server before attempting login.

Include a brief retry/feedback loop for the login step (extract token, verify the cookie was set, re-auth if missing) since auth failure would silently break every downstream screenshot.

State an explicit 'only proceed when screenshots are confirmed' gate before the Image Processing cleanup step, so failed captures aren't deleted along with successful ones.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: terse prerequisite bullets, exact commands, and selectors with no padding explaining concepts Claude already knows (Playwright, CodeMirror, WebP). Every section earns its place and assumes competence.	3 / 3
Actionability	Fully executable and copy-paste ready: exact curl login command, Playwright viewport/cookie config, concrete selectors, cwebp conversion command, and MDX reference/naming conventions.	3 / 3
Workflow Clarity	Steps are clearly sequenced across numbered sections, but a fragile batch/automation workflow lacks explicit validation checkpoints (e.g., verify the screenshot captured the intended state, confirm the dev server is reachable), which caps this dimension at 2 per the rubric.	2 / 3
Progressive Disclosure	No bundle files exist and the skill is self-contained and under ~90 lines; it is well-organized into clear sections with no nested or external references, satisfying the simple-skill case for a top score.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 description: third-person, concise, with an explicit 'Use when' trigger covering both what and when. The only weakness is specificity—the skill is essentially a single action (take screenshots) applied to a documentation context, so it lists few distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names the concrete domain (pgconsole app screenshots) and document-related actions ('updating docs with screenshots', 'adding images to .mdx files'), but the action set is narrow—essentially 'take screenshots' restated across two contexts rather than multiple distinct actions.	2 / 3
Completeness	Explicitly answers both 'what' ('Take screenshots of the running pgconsole app for documentation') and 'when' via an explicit 'Use when...' clause, matching the strongest anchor.	3 / 3
Trigger Term Quality	Uses natural user-facing terms ('screenshots', 'documentation', 'docs', 'images', '.mdx files') that a user would plausibly say when requesting this, with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	The pgconsole-specific doc-screenshot niche gives it clear, distinct triggers unlikely to conflict with unrelated skills.	3 / 3
	Total	11 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: pgplex/pgconsole
Commit: d30071f

Reviewed: 2 days 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.