mechanism-explore

Plans strategic research directions for investigating mechanisms behind observed LLM behaviors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Once you have observed a behavior in a large language model, it is hard to decide how to investigate its internal cause. This Skill provides a macro-level strategy layer that selects and orders research directions for explaining the mechanism behind a validated phenomenon. ## Core Features & Use Cases - Six Research Directions: Choose among Location, Causal Intervention, Tuning & Editing, Formation Tracing, Unit Interpretation, and Decision Auditing, each answering a distinct question about the model. - Strategy Composition: Chain directions into complete strategies such as mechanistic evidence (Location + Causal Intervention), capability editing, complete accounts, model explanation, or decision reliability. - Outcome-Aware Planning: When prior investigation records exist, propose only untried or inconclusive directions, avoiding re-testing confirmed or refuted claims. - Use Case: After discovering that a model exhibits a specific behavior, use this Skill to decide whether to first localize the responsible component, then causally validate it via ablation or activation patching, producing a defensible mechanism claim. ## Quick Start Ask the assistant to design mechanism-research strategies for a validated model behavior, specifying any prior investigation outcomes or pinned directions.

Frequently Asked Questions about mechanism-explore

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

FAQPage Schema
How do I investigate the mechanism behind an LLM behavior?

Start with the Location direction to find candidate components using probing, attribution, or circuit discovery, then apply Causal Intervention such as ablation or activation patching to confirm the component causes the behavior. This two-step chain forms the mechanistic evidence strategy.

What is the difference between causal intervention and tuning in interpretability?

Causal intervention is diagnostic: it tests whether a component causes a behavior by ablating or steering it. Tuning and editing is applied: it modifies the located component to improve downstream task performance, judged by capability gains rather than a causal verdict.

When should I use formation tracing in mechanistic interpretability?

Use formation tracing only when the origin of a component is part of your claim, since it is the most expensive direction. It tracks how a component emerges across training checkpoints and which training data is critical via influence functions or data ablation.

Can I interpret model neurons without training a sparse autoencoder?

Yes. When an SAE is unavailable or too costly, use ICA to recover interpretable directions directly from activations, or apply model-explains-model auto-interpretation where a stronger LLM writes and scores natural-language explanations of the weaker model's units.

What are the limitations of location-only interpretability methods?

Location methods are correlational, not causal. A located component is only a hypothesis; without intervention evidence showing sign, magnitude, and specificity, you cannot claim it is the mechanism behind the behavior.