CD testany-pipeline
Testany pipeline 编排与 CRUD - 基于 automation design 或现有 case keys 创建执行与编排单元
Testany pipeline 编排与 CRUD - 基于 automation design 或现有 case keys 创建执行与编排单元
As a process D 38/100 · Unfinished process — References files that are not bundled: ../testany-guide/references/task-handoff.md, ../testany-guide/references/automation-model.md, ../testany-guide/references/delivery-verification.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 4. 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
missing-refreference to a missing file: ../testany-guide/references/task-handoff.md - warning
missing-refreference to a missing file: ../testany-guide/references/automation-model.md - warning
missing-refreference to a missing file: ../testany-guide/references/delivery-verification.md
Process rating: all ten parameters 38/100
- 0Tools and files. 3 referenced file(s) missing: ../testany-guide/references/task-handoff.md, ../testany-guide/references/automation-model.md, ../testany-guide/references/delivery-verification.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 85 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1649 tokens
- low 12 top-level sections: this looks like several domains in one skill
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)
- +3Description length 72: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 85 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.