lythoskill-project-scribe SKILL.md skillA
lythoskill-project-scribe from lythos-labs/lythoskill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lythos-labs/lythoskill/lythoskill-project-scribe@v0.21.0Pins v0.21.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lythos-labs/lythoskill
- Path
skills/lythoskill-project-scribe/SKILL.md- Versions recorded
- 12
- Latest version
- v0.21.0, committed Oct 30, 2026
- First version recorded
- Sep 9, 2026
- Size
- 18,064 bytes
- Repository stars
- 3
- License
- MIT
Session context dump. Self-assess what the conversation contains that has NO other carrier (no task, no ADR, no epic) — pitfalls, working-tree anomalies, why-we-chose-this, specific next steps — and write to daily/YYYY-MM-DD.md. Things WITH structured carriers go to their carriers AND get one Batch Index line in the handoff (refs + read-when trigger), so carrier-complete batches stay visible to onboarding. Things WITHOUT carriers but needed by the next agent go here. Forms CQRS write-side…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Project Scribe > Write what `ls` + `cat` + `git log` cannot recover. Skip everything else. ## Trigger: save discipline, not session-end The intent is the old **save-to-disk discipline**: save constantly, because a power cut can hit at any moment. For an agent the power cut is compaction / crash / context loss: it can hit mid-task with no warning, and only git-tracked, already-written files survive it. Scribe = save game; the daily file is the save slot. The reliable save anchor is a **batch of commits landing** — scribe right after, while facts are fresh. A session cannot judge its own remaining context; "write the handoff when the session feels done" is unreliable and produces rushed, telegraphic output. Anchor to the commit, not the mood. `## Session Handoff` names the artifact the NEXT session reads, not the moment you write it. One session saves any number of times; saving says nothing about this session ending (record-then-continue is the default, see below). ## Value Boundary **Scribe = session context dump for things WITHOUT structured carriers.** ``` What came out of this conversation? ├── Has a structured carrier (task/ADR/epic/experiment/wiki) → write …
Read the whole file at its exact version.
How to install
mdr add lythos-labs/lythoskill/lythoskill-project-scribe@sha256:7d6fbfb1adea7168The line at the top of this page pins the label v0.21.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t6lhl54b6guxu5ul)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 12 versions of this file, between Sep 9, 2026 and Oct 30, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.21.0 latest | 2026-10-30 | d2f9847 | 18,064 B | A | view · diff |
| v0.21.0 | 2026-10-30 | 51ad063 | 17,801 B | A | view · diff |
| v0.21.0 | 2026-10-30 | 8b2f8af | 17,541 B | A | view · diff |
| v0.21.0 | 2026-10-30 | 133cce3 | 16,701 B | A | view · diff |
| v0.21.0 | 2026-10-23 | afa7efd | 13,570 B | A | view · diff |
| v0.20.1 | 2026-10-14 | 0e42b7b | 13,570 B | A | view · diff |
| v0.20.0 | 2026-10-13 | da50fe4 | 13,570 B | A | view · diff |
| v0.19.3 | 2026-09-11 | b988114 | 13,570 B | A | view · diff |
| v0.19.2 | 2026-09-11 | 8f116d7 | 13,570 B | A | view · diff |
| v0.19.1 | 2026-09-10 | 888ad76 | 13,570 B | A | view · diff |
| v0.19.1 | 2026-09-09 | bc2053c | 13,024 B | A | view · diff |
| v0.19.1 | 2026-09-09 | c3edaf7 | 12,956 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 (18064 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
lythos-labs/lythoskill · 3 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t6lhl54b6guxu5ul GET https://markdownregistry.com/api/v1/resolve?ref=lythos-labs/lythoskill/lythoskill-project-scribe GET https://markdownregistry.com/api/v1/blob/7d6fbfb1adea71685b6da13472a47ee9b9e1f5718e6962661220925d2ae09914
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from lythos-labs/lythoskill
Every file in lythos-labs/lythoskill