update-project skillA
update-project is agent-read markdown (skill) from tartinerlabs/skills: Use when updating docs, syncing CLAUDE.md, AGENTS.md, or README.md, fixing stale documentation, or refreshing project rules and skills. Keeps docs aligned with code changes..
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
You keep project documentation synchronized with recent code changes and git commits. Run after significant code changes, before a release, or whenever docs may be stale. Update only what the project actually changed. Verify a claim against the tree before you write it, and leave sections you cannot verify alone. Detect which agent the project targets and maintain its instruction file accordingly: `CLAUDE.md` (Claude Code), `AGENTS.md` (Codex and the cross-agent standard), or both. Component directories follow the same split — `.claude/` for Claude Code, `.agents/skills/` for Codex and other hosts that use the cross-agent skills path. Do not invent `.agents/agents` or `.agents/rules`. ## Rules Overview | Rule | Impact | File | |------|--------|------| | Agent docs (CLAUDE.md / AGENTS.md / README.md) | HIGH | `rules/agent-docs.md` | | Components (agents, skills, rules) | MEDIUM | `rules/components.md` | ## Workflow ### Step 1: Detect - Run `git log --oneline -20` and `git diff` to identify recent changes - Check which agent instruction files exist (`CLAUDE.md`, `AGENTS.md`) and whether README.md exists (create if missing) …
Read the whole file at its exact version.
How to install
mdr add tartinerlabs/skills/update-project@git:20260817.d88fd50mdr add tartinerlabs/skills/update-project@sha256:dbf6302e55afa810Pin 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_gjs6oirvixdpooaw)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260817.d88fd50 latest | 2026-08-17 | d88fd50 | 2,531 B | A | view · diff |
| git:20260726.9b1c2f9 | 2026-07-26 | 9b1c2f9 | 2,435 B | A | view · diff |
| git:20260726.40e457e | 2026-07-26 | 40e457e | 2,615 B | A | view · diff |
| git:20260718.45adc4f | 2026-07-18 | 45adc4f | 2,542 B | A | view · diff |
| git:20260713.557db9f | 2026-07-13 | 557db9f | 2,442 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 (2531 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
tartinerlabs/skills · 8 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gjs6oirvixdpooaw GET https://markdownregistry.com/api/v1/resolve?ref=tartinerlabs/skills/update-project GET https://markdownregistry.com/api/v1/blob/dbf6302e55afa810c034146923d00ad38e3420453df2c94a408ffb48c96a44f0
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.