mguide

Converts natural-language research requests into task.md files and launches Mechanist experiment runs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Researchers using Mechanist should not have to learn parameter syntax, master writing a compliant task.md, or memorize which skills exist. This Skill acts as a single conversational front door that routes any request to the right place. ## Core Features & Use Cases - Experiment setup (Track A): Works out research requirements through conversation, settles the behavior-source and mechanism parameter axes, writes a compliant task.md into the project root, and submits the /auto run after user confirmation. - Literature search (Track B): Hands explicit search requests directly to /msearch for multi-source retrieval and synthesis. - Field history (Track C): Routes survey and evolution-of-a-field requests to /mhistory for a timeline-based article. - Use Case: A user says "verify whether small models track false beliefs worse than facts." The Skill infers the parameter axes, probes the disk for models and GPUs, asks only what cannot be inferred, writes task.md, and launches the run. ## Quick Start Tell the assistant what you want to study, look up, or survey in plain language and it will set up the experiment or fetch the literature for you.

Frequently Asked Questions about mguide

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

FAQPage Schema
How do I run a mechanistic interpretability experiment without learning pipeline parameters?

Describe what you want to study in plain language. The Skill infers the behavior-source axis from your phrasing, asks only about what cannot be inferred such as method, model, and GPU budget, writes a compliant task.md, and submits the run after you confirm.

How do I search interpretability literature or trace a field's history?

State an explicit search intent like "find papers on X" to be routed to multi-source literature retrieval, or ask "how did X develop" to receive a history article with a real timeline arc. Each request maps to exactly one track.

What happens if task.md already exists in my project directory?

The Skill runs a health check on the existing file and offers three options: run it as written, revise it in place preserving your wording, or back it up to task.md.bak and start fresh. It never silently overwrites the file.

Can I resume an interrupted Mechanist experiment run?

Yes. The Skill probes the working directory for artifacts like refine-logs and CLAIMS_LEDGER.md to detect incomplete runs, then offers to resume with the unfinished parts filled in, modify the running experiment, or start a new round.

When should I declare no mechanistic-interpretability method for a round?

Choose the no-method option when you want conclusions about the phenomenon itself, such as whether it holds and under which conditions, leaving mechanism analysis to a later round. This lands as mechanism given with not-applicable.