Production Harness
v1.0.0Production-grade Agent Harness combining execution discipline (Superpower), knowledge compounding (CE), and product thinking (Gstack) into a single adaptive...
⭐ 0· 49·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description describe a multi-step engineering harness; the instructions only require typical engineering actions (spec, plan, build, test, checkpoint). There are no environment variables, binaries, or external services requested that would be inconsistent with that purpose.
Instruction Scope
SKILL.md directs the agent to read code, write checkpoints to files, run verifications (tests, ls, wc, grep examples), and follow acceptance criteria. Those actions are within scope for a development harness. The instructions do not direct the agent to read unrelated system configs, secrets, or to exfiltrate data externally.
Install Mechanism
No install spec or code files are included; this is instruction-only. That minimizes on-disk risk and matches the skill's stated nature.
Credentials
The skill declares no required env vars, credentials, or config paths. The runtime instructions reference only standard developer operations (files, tests) and do not request tokens or other secrets.
Persistence & Privilege
always is false and autonomous invocation is allowed (the platform default). The skill does advocate writing checkpoints to the filesystem and committing changes, which is expected for this harness and does not modify other skills or system-wide settings.
Assessment
This is a coherent, instruction-only engineering harness. Before installing: (1) understand that the harness expects the agent to read and write repository files and run tests — grant only the minimal filesystem/repo access needed (use a sandbox or a branch), (2) do not provide CI, cloud, or repo credentials to the agent unless you trust and audit its outputs, and (3) review the harness prompts and any automatic commit steps so changes are visible and reversible (use feature branches and a rollback plan). If you need the agent to operate on sensitive repos, require human confirmation for commits or restrict its write permissions.Like a lobster shell, security has layers — review code before you run it.
agentvk9785vqmm105p9radr0as74pth84evwmengineeringvk9785vqmm105p9radr0as74pth84evwmharnessvk9785vqmm105p9radr0as74pth84evwmlatestvk9785vqmm105p9radr0as74pth84evwmtddvk9785vqmm105p9radr0as74pth84evwmverificationvk9785vqmm105p9radr0as74pth84evwmworkflowvk9785vqmm105p9radr0as74pth84evwm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.