odinfree/storm-ecdsa-harness / skills/auto-autoresearch-pipeline
auto-autoresearch-pipeline
VerifiedRun a long autonomous optimization campaign on a scored artifact (circuit, proof, packing) as a role-separated pipeline: one director, parallel area-owning workers, an independent paired verifier, a fail-closed integrator, and a compiled-screen grinder. Use when many small candidate edits compete for a leaderboard score and no single worker can be trusted to measure its own work.
Fliessband (auto-autoresearch-pipeline)
Distilled from haotang1995's "Auto-AutoResearch" harness (two accepted ecdsa.fail record submissions, 2026-10-29). The pattern took the board in one day; it is route-agnostic and reusable for any scored artifact.
Roles — separate them, no exceptions
- Director. Assigns disjoint research areas and owns the idea log. Never edits the artifact. Areas are named by region of the stream (divide walk, multiply walk, history, width), not by technique, so two workers never touch the same rows.
- Workers. One area each. Every candidate ships with: a change note, a paired measurement against its own parent (same shots, same seeds), and an approximate/exact classification. A candidate without all three is not queued.
- Independent verifier. A separate worker re-measures every queued candidate on fresh shots paired against the current leader — never trust the producing worker's numbers. Price conservatively: charge the paired SE and a minimum multi-event floor against the claimed delta. Effects smaller than the verifier's SE must be re-measured by the worker at 4–16× shot count before they count.
- Integrator. Stacks only qualified leaves, using predeclared, frozen compositions. Content-keyed matching of edited bodies; fail-closed where an edit does not match; no resampling and no new policy at merge time; re-verify the merged stream before it becomes the leader.
- Grinder. Compile the screening filter from the final artifact stream so the screen is never hand-written per candidate. The screen is a filter, never the judge: only an exact-evaluator pass counts.
Idea-log discipline
- Log every start and finish with an ID per ingredient (their log: E193…E300).
- Failed attempts are first-class entries with the failure mode named (UNSAT / timeout / byte-identical / overfit) — timeouts are never recorded as impossibility.
- Items with no recorded completion are explicitly unclaimed; the submission note says so.
- A positive control that reproduces the parent stream exactly travels with every structural claim.
Submission note contract
State the harness and models, the parent commit, the measured table with seeds and shot counts, the lambda (failure-rate) position, what is proven vs measured, the failed-attempt list, and which queued improvements were deliberately excluded.
Anti-patterns this prevents
- Worker-measures-itself optimism (independent verifier kills it).
- Merge-time rescue edits (frozen compositions kill them).
- Hand-tuned screens drifting from the stream (compiled screens kill that).
- Silent failure debt (the idea log + unclaimed-item rule kill it).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |