Explore Code (RigorPilot)
Bounded candidate code changes on isolated branches — module transplants, backbone adaptation, LoRA insertion — with rollback-aware records, never touching the trusted baseline
- What
- Bounded candidate code changes on isolated branches — module transplants, backbone adaptation, LoRA insertion — with rollback-aware records, never touching the trusted baseline
- Cost
- Free
- Needs
- a deep-learning repo you control (git branching), and explicit researcher authorization for exploratory code changes at use time — this skill only modifies code on isolated branches/worktrees.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the RigorPilot "Rigor Improve" implementation leaf skill for auditable candidate implementation in deep-learning research repositories. It applies when the researcher explicitly authorizes exploratory code changes on an isolated branch or worktree: source-anchored module transplants, backbone adaptation, LoRA or adapter layer insertion, head replacement, or stitching together meaningful low-risk migration ideas. The governing principle is isolation — exploratory code modifications stay quarantined from the trusted baseline, favoring source-anchored copying and minimal adaptation over freeform rewrites, with a clear record of why a candidate change is meaningful, how to roll it back, and why it remains a candidate rather than a verified contribution. Execution may hand off to `minimal-run-and-audit` or `run-train`; the skill itself owns the code-change side and writes `explore_outputs/` records (`CHANGESET.md`, `SCIENTIFIC_CHANGELOG.md`, `COMPARABILITY_REPORT.md`, `TOP_RUNS.md`, `status.json`). Narrow fits stay narrow: end-to-end exploration orchestration belongs to `ai-research-explore`, trusted baseline work and conservative debugging belong elsewhere. By @lllllllama, listed here with credit to its creator. Honest caveats: exploratory changes only after explicit researcher authorization — never a default for unapproved repo edits; everything produced stays a candidate, never a verified contribution, until evidence says otherwise; it's a code-change leaf, so it relies on sibling skills (or your own runs) for execution evidence. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Explore Code is a free RigorPilot implementation skill for auditable candidate changes in deep-learning research repositories. It applies only when the researcher explicitly authorizes exploratory changes on an isolated branch or worktree, covering module transplants, backbone adaptation, LoRA insertion, and head replacement, while keeping exploratory code quarantined from the trusted baseline.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit fb3ccdfStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a deep-learning repo you control (git branching), and explicit researcher authorization for exploratory code changes at use time — this skill only modifies code on isolated branches/worktrees. Install "Explore Code (RigorPilot)" for me. The RigorPilot implementation leaf skill: bounded candidate code changes (module transplants, backbone adaptation, LoRA insertion) on isolated branches, with rollback-aware records, summary-level logging, and strict separation from the trusted baseline. Repository: https://raw.githubusercontent.com/lllllllama/rigorpilot-skills/fb3ccdf5aa64b1fa5b1d0463e666a8bc8bc26e01/skills/explore-code/SKILL.md Pinned version: install the code at commit fb3ccdf5aa64b1fa5b1d0463e666a8bc8bc26e01 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "rigorpilot-explore-code". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- fb3ccdf · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.