research

Orchestrate an end-to-end research workflow with resumable YAML-defined pipeline stages.

77|16|Updated May 9, 2026
One-click install
npx skills add https://github.com/Lambenthan/empiricalwiki --skill research-lambenthan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/Lambenthan/empiricalwiki/tree/main/.claude/skills/research
Command: npx skills add https://github.com/Lambenthan/empiricalwiki --skill research-lambenthan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning a vague research idea into a complete, repeatable end-to-end pipeline—covering idea discovery, experiment design, deployment, verdict evaluation, and (optionally) paper writing—while maintaining progress you can safely resume after interruption.

Core Features & Use Cases

  • End-to-end orchestration: Coordinates Stage 0–5 (including Human Gates) into a single research workflow from empty wiki to paper-ready outputs.
  • Progress snapshot & recovery: Writes wiki/outputs/pipeline-progress.md after each Gate/Stage so you can resume via --start-from without losing work.
  • Non-blocking experiment execution: Deploys experiments in Stage 3a, returns control during async Stage 3b, then collects results in Stage 3c.
  • Iterative verdict refinement: Uses exp-eval and triggers at most 1 refined iteration loop when claims are insufficient, capped by guardrails.

Quick Start

Run the research pipeline from your direction with: use /research "your research direction" --auto.

Frequently Asked Questions about research

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

FAQPage Schema
How do I run an end-to-end empirical research pipeline asynchronously?

You can resume an interrupted experiment pipeline by using the `--start-from` flag. The workflow saves durable state in `pipeline-progress.md` after each stage, allowing you to safely recover and resume progress without losing completed work.

What is the best way to evaluate research claims against experimental evidence?

The best way to evaluate research claims against evidence is using a verdict-driven iteration loop. This Skill applies claim evaluation against experimental results and triggers at most one refined iteration loop if claims are insufficient, strictly capped by guardrails.

How do I automatically generate a submission-ready paper from experimental results?

To generate a submission-ready paper from experimental results, you need an orchestration workflow that optionally produces the document. This Skill orchestrates the entire pipeline from idea discovery through experiment execution and verdict evaluation to optionally output a submission-ready paper.

Do I need YAML to define stages and gate logic for research orchestration?

Yes, you need YAML to define stages and gate logic for research orchestration. This Skill requires YAML-defined stages and gate logic to coordinate the end-to-end empirical research workflow and manage human gates across the pipeline.

How to start research orchestration from a vague idea automatically?

To start research orchestration from a vague idea automatically, execute the pipeline with your research direction and the auto flag. This triggers end-to-end orchestration from empty wiki to paper-ready outputs, coordinating stages from idea discovery through experiment deployment.