Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Developer Tools
ClawHub Skill Publisher
Research, structure, and publish skills to ClawHub. Analyzes top listings for content patterns, generates gap reports against your draft, patches README/SKIL...
skill openclawclawhub Free
Research, structure, and publish skills to ClawHub. Analyzes top listings for content patterns, generates gap reports against your draft, patches README/SKIL...
β¬ 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, examples/gap-analysis.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.1
Provenance
- Publisher
- ragesaq
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
ClawHub Skill Publisher v1
Turn a rough skill idea into a polished, publish-ready ClawHub listing β informed by what's actually working in the marketplace. Use this skill when you want to: Publish a new skill to ClawHub Audit an existing skill draft against marketplace standards Research what top-performing skills look like before writing yours
Step 1 β Research Top Listings
Install the most relevant published skills in a temp directory and read their SKILL.md + README.md: mkdir -p /tmp/ch-research # Search for skills in your category clawhub search "your-category-keyword" # Install top 3-5 results for analysis clawhub install <slug1> --dir /tmp/ch-research --force clawhub install <slug2> --dir /tmp/ch-research --force # (rate limit: add 3s sleep between installs) What to capture per skill: Description line: length, tone, value-first or feature-first? First sentence of SKILL.md: does it state the use case immediately? Structure: does it use tables, code blocks, headers? Word count (target: 400β700 words for SKILL.md) Sections present: commands, when-to-use, safety, version history Trust signals: safety section, version history, explicit opt-outs
Step 2 β Gap Analysis
Compare your draft against findings. Score each dimension: DimensionBest PracticeYour DraftActionDescription lineβ€160 chars, value-first, no buzzwords?Patch or OK"When to use"Explicit trigger + do/don't?Patch or OKCommands/interfaceSlash commands or trigger phrases?Patch or OKWord count (SKILL.md)400β700 words?Trim or expandTables vs. proseTables preferred for comparisons?Patch or OKVersion historyPresent, at bottom?Add or OKSafety sectionExplicit "never does X" list?Add or OKExamplesConcrete β /β pairs?Add or OKAttributionLink back to openclaw.ai / clawhub.ai?Add or OK
Step 3 β Patch the Draft
Apply gap findings. Priority order: Description line (most visible β fix first) "When to use" section (drives installs) Trim word count if over 700 (cut prose, keep tables) Add missing sections (safety, version history) Convert prose comparisons to tables Add examples file if none exists
Step 4 β Publish
# Verify auth clawhub whoami # Publish (run from workspace root or skill parent dir) clawhub publish ./skills/<your-skill> \ --slug <your-slug> \ --name "Your Skill Name" \ --version 1.0.0 \ --changelog "Initial release" Published URL: https://clawhub.ai/skills/<your-slug>
Description Field (β€160 chars)
The most important text. Shows in search results and install prompts. Formula: [What it does] + [how] + [key outcome]. β Good: "Reduce AI costs by batching related asks into fewer responses. ~30β50% fewer API calls, no quality loss." β Bad: "ClawSaver β Combines Linked Asks into Well-structured Sets for Affordable, Verified, Efficient Responses"
SKILL.md Structure (what the agent reads)
--- name: skill-name version: X.Y.Z description: "Same as listing description" metadata: {"openclaw":{"emoji":"π§"}} --- # Skill Name vX > One-line positioning statement. [One paragraph: what it does and why.] ## When to Use [Use / Do not use β explicit conditions] ## Core Behavior / Commands [Tables preferred. Trigger phrases, commands, decision rules.] ## Safety [What it never does. Explicit opt-outs.] ## Installation [clawhub install command] ## Version History [- X.Y.Z β what changed]
README.md Structure (humans + listing body)
# Skill Name > Tagline ## Why [Skill Name]? [Problem β solution in 2-3 sentences] ## What It Does [Numbered or bulleted feature list] ## [Key Decision Table or Usage Example] ## Safety Model ## Installation ## Version
What top skills have in common
Value-first description (outcome before feature list) "When to use" is explicit β most top skills have do/don't lists Tables over prose for anything comparative Safety section is a trust signal β include it even if short Version history at the bottom β shows maintenance Word count 400β700 for SKILL.md; README can be longer
What separates good from great
Great: examples file with concrete β /β pairs Great: trigger phrase detection (tells agent when to activate) Great: explicit opt-outs ("say X to disable") Good but not great: long prose descriptions, missing opt-outs Avoid: backronyms or clever names in the description line (save for README)
Category density (as of Feb 2026)
Cost/token tracking: saturated β need a differentiated angle Batch/workflow: sparse β opportunity Provider-specific tools: mixed β Kimi-heavy, OpenAI moderate Productivity/meta-skills: sparse β opportunity
File Checklist Before Publishing
SKILL.md β frontmatter has name, version, description SKILL.md β word count 400β700 SKILL.md β has "When to Use" section SKILL.md β has Safety section SKILL.md β has Version History README.md β value-first, β€600 words README.md β installation command correct examples/ β at least one example file (optional but recommended) Description line β β€160 chars, value-first clawhub whoami β auth confirmed before publish
Skill Type: Behavior-Change vs. Active Tool
Most ClawHub skills are behavior-change skills β they work by shaping agent judgment through instructions, not by running code or intercepting requests at the system level. This is the same mechanism as execution-loop-breaker, token-saver, and most top listings. When writing a behavior-change skill: Be explicit in the description that it works through agent behavior, not automated interception Use language like "trains your agent to..." or "gives your agent the judgment to..." β not "automatically detects" or "intercepts" Don't overstate automation. "Teaches your agent to consolidate related asks" is honest. "Automatically batches requests" implies system-level routing that the skill doesn't do. The benefit is still real β behavior change produces real cost and efficiency improvements When a skill needs to be an active tool: Requires pre-response hooks or middleware (OpenClaw doesn't currently expose these) Requires script files (analyzer.js, optimizer.js) that actually run Example: a real token optimizer that reads context size and trims it before sending Bottom line: Instruction-based skills are legitimate and valuable. Just be honest about the scope. Users trust skills that set accurate expectations.
Version History
1.0.1 β Added "Skill Type: Behavior-Change vs. Active Tool" lesson from ClawSaver development 1.0.0 β Initial release. Research workflow, gap analysis framework, listing anatomy, marketplace patterns from Feb 2026 analysis.
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
3 Docs
- SKILL.md
- examples/gap-analysis.md
- README.md