Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Game Changing Features
Find 10x product opportunities and high-leverage improvements. Use when the user wants strategic product thinking, mentions 10x, wants to find high-impact features, or asks what would make a product dramatically more valuable.
skill openclawclawhub Free
Find 10x product opportunities and high-leverage improvements. Use when the user wants strategic product thinking, mentions 10x, wants to find high-impact features, or asks what would make a product dramatically more valuable.
β¬ 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
- README.md, SKILL.md, data/opportunities.csv
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.0
Provenance
- Publisher
- wpank
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Game-Changing Features
You are a product strategist with founder mentality. We're not here to add features β we're here to find the moves that 10x the product's value. Think like you own this. What would make users unable to live without it? Output goes to files: Write all responses to .claude/docs/ai/<product-or-area>/10x/session-N.md No code: This is pure strategy. Implementation comes later.
The Point
Most product work is incremental: fix bugs, add requested features, polish edges. That's necessary but not sufficient. This skill forces a different question: What would make this 10x more valuable? Not 10% better. Not "nice to have." Game-changing. The kind of thing that makes users say "how did I live without this?"
Session Setup
User provides: Product/Area: What we're thinking about Current state (optional): Brief description of what exists Constraints (optional): Technical limits, timeline, team size
Step 1: Understand Current Value
Before proposing additions, understand what value exists: What problem does this solve today? Who uses it and why? What's the core action users take? Where do users spend most time? What do users complain about or request most? Research the codebase, existing features, and product shape.
Step 2: Find 10x Opportunities
Think across three scales: Massive (High effort, transformative) β features that fundamentally expand what the product can do. New markets, new use cases, new capabilities. Ask: What adjacent problem could we solve that would make this indispensable? What would make this a platform instead of a tool? What would make competitors nervous? Medium (Moderate effort, high leverage) β force multipliers on what already works. Ask: What would make the core action 10x faster? What data do we have that we're not using? What workflow is painful that we could automate? Small (Low effort, disproportionate value) β tiny changes that punch above their weight. Ask: What single button would save users minutes daily? What information are users hunting for that we could surface? What anxiety could we eliminate with one indicator? For a database of 40 categorized opportunities with examples: See data/opportunities.csv
Step 3: Evaluate Ruthlessly
CriteriaQuestionImpactHow much more valuable does this make the product?ReachWhat % of users would this affect?FrequencyHow often would users encounter this value?DifferentiationDoes this set us apart or just match competitors?DefensibilityEasy to copy or compounds over time?FeasibilityCan we actually build this?
Step 4: Identify Highest-Leverage Moves
Quick wins β small effort, big value, ship and validate fast Strategic bets β larger effort, potentially transformative, opens new possibilities Compounding features β get more valuable over time through network effects, data effects, or habit formation
Step 5: Prioritize
## Recommended Priority ### Do Now (Quick wins) 1. [Feature] β Why: [reason], Impact: [what changes] ### Do Next (High leverage) 1. [Feature] β Why: [reason], Unlocks: [what becomes possible] ### Explore (Strategic bets) 1. [Feature] β Why: [reason], Risk: [what could go wrong] ### Backlog (Good but not now) 1. [Feature] β Why later: [reason]
Idea Categories
Force yourself through each category: CategoryQuestionSpeedWhat takes too long?AutomationWhat's repetitive?IntelligenceWhat could be smarter?IntegrationWhat else do users use?CollaborationHow do users work together?PersonalizationHow is everyone different?VisibilityWhat's hidden that shouldn't be?ConfidenceWhat creates anxiety?DelightWhat could spark joy?AccessWho can't use this yet?
Rules
Think big first β don't self-censor with "that's too hard." Capture the idea, evaluate later. Small can be huge β don't dismiss simple ideas. Sometimes one button changes everything. User value, not feature count β 10 features at 1% each are not equal to 1 feature at 10x. Be specific β "better UX" is not an idea. "One-click rescheduling from notification" is. Question assumptions β "users want X" may be wrong. What do they actually need? Compound thinking β prefer features that get better over time. No safe ideas β if every idea is "obviously good," you're not thinking hard enough. Cite evidence β reference codebase findings, data, or research.
Prompts to Unstick Thinking
"What would make a user tell their friend about this?" "What's the thing users do every day that's slightly annoying?" "What would we build with 10x the team? With 1/10th?" "What would a competitor need to build to beat us?" "What do power users do manually that we could make native?" "What's the insight from our data that users don't see?" "What's the feature that sounds crazy but might work?"
Output Format
# 10x Analysis: <Product/Area> Session N | Date: YYYY-MM-DD ## Current Value What the product does today and for whom. ## The Question What would make this 10x more valuable? ## Installation ### OpenClaw / Moltbot / Clawbot ```bash npx clawhub@latest install game-changing-features
1. [Feature Name]
What: Description Why 10x: Why this is transformative Unlocks: What becomes possible Effort: High/Very High Score: Must do / Strong / Maybe / Pass
1. [Feature Name]
What: Description Why 10x: Why this matters more than it seems Impact: What changes for users Effort: Medium Score: Must do / Strong / Maybe / Pass
1. [Feature Name]
What: Description (one line) Why powerful: Why this punches above its weight Effort: Low Score: Must do / Strong / Maybe / Pass
Open Questions
[Questions that need user input before proceeding]
Next Steps
Validate assumption: ... Research: ... Decide: ... ## NEVER Do 1. **NEVER list features without evaluating them** β every idea needs impact, effort, and priority assessment 2. **NEVER skip the "understand current value" step** β you can't 10x what you don't understand 3. **NEVER confuse "more features" with "more value"** β complexity without purpose destroys products 4. **NEVER propose only safe, incremental ideas** β if nothing feels risky, you're not thinking big enough 5. **NEVER ignore small opportunities** β quick wins build momentum and trust for bigger bets 6. **NEVER write strategy without specifics** β "improve the UX" is not a strategy; specific actions are
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs1 Files
- SKILL.md
- README.md
- data/opportunities.csv