setup-methods

Scaffold session-local interpretability method stubs from set_up_method specifications.

108|37|Updated Apr 25, 2025
One-click install
npx skills add https://github.com/goodfire-ai/causalab --skill setup-methods
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-methods
Source: https://github.com/goodfire-ai/causalab/tree/main/.claude/skills/setup-methods
Command: npx skills add https://github.com/goodfire-ai/causalab --skill setup-methods

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of creating new session-local interpretability “method” primitives by turning a structured method spec into runnable Python code with tests and documentation, following strict layering rules.

Core Features & Use Cases

  • Scaffold session-local method code: Generates ${SESSION_DIR}/code/methods/<name>/ with an importable module, a placeholder implementation, and a smoke test.
  • Elicit or consume method specifications: Supports interactive single-spec elicitation or batch scaffolding from one or more provided spec paths.
  • Enforce interpretability-layer invariants: Refuses forbidden imports (e.g., from runner/ or analyses/) and keeps methods pure (no disk I/O and no hyperparameter defaults in code).
  • Batch approval workflow: In interactive mode, presents a consolidated batch summary so you can approve or edit specs before code scaffolding.

Quick Start

Run /research-session first, then invoke setup-methods with one or more method spec paths, for example: “/setup-methods path/to/method_1/set_up_method.md path/to/method_2/set_up_method.md”.

Frequently Asked Questions about setup-methods

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

FAQPage Schema
How do I scaffold reusable interpretability methods for mechanistic research workflows?

Scaffolding reusable interpretability methods turns a structured set_up_method spec into runnable Python code with tests under a session directory. It generates an importable module, placeholder implementation, and smoke test while enforcing layering rules.

What is the best way to generate Python method stubs with shape-and-dtype test scaffolds?

Generating Python method stubs with shape-and-dtype test scaffolds uses batch or interactive spec elicitation to produce in-memory, non-disk I/O method primitives. It writes code under the session directory with strict layering invariants and no hyperparameter defaults.

Can I batch scaffold multiple interpretability method specs in a single research session?

Batch scaffolding multiple interpretability method specs is supported by providing one or more spec paths to the tool. In interactive mode, it presents a consolidated batch summary so you can approve or edit specs before code generation begins.

Does scaffolding interpretability method primitives enforce import restrictions for layer purity?

Scaffolding interpretability method primitives enforces import restrictions by refusing forbidden imports from runner or analyses modules. This keeps methods pure with no disk I/O and no hyperparameter defaults in the generated code.

Do I need an active research session before scaffolding mechanistic interpretability methods?

An active research session is required before scaffolding mechanistic interpretability methods because the tool writes generated code under the session directory. You must run the research session initialization first, then invoke the scaffolding with method spec paths.

What limitations exist when scaffolding session-local interpretabilty method primitives?

Limitations of scaffolding session-local interpretability method primitives include strict enforcement of in-memory operations with no disk I/O and no hyperparameter defaults in code. Forbidden imports from runner or analyses modules are refused to maintain layering invariants.