session-chronicle skillA
session-chronicle is agent-read markdown (skill) from terrylica/cc-skills: Session log provenance tracking. TRIGGERS - who created, trace origin, session archaeology, ADR reference..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Session Chronicle Excavate Claude Code session logs to capture **complete provenance** for research findings, ADR decisions, and code contributions. Traces UUID chains across multiple auto-compacted sessions. **CRITICAL PRINCIPLE**: Registry entries must be **self-contained**. Record ALL session UUIDs (main + subagent) at commit time. Future maintainers should not need to run archaeology to understand provenance. **S3 Artifact Sharing**: Artifacts can be uploaded to S3 for team access. See [S3 Sharing ADR](/docs/adr/2026-01-02-session-chronicle-s3-sharing.md). > **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues. ## When to Use This Skill - User asks "who created this?" or "where did this come from?" - User says "document this finding" with full session context - ADR or research finding needs provenance tracking - Git commit needs session UUID references - Tracing edits across auto-compacted sessions - **Creating a registry entry for a research session** --- ## File Ownership Model …
Read the whole file at its exact version.
How to install
mdr add terrylica/cc-skills/session-chronicle@git:20260415.9961df1mdr add terrylica/cc-skills/session-chronicle@sha256:d404f5836469643cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_jnogrehfmifo7t6w)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260415.9961df1 latest | 2026-04-15 | 9961df1 | 16,404 B | A | view · diff |
| git:20260401.b664eaf | 2026-04-01 | b664eaf | 13,875 B | A | view · diff |
| git:20260401.6be22af | 2026-04-01 | 6be22af | 13,653 B | A | view · diff |
| git:20260226.c78f2f5 | 2026-02-26 | c78f2f5 | 13,083 B | A | view · diff |
| git:20260131.61c297b | 2026-01-31 | 61c297b | 25,309 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16404 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
terrylica/cc-skills · 74 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jnogrehfmifo7t6w GET https://markdownregistry.com/api/v1/resolve?ref=terrylica/cc-skills/session-chronicle GET https://markdownregistry.com/api/v1/blob/d404f5836469643cc58e42f4cdecce9e96dc6a8532fda99bfe7d2a1155c0f9f8
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.