refiners-update SKILL.md skillA
refiners-update from techygarg/lattice is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add techygarg/lattice/refiners-update@git:20260903.83fa756Pins git:20260903.83fa756 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- techygarg/lattice
- Path
source/molecules/refiners-update/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260903.83fa756, committed Sep 3, 2026
- Size
- 8,722 bytes
- Repository stars
- 206
- License
- MIT
Update existing Lattice standards after a significant change — the update-mode counterpart to lattice-init. Scans .lattice/standards/, asks what changed, and routes each affected standard to its refiner's revise mode, recording a git-native change note. Use when the user says 'update refiners', 'refiners update', 'our standards changed', 'update our standards', 'the architecture changed, update the standards', 'we switched languages, update the standards', 'revise standards after a big…
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
# Refiners Update The update-mode counterpart to `lattice-init`. Where `lattice-init` detects *missing* standards and routes you to refiners to **create** them, this molecule detects *existing* standards and routes you to each refiner's **revise** mode to update them after a significant change — then records what changed and why. It orchestrates the refiners; it never reimplements their interviews. Versioning is git-native: history lives in commits, and each revised document gets a one-line change note. No version numbers are introduced. ## Required Skills Read, apply: 1. `framework:knowledge-priming` -- Load project context. Understand what the project is and how the code has drifted from the current standards (always). ## What This Does (and does not) - **Does**: coordinate revising one or more *existing* standards documents after a change, and append a change note to each. - **Does not**: create standards that do not exist yet (that is `lattice-init` + the relevant refiner), reimplement any refiner's interview, or introduce version numbers. …
Read the whole file at its exact version.
How to install
mdr add techygarg/lattice/refiners-update@sha256:efb0be85f6f2e4fcThe line at the top of this page pins the label git:20260903.83fa756, 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_dazxwoubnxqo3aky)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 3, 2026.
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 (8722 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
techygarg/lattice · 206 stars · license MIT · pushed 2026-10-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dazxwoubnxqo3aky GET https://markdownregistry.com/api/v1/resolve?ref=techygarg/lattice/refiners-update GET https://markdownregistry.com/api/v1/blob/efb0be85f6f2e4fc052684f3d76626687e30f3d366653af4db39944767d2bbb7
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 techygarg/lattice
Every file in techygarg/lattice