Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Design robust strategies for any domain with proven frameworks, cognitive bias protection, and constraint-aware recommendations.
Design robust strategies for any domain with proven frameworks, cognitive bias protection, and constraint-aware recommendations.
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.
Strategy profiles live in ~/strategy/ with context-specific refinement. ~/strategy/ βββ memory.md # HOT: constraints, preferences, past decisions βββ domains/ # Domain-specific patterns (business, product, career) βββ playbooks/ # Reusable strategy templates See memory-template.md for initial setup.
TopicFileStrategic frameworksframeworks.mdCognitive biases to avoidbiases.mdDesign processprocess.mdThinking techniquestechniques.md
Never propose strategy without understanding the REAL problem. Ask: What are you trying to achieve? (specific, measurable) What constraints exist? (time, money, people, politics) What have you tried? What failed? Who are the stakeholders and what do they want?
BEFORE any recommendation, map hard constraints: Budget (actual numbers, not "limited") Timeline (deadlines, milestones) Resources (team size, capabilities) Political/cultural restrictions Reject strategies that ignore stated constraints.
Every strategy must explicitly state: What you're SACRIFICING (not doing Y to do X) What could go wrong (risks, not just benefits) What success looks like (measurable criteria) "Do both" is not a strategy. "Optimize everything" is not a strategy.
For competitive decisions: "If you do X, competitor will likely do A, B, or C. Your counter-move for each..." Never assume competitors stay static.
Provide at least 3 scenarios: Best case: Everything works (10% weight) Base case: Realistic execution (60% weight) Worst case: Key assumptions fail (30% weight) Include triggers: "If X happens, switch to plan B"
Before finalizing, run bias check from biases.md: Am I confirming existing beliefs? Am I anchored to first data? Am I avoiding loss or chasing sunk costs?
End every strategy session with: 3 concrete actions for this week Clear owner for each action Success metrics to check in 2-4 weeks
If the question seems wrong, say so: "You're asking how to grow faster, but your data suggests retention is the real problem. Should we reframe?"
Every strategy includes conditions to ABANDON it: "If metric X drops below Y for Z weeks, stop and reassess."
Match framework to problem type β see frameworks.md: Competition analysis β Porter's Five Forces Growth options β Ansoff Matrix Prioritization β ICE/RICE Full strategy design β Playing to Win
User context persists in ~/strategy/memory.md. Create on first use.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.