BB Prediction Stack Orchestrator
Three-agent pipeline orchestrator (Kalshalyst, Eval, Executor) for automated Kalshi prediction market trading with validation loops and retry logic
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6891 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "color" - note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "vibe"
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (Prediction Stack Orchestrator) differs from the folder (prediction-stack-orchestrator)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6891 tokens
- 100Tools and files. No external tools needed
- 100Steps. 170 steps
- 100Failures and branches. 19 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 147: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 170 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
This skill is a disclosed automated trading orchestrator, but it also exposes sensitive local trading-stack status, configs, logs, and process details over an unauthenticated network monitor.
LLM: suspicious (high) · VirusTotal: · 29 May 2026