auto

Orchestrates autonomous research pipelines from claim generation through experiments to verification and iteration.

75|7|Updated May 2, 2026
One-click install
npx skills add https://github.com/zjunlp/Mechanist --skill auto-zjunlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto
Source: https://github.com/zjunlp/Mechanist/tree/main/skills/auto
Command: npx skills add https://github.com/zjunlp/Mechanist --skill auto-zjunlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a full mechanistic interpretability research workflow — literature review, hypothesis formulation, experiment execution, robustness verification, and iterative refinement — requires manually chaining many stages and agents. This Skill automates that entire pipeline end-to-end, delegating each stage to an isolated agent with its own context window and configurable model. ## Core Features & Use Cases - Multi-Stage Orchestration: Chains claim, experiment, verify, and iteration stages, each running in a dedicated agent with per-stage model selection (opus/sonnet/haiku) and AUTO_PROCEED-governed gates. - Flexible Behavior & Mechanism Modes: Supports given, given-validation, and discovery behavior sources, plus user-specified or auto-routed mechanism families, including a phenomenon-validation M0 gate. - Resume & Safety Guards: RESUME mode skips completed stages based on artifact checks, and a multi-round guard prevents silently overwriting prior-round outputs. - Use Case: A researcher provides a research direction about an LLM behavior, and the pipeline autonomously generates claims, runs mechanism experiments on local GPUs, stress-tests claims with swap variants, and iterates until a target review score is reached. ## Quick Start Run the auto pipeline with a research direction such as asking it to investigate how a specific model behavior emerges internally, optionally overriding flags like auto-proceed or per-stage models.

Frequently Asked Questions about auto

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

FAQPage Schema
How do I run an autonomous research pipeline from a research question?

Invoke the auto pipeline with a research direction as an argument, or place the direction in a task.md file. The orchestrator chains claim, experiment, verify, and iteration stages automatically, running end-to-end without confirmation by default.

How do I resume an interrupted pipeline run without restarting?

Set RESUME to true when invoking the pipeline. The orchestrator checks each stage's completion artifacts on disk, skips finished stages, and forwards resume mode to incomplete stages so they continue at phase level.

Can I use different models for each pipeline stage?

Yes, set a global MODEL family alias (opus, sonnet, or haiku) or per-stage overrides like CLAIM_MODEL and VERIFY_MODEL. Per-stage settings take precedence, and version pinning is managed in the agent frontmatter files.

What happens if the phenomenon being studied cannot be validated?

When behavior source is given-validation or discovery, the experiment stage runs an M0 phenomenon-validation gate first. A not-established verdict ends the pipeline with a negative-result report, skipping verify and iteration.

Does the pipeline overwrite results from a previous run?

No, a multi-round guard halts fresh runs when un-archived prior artifacts like CLAIMS_LEDGER.md exist. You must archive the round, resume it, or manually delete the artifacts before proceeding.