AF marp
Use when creating slide decks, presentations, product requirement docs with diagrams, or converting markdown to PDF/PPTX/HTML slides. Triggers on "make a deck", "create slides", "presentation", "export to PDF", "requirement doc with diagrams", or any Marp-related request.
As a process F 46/100 · Will not run — References files that are not bundled: image.png, image1.png, image2.png
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: image.png - warning
missing-refreference to a missing file: image1.png - warning
missing-refreference to a missing file: image2.png - warning
missing-refreference to a missing file: image3.png - warning
missing-refreference to a missing file: diagram.png - warning
missing-refreference to a missing file: diagram.svg - warning
missing-refreference to a missing file: diagrams/user-flow.svg - warning
missing-refreference to a missing file: diagrams/architecture.svg - warning
missing-refreference to a missing file: path - warning
missing-refreference to a missing file: img
Process rating: all ten parameters 46/100
- 0Tools and files. 10 referenced file(s) missing: image.png, image1.png, image2.png
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2106 tokens
- low 12 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 272: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.