Automated summary
This skill drives ResearchClaw's 23-stage autonomous research pipeline, taking a topic through literature review, experiments and peer review to a written paper.
Strengths
- Covers the full chain: literature review, hypotheses, experiment design, code generation, analysis, paper writing and export
- Three configurable experiment modes (simulated, sandbox, ssh_remote) fitting different compute setups
- Supports resuming from a specific stage with --from-stage and skipping human gates with --auto-approve
- Produces structured per-stage artifacts, including a paper draft, a LaTeX results table and generated charts
Limitations
- Requires the researchclaw package installed, a valid config.yaml and a configured LLM API key
- Simulated mode produces LLM-generated synthetic results rather than real empirical evidence
- Gate stages (5, 9, 20) need human approval or --auto-approve, and sandbox mode assumes a Python interpreter with numpy available
Use it when you want to automatically generate a full research paper draft, complete with experiments and visualizations, from a single topic.
Avoid it when you need verified, publication-grade empirical results, or when the execution environment and LLM API key are not set up.
Security analysis
CautionThe skill is a legitimate orchestration guide for a research pipeline, but it instructs use of Bash, local subprocess execution of generated code, SSH remote execution, and API-key configuration. These are powerful capabilities rather than malicious actions, so it warrants caution rather than risky.
- •No allowed-tools declared, yet instructions require Bash/file access and invoke a CLI that can execute generated code.
- •Sandbox mode executes generated experiment code locally via subprocess, which is powerful and requires isolation/trust boundaries.
- •ssh_remote mode can execute code on a remote GPU server via SSH, adding network and remote-execution risk.
- •Reads LLM API keys from config.yaml or environment variables; handling should avoid logging or leaking secrets.
- •--auto-approve bypasses human approval gates at stages 5, 9, and 20, reducing oversight of generated experiments.
Examples
Research quantum error correction with surface codes and write a paper — run the ResearchClaw pipeline with --auto-approve and output to artifacts/qec-run.Resume my ResearchClaw run from the PAPER_OUTLINE stage using config.yaml and finish the paper draft.Run ResearchClaw on 'sparse attention efficiency in transformers' using sandbox experiment mode, then generate the result charts and LaTeX table.name: researchclaw description: Run the ResearchClaw autonomous research pipeline from a topic, config, and output directory.
ResearchClaw — Autonomous Research Pipeline Skill
Description
Run ResearchClaw's 23-stage autonomous research pipeline. Given a research topic, this skill orchestrates the entire research workflow: literature review → hypothesis generation → experiment design → code generation & execution → result analysis → paper writing → peer review → final export.
Trigger Conditions
Activate this skill when the user:
- Asks to "research [topic]", "write a paper about [topic]", or "investigate [topic]"
- Wants to run an autonomous research pipeline
- Asks to generate a research paper from scratch
- Mentions "ResearchClaw" by name
Instructions
Prerequisites Check
- Verify config file exists:
ls config.yaml || ls config.researchclaw.example.yaml - If no
config.yaml, create one from the example:cp config.researchclaw.example.yaml config.yaml - Ensure the user's LLM API key is configured in
config.yamlunderllm.api_keyor viallm.api_key_envenvironment variable.
Running the Pipeline
Option A: CLI (recommended)
researchclaw run --topic "Your research topic here" --auto-approve
Options:
--topic/-t: Override the research topic from config--config/-c: Config file path (default:config.yaml)--output/-o: Output directory (default:artifacts/rc-YYYYMMDD-HHMMSS-HASH/)--from-stage: Resume from a specific stage (e.g.,PAPER_OUTLINE)--auto-approve: Auto-approve gate stages (5, 9, 20) without human input
Option B: Python API
from researchclaw.pipeline.runner import execute_pipeline
from researchclaw.config import RCConfig
from researchclaw.adapters import AdapterBundle
from pathlib import Path
config = RCConfig.load("config.yaml", check_paths=False)
results = execute_pipeline(
run_dir=Path("artifacts/my-run"),
run_id="research-001",
config=config,
adapters=AdapterBundle(),
auto_approve_gates=True,
)
# Check results
for r in results:
print(f"Stage {r.stage.name}: {r.status.value}")
Option C: Iterative Pipeline (multi-round improvement)
from researchclaw.pipeline.runner import execute_iterative_pipeline
results = execute_iterative_pipeline(
run_dir=Path("artifacts/my-run"),
run_id="research-001",
config=config,
adapters=AdapterBundle(),
max_iterations=3,
convergence_rounds=2,
)
Output Structure
After a successful run, the output directory contains:
artifacts/<run-id>/
├── stage-1/ # TOPIC_INIT outputs
├── stage-2/ # PROBLEM_DECOMPOSE outputs
├── ...
├── stage-10/
│ └── experiment.py # Generated experiment code
├── stage-12/
│ └── runs/run-1.json # Experiment execution results
├── stage-14/
│ ├── experiment_summary.json # Aggregated metrics
│ └── results_table.tex # LaTeX results table
├── stage-17/
│ └── paper_draft.md # Full paper draft
├── stage-22/
│ └── charts/ # Generated visualizations
│ ├── metric_trajectory.png
│ └── experiment_comparison.png
└── pipeline_summary.json # Overall pipeline status
Experiment Modes
| Mode | Description | Config |
|------|-------------|--------|
| simulated | LLM generates synthetic results (no code execution) | experiment.mode: simulated |
| sandbox | Execute generated code locally via subprocess | experiment.mode: sandbox |
| ssh_remote | Execute on remote GPU server via SSH | experiment.mode: ssh_remote |
Troubleshooting
- Config validation error: Run
researchclaw validate --config config.yaml - LLM connection failure: Check
llm.base_urland API key - Sandbox execution failure: Verify
experiment.sandbox.python_pathexists and has numpy installed - Gate rejection: Use
--auto-approveor manually approve at stages 5, 9, 20
Tools Required
- File read/write (for config and artifacts)
- Bash (for CLI execution)
- No external MCP servers required for basic operation
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/researchclaw-autonomous-research-pipeline-mrwakcx1/download' --output '.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1/SKILL.md.part' && mv '.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1/SKILL.md.part' '.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1/SKILL.md' && test -s '.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/researchclaw' && cp -R '.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1' '.claude/skills/researchclaw'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1'openskills read 'researchclaw-autonomous-research-pipeline-mrwakcx1'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/researchclaw-autonomous-research-pipeline-mrwakcx1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Create Interactive Maps with kepler.gl
Data & AI
Create interactive map visualizations and export standalone HTML using the keplergl Python package. Use to plot geospatial data from DataFrames, GeoJSON, or CSV.
Agent-Driven Parameter Optimization
Data & AI
Guide for optimizing configurable systems with a measurable objective, using bounded trials and evidence-based recommendations.
ICP Visitor Outreach
Data & AI
Identify signed-up users matching the ideal customer profile but stalled, and draft personalized outreach to re-engage them.