Executing Plans
v1.0.0Use when executing a written implementation plan in the current session with sequential task execution and review checkpoints - for when subagent-driven mode...
⭐ 0· 92·0 current·0 all-time
by@axelhu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the actual instructions: sequentially load/review/execute a plan and hand off to finishing/verification skills. It does not request unrelated credentials, binaries, or installs. Declaring dependent workflow skills (isolated workspace, verification, finishing-branch, etc.) is consistent with the stated goal.
Instruction Scope
The SKILL.md tells the agent to read a plan file, produce task lists, execute steps, run validations, and invoke other named skills. This is within scope, but the instructions are high-level and grant broad discretion (e.g., 'read plan file', '按指定运行验证', batch review cadence). That vagueness could let an agent access arbitrary session files or invoke other skills with different permissions — review how 'read plan file' is resolved and what the downstream skills do.
Install Mechanism
No install spec and no code files. Instruction-only skills carry minimal install risk because nothing is written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. It does require other workflow skills, which themselves may request credentials; those should be evaluated separately.
Persistence & Privilege
always is false and the skill does not request persistent presence or to alter other skills' configs. It does rely on autonomous invocation (platform default) but that is normal and not by itself concerning.
Assessment
This instruction-only skill appears coherent for executing written plans, but before installing you should: 1) confirm what 'read plan file' means in your environment (which files the agent may access); 2) review the referenced dependent skills (superpowers-isolated-workspace, verification, finishing-branch, etc.) to see what permissions or credentials they require; 3) avoid putting secrets or sensitive system paths into the plan content; and 4) test the skill in an isolated environment to observe what other skills it invokes and whether any unexpected file or network access occurs. If you need higher assurance, ask for the implementations or policies of the dependent skills before enabling this one.Like a lobster shell, security has layers — review code before you run it.
latestvk973q9zdc4jzjw6b0yp9z1ktt583m7p9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.