CD polly-e2e-dev
End-to-end test the polly multi-agent coding orchestrator's critical user journeys (CUJs). Two halves — a deterministic mock-LLM driver (polly_cuj.py) that boots a throwaway local server + mock LLM and asserts the substrate (boot, bridged sys_* tool dispatch, the blast_radius / spawn_bounds / headless_subagent_purpose_guard guardrails, fan-out delegation), and a live real-CLI recipe (real claude/codex/pi, real worktrees/PRs) for polly's actual judgment. Load when developing, testing, or debugging examples/polly — its config.yaml, the claude_code/codex/pi sub-agents, the investigate/fanout/cross-review skills, or the omnigent.inner.nessie.policies guardrails — or reproducing a polly orchestration bug.
End-to-end test the polly multi-agent coding orchestrator's critical user journeys (CUJs).
As a process D 35/100 · Unfinished process — References files that are not bundled: examples/polly/, examples/polly/config.yaml, examples/polly/agents/{claude_code,codex,pi}/config.yaml
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: examples/polly/ - warning
missing-refreference to a missing file: examples/polly/config.yaml - warning
missing-refreference to a missing file: examples/polly/agents/{claude_code,codex,pi}/config.yaml - warning
missing-refreference to a missing file: examples/polly/skills/{investigate,fanout,cross-review}/SKILL.md
Process rating: all ten parameters 35/100
- 0Tools and files. 4 referenced file(s) missing: examples/polly/, examples/polly/config.yaml, examples/polly/agents/{claude_code,codex,pi}/config.yaml
- 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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2712 tokens
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (3 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 709: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.