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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/take-doc-screenshots/SKILL.md

Quality

Content

68%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 well-structured and highly actionable with concrete commands and selectors throughout. Its main gap is the missing verify-before-cleanup checkpoint in a workflow that deletes temporary files.

Suggestions

Add a validation step before cleanup: verify each output .webp exists (and is non-empty) before deleting its source PNG, and only delete the PNGs whose conversion succeeded.

Provide a complete copy-paste Playwright .mjs scaffold (launch, addCookies, goto, screenshot) instead of listing the steps as prose, to lift actionability to fully executable.

Consider moving the CodeMirror interaction and UI navigation button lists into a references/ file, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and no concept over-explanation, but a few justifications like "An open overlay blocks clicks on other elements" could be trimmed.	4 / 5
Actionability	Concrete curl, JSON auth state, CSS selectors, keyboard commands, and cwebp invocations are provided, but the Playwright screenshot script is given as numbered steps and config values rather than full copy-paste code.	4 / 5
Workflow Clarity	The Prerequisites → Authentication → Screenshots → Image Processing sequence is clear and numbered, but the destructive "Clean up temporary PNG files after conversion" step lacks a validation checkpoint confirming the WebP output succeeded, which caps this at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and sections are well-organized with no nested references, but at 97 lines the dense inline CodeMirror/UI navigation detail sits just above the simple-skill threshold where it could warrant a reference file.	4 / 5
	Total	15 / 20 Passed

Description

82%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 concise, in third person, and clearly pairs a what with an explicit when-clause tied to a specific app. Its only weakness is that it describes essentially one action rather than a breadth of capabilities.

Dimension	Reasoning	Score
Specificity	"Take screenshots" is the one concrete action named; the remainder restates the same action as a use-case, so it names the domain plus 1-2 actions but is not comprehensive.	3 / 5
Completeness	It explicitly answers both what ("Take screenshots of the running pgconsole app for documentation") and when ("Use when updating docs with screenshots or adding images to .mdx files") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a user would say are present ("screenshots", "docs", "documentation", ".mdx files", "images"), but a few synonyms like "capture" or "pictures" are missing.	4 / 5
Distinctiveness Conflict Risk	It is scoped to a specific app (pgconsole) and a narrow purpose (documentation screenshots), giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	17 / 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
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
Path: .claude/skills/take-doc-screenshots/SKILL.md
Commit: bf166f0

Reviewed: 5 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.