AC loongflow
LoongFlow brings evolutionary multi-agent optimization to your coding agent harness. Drop it into Codex, Claude Code, Cursor or any OpenClaw agent — then watch PEES (Plan-Execute-Evaluate-Summary) iterate your code, algorithms, or prompts toward a target score, just like a harness-native eval loop but without writing a single test fixture. Two modes: Native PEES (async subagent, zero config, fires-and-forgets into the background) and LoongFlow Engine (full evolutionary search with islands, Boltzmann selection, MAP-Elites diversity, 50+ iterations, checkpoint/resume). Pairs perfectly with any task where 'run it once' isn't good enough. Use when tasks need structured iteration, optimization, evolution, or when user mentions loongflow/PEES.
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 5. 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 55/100
- 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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 424 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +1No license
- +2Single-language instructions
- +3Description length 747: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.