co-write SKILL.md skillA
co-write from jkaloger/lazyspec is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jkaloger/lazyspec/co-write@git:20260903.f1f85b0Pins git:20260903.f1f85b0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jkaloger/lazyspec
- Path
skills/co-write/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260903.f1f85b0, committed Sep 3, 2026
- First version recorded
- Jun 23, 2026
- Size
- 4,293 bytes
- Repository stars
- 10
- License
- MIT
Use when drafting a document of a configured type collaboratively -- AI proposes a draft body, the human edits, iterate -- up to the type's authorship ceiling.
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
``` PROPOSE A DRAFT, THE HUMAN EDITS, ITERATE ``` <HARD-GATE> Do NOT proceed when the target type's `authorship` ceiling is `human` -- that type tops out at scaffold. Read the ceiling from `lazyspec config --json` and refuse, naming the ceiling. Co-write proposes a draft for human editing; it does not finalise a body unilaterally. </HARD-GATE> <NEVER> - Do NOT hand-edit document files. The CLI is the only writer: `lazyspec create` (seed with `--body`), `lazyspec link`, and `lazyspec update <id> --body` to change body content. This holds for EVERY store, filesystem included. - Do NOT edit a document you haven't read. Always `lazyspec show <id> --json` or `Read` first. - Do NOT skip the workflow pipeline. Respect the configured DAG -- type boundaries come from the `edges` table and from nothing else; honor every edge. </NEVER> <BODY-CONTENT> Set body at creation: `lazyspec create <type> "<title>" --body "content"`. Change it later: `lazyspec update <ID> --body "content"`. Prefer `--body` over any direct file edit, for ALL stores (filesystem and github-issues alike). …
Read the whole file at its exact version.
How to install
mdr add jkaloger/lazyspec/co-write@sha256:8e840eb1f46eef40The line at the top of this page pins the label git:20260903.f1f85b0, 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_iaxcz55qv2o3xs2q)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 23, 2026 and Sep 3, 2026, about one every 72 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.f1f85b0 latest | 2026-09-03 | f1f85b0 | 4,293 B | A | view · diff |
| git:20260623.d2a2f44 | 2026-06-23 | d2a2f44 | 4,098 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 (4293 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
jkaloger/lazyspec · 10 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iaxcz55qv2o3xs2q GET https://markdownregistry.com/api/v1/resolve?ref=jkaloger/lazyspec/co-write GET https://markdownregistry.com/api/v1/blob/8e840eb1f46eef40069a19ea9e13f261411e3c3f3e8d2880b5367a46d8e33fb7
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.