BF doc-snapshot-agent
Automatically illustrate Markdown documents by turning image markers into screenshots or generated images, then writing an image-enriched Markdown output. Use this skill when a document needs screenshots, AI-generated visuals, image placement, or end-to-end document illustration automation.
As a process F 63/100 · Will not run — References files that are not bundled: ../{article-id}/A1_workspace-dashboard.png, ../{article-id}/architecture-decisions.png
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 291 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 5094 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../{article-id}/A1_workspace-dashboard.png - warning
missing-refreference to a missing file: ../{article-id}/architecture-decisions.png
Process rating: all ten parameters 63/100
- 0Tools and files. 2 referenced file(s) missing: ../{article-id}/A1_workspace-dashboard.png, ../{article-id}/architecture-decisions.png
- 60Result and completion. Output format stated, no completion criterion
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 19 branches
- 70Execution cost. Instruction body is 5094 tokens
- 85Steps. 169 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 291: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 169 items
- +3Output format is stated explicitly
- +4Has examples (22 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.