CD verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr <n>", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr<n>-verify-<ts>/report.md plus a machine-readable verdict. Designed for the token-free CI verify job; also usable locally.
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr <n>", "深度验证这个 PR", A/B load-bearing proof against the base…
As a process D 47/100 · Unfinished process — References files that are not bundled: scripts/sandbox-prototype/build.mjs, scripts/check-flyway-migrations.js
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:434Offensive-security / dual-use content (legitimate for authorised testing; review intended use)installs unhashed — and privilege escalation was **disproved** —
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 22842 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/sandbox-prototype/build.mjs - warning
missing-refreference to a missing file: scripts/check-flyway-migrations.js - note
edit-residuethe text marks something as outdated (lines 1088): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 47/100
- 0Tools and files. 2 referenced file(s) missing: scripts/sandbox-prototype/build.mjs, scripts/check-flyway-migrations.js
- 0Result and completion. Does not say what the result is
- 10Execution cost. Instruction body is 22842 tokens: crowds the task out of the window
- 30Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 85Steps. 103 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 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 The response is described with custom markup (14 tags): a typed call is more reliable
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 359: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 103 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.