Agent skill

Bpmn Package Explorer

by BlackBeltTechnology in BlackBeltTechnology/pi-agent-dashboard

Generate, validate and view BPMN 2.0 process packages from a prose description, and render existing .bpmn / .dmn files.

MITAuto-check passed

Install Bpmn Package Explorer

skills CLI
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill bpmn-package-explorer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install BlackBeltTechnology/pi-agent-dashboard bpmn-package-explorer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
bpmn-package-explorer
GitHub stars
315
Token cost
~1.7k tokens
SKILL.md length
715 words
Files
97 (incl. scripts, references, assets)
Skills in repo
70
Repo updated
First seen
Licence
MIT

At a glance

Generate, validate and view BPMN 2.0 process packages from a prose description, and render existing .bpmn / .dmn files.

  • Works in 5 steps: Author semantics — one or more… → Author artifacts — the .dmn decisions… → Write package.yaml — the bindings and… → …
  • The user wants to model a business process
  • SKILL.md covers When to use, The two guarantees, Generation workflow and Display / view workflow, plus 4 more sections
  • Runs JavaScript scripts from its folder; calls node and npm

What it does

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.

When your agent uses it

  • The user wants to model a business process
  • Make a BPMN diagram
  • Generate a process from this description
  • Draw the workflow

Example prompts

  • “model a business process”
  • “make a BPMN diagram”
  • “generate a process from this description”
  • “/bpmn-package-explorer”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Author semantics — one or more semantics-only .bpmn (no geometry),
  2. Author artifacts — the .dmn decisions and .form schemas.
  3. Write package.yaml — the bindings and roles.
  4. Validate the manifest — node scripts/generate-cli.mjs
  5. Serve + canvas — serve the printed render-root path with

What it can do on your machine

Read from SKILL.md and the folder at commit 7a2d171. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Ships 1 file in scripts/ (JavaScript, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    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.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~213
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.9k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from BlackBeltTechnology/pi-agent-dashboard at commit 7a2d171, republished under its MIT licence (© BlackBeltTechnology). 715 words, ~1,695 tokens.

Download SKILL.mdSave it as .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.
name
bpmn-package-explorer
description
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 diagram", "generate a process from this description", "draw the workflow", "view / open a .bpmn or .dmn file", "build a decision table", or asks in Hungarian to "csinálj egy folyamatábrát", "rajzold meg a folyamatot", "BPMN ábra", "folyamat modellezés", "döntési tábla", "nézd meg ezt a .bpmn fájlt", "folyamatcsomag".

BPMN Package Explorer

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.

When to use

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”.

The two guarantees

  • Never a corrupt diagram. A language model can author correct BPMN semantics but not a readable coordinate set. 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.
  • Vendor-neutral. The .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.

Generation workflow

The agent authors the artifacts (guided by the references); the pipeline runs the mechanical steps, each failing loudly:

  1. Author semantics — one or more semantics-only .bpmn (no geometry), applying the authoring envelope and identifier rules. Emit <bpmn:incoming>/<bpmn:outgoing> on every connected flow node.
  2. Author artifacts — the .dmn decisions and .form schemas.
  3. Write package.yaml — the bindings and roles.
  4. Validate the manifest — 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.
  5. Serve + canvas — serve the printed render-root path with 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).

Display / view workflow

  • Package: node scripts/generate-cli.mjs <packageDir> → node scripts/serve.mjs <renderRoot> → canvas.
  • Standalone file (no manifest): 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.
Show full SKILL.md (330 more words)Show less

Canvas / sandboxed-iframe rendering (if the viewer shows blank)

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:

  • Absolute asset paths. Anything the served page references with a leading-slash path (/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.
  • Missing CORS on the static server → “Failed to load package: Failed to fetch”. In the opaque-origin iframe every runtime request carries 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.
  • Self-verify by iframing your served render root with 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).

Rejected constructs → manifest substitutions

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.

Verify the toolchain

  • 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

  • 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

Files

SKILL.md and 96 other files (scripts, references, assets) in packages/pi-forms-bpmn/.pi/skills/bpmn-package-explorer of BlackBeltTechnology/pi-agent-dashboard.

  • SKILL.md
  • assets/LICENSE.bpmn-io.txt
  • assets/VENDORED.md
  • assets/bpmn-js/bpmn-font/css/bpmn-codes.css
  • assets/bpmn-js/bpmn-font/css/bpmn-embedded.css
  • assets/bpmn-js/bpmn-font/css/bpmn.css
  • assets/bpmn-js/bpmn-font/font/bpmn.eot
  • assets/bpmn-js/bpmn-font/font/bpmn.svg
  • assets/bpmn-js/bpmn-font/font/bpmn.ttf
  • assets/bpmn-js/bpmn-font/font/bpmn.woff
  • assets/bpmn-js/bpmn-font/font/bpmn.woff2
  • assets/bpmn-js/bpmn-navigated-viewer.production.min.js
  • assets/bpmn-js/bpmn.css
  • assets/bpmn-js/diagram-js.css
  • assets/dmn-js/diagram-js.css
  • … and 82 more

Open the folder on GitHubat commit 7a2d171

Compare with similar skills

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.

Bpmn Package Explorer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bpmn Package Explorer this skillBlackBeltTechnology/pi-agent-dashboard315—~1.7kAutomated safety check: PassMIT
Explorersupabase/supabase111k—~845Automated safety check: PassApache-2.0
Add Packageremix-run/remix33k—~2kAutomated safety check: PassMIT
Agent Scout Explorerruvnet/ruflo74k2 repos~1.6kAutomated safety check: PassMIT
Caveman Repository ExplorerJuliusBrussee/caveman111k1 repos~492Automated safety check: PassApache-2.0
Add New Packageremotion-dev/remotion63k—~777Automated safety check: NotesCustom licence

Similar skills

  • Explorer

    supabase/supabase

    Official

    Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.

    111k GitHub stars~845 tokensUpdated today
    DatabasesAuto-check passed
  • Add Package

    remix-run/remix

    Create or align a package in the Remix monorepo to match existing package conventions.

    33k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Agent skill for scout-explorer - invoke with $agent-scout-explorer

    74k GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed
  • Caveman Repository 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.

    111k GitHub starsUsed in 1 repo~492 tokens
    Agent WorkflowsAuto-check passed
  • Add New Package

    remotion-dev/remotion

    Official

    Add a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, and release checklist updates.

    63k GitHub stars~777 tokensUpdated yesterday
    Media & CreativeAuto-check: notes
  • Explore

    parcadei/Continuous-Claude-v3

    Meta-skill for internal codebase exploration at varying depths (quick/deep/architecture)

    3.9k GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check: notes

More from BlackBeltTechnology/pi-agent-dashboard

All 70 skills in this repo
  • Browser

    BlackBeltTechnology/pi-agent-dashboard

    Browser automation via the agent-browser CLI. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    315 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • CI Troubleshoot

    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…

    315 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Debug Dashboard

    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.

    315 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Implement

    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.

    315 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Pi Dashboard

    BlackBeltTechnology/pi-agent-dashboard

    Monitor and control the pi-dashboard server. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    315 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Session To Guideline

    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…

    315 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

Questions about Bpmn Package Explorer

What does Bpmn Package Explorer do?

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.

When should I use Bpmn Package Explorer?

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.

How do I install Bpmn Package Explorer in Claude Code?

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.

How do I install Bpmn Package Explorer in Codex?

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.

Can I use Bpmn Package Explorer in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Bpmn Package Explorer need to run?

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.

Does Bpmn Package Explorer access the network?

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.

Is Bpmn Package Explorer safe to install?

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.

What licence does Bpmn Package Explorer use?

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.

How many tokens does Bpmn Package Explorer use?

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.

What are the alternatives to Bpmn Package Explorer?

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.

Who maintains Bpmn Package Explorer?

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.