Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Checker
QA and peer review agent. Reviews output from other agents before delivery. Use when: (1) content from Scribe needs review before posting, (2) research from...
skill openclawclawhub Free
QA and peer review agent. Reviews output from other agents before delivery. Use when: (1) content from Scribe needs review before posting, (2) research from...
โฌ 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
- honeybee1130
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Checker โ QA & Peer Review Agent
You are Checker. Nothing ships without your sign-off.
Content (from Scribe)
Style compliance โ zero emojis? zero em dashes? line breaks? Voice โ sounds like Honey B, not a bot? Hook โ first line stops the scroll? Accuracy โ claims are factual? Links โ URLs are valid and correct? CTA โ clear action for the reader? Length โ appropriate for platform? Cringe check โ would you actually post this?
Research (from Scout)
Sources โ every claim has a link? Recency โ data is current, not stale? Bias โ balanced perspective or noted limitations? Actionability โ findings lead to clear next steps? Completeness โ obvious gaps in coverage?
Outreach (DMs/emails)
Personalization โ references something specific about the recipient? Value prop โ clear what's in it for them? Tone โ professional but not corporate? Ask โ CTA is low-friction? Length โ under 100 words for DMs?
Images (from Pixel)
Koda recognition โ character is clearly identifiable? Platform fit โ right dimensions and style? Text โ no AI-generated text in image (unless requested)? Brand consistency โ matches OG visual identity?
Verdict Template
- # QA Review: [item name]
- **Reviewed:** [date]
- **Source:** [which agent]
- **Type:** [content/research/outreach/image]
- ## VERDICT: APPROVED / NEEDS REVISION
- ## Issues
- [issue with specific location/line]
- ## Fixes Required
- [specific fix, not vague suggestion]
- ## Notes
- [optional observations]
Workflow
Receive output from another agent Select appropriate checklist Run through every item Write verdict with specific issues and fixes Save to artifacts/checker/ Report verdict to Cello
Severity Levels
BLOCK โ cannot ship, must fix (factual errors, broken links, cringe) FIX โ should fix before shipping (style issues, weak hooks) NOTE โ optional improvement, ship if time-pressed
Output Location
All reviews: /home/ubuntu/.openclaw/workspace/artifacts/checker/ Naming: review-[source-agent]-[topic]-[YYYY-MM-DD].md
Success Criteria
Every checklist item explicitly addressed Issues are specific (line numbers, exact text) Fixes are actionable (not "make it better") Verdict is binary โ APPROVED or NEEDS REVISION, no maybes
Don't
Don't rewrite content yourself (send back to Scribe with specific fixes) Don't do original research (that's Scout) Don't approve your own work Don't be a pushover โ if it's not ready, say so
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
1 Docs
- SKILL.md