BC orche
A multi-agent orchestration engine that systematically executes complex tasks in 4 phases (Query → Plan → Execute → Verify). Ensures high-quality deliverables through phase gates, Critic debates, 14-item hallucination checks, and automatic regression on verification failure.
As a process C 63/100 · Has gaps — weak spots: result and completion, when it triggers, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
body-longSKILL.md body ≈ 9408 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 63/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 15 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Execution cost. Instruction body is 9408 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 175 steps, 1 vague phrases
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 26 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)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -2117 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 275: enough signal without eating the budget
- +4Structure: 97 headings
- +3Step-by-step instructions: 175 items
- +4Has examples (32 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.