deepworkplan-upgrade SKILL.md skillA
deepworkplan-upgrade from dailybothq/deepworkplan-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dailybothq/deepworkplan-skill/deepworkplan-upgrade@v7.8.1Pins v7.8.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dailybothq/deepworkplan-skill
- Path
skills/deepworkplan/upgrade/SKILL.md- Versions recorded
- 10
- Latest version
- v7.8.1, committed Oct 14, 2026
- First version recorded
- Oct 10, 2026
- Size
- 11,525 bytes
- Repository stars
- 23
- License
- MIT
Check whether a newer DeepWorkPlan skill and DWP standard exists and — only after the developer explicitly accepts — install the latest published tag through the documented channel and re-run onboarding exactly as if https://deepworkplan.com/init.md were executed fresh, preserving every plan under .dwp/ and surfacing local adaptations instead of silently overwriting them. Use when the developer asks to upgrade, update, or refresh DWP in a repository that already has it installed. Do not use it…
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
# DeepWorkPlan — Upgrade (Sub-Skill) Keep a repository's installed DeepWorkPlan skill and its declared DWP standard current. Three phases, strictly ordered: **check** (read-only, safe to run anytime), **consent** (nothing downloads without an explicit yes), **upgrade** (same install command a fresh consumer runs, then onboarding re-executed as if https://deepworkplan.com/init.md were executed fresh). An upgrade never touches `.dwp/` plans — plans and their recorded evidence are history, not state to migrate (`../spec/DWP_SPECIFICATION.md` §6.5); its one `.dwp/` write is the addon registry back-fill (Phase 3 step 4). --- ## Trust boundary (write scope) `allowed-tools` includes write-capable `Edit`, `Write` and `Bash`. Phase 1 (check) and Phase 2 (consent) are **read-only**. Only after the developer's explicit acceptance does Phase 3 write: the vendored skill tree at the exact accepted **stable** tag (pre-release tags only on an explicit request for that channel), through the documented installer, then the onboarding reconciliation. It **MUST NOT** download anything before acceptance, install a moving ref (`@main`, `@latest`) or an unpinned source, overwrite local …
Read the whole file at its exact version.
How to install
mdr add dailybothq/deepworkplan-skill/deepworkplan-upgrade@sha256:3bc94d74f87601cfThe line at the top of this page pins the label v7.8.1, 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_twa4uyon5t2e3zdx)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Oct 10, 2026 and Oct 14, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v7.8.1 latest | 2026-10-14 | 1974640 | 11,525 B | A | view · diff |
| v7.8.0 | 2026-10-13 | 17d71ec | 11,525 B | A | view · diff |
| v7.7.1 | 2026-10-13 | 8fdf831 | 11,525 B | A | view · diff |
| v7.7.0 | 2026-10-12 | 61de123 | 11,525 B | A | view · diff |
| v7.6.3 | 2026-10-12 | 782e1e7 | 11,525 B | A | view · diff |
| v7.3.2 | 2026-10-11 | cbd8707 | 11,525 B | A | view · diff |
| v7.3.1 | 2026-10-11 | 0571af7 | 11,525 B | A | view · diff |
| v7.3.0 | 2026-10-11 | 390a7a9 | 11,525 B | A | view · diff |
| v7.2.0 | 2026-10-11 | f4c49bf | 11,525 B | A | view · diff |
| v7.1.4 | 2026-10-10 | 71b0379 | 11,525 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 (11525 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
dailybothq/deepworkplan-skill · 23 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_twa4uyon5t2e3zdx GET https://markdownregistry.com/api/v1/resolve?ref=dailybothq/deepworkplan-skill/deepworkplan-upgrade GET https://markdownregistry.com/api/v1/blob/3bc94d74f87601cf8d4542f3007abfa42a655948c1191a959368d970fa804798
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 dailybothq/deepworkplan-skill
Every file in dailybothq/deepworkplan-skill