@blackbelt-technology/pi-dashboard-plugin-skill
v0.5.3
Published
Pi skill that scaffolds new dashboard plugins or augments existing pi-extension projects with dashboard plugin contributions
Readme
@blackbelt-technology/pi-dashboard-plugin-skill
Pi skill that scaffolds dashboard plugins — either by creating a new plugin package inside the dashboard monorepo, or by retrofitting an existing pi-extension project on disk with dashboard plugin contributions.
Install
Globally:
npm i -g @blackbelt-technology/pi-dashboard-plugin-skillPer-workspace (preferred for projects you regularly augment):
// ~/.pi/agent/settings.json
{
"packages": [
"@blackbelt-technology/pi-dashboard-plugin-skill"
]
}Invoke
In any pi session:
/skill dashboard-plugin-scaffoldThe skill begins with a single ask_user batch:
- Mode:
new(scaffold inside the dashboard monorepo) oraugment(retrofit the pi-extension at the current working directory) - For
new: id, displayName, priority, slot multiselect (10 React slots), server entry?, bridge entry? (default off), config schema? - For
augment: no extra questions up front — the skill runs a grep prelude, drives the agent through the canonical TUI → dashboard mapping table, and asks per-callsite confirmation before injecting anything.
After the batch, the skill is fully prescriptive: render templates, write files, register the workspace (mode new) or inject the manifest field (mode augment), print next-steps. The skill never auto-runs builds, restarts, or publishes.
Why this exists
packages/dashboard-plugin-runtime/ ships the loader, slot registry, and React context. packages/demo-plugin/ is the canonical fixture. What was missing is the human-and-agent on-ramp from "I have an idea for a plugin" to "I have a manifest, a client.tsx, and a working dev loop." This skill is that on-ramp.
See also
- Architecture: dashboard-plugin-architecture
- Reference fixture:
packages/demo-plugin/ - Runtime:
@blackbelt-technology/dashboard-plugin-runtime
