Explorer
supabase/supabase
Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.
Generate, validate and view BPMN 2.0 process packages from a prose description, and render existing .bpmn / .dmn files.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard bpmn-package-explorer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer .claude/skills/bpmn-package-explorer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bpmn-package-explorer" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer into .claude/skills/bpmn-package-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bpmn-package-explorer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard bpmn-package-explorer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer .agents/skills/bpmn-package-explorer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bpmn-package-explorer" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer into .agents/skills/bpmn-package-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bpmn-package-explorer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard bpmn-package-explorer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer .cursor/skills/bpmn-package-explorer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bpmn-package-explorer" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer into .cursor/skills/bpmn-package-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bpmn-package-explorer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BlackBeltTechnology/pi-agent-dashboard.git --path packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard bpmn-package-explorer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer .gemini/skills/bpmn-package-explorer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bpmn-package-explorer" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer into .gemini/skills/bpmn-package-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bpmn-package-explorer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard bpmn-package-explorerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer .github/skills/bpmn-package-explorer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bpmn-package-explorer" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer into .github/skills/bpmn-package-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bpmn-package-explorer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BlackBeltTechnology/pi-agent-dashboard bpmn-package-explorer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer .opencode/skills/bpmn-package-explorer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bpmn-package-explorer" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer into .opencode/skills/bpmn-package-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bpmn-package-explorer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
bpmn-package-explorerGenerate, validate and view BPMN 2.0 process packages from a prose description, and render existing .bpmn / .dmn files.
Bpmn Package Explorer is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Generate, validate and view BPMN 2.0 process packages from a prose description, and render existing .bpmn / .dmn files. Turns a described business process into plain vendor-neutral BPMN semantics, auto-lays it out with a verifying layout guard (never emits a corrupt diagram), wires decisions (.dmn), forms (.form) and sub-processes through a sidecar package.yaml manifest, and serves a buildless offline bpmn-js / dmn-js viewer on the canvas. Use when the user wants to "model a business process", "make a BPMN…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 102 other files, including scripts, reference files and assets (for example `assets/VENDORED.md` and `assets/bpmn-js/bpmn-navigated-viewer.production.min.js`).
The repository describes itself as: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote… The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 7a2d171. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (JavaScript, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
nodenpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Bpmn Package Explorer loads about 1.7k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 213 tokens; SKILL.md has 715 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from BlackBeltTechnology/pi-agent-dashboard at commit 7a2d171, republished under its MIT licence (© BlackBeltTechnology). 715 words, ~1,695 tokens.
.claude/skills/bpmn-package-explorer/SKILL.md (or your agent's skills folder). This skill also uses 96 other files; get the full folder from GitHub.Generate and view BPMN 2.0 process packages: a process plus the decisions its
rule tasks evaluate, the forms its user tasks present, and a manifest binding
them — kept as plain, vendor-neutral BPMN 2.0. Buildless and offline: it
vendors pre-built viewers and a self-contained Node layout bundle; generating or
rendering a package needs no npm install, no bundler and no network. Requires
Node ≥ 20.12 and a browser.
Model a business process from a prose description; make/view a BPMN diagram or a DMN decision table; build a cross-linked process package. Hungarian triggers: „csinálj egy folyamatábrát”, „rajzold meg a folyamatot”, „döntési tábla”, „nézd meg ezt a .bpmn fájlt”.
bpmn-auto-layout fills that
gap but fails silently on sub-processes, pools and lanes (all outputs stay
schema-valid). A layout guard verifies every laid-out diagram against its
own semantics and aborts on any corruption, in strict mode..bpmn/.dmn/.form files carry no engine
extension. A sidecar package.yaml holds the link graph (bindings, roles),
so a package opens in Camunda Modeler, Signavio or any conformant tool.The agent authors the artifacts (guided by the references); the pipeline runs the mechanical steps, each failing loudly:
.bpmn (no geometry),
applying the authoring envelope and identifier rules. Emit
<bpmn:incoming>/<bpmn:outgoing> on every connected flow node..dmn decisions and .form schemas.package.yaml — the bindings and roles.node scripts/generate-cli.mjs <packageDir>
runs the envelope check, manifest validation, layout + guard, and assembles a
render root; it stops before serving on any error.node scripts/serve.mjs <renderRoot> [port] (CORS-enabled) and open the
printed URL on the canvas (never file://). Do not use serve_mockup
for canvas display: it omits Access-Control-Allow-Origin, so the viewer's
fetch('package-data.json') fails in the opaque-origin sandbox (“Failed to
fetch” → blank diagram).node scripts/generate-cli.mjs <packageDir> → node scripts/serve.mjs <renderRoot> → canvas.node scripts/view-cli.mjs <file.bpmn|.dmn>.
A file with DI renders as authored; a semantics-only .bpmn is laid out into a
separate render artifact (the source is never overwritten). A DI-less file
containing a rejected construct is refused with that construct's diagnostic.The dashboard opens a loopback canvas(kind:"url") target inside a
sandbox="allow-scripts" iframe with no allow-same-origin (opaque origin),
proxied under /live/<id>/. The vendored bpmn-js / dmn-js viewers are buildless
and offline, so they usually render fine — but if the canvas comes up blank
or 404s, it is almost always one of these, not a viewer bug:
/vendor/..., /main.js) resolves to the dashboard root
under the /live/<id>/ prefix → 404. Keep every path in the render root
relative (./vendor/...). Serve the render root with serve_mockup (never
file://) and open the returned URL on the canvas.Origin: null: the viewer's fetch('package-data.json') (and any
<script type="module">) is rejected unless the server answers with
Access-Control-Allow-Origin: *. serve_mockup does NOT set it, so serve
canvas render roots with node scripts/serve.mjs <renderRoot> (this skill's
CORS server) rather than serve_mockup.sandbox="allow-scripts" and screenshotting before trusting the canvas — that
reproduces the exact dashboard sandbox.Full rationale, the CORS static-server pattern, and adjacent pitfalls (IPv6-only
dev binds → ECONNREFUSED, kill %1 not persisting across tool calls) are in
the canvas-webapp skill (bundled with the pi-dashboard extension).
Inline subProcess → callActivity + separate .bpmn + kind: process
(drill-down). Pools (collaboration) → one .bpmn per participant +
kind: participant (switcher). laneSet → manifest roles (markers + legend).
messageFlow → unrepresentable (rejected). ≥2 boundary events on one activity →
rejected. See references/authoring-envelope.md.
node scripts/fixtures.mjs — layout regression suite (catches upstream drift).node scripts/selftest.mjs — envelope / identifier / manifest / guard /
workflow unit tests.node scripts/vendor.mjs — verify vendored bundle hashes
(--rebuild re-vendors from pinned inputs).references/authoring-envelope.md — generation contract + rejected constructs.references/identifiers.md — deterministic ids, Hungarian deburring,
uniqueness errors, authoring-vs-ingestion.references/package-manifest.md — the package.yaml contract, reconciliation.references/layout-envelope.md — the measured fixtures and outcomes.references/licensing.md — the bpmn.io watermark obligation and Apache 2.0.assets/VENDORED.md — pinned versions, hashes, the Node floor (20.12).© BlackBeltTechnology, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 96 other files (scripts, references, assets) in packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer of BlackBeltTechnology/pi-agent-dashboard.
Open the folder on GitHubat commit 7a2d171
Bpmn Package Explorer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bpmn Package Explorer this skillBlackBeltTechnology/pi-agent-dashboard | 315 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Explorersupabase/supabase | 111k | — | ~845 | Automated safety check: Pass | Apache-2.0 | |
| Add Packageremix-run/remix | 33k | — | ~2k | Automated safety check: Pass | MIT | |
| Agent Scout Explorerruvnet/ruflo | 74k | 2 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Caveman Repository ExplorerJuliusBrussee/caveman | 111k | 1 repos | ~492 | Automated safety check: Pass | Apache-2.0 | |
| Add New Packageremotion-dev/remotion | 63k | — | ~777 | Automated safety check: Notes | Custom licence |
supabase/supabase
Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.
remix-run/remix
Create or align a package in the Remix monorepo to match existing package conventions.
ruvnet/ruflo
Agent skill for scout-explorer - invoke with $agent-scout-explorer
JuliusBrussee/caveman
A read-only explorer for cold-start orientation or failed searches that replies with nothing but file path and line range citations, keeping its reads out of main context.
remotion-dev/remotion
Add a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, and release checklist updates.
parcadei/Continuous-Claude-v3
Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)
BlackBeltTechnology/pi-agent-dashboard
Browser automation via the agent-browser CLI. An agent skill from BlackBeltTechnology/pi-agent-dashboard.
BlackBeltTechnology/pi-agent-dashboard
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and…
BlackBeltTechnology/pi-agent-dashboard
Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.
BlackBeltTechnology/pi-agent-dashboard
Disciplined implementation in pi-agent-dashboard: the rebuild matrix (extension→reload, server→restart, client→build+restart, openspec-apply→full rebuild) plus the project's code discipline rules.
BlackBeltTechnology/pi-agent-dashboard
Monitor and control the pi-dashboard server. An agent skill from BlackBeltTechnology/pi-agent-dashboard.
BlackBeltTechnology/pi-agent-dashboard
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered…
Generate, validate and view BPMN 2.0 process packages from a prose description, and render existing .bpmn / .dmn files. Bpmn Package Explorer is an agent skill from BlackBeltTechnology/pi-agent-dashboard.dmn files.
Bpmn Package Explorer fits situations like: the user wants to model a business process; make a BPMN diagram; generate a process from this description; draw the workflow.
Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a claude-code`. Or copy the skill folder (packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer in BlackBeltTechnology/pi-agent-dashboard) into .claude/skills/bpmn-package-explorer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a codex`. Or copy the skill folder (packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer in BlackBeltTechnology/pi-agent-dashboard) into .agents/skills/bpmn-package-explorer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bpmn-package-explorer, .gemini/skills/bpmn-package-explorer, .github/skills/bpmn-package-explorer and .opencode/skills/bpmn-package-explorer in your project.
Going by SKILL.md and its folder, Bpmn Package Explorer needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and npm). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Bpmn Package Explorer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Bpmn Package Explorer: Explorer (supabase/supabase, 111k stars), Add Package (remix-run/remix, 33k stars), Agent Scout Explorer (ruvnet/ruflo, 74k stars) and Caveman Repository Explorer (JuliusBrussee/caveman, 111k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
BlackBeltTechnology (a GitHub organization) maintains it in BlackBeltTechnology/pi-agent-dashboard, which has 315 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 10, 2026.
Source: BlackBeltTechnology/pi-agent-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.