Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Developer
Write clean, maintainable code with debugging, testing, and architectural best practices.
skill openclawclawhub Free
Write clean, maintainable code with debugging, testing, and architectural best practices.
โฌ 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
Code Quality
Readable code beats clever code โ you'll read it 10x more than write it Functions do one thing โ if you need "and" to describe it, split it Name things by what they do, not how โ implementation changes, purpose doesn't Delete dead code โ version control remembers, codebase shouldn't carry weight Consistent style matters more than which style โ match the project
Debugging
Read the error message completely โ the answer is often in there Reproduce before fixing โ if you can't trigger it, you can't verify the fix Binary search: comment out half the code to find the problem half Check the obvious first โ typos, wrong file, stale cache, wrong environment Print/log liberally when stuck โ assumptions are usually wrong
Testing
Test behavior, not implementation โ tests shouldn't break when you refactor One assertion per test when possible โ failures point to exact problem Name tests as sentences describing expected behavior โ readable test names are documentation Mock external dependencies, not internal logic โ integration points are boundaries Fast tests run often, slow tests get skipped โ optimize for feedback speed
Error Handling
Fail fast and loud โ silent failures create debugging nightmares Catch specific exceptions, not generic โ different errors need different handling Log enough context to debug โ error type alone isn't enough User-facing errors should be helpful โ "something went wrong" helps nobody Don't catch exceptions you can't handle โ let them bubble up
Architecture
Start simple, add complexity when needed โ premature abstraction wastes time Separate concerns โ UI, business logic, data access are different responsibilities Dependencies flow inward โ core logic shouldn't know about frameworks Configuration separate from code โ environment-specific values externalized Document decisions, not just code โ why matters more than what
Code Review
Review for understanding, not just correctness โ if you can't follow it, others won't Ask questions instead of making demands โ "what if..." opens discussion Small PRs get better reviews โ 500 lines gets skimmed, 50 lines gets read Approve when good enough, not perfect โ progress beats perfection Catch bugs early, style issues are secondary โ priorities matter
Performance
Measure before optimizing โ intuition about bottlenecks is usually wrong Optimize the hot path โ 90% of time is spent in 10% of code Database queries are usually the bottleneck โ check there first Caching solves many problems โ but cache invalidation creates new ones Premature optimization wastes time โ make it work, then make it fast
Dependencies
Evaluate before adding โ every dependency is code you don't control Pin versions โ "latest" breaks builds unpredictably Check maintenance status โ abandoned packages become security risks Fewer dependencies is better โ each one adds supply chain risk Read changelogs before upgrading โ breaking changes hide in minor versions
Working in Existing Codebases
Match existing patterns โ consistency beats personal preference Improve incrementally โ boy scout rule, leave it better than you found it Understand before changing โ read the tests, check git history Don't refactor while fixing bugs โ separate commits, separate PRs Legacy code works โ respect the battle scars
Communication
Commit messages explain why, not what โ diff shows what changed Document surprising behavior โ future developers need context Ask before large refactors โ alignment prevents wasted work Estimate with ranges, not points โ "2-4 days" is more honest than "3 days" Say "I don't know" when you don't โ guessing wastes everyone's time
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