mechinterp-next-step-planner

Analyze hypotheses and evidence to generate 2-3 ExperimentSpec JSON files.

1|Updated Jul 9, 2024
One-click install
npx skills add https://github.com/cesaregarza/SplatNLP --skill mechinterp-next-step-planner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mechinterp-next-step-planner
Source: https://github.com/cesaregarza/SplatNLP/tree/main/.claude/skills/mechinterp-next-step-planner
Command: npx skills add https://github.com/cesaregarza/SplatNLP --skill mechinterp-next-step-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes current hypotheses and evidence in mechanistic interpretability research to identify the most informative next experiments and generate ready-to-run specifications.

Core Features & Use Cases

  • Analyze hypotheses, evidence, and gaps to recommend 2-3 experiments that maximize discriminative power.
  • Generate ExperimentSpec JSON files directly to the specs directory for execution by mechinterp-runner.
  • Enforce guardrails (one-rung-per-family, ReLU floor, evidence diversification, hypothesis coverage, token-influence planning) to ensure safe, interpretable experimentation.

Quick Start

Run the planner on the current research state to produce the next-step experiment specs in the specs directory.

Frequently Asked Questions about mechinterp-next-step-planner

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

FAQPage Schema
How do I plan mechanistic interpretability experiments from existing hypotheses?▼

Planning mechanistic interpretability experiments involves analyzing current hypotheses and supporting evidence to identify gaps, then generating 2-3 ExperimentSpec JSON files that maximize discriminative power.

What guardrails do I need for safe mechanistic interpretability experimentation?▼

Mechanistic interpretability experimentation guardrails include one-rung-per-family constraints, ReLU floor checks, evidence diversification, hypothesis coverage, and token-influence planning to ensure interpretable and safe results.

How do I generate experiment specifications for mechanistic interpretability research?▼

You generate experiment specifications by analyzing your research state and outputting 2-3 ExperimentSpec JSON files directly to the specs directory for execution by the runner.

Can I use this approach to decide which mechanistic interpretability hypothesis to test next?▼

Yes, you decide which mechanistic interpretability hypothesis to test next by evaluating existing evidence gaps and proposing next-best experiments that maximize discriminative power across multiple hypotheses.

What is the best way to structure mechanistic interpretability experiment specs for automated execution?▼

The best way to structure mechanistic interpretability experiment specs is generating ExperimentSpec JSON files in the specs directory, ensuring they meet hypothesis coverage and token-influence constraints for runner execution.

Why does my mechanistic interpretability experiment planning fail without evidence diversification?▼

Mechanistic interpretability experiment planning fails without evidence diversification because it risks generating redundant specs lacking discriminative power across competing hypotheses, violating required guardrails.