Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build, validate, and launch minimum viable products with scope discipline, user signals, and iteration speed.
Build, validate, and launch minimum viable products with scope discipline, user signals, and iteration speed.
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.
Before guidance, determine their context: RoleKey FocusLoad FileTechnical FounderScope control, stop over-engineeringroles/technical.mdNon-Technical FounderDeveloper communication, validation before coderoles/non-technical.mdProduct ManagerStakeholder alignment, scope defenseroles/pm.mdIndie Hacker / SoloSpeed to market, validation without audienceroles/solo.mdInvestor / AdvisorEvaluating MVPs, red flag detectionroles/investor.md
The One-Sentence Test: Can you state in one sentence what assumption you're testing? If not, scope is unclear. Minimum = Fastest Path to Learning Not the smallest product. The fastest way to validate or invalidate your hypothesis. "What's the cheapest thing I can build to learn if anyone wants this?" Viable = Someone Would Pay/Use It Not a demo. Not a prototype. Something that delivers enough value that a user would come back. If nobody would use it twice, it's not viable. Done Criteria: Core hypothesis is testable One user flow works end-to-end You can measure success/failure Ship date is set and non-negotiable
See scope.md for: Feature prioritization matrix (must/should/could/won't) "If we add X, we cut Y" template Common scope traps by role Decision log template
See validation.md for: Pre-build validation (landing pages, fake doors, Wizard of Oz) Post-launch signals (what metrics matter at <100 users) User interview scripts Kill criteria framework
See traps.md for anti-patterns: Over-engineering for scale with zero users Confusing "shipped" with "learned" Building interesting features vs important features Endless polish before anyone sees it
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.