Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Enforce immediate execution behavior when the user asks to implement/run/do something now. Use this skill to prevent delay between commitment and action, and...
Enforce immediate execution behavior when the user asks to implement/run/do something now. Use this skill to prevent delay between commitment and action, and...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
When the user requests execution, run this protocol.
Start execution first. Trigger tools/subagent/cron immediately before long explanations. Send start signal within 90 seconds. Format: ๐ ๅฎ่ก้ๅง: <task> Keep visibility during long work. Send progress every 2โ5 minutes. Format: ๐ก ้ฒ่กไธญ: <done>/<total> | blocker(if any) Send completion within 60 seconds of finish signal. Format: โ ๅฎไบ / โ ๏ธ้จๅๆๅ / โๅคฑๆ Include: what changed, evidence, remaining items, next action.
Do not say "I will do it" without actually launching execution. Do not delay execution for planning text unless safety-critical. Do not ask user to run commands unless blocked by unavoidable identity/auth constraints. If blocked, report exact blocking layer and propose only design/permission change. Do not treat a kickoff/progress message as completion. For subagent runs, verify final outcome (published count / URLs / blockers) before reporting done. If a run ends with kickoff-only output, immediately relaunch with explicit "finish-required" constraints.
Start: ๐ ๅฎ่ก้ๅง: <task>. ๆๅฐๅคๆดใง้ฉ็จใใใ Progress: ๐ก ้ฒ่กไธญ: <current step>. ๅ้ก: <none|brief>. Complete: โ ๅฎไบ: <result>. ๅคๆด: <files/config/jobs>. ๆฌก: <next>.
When the task is execution-heavy (publish/release/distribution): Record KPI in memory/YYYY-MM-DD.md executed: what shipped result: measurable outcome (URL/count/status) next: one concrete optimization Mirror the same KPI block to Obsidian daily note. Include KPI in the completion message.
Use this skill when your agent has a conversion-sensitive workflow: paid content publishing product/skill release windows campaign distribution and post-release checks Primary outcomes this skill should improve: faster time-to-first-action (TTFA) fewer "started but not finished" runs faster user-visible completion reporting
Track these after each release: SLA start rate: % runs with start signal <=90s Finish integrity: % runs with evidence URLs/paths attached Kickoff-only failure rate: runs ended without final outputs Revenue-proxy conversion: CTA links added / clicked / downstream paid actions
Before each publish, ensure listing copy includes: Immediate business outcome (faster shipping / fewer dropped tasks) Clear operator steps (start/progress/finish format) KPI proof points to measure value in 24h Best-fit use cases (paid content, release windows, conversion funnels)
If a cron task explicitly requires Discord reporting: include executed/result/next KPI in one compact completion block, attach evidence pointers (URL/path/command output), if direct sending is delegated by runtime, clearly note destination channel and message body draft.
If a delay occurs, immediately: acknowledge miss, apply a permanent rule update (MISSION or this skill), log the change in memory/YYYY-MM-DD.md.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.