work-tracking skillA
work-tracking is agent-read markdown (skill) from clickety-clacks/tightbeam: Tracking policy over the substrate's work records — when to create them, at what grain, and what a fact must contain. Use when deciding whether work needs a record and how to record it..
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 before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Work tracking Tracking policy over the substrate's work records. The records are not bookkeeping: they are the state a reset session rebuilds its board from, so a fact you do not write is a fact the next you cannot recover. (The operating manual teaches the mechanism — work-items, assignments, attests; this is the policy for using them well.) - Create a work-item when a feature, bug, or investigation will outlive one session's context or involve more than one session. One work-item per feature or bug; sub-steps are assignments on it, not new work-items — genuinely new discovered scope goes back up to the work-item's owner as a proposal, never minted sideways. When the work is driven from a spec, bind the spec to the work-item by content (`--spec-ref <name> --spec-sha256 <hex>`) so the thread names the exact spec version it serves. - Every delegated obligation is an assignment on the work-item, held by one session. The holder owes an outcome fact: a completion or a verdict. A cannot-proceed filing records why the still-open card cannot move. An assignment with none of these is open work, and the holder is accountable for it. …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/work-tracking@git:20260831.c321d74mdr add clickety-clacks/tightbeam/work-tracking@sha256:d72aaf4c50ae893dPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_lzfv7xtm24hxbq76)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260831.c321d74 latest | 2026-08-31 | c321d74 | 2,121 B | A | view · diff |
| git:20260723.7608dd1 | 2026-07-23 | 7608dd1 | 2,059 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 (2121 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
clickety-clacks/tightbeam · 14 stars · license none · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lzfv7xtm24hxbq76 GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/work-tracking GET https://markdownregistry.com/api/v1/blob/d72aaf4c50ae893da437818a202698751ea157abff118d9e8bcfd35b5c78c961
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.