Configures and uses snipgrapher to generate polished code snippet images, including syntax-highlighted PNGs, SVGs, and WebP exports with custom themes, profiles, and styling options. Use when the user wants to create code screenshots, turn code into shareable images, generate pretty code snippets for docs or social posts, produce syntax-highlighted images from source files, or explicitly mentions snipgrapher. Supports single-file renders, batch jobs, watch mode, and reusable named profiles via the snipgrapher CLI or npx.
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities, includes a comprehensive 'Use when...' clause with natural trigger terms, names the specific tool, and occupies a clear niche that won't conflict with other skills. The description is detailed yet concise, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generate polished code snippet images', 'syntax-highlighted PNGs, SVGs, and WebP exports', 'custom themes, profiles, and styling options', 'single-file renders, batch jobs, watch mode, and reusable named profiles'. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (configures and uses snipgrapher to generate code snippet images with various formats and options) and 'when' (explicit 'Use when...' clause listing five distinct trigger scenarios). Both are well-articulated. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'code screenshots', 'turn code into shareable images', 'pretty code snippets', 'syntax-highlighted images', 'snipgrapher', 'docs or social posts', 'source files'. These are highly natural phrases a user would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: code-to-image generation via a specific tool (snipgrapher). The combination of the tool name, the specific output formats (PNG, SVG, WebP), and the use case (shareable code images) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and progressive disclosure. The quick start is immediately useful with executable commands, and detailed content is properly delegated to referenced rule files. Minor verbosity in the 'When to use' section and some explanatory padding in troubleshooting prevent a perfect conciseness score.
Suggestions
Trim or remove the 'When to use' section since it largely duplicates the frontmatter description, or reduce it to a single-line trigger summary.
Tighten the troubleshooting section by removing the introductory sentence and using a more telegraphic style (e.g., '**Missing fonts** → ensure custom fonts are installed').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary padding. The 'When to use' section repeats information likely in the frontmatter description. The troubleshooting section, while useful, includes some explanatory text that could be tightened (e.g., 'If a render fails or produces an unexpected output, check for these common causes'). | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands for quick start (npx snipgrapher render, init), includes a concrete verification step (ls -lh), and gives specific actionable troubleshooting steps with exact commands and flags. | 3 / 3 |
Workflow Clarity | Clear sequencing from init to render to verification. Includes an explicit validation checkpoint (verify output exists and is non-zero size). The troubleshooting section provides error recovery guidance. The workflow is simple enough that the presented steps are sufficient. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise quick start inline, then clear one-level-deep references to detailed rule files (setup-and-configuration.md, rendering-workflows.md) with descriptive labels. Content is appropriately split between overview and detailed materials. | 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents