Loading the registry…
Picks up a generated Buildr workspace and executes it — wave by wave — to completion. The Executor is the runtime counterpart to the Operator: where the Operator creates the workspace, the Executor runs it. USE THIS SKILL when: you open a project directory with a WORKSPACE.md, RUN.md, and state/orchestration.yaml, and your job is to build the project to completion. This skill governs the entire execution lifecycle: context loading, wave selection, task execution, state management, contract verification, failure recovery, and handoff. Triggers on: "bygg projektet", "kör workspace", "fortsätt projektet", "execute the project", "run the workspace", "continue building", "next wave", "start execution", or any instruction to build a Buildr project from an existing workspace. The Operator builds the runway. The Executor flies the plane.
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.
189 critical findings reported by cisco-skill-scanner, agent-audit-kit, 149 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- buildr-executor
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- buildr-executor ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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
144 findings · 29.0s
v0.3.26
200 findings · 6.1s
v0.1.0
0 findings · 7.0s
v0.1.0
9 findings · 7.0s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 15, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | 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 353 findings above stand exactly as their scanners reported them, at full severity.