update SKILL.md skillB
update from jebel-quant/rhiza-claude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jebel-quant/rhiza-claude/update@git:20261009.391e44aPins git:20261009.391e44a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jebel-quant/rhiza-claude
- Path
plugin/skills/update/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261009.391e44a, committed Oct 9, 2026
- First version recorded
- Aug 5, 2026
- Size
- 11,069 bytes
- Repository stars
- 6
- License
- a license file GitHub does not identify
Sync this rhiza-managed repo to the latest (or a given) template release and open a PR containing only template-owned files. Runs no gates and files no issues — use /rhiza:quality for a score.
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
You are running `/update` in the **current working directory's repo**. Goal: bump the template `ref`, apply the sync, and open a PR with **nothing but template-owned files** in it. **Only files that come from the template repository may be touched.** The sync records exactly which paths it materialized in `.rhiza/template.lock`'s `files` list, and `plugin/scripts/stage_synced.py` (step 7) stages precisely that set — so the guarantee is mechanical, not something this prose has to be trusted to honour. **Never `git add --all`** and never fold in unrelated edits: no reformatting of the repo's own source, no dependency changes, no test fixes. Anything outside the set stays in the working tree and gets reported. **No gates, no scorecard, no issues.** `/update` syncs; `/quality` scores. Don't run `make test`/`make lint`/`make fmt` here — `make fmt` in particular would rewrite the repo's own files and break the rule above. Point the user at `/rhiza:quality` in the report instead. Argument (optional): `$ARGUMENTS` — an explicit template version tag like `v1.2.0`. If empty, use the template's latest release. Work through these steps. Stop and report if a precondition fails. …
Read the whole file at its exact version.
How to install
mdr add jebel-quant/rhiza-claude/update@sha256:1ad693f22fb5e541The line at the top of this page pins the label git:20261009.391e44a, 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_xuywtspfhwqjxwgg)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 5, 2026 and Oct 9, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261009.391e44a latest | 2026-10-09 | 391e44a | 11,069 B | B | view · diff |
| git:20260822.f1c4320 | 2026-08-22 | f1c4320 | 10,706 B | B | view · diff |
| git:20260817.5f0100a | 2026-08-17 | 5f0100a | 10,073 B | B | view · diff |
| git:20260805.c378bcf | 2026-08-05 | c378bcf | 9,831 B | B | view · diff |
| git:20260805.bd32c9f | 2026-08-05 | bd32c9f | 9,809 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11069 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
jebel-quant/rhiza-claude · 6 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xuywtspfhwqjxwgg GET https://markdownregistry.com/api/v1/resolve?ref=jebel-quant/rhiza-claude/update GET https://markdownregistry.com/api/v1/blob/1ad693f22fb5e5411843e1390134b5443db5ce301d183423d0d07b0a61d68b52
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 jebel-quant/rhiza-claude
Every file in jebel-quant/rhiza-claude