vault-upgrade SKILL.md skillA

vault-upgrade from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add atman-33/workhub/vault-upgrade@git:20260918.40fa85c

Pins git:20260918.40fa85c in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
atman-33/workhub
Path
plugins/workhub/skills/vault-upgrade/SKILL.md
Versions recorded
2
Latest version
git:20260918.40fa85c, committed Sep 18, 2026
First version recorded
Sep 17, 2026
Size
5,327 bytes
Repository stars
3
License
MIT

Bring a workhub vault's layout up to what the current app and plugins expect, after a structural change. Use when hooks stop injecting owner context, when the app reports a breaking change, or when a vault has not been opened in a long time.

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

# Vault Upgrade — carry a vault forward through a structural change

When the vault's shape changes — a folder moves, a note splits — existing
vaults do not move with it. They break **silently**: a hook gates on a path
that no longer exists, exits 0, and nothing tells anyone. The symptom is an
agent that asks things it should already know, which looks like the model
having a bad day rather than a layout problem.

This skill is the one place those changes are carried forward.

It is **not** the same as `vault-migrate`, which copies a *different* Obsidian
vault into this one. This one restructures the vault you are already in.

## Steps

### 1. See what applies

```bash
node "${CLAUDE_PLUGIN_ROOT}/skills/vault-upgrade/scripts/vault-upgrade.mjs" status
```

Each migration reports `NEEDED` or `done`, with the reason. Nothing needed
means the vault is current — say so and stop; do not go looking for work.

### 2. Show the owner exactly what would move

```bash
node "${CLAUDE_PLUGIN_ROOT}/skills/vault-upgrade/scripts/vault-upgrade.mjs" plan <id>
```

This is a dry run and touches nothing. Put its output in front of the owner
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add atman-33/workhub/vault-upgrade@sha256:09f8725711a51d88

The line at the top of this page pins the label git:20260918.40fa85c, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_3jgq45rmai4myuci.svg)](https://markdownregistry.com/a/art_3jgq45rmai4myuci)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Sep 17, 2026 and Sep 18, 2026, more than one a day.

versioncommittedcommitsizeaudit
git:20260918.40fa85c latest2026-09-18 40fa85c 5,327 BA view · diff
git:20260917.68a90292026-09-17 68a9029 4,798 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (5327 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

GitHub

atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_3jgq45rmai4myuci
GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/vault-upgrade
GET https://markdownregistry.com/api/v1/blob/09f8725711a51d88d81ef2f347cc191265cfd500c204f2769b7834c06bdf057c

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 atman-33/workhub

CLAUDE.md CLAUDE.md file
atman-33/workhub · CLAUDE.md
git:20260929.5a11e52 · audit A · 3 stars
AGENTS.md@demo-vault AGENTS.md file
atman-33/workhub · demo-vault/AGENTS.md
git:20260830.27fbb5d · audit A · 3 stars
CLAUDE.md@demo-vault CLAUDE.md file
atman-33/workhub · demo-vault/CLAUDE.md
git:20260930.4c9347d · audit A · 3 stars
handoff-go SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/handoff-go/SKILL.md · Write a handoff document and launch the next agent in a split multiplexer pane (herdr or zellij), with new-window and…
git:20260901.114c610 · audit A · 3 stars
handoff SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/handoff/SKILL.md · Compact the current conversation into a handoff document for another agent to pick up.
git:20260901.114c610 · audit A · 3 stars
herdr SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/herdr/SKILL.md · Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state…
git:20260901.114c610 · audit A · 3 stars
launch-team SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/launch-team/SKILL.md · Launch a role-based team of Claude Code agents in separate multiplexer panes that coordinate on one task by messaging…
git:20260901.114c610 · audit A · 3 stars
setup-herdr SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/setup-herdr/SKILL.md · Install herdr (terminal-native agent multiplexer), set up its Claude Code and OpenCode integrations, and configure…
git:20260901.114c610 · audit B · 3 stars
setup-zellij SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/setup-zellij/SKILL.md · Install Zellij and configure shell profiles to auto-launch Zellij on startup (replacing any existing herdr autostart…
git:20260901.114c610 · audit A · 3 stars
sidekick-go SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/sidekick-go/SKILL.md · Use when the user explicitly asks to delegate work to a persistent sidekick/helper agent in its own pane that you can…
git:20260901.114c610 · audit A · 3 stars
wsl-vscode-doctor SKILL.md skill
atman-33/workhub · plugins/agent-ops/skills/wsl-vscode-doctor/SKILL.md · Diagnose and fix `code .` failing to launch, or opening a disconnected Windows-side VS Code instead of a WSL-connected…
git:20260901.114c610 · audit A · 3 stars
create-claude-md SKILL.md skill
atman-33/workhub · plugins/authoring/skills/create-claude-md/SKILL.md · Generate or refine a concise, effective CLAUDE.md for the current project following official best-practice guidelines…
git:20260901.114c610 · audit A · 3 stars

Every file in atman-33/workhub

Browse by kind, by grade A, or by owner.