Loading the registry…
Use this skill when a Camunda Platform 7 `.bpmn` must actually deploy and run on the engine — not just look right as a diagram. Covers the C7 engine, the CIB seven fork, and Spring Boot camunda-bpm starters. Reach for it to: assemble an executable process by wiring existing service tasks (Java delegates, external-task topics) from a catalog and stubbing steps that don't exist yet; make a plain diagram deployable; add or edit gateways, user tasks + forms, DMN, boundary/timer & escalation events, error handling, async, candidate groups, historyTimeToLive; or fix why a process won't deploy or misbehaves at runtime (historyTimeToLive cannot be null, a service task with no implementation, broken delegateExpression wiring, a gateway running everything twice after a merge). Signals: Camunda 7, camunda-bpm, CIB seven, camunda:*, JavaDelegate, external task, business rule task. Not for engine-agnostic diagrams (use bpmn) or Camunda 8 / Zeebe (zeebe:, FEEL).
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/architawr/claude-camunda-skill, 17 findings
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'architawr/claude-camunda-skill (camunda7)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'architawr/claude-camunda-skill (camunda7)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
14 findings · 11.4s
v0.3.74
1 finding · 2.7s
v0.1.0
0 findings · 5.9s
v0.1.0
0 findings · 5.9s
v0.1.0
0 findings · 9.6s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: complete | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 15 findings above stand exactly as their scanners reported them, at full severity.