SkillRunes
Analyse coding-agent session transcripts and recursively improve a SKILL.md file.
SkillRunes turns past coding-agent sessions into reusable project memory. It
reads local transcript files, extracts what the assistant tried, what worked,
what failed, and what patterns are worth remembering, then uses those learnings
to generate or update a project SKILL.md.
The goal is simple: each time you run SkillRunes, your project-level assistant instructions get a little sharper.
SkillRunes is provider-based. The first working provider is Claude Code. Codex support is planned and exposed as an experimental provider path, but transcript ingestion is not implemented yet.
How It Works
- SkillRunes scans transcript files for the current project.
- New sessions are parsed and archived locally.
- A model extracts structured session summaries.
- SkillRunes synthesizes those summaries into a versioned
SKILL.md. - The dashboard shows session metrics, failure patterns, and skill history.
All SkillRunes state is written inside the current project under .skillrunes/.
Install
pip install skillrunes
Usage
# Initialise for the current project
skillrunes init
# Analyse new sessions and update SKILL.md
skillrunes run
# Choose a transcript provider explicitly
skillrunes run --provider claude_code
# Preview changes without writing files
skillrunes run --dry-run
# Launch the local observability dashboard
skillrunes visualize
Setup
SkillRunes needs model access when running transcript analysis.
You can use an Anthropic API key:
cp .env.example .env
# Edit .env and set ANTHROPIC_API_KEY=sk-ant-...
Or, if no ANTHROPIC_API_KEY is set, SkillRunes falls back to the local Claude
Code CLI:
claude --print
That means SkillRunes can run without an Anthropic API key as long as Claude
Code is installed and authenticated. Without either an API key or a working
Claude Code login, skillrunes run cannot extract summaries.
Provider selection can also be configured with:
export SKILLRUNES_PROVIDER=claude_code
Providers
Supported provider names today:
claude_code— supported, defaultcodex— planned / experimental; currently raises a clear not-implemented error
The Claude Code provider reads JSONL transcripts from ~/.claude/projects/ and
matches sessions to the current working directory.
Local Files
Running SkillRunes creates:
.skillrunes/sessions/— raw transcript archives and extracted summaries.skillrunes/skills/— versionedSKILL.mdhistory.skillrunes/metrics.json— dashboard metricsSKILL.md— the current generated skill file
Roadmap
- Claude Code provider
- Codex provider
- Cursor provider
- Provider-agnostic dashboard
Metadata
Release files for skillrunes 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| skillrunes-0.1.1.tar.gz | 30.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skillrunes-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 68.5 kB
Release files / skillrunes-0.1.1.tar.gz
| Download URL | skillrunes-0.1.1.tar.gz |
|---|---|
| Size | 30.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a164078ef834891cdc98bf8cde517d1e2da53bfb4482a19dbedf10b46fba0e4b
|
|
BLAKE2b-256 checksum How to use checksums |
3213f4f0090b632c00400f355acc5bd08d30801718c93060d659d89df82462c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 27, 2026.
Transparency logRelease files / skillrunes-0.1.1-py3-none-any.whl
| Download URL | skillrunes-0.1.1-py3-none-any.whl |
|---|---|
| Size | 38.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e68ff8f46cfdf9fd98e06183857520847a4ab2bbff50e1e9abaaeb971fff61f
|
|
BLAKE2b-256 checksum How to use checksums |
9050307eff438464fba9c02f63e01d7d37abc8b3ce900dc520eccb9cbf143c13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 27, 2026.
Transparency log