BC reproduce
Reproduces a paper's result, a claim, an artifact or a previous run with the target and success criterion frozen first, the canonical code path run before any substitute, exact inputs, environment, seeds and commands captured, and a verdict from a fixed set, reproduced, reproduced within tolerance, partially reproduced, not reproduced, or untestable. Use for "reproduce", "replicate", "re-run", "does this hold", or checking a result before building on it. Not for open-ended exploration or for improving the result (use autoresearch).
Reproduces a paper's result, a claim, an artifact or a previous run with the target and success criterion frozen first, the canonical code path run before any…
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash python glob grep webfetch compute_job experiments
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "role"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1102 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 537: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.