depth-research-loop

Orchestrates an autonomous performance-research pipeline from baseline through promotion and paper handoff.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill depth-research-loop-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: depth-research-loop
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/depth-research-loop
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill depth-research-loop-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous research projects often lose coherence across long sessions: state gets duplicated, negative results derail the pipeline, and transitions between literature review, experimentation, and promotion happen without evidence gates. This Skill enforces a single canonical state machine that routes one active candidate through literature, adaptation, screening, confirmation, and promotion with auditable transitions. ## Core Features & Use Cases - Canonical State Management: Uses research/STATE.json and transition_guard.py to validate and append every pipeline transition to an append-only PIPELINE.jsonl log. - Stage-Gated Pipeline: Enforces evidence requirements at each phase (baseline, literature, mapping, adaptation, screening, confirmation, promotion, frozen) before allowing progression. - Failure Routing: Converts screening failures and unconfirmed results into structured next steps—either an unused mapped candidate or a targeted literature refresh—instead of stalling. - Use Case: After an entrance skill initializes a research goal to improve a model's primary metric, this loop deep-reads relevant literature, maps ranked candidate mechanisms, runs precommitted screening and confirmation experiments, audits the evidence, and hands off a promoted method or triggers paper writing. ## Quick Start Resume the research pipeline by running the transition guard to show current canonical state, then dispatch the skill matching the active phase.

Frequently Asked Questions about depth-research-loop

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

FAQPage Schema
How do I resume an autonomous research pipeline after a session break?▼

Run `transition_guard.py show <root>` before every continuation to load the canonical state from research/STATE.json. Treat entry_mode, deliverable, and target_venue as fixed properties of the original objective, then dispatch the skill matching the current phase.

How do I handle failed experiments in an automated research loop?▼

Record only the observed metric delta, the failed assumption, run validity, and the next route. Use an unused mapped candidate when it matches the failure, or refresh literature when the candidate pool is exhausted or two consecutive valid candidates show no gain.

What is a transition guard in research pipeline automation?▼

A transition guard is a script that validates phase changes before applying them. Use `check` to verify a transition, `apply` to commit it, and `reserve-run` before launching any screening or confirmation experiment, keeping one canonical state machine.

When should an AI research agent escalate to external advice?▼

Escalate only for a major unresolved decision, never for ordinary negative results or routine transitions. An automatic Oracle call must first load the askgpt-governor skill, and the owning skill remains responsible for checking advice against local evidence.

What are the limitations of state-machine-driven research loops?▼

The loop keeps at most five mapped candidates and exactly one active implementation, so highly parallel exploration is restricted. It also depends on an entrance skill for initialization and should not be used as the user-facing entry point or for read-only requests.