Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vstorm-co/verification-strategy
Thorough verification of completed work before declaring done
Passed 14 of 21 test cases with the skill, and 9 of 21 without it.
and 8 more in the full report
7 fixed8 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I generated a binary dataset file /data/processed.bin and a summary log /data/summary.txt in my shell pipeline. Usually I just run cat on the summary file. What bash commands should I run to inspect file existence, detailed permissions, exact byte count, file encoding/type, and initial lines before committing?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using ls -la to check file existence and permissions. | Passed | Passed |
| Recommends using wc -c to measure exact file byte size. | Missed | Passed |
| Recommends using file command to detect file format. | Passed | Passed |
The instructions your model reads when the skill loads.
How to verify your work is correct before declaring a task complete.
After implementing a solution, go through ALL of these:
ls -la /path/to/expected/output
wc -c /path/to/output # byte count
file /path/to/output # format detection
head -5 /path/to/output # content preview
echo $? (should be 0 for success)test cases passed, vs 9 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.