AB document-diff
Compare two documents (PDF, Word, images, PPT) and generate a structured diff report highlighting what changed, what was added, and what was removed. Uses SoMark to parse both documents first for accurate structure-aware comparison. Requires SoMark API Key (SOMARK_API_KEY).
As a process B 71/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Lint
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
spec-missingno spec.yaml: behaviour contract not defined (run `skilltest init`) - warning
triggers-missingspec.yaml has no triggers.positive: skill triggering is not tested - warning
evals-missingno evals/evals.json: behaviour is not tested (run `skilltest init`)
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 31 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2035 tokens
- 100Progress reporting. Reports progress
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)
- +1No license
- +2Single-language instructions
- +3Description length 274: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 31 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.