research-autoresearch-loop

Coordinates human-supervised experiment iterations with verify and guard gates across local and remote GPU runs.

2|Updated May 22, 2026
One-click install
npx skills add https://github.com/CDUTAKL/research-workflow-kit --skill research-autoresearch-loop-cdutakl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-autoresearch-loop
Source: https://github.com/CDUTAKL/research-workflow-kit/tree/main/skills/research-autoresearch-loop
Command: npx skills add https://github.com/CDUTAKL/research-workflow-kit --skill research-autoresearch-loop-cdutakl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Iterating on research experiments often leads to lost results, unverifiable claims, and unsafe conclusions such as data leakage or metric inflation. This Skill structures each experiment iteration with recorded state, dual verification gates, and resumable tracking so every run is auditable and reproducible. ## Core Features & Use Cases - Structured Iteration Recording: Logs every experiment iteration to autoresearch-results.tsv and maintains resumable state in autoresearch-state.json. - Dual-Gate Verification: Applies a verify gate (did the metric improve?) and a guard gate (no leakage, config drift, phantom results, or claim inflation) before promoting results. - Local-to-Remote Workflow: Coordinates local_mac smoke tests with formal runs on remote_desktop_4060, generating experiment reports with baseline comparisons. - Use Case: A graduate student testing a new model variant runs a local smoke test, launches the formal GPU run remotely, then records the iteration with verify/guard status and a baseline comparison report before deciding whether to update the thesis claims. ## Quick Start Use the research-autoresearch-loop skill to plan and record my next experiment iteration against claim CLM-001 with a baseline comparison.

Frequently Asked Questions about research-autoresearch-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a supervised research experiment iteration?

Choose a target claim, current best run, primary metric, and candidate change, then run a local smoke test before the formal remote GPU run. Record the iteration with scripts/new_autoresearch_iteration.py and apply the verify and guard gates before promoting results.

What is the difference between the verify gate and guard gate?

The verify gate checks whether the experiment answered the intended question or improved the metric. The guard gate checks scientific validity, catching data leakage, config incomparability, metric integrity issues, missing artifacts, and overclaimed scope.

How do I record experiment results in autoresearch-results.tsv?

Run scripts/new_autoresearch_iteration.py with the experiment ID, target claim, change summary, primary metric, baseline and new values, verify status, guard status, and decision. The script appends a structured row to docs/thesis/autoresearch-results.tsv.

Can this skill run experiments autonomously without supervision?

No. The skill explicitly prohibits unattended autonomous research. Every iteration requires human decisions on research direction, claims, and result promotion, with the user retaining final control.

When should I use remote_desktop_4060 versus local_mac for experiments?

Use local_mac for quick smoke tests to validate code and configuration before committing GPU time. Use remote_desktop_4060 for formal runs that produce reportable results, with cloud_autodl as a fallback option.