A persistent autonomous engineering harness runtime that transforms any repository into a self-improving software system. Use this skill whenever the user wa...
Security Analysis
high confidenceThis is an instruction-only harness runtime whose requested capabilities and safeguards align with its stated purpose — it requires the host platform to enforce the dangerous operations, and the skill itself contains many safeguards and human gates.
The skill is an instruction-only 'harness' for running multi-agent engineering cycles. It requests no binaries, env vars, or installs and all declared tool usage (read_file, write_file, git_*, web_search, test runners) matches the stated purpose of transforming repositories and orchestrating agents. The extensive protected-path and router requirements are appropriate for a harness.
SKILL.md and supporting docs instruct agents to read repo files, run tests, create branches/PRs, and spawn subagents. These are within the declared purpose, but they assume the platform enforces a central tool router, sandboxed test execution, scoped git credentials, and human approval gates. If the host platform does not implement those enforcement points, the instructions could enable risky autonomous behavior. The skill repeatedly warns to verify platform requirements before use.
Instruction-only; no install spec, no downloads, and no code execution packaged with the skill. This minimizes on-disk footprint and avoids installing arbitrary binaries.
The skill declares no required environment variables, no credentials, and no config paths. It explicitly instructs the platform to manage scheduler credentials and git tokens and forbids writing credentials to memory or logs. The requested environment access is proportionate to an orchestration/instruction-only skill.
always:false (not force-included). Model invocation/autonomous invocation is allowed (platform default). This is expected for an autonomous harness, but because the skill orchestrates actions that can modify a repo (commits/PRs, tests, staging docs) users must ensure platform-enforced human gates, tool-routing, and git scoping are present. The skill itself repeatedly mandates human approval gates and protected paths.
Guidance
This skill is a documentation-driven orchestration runtime (no code bundled) and is internally consistent with its purpose. It delegates all enforcement to the host platform — before enabling autonomous runs, verify the platform actually provides: (1) a tool router that blocks protected-path writes, redacts secrets, and logs BLOCKED_READ/BLOCKED_WRITE events; (2) sandboxed test execution with no access to host env vars or harness files; (3) fine‑grained git credentials scoped to the current repo and branch protections (no direct push to main); and (4) human approval gates for plan/PR/critical actions. If you cannot confirm those controls, run the skill only in single-pass/manual mode and do not enable continuous/autonomous operation. Because the skill can orchestrate commits, tests, and subagents, lack of platform enforcement increases the risk of unwanted changes or data exposure — ensure you test the harness in a safe repository first and confirm logs and redaction behavior before trusting it with production repos.
Latest Release
v5.3.0
- More extensive review scope - Detailed nested subtasks breakdown instructions - accept Obsidian-type LLM Wiki - Allow clean pass only for reviewers - Reinforced ITR loop - Updated the "10-MIN STUCK KILL" rule to require that a cron job is always set when a subagent is given a long-running command, to periodically check its progress.
Popular Skills
Published by @louis-szeto on ClawHub
