dispatch
Skill4 starsChanged 41 days agoApache-2.0View on GitHub
Activate an Aevum block and launch the unattended orchestrator loop for it in the background.
45 other projects use a version of this.
Adopted by
Most recently taken up by
- neskuchny/content_factorytheir own version, first seen Nov 16, 2026
- Sagargupta16/foremantheir own version, first seen Nov 16, 2026
- eyhshen/multiagent-dispatchtheir own version, first seen Nov 16, 2026
- warrendeanlangeveldt/code-kittheir own version, first seen Nov 15, 2026
- tylerjrbuell/Wardenstheir own version, first seen Nov 15, 2026
- KalastajaM/Cluidetheir own version, first seen Nov 11, 2026
Used with
Projects with it also use edge-detection, odds-analysis and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
noahowshSkilledge-detection
Comparing a tennis model's probability with the market: no-vig close, expected value at the best available price, closing line value, fractional Kelly sizing, and the checks that separate an estimated edge from noise. Use when the user has a probability and wants to know whether a price is better than fair, how large a stake is reasonable, or whether an edge is real. Requires a probability the user trusts. Do not use for fetching prices: see odds-explorer. Do not use for devig math alone: see odds-analysis. Do not use for historical testing: see backtesting.
Also in 4 projects that use this
noahowshSkillodds-analysis
Odds math for two-way tennis markets: American to implied probability, margin, devigging (multiplicative, power, Shin), no-vig fair odds, consensus across books, favorite-longshot bias, and expected value of a price. Use when the user asks what a price implies, how to remove the vig, what the true probability is, or how to compare books. Do not use for fetching or comparing live prices: see odds-explorer. Do not use for deciding a bet against a model: see edge-detection.
Also in 4 projects that use this
agiprolabsSkillwalk-forward-validation
Walk-forward validation framework for trading strategies and ML models with time-series-aware splits, overfit detection, and regime-aware validation
Also in 4 projects that use this
Yahmez3Skillbacktesting
Use when backtesting a trading strategy — evaluating a signal series against historical price data and computing performance metrics (Sharpe, Sortino, max drawdown, CAGR, win rate, expectancy). Triggers on "backtest this strategy", "what's the Sharpe on X", "run a walk-forward test", or "compare strategies A and B". Produces equity curves, trade logs, and tear sheets.
Also in 4 projects that use this
ffsshhttiikkSkillfeature-engineering
Machine learning feature engineering
Also in 4 projects that use this
varun29ankuSSkillorchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
Also in 4 projects that use this
- +3 more from noahowsh
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- your-papa/obsidian-Smart2Brain★ 1.3ksame name
- s2b-dev/smart-second-brain★ 1.3ksame name
- bassimeledath/dispatch★ 411same name
- renzrollon/interlock★ 62same name
- fagemx/edda★ 36same name
- phj128/autoworker★ 18same name
- clonable-eden/cekernel★ 17same name
- mhlaghari/stuntman★ 16same name
- YippeeXuXu/dsh-collab-mode★ 5same name
- BigY0shi/super-skills★ 4same name
35 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Check each precondition and stop with a clear message if one fails:
- Very specific: line 16
If status: draft, ask the user to confirm activation.
- Very specific: line 23
Start the loop with the Bash tool's run_in_background:
- Very specific: line 35
when the block is ready, /signoff <BLOCK_ID> (/aevum:signoff with the plugin) reviews it.
- Distinctive: line 37
Do not poll the run. You are notified when the background command exits.
“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch block $ARGUMENTS. The run is unattended and can take hours.
- Check each precondition and stop with a clear message if one fails:
docs/blocks/<BLOCK_ID>/block.yamlandbaseline.jsonexist (offerbash scripts/capture-baseline.sh <BLOCK_ID>if the baseline is missing).git status --porcelainis empty: workers branch from committed state.
If
status: draft, ask the user to confirm activation. On yes, setstatus: active,activated_at(UTC now) andactivated_by(ask for the name), refreshbase_shato the tip ofbase_branch, and let the user commit that change before launching.Then
python3 scripts/block-preflight.py <BLOCK_ID>must exit 0.Start the loop with the Bash tool's
run_in_background:bash .claude/scripts/orchestrate-block-loop.sh $ARGUMENTS- Tell the user, briefly:
- progress:
tail -f logs/blocks/<BLOCK_ID>/progress.jsonl - early abort: write
logs/blocks/<BLOCK_ID>/signoff/ABORT.md - knobs, set before launch:
AEVUM_EFFORT(default medium),AEVUM_PERMISSION_MODE(default auto),AEVUM_MODEL,AEVUM_MAX_CONCURRENT_SUBAGENTS(default 4),MAX_CONTINUATIONS - when the block is ready,
/signoff <BLOCK_ID>(/aevum:signoffwith the plugin) reviews it.
- progress:
Do not poll the run. You are notified when the background command exits; then report the loop's exit code and the last ledger events.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

