SOTA Agent
by @zack-dev-cm
SOTA Agent is a public ClawHub SOTA-campaign skill for CV and DS work. Use it when the user says "sota agent", "state of the art benchmark scouting", or want...
clawhub install sota-agentπ About This Skill
name: sota-agent description: SOTA Agent is a public ClawHub SOTA-campaign skill for CV and DS work. Use it when the user says "sota agent", "state of the art benchmark scouting", or wants benchmark planning, paper triage, ablation design, and claim review for CV or data-science campaigns. version: 1.4.4 homepage: https://zack-dev-cm.github.io/ user-invocable: true metadata: {"openclaw":{"homepage":"https://zack-dev-cm.github.io/","skillKey":"sota-agent","requires":{"anyBins":["python3","python"]}}}
SOTA Agent
Search intent: sota agent, state of the art benchmark scouting, cv benchmark campaign, gpu vm research workflow
Goal
Turn a vague "beat the benchmark" request into a disciplined campaign:
This skill is the frontier-planning and candidate-selection layer.
For execution artifacts or promotion evidence, pair it with
data-science-cv-repro-lab; this skill stays focused on planning and claim review.
Use This Skill When
If the campaign includes serious execution or release review, use this skill to choose and rank candidates,
then use data-science-cv-repro-lab as the execution lane.
Quick Start
1. Freeze the claim target before touching recipes. - Name the task, dataset, metric, split, and target score. - Name the current trusted baseline. - Name the claim threshold for "match", "beat", or "not enough".
2. Initialize the campaign records immediately.
- Use python3 {baseDir}/scripts/init_sota_campaign.py --root .
- Use python3 {baseDir}/scripts/init_sota_leaderboard_snapshot.py --out .
- Use python3 {baseDir}/scripts/init_sota_paper_triage.py --out .
- Use python3 {baseDir}/scripts/init_sota_program.py --out when you need one machine-readable benchmark, rerun, delegation, and auth plan.
- Use python3 {baseDir}/scripts/init_sota_candidate_card.py --out .
- If execution review depends on synced QA runs, runtime sweeps, or benchmark panels, store the paired data-science-cv-repro-lab review dashboard path in the program and candidate records before the claim review starts.
- If external execution evidence exists, record the reviewed artifact manifest path in the program and candidate records instead of acting through a live session.
- If the review surface needs manual or visual QA, use python3 {baseDir}/scripts/init_sota_validation_scorecard.py --out .
- If an external export bundle matters, use python3 {baseDir}/scripts/init_sota_artifact_manifest.py --out .
- If a long execution run is involved, record only sanitized summaries and artifact references in the SOTA campaign files.
3. Separate the campaign roles even if one agent performs all of them. - Scout: papers, leaderboards, repos, and benchmark rules. - Reproducer: baseline and top-paper reproduction. - Ablator: controlled change sets and compute allocation. - Reviewer: contamination, metric drift, and claim integrity. - Promoter: final claim or hold decision. - Keep the benchmark definition and final claim wording fixed. - Use bounded scouting and review lanes for literature triage, repo inspection, per-paper extraction, and hard-case review. - For repeated audits, batch over a manifest or CSV instead of free-form context accumulation.
4. Pick the execution lane explicitly.
- Execution handoff lane: use data-science-cv-repro-lab for external runs and artifact capture.
- Local lane: cheap falsification, tiny reruns, and artifact review.
5. Keep file writes inside one campaign workspace.
- Create one dedicated campaign root and keep every --out, --bundle-root, and --output-root path under it.
- Do not point the bundled scripts at unrelated home-directory or system paths.
- Treat scripts/sota_public_safety.py as the canonical public-redaction layer for URLs, refs, and paths.
6. Work the SOTA ladder in order. - Freeze the benchmark definition and auth rule before using more compute. - Reproduce the trusted baseline first. - Reproduce one relevant reference result or a close public checkpoint. - Build a hypothesis backlog from literature gaps, not vibes. - Run narrow ablations before broad recipe churn. - Stress the best candidate on the fixed review surfaces.
7. Claim only on full-surface wins.
- Fixed benchmark score
- Reproduced baseline delta
- Compute or cost context
- Browser or GUI evidence if that lane mattered
- Failure-case review
- Exact evidence bundle
- Render the final review with python3 {baseDir}/scripts/render_sota_claim_summary.py --candidate-card .
Operating Rules
Campaign rules
Codex multi-agent rules
Literature rules
Ablation rules
Compute rules
Runtime and auth rules
OPENAI_API_KEY, other vendor API keys, or paid inference APIs as the default campaign runtime path.External execution rules
data-science-cv-repro-lab.Claim safety rules
References
Read only the reference that matches the task:
references/sota-campaign-playbook.mdreferences/sota-program-rules.mdreferences/campaign-harness-stack.mdreferences/benchmark-discipline.mdreferences/paper-triage.mdreferences/public-research-lane.mdreferences/external-evidence-handoff.mdreferences/execution-evidence-summary.mdreferences/claim-safety.mdreferences/public-safety.mdBundled Scripts
scripts/sota_public_safety.pyscripts/init_sota_campaign.pyscripts/init_sota_program.pyscripts/init_sota_leaderboard_snapshot.pyscripts/init_sota_paper_triage.pyscripts/init_sota_browser_run_card.pyscripts/init_sota_validation_scorecard.pyscripts/init_sota_artifact_manifest.pyscripts/init_sota_candidate_card.pyscripts/init_sota_candidate.pyscripts/init_sota_ablation_queue.pyscripts/init_sota_vm_bootstrap_manifest.pyscripts/update_sota_scoreboard.pyscripts/init_sota_review_packet.pyscripts/render_sota_claim_summary.pyscripts/render_sota_program_summary.pyπ‘ Examples
1. Freeze the claim target before touching recipes. - Name the task, dataset, metric, split, and target score. - Name the current trusted baseline. - Name the claim threshold for "match", "beat", or "not enough".
2. Initialize the campaign records immediately.
- Use python3 {baseDir}/scripts/init_sota_campaign.py --root .
- Use python3 {baseDir}/scripts/init_sota_leaderboard_snapshot.py --out .
- Use python3 {baseDir}/scripts/init_sota_paper_triage.py --out .
- Use python3 {baseDir}/scripts/init_sota_program.py --out when you need one machine-readable benchmark, rerun, delegation, and auth plan.
- Use python3 {baseDir}/scripts/init_sota_candidate_card.py --out .
- If execution review depends on synced QA runs, runtime sweeps, or benchmark panels, store the paired data-science-cv-repro-lab review dashboard path in the program and candidate records before the claim review starts.
- If external execution evidence exists, record the reviewed artifact manifest path in the program and candidate records instead of acting through a live session.
- If the review surface needs manual or visual QA, use python3 {baseDir}/scripts/init_sota_validation_scorecard.py --out .
- If an external export bundle matters, use python3 {baseDir}/scripts/init_sota_artifact_manifest.py --out .
- If a long execution run is involved, record only sanitized summaries and artifact references in the SOTA campaign files.
3. Separate the campaign roles even if one agent performs all of them. - Scout: papers, leaderboards, repos, and benchmark rules. - Reproducer: baseline and top-paper reproduction. - Ablator: controlled change sets and compute allocation. - Reviewer: contamination, metric drift, and claim integrity. - Promoter: final claim or hold decision. - Keep the benchmark definition and final claim wording fixed. - Use bounded scouting and review lanes for literature triage, repo inspection, per-paper extraction, and hard-case review. - For repeated audits, batch over a manifest or CSV instead of free-form context accumulation.
4. Pick the execution lane explicitly.
- Execution handoff lane: use data-science-cv-repro-lab for external runs and artifact capture.
- Local lane: cheap falsification, tiny reruns, and artifact review.
5. Keep file writes inside one campaign workspace.
- Create one dedicated campaign root and keep every --out, --bundle-root, and --output-root path under it.
- Do not point the bundled scripts at unrelated home-directory or system paths.
- Treat scripts/sota_public_safety.py as the canonical public-redaction layer for URLs, refs, and paths.
6. Work the SOTA ladder in order. - Freeze the benchmark definition and auth rule before using more compute. - Reproduce the trusted baseline first. - Reproduce one relevant reference result or a close public checkpoint. - Build a hypothesis backlog from literature gaps, not vibes. - Run narrow ablations before broad recipe churn. - Stress the best candidate on the fixed review surfaces.
7. Claim only on full-surface wins.
- Fixed benchmark score
- Reproduced baseline delta
- Compute or cost context
- Browser or GUI evidence if that lane mattered
- Failure-case review
- Exact evidence bundle
- Render the final review with python3 {baseDir}/scripts/render_sota_claim_summary.py --candidate-card .