Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lllllllama avatar

Explore Code

  • 429 installs
  • 513 repo stars
  • Updated July 26, 2026
  • lllllllama/ai-paper-reproduction-skill

This is a copy of explore-code by lllllllama - installs and ranking accrue to the original listing.

explore-code is a Claude agent skill that navigates unfamiliar ML paper codebases to locate training scripts, configs, datasets, and entrypoints for developers reproducing published results before drafting an implementat

About

explore-code is a skill from lllllllama/ai-paper-reproduction-skill that helps agents orient inside third-party ML research repositories. Before writing a reproduction plan, it systematically finds training scripts, configuration files, dataset loaders, and main entrypoints that authors used to produce published numbers. Developers reach for explore-code when cloning a paper's GitHub repo and facing an unfamiliar layout—multiple experiment folders, nested configs, or undocumented launch commands. The skill reduces time lost grep-wandering and prevents wrong-script execution that wastes GPU hours. It pairs with downstream reproduction skills by delivering a navigable map of the codebase's execution paths and data dependencies.

  • Maps ML repo layout quickly
  • Finds train and eval entrypoints
  • Surfaces config and dataset hooks
  • De-risks paper reproduction effort
  • Guides agentic codebase exploration

Explore Code by the numbers

  • 429 all-time installs (skills.sh)
  • +12 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lllllllama/ai-paper-reproduction-skill --skill explore-code

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs429
repo stars513
Last updatedJuly 26, 2026
Repositorylllllllama/ai-paper-reproduction-skill

How do you find training entrypoints in paper code?

Navigate unfamiliar ML paper codebases to locate training scripts, configs, datasets, and entrypoints when reproducing published results before committing to a full implementation plan.

Who is it for?

ML engineers cloning research paper repositories who need a structured codebase orientation before committing GPU time to reproduction.

Skip if: Implementing novel architectures from scratch with no reference repo, or production deployment tasks unrelated to paper code exploration.

When should I use this skill?

The developer is reproducing published ML results and needs to locate training scripts, configs, datasets, or entrypoints in an unfamiliar repo.

What you get

Identified training scripts, config files, dataset paths, and main entrypoints mapped across the paper's codebase.

  • entrypoint map
  • config and dataset path inventory
  • training script locations

Files

SKILL.mdMarkdownGitHub ↗

explore-code

Use this as the Rigor Improve implementation leaf skill. The installed slug remains explore-code for compatibility.

Use the shared operating principles in ../../references/agent-operating-principles.md; this skill should guide bounded candidate code work without over-prescribing implementation details.

When to apply

  • When the researcher explicitly authorizes exploratory code changes on an isolated branch or worktree.
  • When the task is source-anchored module transplant, backbone adaptation, LoRA or adapter insertion, or low-risk module combination.
  • When summary-level recording is sufficient and the result is a candidate, not a trusted conclusion.

When not to apply

  • When the request is for trusted baseline work, conservative debugging, or normal training execution.
  • When the user did not explicitly authorize exploratory modifications.
  • When the task is a broad refactor or a from-scratch idea implementation.

Clear boundaries

  • This skill owns exploratory code modifications only.
  • It must keep work isolated from the trusted baseline.
  • Use ai-research-explore instead when the task spans both current_research coordination and exploratory runs.
  • It may hand off execution to minimal-run-and-audit or run-train.
  • It should favor source-anchored copying and minimal adaptation over freeform rewrites.
  • It should record why a candidate change is meaningful, how to roll it back,

and why it remains a candidate rather than a verified contribution.

Output expectations

  • explore_outputs/CHANGESET.md
  • explore_outputs/SCIENTIFIC_CHANGELOG.md
  • explore_outputs/COMPARABILITY_REPORT.md
  • explore_outputs/TOP_RUNS.md
  • explore_outputs/status.json

Notes

Use references/explore-policy.md, ../../references/research-rigor-principles.md, scripts/plan_code_changes.py, and scripts/write_outputs.py.

Related skills

How it compares

Use explore-code before writing reproduction code when the blocker is understanding repo layout rather than implementing model math.

FAQ

What does explore-code produce before reproduction?

explore-code produces a navigable map of training scripts, configuration files, dataset paths, and main entrypoints in an ML paper repository—inputs for a full reproduction implementation plan.

When should explore-code run in paper reproduction?

explore-code should run immediately after cloning a paper's repository and before committing to a full implementation plan, so training paths and data dependencies are identified early.

AI & Agent Buildingresearchllmautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.