Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Developer Tools
Upstream Recon
Investigate an open-source project before interacting with it — PRs, issues, or comments. Use BEFORE: filing an issue, submitting a PR, or commenting on an e...
skill openclawclawhub Free
Investigate an open-source project before interacting with it — PRs, issues, or comments. Use BEFORE: filing an issue, submitting a PR, or commenting on an e...
⬇ 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
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
- 1.0.0
Provenance
- Publisher
- SeMmyT
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Upstream Recon
Investigate a repo's culture and existing threads before interacting. Prevents duplicate issues, wasted PR effort, and uninformed comments. Arguments: <owner/repo> [topic-keyword]
Procedure
Use gh CLI throughout. Run independent queries in parallel. Repo metadata — stars, forks, license, last push date, archived status Top 10 contributors — commit counts. Is it one person with 90%+ commits? Existing issues search — search open AND closed issues for the topic keyword. Check for duplicates, prior art, and maintainer responses. Report what was found. Recent 30 PRs (all states) — get the lay of the land Merged PRs (last 20) — who merges them? How fast? What types get accepted? Closed-without-merge PRs (last 50, filter mergedAt == null) — deep-dive 2-3 notable rejections: read comments for maintainer reasoning Open PRs — how many sit with 0 reviews? For how long? Topic deep-dive (if keyword given) — read comments on 2-3 most relevant existing issues/PRs to understand maintainer sentiment and community workarounds
Analysis Dimensions
Governance: Solo maintainer / small team / community-driven External PR reception: Welcoming / selective (bugs yes, features no) / closed shop Issue responsiveness: How fast do maintainers respond to issues? Do they engage or auto-close? Merge velocity: Days from open to merge for external contributors Rejection patterns: Ghosted? "Building it myself"? "File issue first"? Bot auto-closed? Topic overlap: Has this been attempted or discussed before? Active workarounds?
Recommendation
End the report with one of: MERGE-LIKELY — project merges external feature PRs, no competing work, maintainer receptive MERGE-UNLIKELY — maintainer builds features themselves, similar PRs closed/ignored, feature contradicts direction FILE-ISSUE-FIRST — feature not yet discussed, maintainer is selective but responsive to issues, gauge interest before coding COMMENT-ON-EXISTING — existing issue/PR already covers this, add your workaround or +1 there instead DUPLICATE-EXISTS — exact issue already filed, do not create another Include concrete next steps (e.g., "comment on #13738 with your workaround", "start with a bug fix PR to build credibility", "file an issue referencing #189", "fork and maintain independently").
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
2 Docs
- SKILL.md
- README.md