@blackbelt-technology/pi-dashboard-plugin-skill

Pi skill that scaffolds new dashboard plugins or augments existing pi-extension projects with dashboard plugin contributions

Package details

← Back
skill

Install @blackbelt-technology/pi-dashboard-plugin-skill from npm and Pi will load the resources declared by the package manifest.

npm repohome report
$ pi install npm:@blackbelt-technology/pi-dashboard-plugin-skill
Package
@blackbelt-technology/pi-dashboard-plugin-skill
Version
0.4.6
Published
May 4, 2026
Downloads
not available
Author
mbotond
License
MIT
Types
skill
Size
83.4 KB
Dependencies
1 dependency · 0 peers
Pi manifest JSON
{
  "skills": [
    ".pi/skills/dashboard-plugin-scaffold"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

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-skill

Per-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-scaffold

The skill begins with a single ask_user batch:

  • Mode: new (scaffold inside the dashboard monorepo) or augment (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