Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Other
Product Manager
Build products users love with discovery, prioritization, roadmapping, and cross-functional leadership.
skill openclawclawhub Free
Build products users love with discovery, prioritization, roadmapping, and cross-functional leadership.
โฌ 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
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
Discovery
Talk to users weekly โ not just at project kickoff Watch behavior, don't just collect opinions โ users say one thing, do another Problem validation before solution validation โ are we solving the right thing? Jobs to be done: what's the user trying to accomplish? Competitors show what's possible, not what to copy
Prioritization
Impact vs effort is a starting point, not the answer Say no more than yes โ focus is a feature Urgent vs important: stakeholder pressure isn't priority Stack rank ruthlessly โ "everything is P1" means nothing is Revisit priorities when context changes โ quarterly at minimum
Roadmapping
Outcomes over outputs โ what will change, not what we'll build Time horizons: now (committed), next (planned), later (possible) Communicate uncertainty honestly โ roadmaps aren't promises Dependencies surfaced early โ blocked work wastes everyone's time Update when reality changes โ stale roadmaps destroy trust
Requirements
User stories: who, what, why โ not how Acceptance criteria define done โ ambiguity creates rework Edge cases addressed upfront โ not discovered in QA Scope creep is the enemy โ good enough now beats perfect later Technical constraints are real โ work with engineering, not around them
Working with Engineering
Context over directives โ explain why, not just what Tradeoffs are collaborative decisions Spec before sprint, not during โ no designing on the fly Protect focus time โ meetings kill flow Trust their estimates, push back on scope not time
Working with Design
Research together, don't hand off briefs Critique the work, not the designer Design reviews with users, not just stakeholders Mobile and edge cases early โ not afterthoughts Design system enables speed โ support it
Stakeholder Management
Regular updates prevent surprise requests Data calms opinion battles Explain trade-offs, don't just defend decisions Feedback channels prevent end-runs โ make input easy Executive sponsors for big initiatives
Metrics
One north star metric, 2-3 supporting Leading indicators for early signal โ don't wait for lagging Dashboards should prompt questions, not just display numbers Vanity metrics feel good, don't drive decisions A/B test when data beats intuition
Launch
Soft launch catches problems before scale Success criteria defined before launch โ not after Rollback plan before rollout Cross-functional checklist: docs, support, marketing Post-launch review: what worked, what didn't
Common Mistakes
Feature factory: shipping without learning Overspeccing: killing engineering autonomy Consensus seeking: decisions by committee Ignoring qualitative: data alone misses why Roadmap as backlog: detail everything, commit nothing
Category context
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md