CD ship
Commit, push, and open a PR to staging in one shot — runs the cleanup pass and, when migrations changed, the db-migrate safety review first
Commit, push, and open a PR to staging in one shot — runs the cleanup pass and, when migrations changed, the db-migrate safety review first
As a process D 42/100 · Unfinished process — References files that are not bundled: row|chunk|document|vector|tuple|doc, CONTRIBUTING.md, scripts/*.test.ts
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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: row|chunk|document|vector|tuple|doc - warning
missing-refreference to a missing file: CONTRIBUTING.md - warning
missing-refreference to a missing file: scripts/*.test.ts - warning
missing-refreference to a missing file: scripts/check-*.test.ts - warning
missing-refreference to a missing file: scripts/generate-docs.ts
Process rating: all ten parameters 42/100
- 0Tools and files. 5 referenced file(s) missing: row|chunk|document|vector|tuple|doc, CONTRIBUTING.md, scripts/*.test.ts
- 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
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4065 tokens
- 100Steps. 35 steps
- 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
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (8 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
- +5Description has no quoted example phrases that should trigger the skill
- +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
- +3Description length 139: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.