pyvene-interventions

Provides guidance for performing causal interventions on PyTorch models using pyvene's declarative intervention framework. Use when conducting causal tracing, activation patching, interchange intervention training, or testing causal hypotheses about model behavior.

by Orchestra-Research 12k GitHub stars MIT Updated Jun 16, 2026
pyvene-interventions skill by Orchestra-Research
pyvene-interventions — Testing skill by Orchestra-Research

Overview

pyvene-interventions is an open-source testing skill for Claude Code and compatible agents, published by Orchestra-Research. Its author describes it as: “Provides guidance for performing causal interventions on PyTorch models using pyvene's declarative intervention framework. Use when conducting causal tracing, activation patching, interchange intervention training, or…”. The project has 12k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add Orchestra-Research/AI-Research-SKILLs`.

What pyvene-interventions does

pyvene is Stanford NLP's library for performing causal interventions on PyTorch models. It provides a declarative, dict-based framework for activation patching, causal tracing, and interchange intervention training - making intervention experiments reproducible and shareable.

What’s inside

The SKILL.md for pyvene-interventions is organised into these sections:

  • When to Use pyvene
  • Installation
  • Core Concepts
  • IntervenableModel
  • Intervention Types
  • Component Targets
  • Workflow 1: Causal Tracing (ROME-style)
  • Step-by-Step
  • Checklist
  • Workflow 2: Activation Patching for Circuit Analysis
  • Workflow 3: Interchange Intervention Training (IIT)
  • DAS (Distributed Alignment Search)

Installation

Add pyvene-interventions to your agent with:

/plugin marketplace add Orchestra-Research/AI-Research-SKILLs

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Claude Code — ships a claude code plugin marketplace
  • Codex — declared in the repository topics

License

pyvene-interventions is published under the MIT license.

Strengths

  • Clear MIT license — safe to read and adapt within its terms
  • Ships in Orchestra-Research/AI-Research-SKILLs, an established project with 11,807 GitHub stars
  • Works with Claude Code, Codex

Author

Orchestra-Research 41 skills in the catalog · GitHub profile ↗
View skills

Topics

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does pyvene-interventions do?
Provides guidance for performing causal interventions on PyTorch models using pyvene's declarative intervention framework. Use when conducting causal tracing, activation patching, interchange intervention training, or testing causal hypotheses about model behavior.
How do I install pyvene-interventions?
Run /plugin marketplace add Orchestra-Research/AI-Research-SKILLs in your agent, then reload your skills. Review the source at https://github.com/Orchestra-Research/AI-Research-SKILLs before installing.
Is pyvene-interventions free to use?
Yes. pyvene-interventions is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
Which agents does pyvene-interventions work with?
pyvene-interventions lists Claude Code and Codex — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does pyvene-interventions come from?
pyvene-interventions ships inside Orchestra-Research/AI-Research-SKILLs, a repository that contains 41 catalogued skills in total. The repository's 11,807 GitHub stars apply to that whole collection, not to this skill on its own.

QA opencode itself, per case: verify the CLI/terminal (opencode run, db, serve, export), prove a specific plugin hook/action/event fired via the SSE event stream, smoke-test the TUI under tmux, and investigate sessions in opencode's SQLite DB by id, title/name, or message text. Ships tested helper scripts (each with a --self-test) plus per-domain references. Use whenever someone wants to QA, smoke-test, verify, or debug opencode's CLI, HTTP server, plugin hooks/events, or TUI, or to find/inspect opencode sessions in the database. Triggers: opencode qa, qa opencode, test opencode, verify opencode hook, opencode session db, find opencode session by id/name/text, opencode tui test, opencode server health, opencode event stream.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

QA the omo Senpi adapter (packages/omo-senpi, packages/senpi-task) against the REAL senpi binary in strict isolation, and write every artifact to the one canonical evidence path .omo/evidence/omo-senpi-adapter/<slug>/. The live drivers under packages/omo-senpi/scripts/qa/ create their own isolated SENPI_CODING_AGENT_DIR and ignore the caller's, so the real ~/.senpi/agent is never written. Ships scripts/resolve-evidence-dir.mjs, which is the ONLY sanctioned way to pick an evidence directory: it rejects traversal, separators, absolute paths, and stray roots such as local-ignore/qa-evidence. Use whenever someone changes anything under packages/omo-senpi or packages/senpi-task, or wants to QA, smoke-test, verify, or debug the Senpi adapter, the task/team engine, the DAG, task RPC, or skill delivery. Triggers: senpi qa, qa senpi, senpi-qa, test senpi adapter, verify senpi task, senpi task e2e, senpi team e2e, task dag qa, live senpi driver, senpi evidence path.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free

Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free