.claude/skills/bench-all/SKILL.md
Run all framework benchmarks. Default is sequential (single `deno task bench`). Use `--parallel` for 5-subagent parallel mode. Triggers on "run all benchmarks", "bench all", "/bench-all".
npx skillsauth add korchasa/flow bench-allInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
deno task bench invocation.--parallel): Split across 5 subagents.Run all benchmarks in one command:
deno task bench
Report results as they appear. After completion, summarize pass/fail counts.
deno eval "
import { dirname, join } from '@std/path';
import { existsSync, walk } from '@std/fs';
const fw = join(Deno.cwd(), 'framework');
const ids = [];
for await (const pe of Deno.readDir(fw)) {
if (!pe.isDirectory) continue;
const sd = join(fw, pe.name, 'skills');
if (!existsSync(sd)) continue;
for await (const e of walk(sd, { maxDepth: 10, includeFiles: true, match: [/mod\.ts$/] })) {
if (!e.path.includes('/benchmarks/') || e.path.includes('/fixture/')) continue;
try {
const m = await import('file://' + e.path);
for (const k in m) { if (m[k]?.id && m[k]?.userQuery) ids.push(m[k].id); }
} catch {}
}
}
console.log(JSON.stringify(ids));
"
Distribute scenarios round-robin across 5 batches.
For each batch N (1-5), launch a benchmark-runner subagent with this prompt template:
Run these benchmark scenarios sequentially using deno task bench.
For each scenario, run: deno task bench -f <scenario-id> --lock batch-N.lock
Scenarios: <comma-separated list of IDs in this batch>
IMPORTANT: Always pass --lock batch-N.lock to avoid lock conflicts with other parallel agents.
Run them one by one. After each scenario completes, report its result (PASS/FAIL, errors, warnings).
At the end, provide a summary of all scenarios in this batch.
Launch ALL 5 subagents in a SINGLE message (parallel Agent tool calls). Use run_in_background: true for each.
While subagents are running, report status to the user every ~60 seconds:
After all scenarios complete, compile results into a summary:
## Benchmark Results
- Total scenarios: N
- Passed: N
- Failed: N
- Errors: N
- Warnings: N
### Failed scenarios
- scenario-id: reason
benchmark-runner agent is READ-ONLY. It runs benchmarks but does not fix anything.deno task bench -f <id> runs a single scenario. The -f flag filters by substring match, so use exact scenario IDs to avoid matching multiple scenarios.--lock batch-N.lock (where N is the batch number 1-5) to avoid lock conflicts between parallel agents.development
Use when the user asks to add TypeScript strict-mode code-style rules to AGENTS.md for a TypeScript project using strict mode. Do NOT trigger for Deno projects (use setup-agent-code-style-deno) or non-strict TS configurations.
development
Use when the user asks to add Deno/TypeScript code-style rules to AGENTS.md, or during initial Deno project setup when code-style guidelines need to be established. Do NOT trigger for non-Deno TypeScript projects (use setup-agent-code-style-strict), or for runtime-agnostic style advice.
testing
Use when the user provides a source (URL, file path, or free text) to save into the project's memex — a long-term knowledge bank for AI agents. Stores the raw source, extracts entities into cross-linked pages, runs a backlink audit, and updates the index and activity log. Do NOT trigger on casual reads; only when the intent is to persist a source into the memex.
development
Use when the user asks to audit a memex (long-term knowledge bank for AI agents) for orphans, dead SALP REFs, missing sections, contradictions, or index drift. Runs a deterministic structural check, layers LLM-judgement findings, optionally auto-fixes trivial issues with `--fix`. Do NOT trigger on general code linting.