AB fde-poc-runner
Stage 6 of FDE Delivery Loop. Run a deployable solution and Agent Skill in representative or controlled customer scenarios against pre-agreed evidence, tests, and success criteria, then produce a Continue, Adjust, or Stop decision report. Use for POC trials, demo execution, acceptance validation, issue triage, and POC retrospectives. Do not rewrite success criteria during a run, conceal failure evidence, or declare production approval.
Stage 6 of FDE Delivery Loop.
As a process B 70/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
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 · 0
✓ No critical or high findings
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 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
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 31 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1396 tokens
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)
- +4No input/output examples
- +2Single-language instructions
- +3Description length 439: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 31 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (9 of 9)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.