Claude Multi Session Research Skills
Description
Personal Claude Code skills for running work across several concurrent sessions — one that builds, one that explains, one that audits — and for keeping experimental results trustworthy enough to cite later.
Installation
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open the source below and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
README
Claude Code skills
A personal skill set for running work across several Claude Code sessions — one that builds, one that explains, one that audits — and for keeping experimental results trustworthy enough to cite months later.
These are **not** a framework. Every rule here exists because a specific mistake got through, and each one carries the failure that produced it. They are written to be edited: see `skill-maintenance`.
Two layers
Skills here are **generic** — they should help a project with entirely different subject matter. Anything that needs a particular project's nouns belongs in that project's own skill (`/.claude/skills//`), not here.
| skill | what it owns |
|---|---|
multi-session-protocol |
Roles; who owns a claim and its scope; who may close a finding; how a retraction propagates instead of staying alive in documents nobody re-read. Load first when sessions share a project. |
experiment-engineering |
The build role. Your own pipeline is the first suspect behind a result; decomposing a null against a published configuration; long jobs that survive interruption. |
experiment-provenance |
Append-only run directories; what a run's metadata must answer; when a result may not be cited; grading design decisions A/B/C; pre-registering before the run. |
research-companion |
The learn role. Explaining a codebase at the user's pace, graded literature work, re-deriving the builder's numbers before believing them. |
project-audit |
The audit role. Checking claims against the filesystem rather than against conversation. Never briefed by the sessions it audits. |
study-notes |
Turning a study session into atomic Obsidian notes with a linking index. |
publishing-to-github |
Publishing a repo and keeping it updated: the checks before an irreversible first push, and explaining every subsequent one — what changed, why, and what a user should do differently. |
skill-maintenance |
Keepin |
Related Skills
Auto Update
Pull the latest ECC repo changes and reinstall the current managed targets.
Ecc Guide
Navigate ECC's current agents, skills, commands, hooks, install profiles, and docs from the live repository su
Epic Claim
Claim an epic issue, stamp coordination state, and sync local ownership.
Epic Publish
Publish a validated epic update back to the issue and local cache.
Epic Review
Mark epic review requested, approved, or changes requested.
Epic Unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.