upgrade-zymtrace-backend SKILL.md skillA
upgrade-zymtrace-backend from zystem-io/zymtrace-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zystem-io/zymtrace-skills/upgrade-zymtrace-backend@git:20260715.fbd20f5Pins git:20260715.fbd20f5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zystem-io/zymtrace-skills
- Path
zymtrace/skills/upgrade-zymtrace-backend/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260715.fbd20f5, committed Jul 15, 2026
- First version recorded
- May 19, 2026
- Size
- 16,784 bytes
- Repository stars
- 6
- License
- Apache-2.0
Use when upgrading a zymtrace backend that's already deployed via Helm. Covers image-tag-only bumps, chart-version bumps, and combined upgrades. Handles the migration job, --reset-then-reuse-values requirement, rollback when --atomic fails, and post-upgrade verification. Trigger phrases: "upgrade zymtrace", "upgrade zymtrace backend", "bump zymtrace version", "update zymtrace to 26.5.0 / latest", "helm upgrade zymtrace", "upgrade the chart", "bump backend image tag…
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
# Upgrade zymtrace Backend
Helps the user upgrade an already-installed zymtrace backend. Three paths:
| Path | What changes | When to use |
|------|-------------|------------|
| **A. Image-only bump** | `services.common.imageTag` (and pulled image) | Apply a patch/hotfix on the same chart. Lowest risk. |
| **B. Chart version bump** | Helm chart version + templates + defaults | New chart features, schema additions, new config keys. |
| **C. Combined** | Chart + image together | The common case for moving between zymtrace minor/major releases. |
Deep details (backup, rollback, schema migrations, the `migrate` job) live in `${CLAUDE_PLUGIN_ROOT}/skills/upgrade-zymtrace-backend/reference.md`.
> Fresh install? Use the `install-zymtrace-backend` skill instead.
## Sources of truth
- Live `values.yaml`: <https://raw.githubusercontent.com/zystem-io/zymtrace-charts/main/charts/backend/values.yaml>
- Chart releases (versions & appVersions): `helm search repo zymtrace/backend --versions`
- Docs: <https://docs.zymtrace.com/install/backend/helm-docker>
…Read the whole file at its exact version.
How to install
mdr add zystem-io/zymtrace-skills/upgrade-zymtrace-backend@sha256:da9046596d6b68c3The line at the top of this page pins the label git:20260715.fbd20f5, 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_niarha7f7taf2225)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 19, 2026 and Jul 15, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260715.fbd20f5 latest | 2026-07-15 | fbd20f5 | 16,784 B | A | view · diff |
| git:20260605.f5be030 | 2026-06-05 | f5be030 | 15,830 B | A | view · diff |
| v26.5.0 | 2026-05-30 | d71575d | 16,024 B | A | view · diff |
| v26.5.0 | 2026-05-19 | 71c3238 | 15,841 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 (16784 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
zystem-io/zymtrace-skills · 6 stars · license Apache-2.0 · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_niarha7f7taf2225 GET https://markdownregistry.com/api/v1/resolve?ref=zystem-io/zymtrace-skills/upgrade-zymtrace-backend GET https://markdownregistry.com/api/v1/blob/da9046596d6b68c3fb5777d58aff7b68342b9b601f842aaa6167c41793c78f82
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.