Planr Doctor
Diagnose OpenPlanr CLI, pipeline, runtime-adapter, installation, and lock health. Use when setup, discovery, versions, generated assets, or runtime behavior seems wrong.
Install
$ agentstack add skill-openplanr-openplanr-planr-doctor ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-openplanr-openplanr-planr-doctor) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Planr Doctor
Run planr doctor with the requested flags. Prefer --json for diagnosis. Preview every repair; package installation, version changes, provenance recovery, and deletion always require explicit confirmation.
Driving an upgrade
planr owns only half of an OpenPlanr upgrade — the npm CLI. The other half, the host plugins, cannot be installed by a CLI; it needs a tool with host shell access. That is this skill's job: drive the plugin half, then report what actually changed — never what was merely attempted.
- Decide. Run
planr upgrade status --jsonand readstatus. If it is
aligned or unknown, there is nothing to drive — report it and stop. Record the reported installed versions; that is the before state.
- Own half, prescribe half. If
statusisupgrade-availableor
incompatible, confirm with the user (this upgrades the npm CLI), then run planr upgrade apply --yes --json. The CLI performs the npm half itself and returns the plugin half as an ordered pluginHalfCommands array — the exact argv it would run, so the list can never drift from the engine. Take the commands from there; never write a plugin command of your own.
- Refresh first, then execute in order. Run every entry of
pluginHalfCommands verbatim, in the array's given order, with your shell. The first entry is a marketplace refresh and must run first: skip it and the installer reinstalls the cached, stale version while the user believes they upgraded. Do not reorder, drop, or substitute an entry.
- Verify and report the real diff. Re-run
planr upgrade status --jsonand
compare its installed versions against the before state. Report only what actually moved and to what. If a component did not move, say so — never claim "upgraded" for a version that did not change.
For the longer walkthrough, JSON output shape, and reporting format, read the [upgrade guide](references/upgrade.md).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: openplanr
- Source: openplanr/OpenPlanr
- License: MIT
- Homepage: https://openplanr.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.