instant-execution-discipline
ReviewAudited by ClawScan on May 10, 2026.
Overview
This instruction-only skill is transparent about wanting faster execution, but it pushes agents to launch tools/subagents/cron immediately and to make permanent rule changes, so it should be reviewed before use.
Install this only if you want the agent to move quickly after explicit execution requests. Before using it for publishing, releases, finance, public posting, or other high-impact work, add confirmation gates and disable or constrain the permanent rule-update and persistent logging behavior unless you explicitly want those records and behavior changes.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent may begin actions such as publishing, releasing, or running delegated/background work before the user has a chance to review the exact plan.
The skill directs immediate invocation of tools, subagents, or cron before explanation, without defining scope limits or confirmation requirements for high-impact execution tasks.
Start execution first. - Trigger tools/subagent/cron immediately before long explanations.
Use only for clearly approved tasks, and add explicit confirmation requirements for public, destructive, financial, account-changing, or long-running actions.
A one-time delay could cause lasting changes to how the agent behaves in later sessions or tasks.
The skill instructs the agent to make persistent changes to controlling instructions, including MISSION or the skill itself, after a delay; this is broader than completing the user's immediate task.
If a delay occurs, immediately: ... apply a permanent rule update (MISSION or this skill), ... log the change in `memory/YYYY-MM-DD.md`.
Require explicit user approval before changing MISSION, skill files, or other persistent agent rules; prefer a temporary postmortem note unless the user approves a permanent policy change.
Operational or business details may be stored and reused later by the agent or appear in the user's Obsidian notes.
The skill creates persistent memory and note entries containing shipped work, measurable results, next actions, and evidence pointers.
Record KPI in `memory/YYYY-MM-DD.md` ... Mirror the same KPI block to Obsidian daily note.
Confirm that persistent KPI logging is desired, avoid including secrets or sensitive business data, and define where Obsidian notes and memory files are written.