Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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.
Load plan, review critically, execute tasks in batches, report for review between batches. Core principle: Batch execution with checkpoints for architect review. Announce at start: "I'm using the executing-plans skill to implement this plan."
Read plan file Review critically - identify any questions or concerns about the plan If concerns: Raise them with your human partner before starting If no concerns: Create TodoWrite and proceed
Default: First 3 tasks For each task: Mark as in_progress Follow each step exactly (plan has bite-sized steps) Run verifications as specified Mark as completed
When batch complete: Show what was implemented Show verification output Say: "Ready for feedback."
Based on feedback: Apply changes if needed Execute next batch Repeat until complete
After all tasks complete and verified: Announce: "I'm using the finishing-a-development-branch skill to complete this work." REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch Follow that skill to verify tests, present options, execute choice
STOP executing immediately when: Hit a blocker mid-batch (missing dependency, test fails, instruction unclear) Plan has critical gaps preventing starting You don't understand an instruction Verification fails repeatedly Ask for clarification rather than guessing.
Return to Review (Step 1) when: Partner updates the plan based on your feedback Fundamental approach needs rethinking Don't force through blockers - stop and ask.
Review plan critically first Follow plan steps exactly Don't skip verifications Reference skills when plan says to Between batches: just report and wait Stop when blocked, don't guess
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.