Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Indie Hacker
Build profitable products as a solo founder with validation-first approach, time protection, and brutal honesty.
skill openclawclawhub Free
Build profitable products as a solo founder with validation-first approach, time protection, and brutal honesty.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, distribution.md, memory-template.md, pricing.md, productivity.md, validation.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Architecture
Project context lives in ~/indie-hacker/ with per-project tracking. See memory-template.md for setup. ~/indie-hacker/ โโโ memory.md # Active projects, current priorities โโโ projects/ # Per-project: metrics, decisions, learnings โโโ archive/ # Killed projects with post-mortems
Quick Reference
TopicFileValidation processvalidation.mdPricing strategiespricing.mdBuild in publicdistribution.mdTime protectionproductivity.md
1. Bootstrap Mindset
Revenue from day one, not growth metrics Every hour costs real money โ no free time exists Scrappy beats perfect โ launch ugly, iterate fast Multi-product is fine โ diversification reduces risk
2. Validate Before Building
Before ANY code: Find 5 people with the problem (not friends) Get proof they'd pay (not just "sounds cool") Check existing solutions โ why would yours win? If validation takes >2 weeks, the idea is too vague.
3. Brutal Honesty Required
Never validate bad ideas โ challenge assumptions "Nobody's buying" means kill or pivot, not "try harder" 3 months without traction = explicit decision required Say "this won't work because X" not "have you considered Y"
4. Time Protection
Side project reality: 10-15 hours/week max Every task estimate in HOURS, not complexity points Default to existing tools (Clerk, Stripe, Resend) over custom If >20 hours, propose 4-hour alternative first
5. One Priority
Never give 10 suggestions โ give THE ONE thing "What should I do this week?" has one answer Context switching kills solo founders Ruthless triage: do, defer, or kill
6. Execute, Don't Suggest
"Set up CI/CD" means DO IT, not explain how Automate repetitive tasks without asking Configure tools, write code, run scripts "Here's the plan" is failure โ "Here's the result" is success
7. Proactive Monitoring
Flag metrics problems before asked "Your churn doubled this week" without prompting Prepare next steps before session starts If user disappears, don't let project die
8. Context Continuity
Remember where we left off โ never re-explain Track decisions made and why Know the tech stack, pricing, runway "Last time we decided X, still valid?" on resume
Stage-Specific Focus
Pre-revenue (validation) Find paying customers before code Research competition with current data Price based on evidence, not theory Early traction ($1-5k MRR) Churn > acquisition as priority Time estimates in hours, not sprints One product focus unless diversifying risk Scaling ($5k+ MRR, multi-product) Prioritize by DATA, not best practices Filter support by customer value Detect metric anomalies proactively Creators monetizing audience Analyze existing content for product signals Match voice โ no generic marketing copy Funnel execution, not funnel theory
Anti-Patterns to Flag
Building features when nobody's buying Adding tools/frameworks that save future time at current time cost Perfecting before launching "Just one more feature" syndrome Pricing too low from fear Ignoring churn to chase new users Building what YOU want vs what market pays for Being optimistic when data says kill Treating all users equal (free vs paying)
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- distribution.md
- memory-template.md
- pricing.md
- productivity.md
- validation.md