verify-optimistic-update SKILL.md skillA
verify-optimistic-update from reticlehq/reticle is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add reticlehq/reticle/verify-optimistic-update@v3.9.0Pins v3.9.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- reticlehq/reticle
- Path
skills/verify-optimistic-update/SKILL.md- Versions recorded
- 7
- Latest version
- v3.9.0, committed Oct 29, 2026
- First version recorded
- Oct 2, 2026
- Size
- 5,231 bytes
- Repository stars
- 1,249
- License
- a license file GitHub does not identify
Prove a UI that updates before the server answers puts things back and says so when the request fails, and keeps the change when it succeeds. Use when a like, toggle, rename, reorder, delete or add-to-cart updates instantly, when an optimistic update was added or changed, or when a user reports a change that "saved" but was gone after a reload.
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
# An optimistic update is a promise the server can break
Updating the UI before the server answers makes an app feel fast. It also means the UI claims something the server has not agreed to yet. The failure path, where the request fails and the UI has to take the claim back, is the one nobody clicks through, because on a working backend it never happens.
**Reticle** can make it happen in the running app. Not set up? Follow the [`reticle`](https://github.com/reticlehq/reticle/blob/main/skills/reticle/SKILL.md) skill: it installs Reticle, asks the user before `init` changes the app's files, and proves one flow.
## Read this before you start: failing a request needs a browser Reticle owns
`reticle_network_mock` works in a leased tab (`reticle_run({ tool: "reticle_lease", args: { action: "acquire", url } })`) or a driven one, and not through the always-on SDK, which answers `{ ok: false, reason: "no-cdp-provider" }`. Without one, do step 4 (the success path) and report the rollback as **unknown**. Driving the happy path and reporting that rollback works is the one thing you may not do.
…Read the whole file at its exact version.
How to install
mdr add reticlehq/reticle/verify-optimistic-update@sha256:6ed8bbf3d919bebdThe line at the top of this page pins the label v3.9.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_xfov3zgf6fn57w2q)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Oct 2, 2026 and Oct 29, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.9.0 latest | 2026-10-29 | f2e07e0 | 5,231 B | A | view · diff |
| v3.8.2 | 2026-10-26 | f8a40d5 | 5,231 B | A | view · diff |
| v3.8.1 | 2026-10-26 | a6b11ca | 5,231 B | A | view · diff |
| v3.8.0 | 2026-10-25 | 68dd8a1 | 5,231 B | A | view · diff |
| v3.7.0 | 2026-10-09 | 4019204 | 5,229 B | A | view · diff |
| v3.6.0 | 2026-10-07 | c08be48 | 5,229 B | A | view · diff |
| v3.5.0 | 2026-10-02 | 774ab46 | 5,229 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 (5231 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
reticlehq/reticle · 1,249 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xfov3zgf6fn57w2q GET https://markdownregistry.com/api/v1/resolve?ref=reticlehq/reticle/verify-optimistic-update GET https://markdownregistry.com/api/v1/blob/6ed8bbf3d919bebdf85915506540fe585e559d7da3ee28de48f4121206ac05bd
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.