ACPX Supervised Execution
v0.1.0Use when a coding, debugging, or research task should run inside one long-lived ACPX session while a separate supervisor keeps checking real engineering prog...
⭐ 1· 98·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the SKILL.md: the document defines a single long-lived ACPX execution session and a separate supervisor that checks concrete engineering artefacts. There are no unexpected binaries, env vars, or external integrations demanded that would be inconsistent with this coordination purpose.
Instruction Scope
All runtime instructions are focused on reading/writing project-local evidence files (reports/<slug>/*), evaluating diffs/tests/logs, and sending correction prompts back to the same session. The instructions do not ask the agent to read unrelated system files, external secrets, or to exfiltrate data to third-party endpoints.
Install Mechanism
No install spec and no code files — this is instruction-only, so nothing is written to disk or pulled from external URLs during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. The only implicit resource access is project-local report files (reports/<slug>/...), which aligns with the stated artifact-based supervision model.
Persistence & Privilege
The skill instructs using long-lived ACPX sessions and automated supervisor loops (default 5-minute cadence) and requires the supervisor and executor to close/ self-delete at terminal state. While this is coherent for the described workflow, long-lived sessions increase operational blast radius compared with short lived ones — recommend verifying session lifecycle controls and auditability in your environment.
Assessment
This skill is internally consistent and doesn’t ask for extra credentials or installs. Before using it: (1) confirm where reports/<slug> is stored and who/what can read those files (least privilege for evidence files); (2) ensure your ACPX session lifecycle, termination, and audit/logging behave as expected so long‑lived sessions can't be abused; (3) test the monitor→executor messaging in a sandbox to verify prompts/corrections are scoped and cannot cause undesired side effects; (4) keep the supervisor cadence and evidence paths explicit in the task brief; and (5) avoid granting the sessions broader filesystem or network access than necessary. If you want a lower-risk setup, prefer shorter sessions or manual supervision rather than automated long-lived loops.Like a lobster shell, security has layers — review code before you run it.
latestvk9708r1bshe1e30tmka8mvxx2h83na54
License
MIT-0
Free to use, modify, and redistribute. No attribution required.