take-doc-screenshots
Take screenshots of the running pgconsole app for documentation. Use when updating docs with screenshots or adding images to .mdx files.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
75%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 functional and clearly scoped to a specific app and use case, with explicit 'Use when' guidance that makes it easy for Claude to know when to select it. Its main weakness is that it could be more specific about the concrete actions involved (e.g., capturing specific views, saving formats) and include more natural trigger term variations.
Suggestions
Add more specific concrete actions, e.g., 'Launches pgconsole, captures specific UI views, saves screenshots as PNG, and embeds them in documentation files.'
Include additional natural trigger terms like 'screen capture', 'snapshot', 'capture UI state', or 'visual documentation' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (screenshots of pgconsole app) and one action (take screenshots for documentation), but doesn't list multiple concrete actions like capturing specific UI states, annotating, resizing, or saving in particular formats. | 2 / 3 |
Completeness | Clearly answers both 'what' (take screenshots of the running pgconsole app for documentation) and 'when' (updating docs with screenshots or adding images to .mdx files) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'screenshots', 'pgconsole', 'docs', '.mdx files', and 'images', but misses natural variations users might say such as 'screen capture', 'snapshot', 'capture UI', or 'visual documentation'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche — screenshots of a particular app (pgconsole) for documentation purposes with .mdx files. Unlikely to conflict with other skills due to the app-specific and task-specific scope. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, well-structured skill that provides specific, actionable guidance for a niche task. It excels at providing app-specific details Claude couldn't know (CodeMirror interaction patterns, UI selectors, auth flow) without any unnecessary verbosity. The main gap is the lack of validation steps — particularly verifying auth success, screenshot capture, and image conversion.
Suggestions
Add a validation step after the login curl command to verify authentication succeeded (e.g., check HTTP status code or verify cookie file contents)
Add a verification step after screenshot capture to confirm the PNG file exists and has expected dimensions before proceeding to WebP conversion
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section provides specific, necessary information that Claude wouldn't inherently know — app-specific auth flow, CodeMirror quirks, UI button labels, file paths, and image conventions. No padding or concept explanations. | 3 / 3 |
Actionability | Provides executable curl commands, specific JSON structures, exact Playwright API calls with correct syntax, concrete CSS selectors (.cm-content), specific keyboard shortcuts, and exact cwebp commands. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The overall flow (auth → screenshot → process images) is clear and well-sequenced, but there are no validation checkpoints — no verification that the dev server is running, that authentication succeeded, that screenshots captured correctly, or that WebP conversion produced valid output. | 2 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Prerequisites, Authentication, Taking Screenshots, Image Processing, Image Convention) with clear subsections. The skill is appropriately sized for a single file with no need for external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- pgplex/pgconsole
- Commit
2b49a9b
- 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.