aris-ablation-planner

Designs and implements ML ablation studies from a reviewer perspective using Codex and Claude Code.

1.1k|116|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/OpenLAIR/dr-claw --skill aris-ablation-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aris-ablation-planner
Source: https://github.com/OpenLAIR/dr-claw/tree/main/skills/aris-ablation-planner
Command: npx skills add https://github.com/OpenLAIR/dr-claw --skill aris-ablation-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Researchers preparing ML papers often struggle to decide which ablation studies reviewers will demand, wasting GPU hours on uninformative experiments or missing critical ones. This Skill systematically designs, prioritizes, and implements ablation studies that isolate each component's contribution.

Core Features & Use Cases

  • Reviewer-Perspective Design: Codex generates ablations that isolate novel components, test hyperparameter sensitivity, and compare design choices, each with priority and expected outcomes.
  • Feasibility Review and Implementation: Claude Code checks compute budget, code-change requirements, and parallelism, then creates configs, smoke tests, and runs ablations in an optimized order.
  • Use Case: After your main results pass claim verification, invoke this Skill to produce a prioritized ablation plan with GPU-hour estimates, run config-only ablations first, and log all results—including negative findings—into EXPERIMENT_LOG.md.

Quick Start

Ask the assistant to design ablation studies for your method by providing a method description or claim, for example: plan ablations for our joint matching module given the current experiment results.

Frequently Asked Questions about aris-ablation-planner

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

FAQPage Schema
How do I design ablation studies for an ML paper?

Provide your method description, components, current results, and claims. Codex generates ablations that isolate each component, test hyperparameter sensitivity, and compare design choices, each with a priority and expected outcome if the component matters.

When should I run ablation planning in a research workflow?

Run it after main results pass result-to-claim verification with claim_supported yes or partial, when a user explicitly requests ablation planning, or when an auto-review loop identifies missing ablations before paper submission.

How are ablations prioritized when compute budget is limited?

Component ablations rank above hyperparameter sweeps, and config-only changes run before code modifications. If total compute exceeds budget, Claude Code proposes cuts and asks Codex to re-prioritize rather than silently dropping experiments.

Does this Skill handle negative ablation results?

Yes. All ablation outcomes, including cases where removing a component had no effect, are recorded in EXPERIMENT_LOG.md and findings.md, since a null result is treated as an important finding rather than a failure.

What tools does the ablation planner depend on?

It coordinates Codex via MCP for reviewer-perspective design and Claude Code for feasibility review, config creation, smoke testing, and execution. It reads project files like research contracts, experiment logs, and CLAUDE.md for context.