Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Productivity
Verification Before Completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
skill openclawclawhub Free
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
โฌ 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
- 0.1.0
Provenance
- Publisher
- zlc000190
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Overview
Claiming work is complete without verification is dishonesty, not efficiency. Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of this rule.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE If you haven't run the verification command in this message, you cannot claim it passes.
The Gate Function
BEFORE claiming any status or expressing satisfaction: 1. IDENTIFY: What command proves this claim? 2. RUN: Execute the FULL command (fresh, complete) 3. READ: Full output, check exit code, count failures 4. VERIFY: Does output confirm the claim? - If NO: State actual status with evidence - If YES: State claim WITH evidence 5. ONLY THEN: Make the claim Skip any step = lying, not verifying
Common Failures
ClaimRequiresNot SufficientTests passTest command output: 0 failuresPrevious run, "should pass"Linter cleanLinter output: 0 errorsPartial check, extrapolationBuild succeedsBuild command: exit 0Linter passing, logs look goodBug fixedTest original symptom: passesCode changed, assumed fixedRegression test worksRed-green cycle verifiedTest passes onceAgent completedVCS diff shows changesAgent reports "success"Requirements metLine-by-line checklistTests passing
Red Flags - STOP
Using "should", "probably", "seems to" Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.) About to commit/push/PR without verification Trusting agent success reports Relying on partial verification Thinking "just this once" Tired and wanting work over ANY wording implying success without having run verification
Rationalization Prevention
ExcuseReality"Should work now"RUN the verification"I'm confident"Confidence โ evidence"Just this once"No exceptions"Linter passed"Linter โ compiler"Agent said success"Verify independently"I'm tired"Exhaustion โ excuse"Partial check is enough"Partial proves nothing"Different words so rule doesn't apply"Spirit over letter
Key Patterns
Tests: โ [Run test command] [See: 34/34 pass] "All tests pass" โ "Should pass now" / "Looks correct" Regression tests (TDD Red-Green): โ Write โ Run (pass) โ Revert fix โ Run (MUST FAIL) โ Restore โ Run (pass) โ "I've written a regression test" (without red-green verification) Build: โ [Run build] [See: exit 0] "Build passes" โ "Linter passed" (linter doesn't check compilation) Requirements: โ Re-read plan โ Create checklist โ Verify each โ Report gaps or completion โ "Tests pass, phase complete" Agent delegation: โ Agent reports success โ Check VCS diff โ Verify changes โ Report actual state โ Trust agent report
Why This Matters
From 24 failure memories: your human partner said "I don't believe you" - trust broken Undefined functions shipped - would crash Missing requirements shipped - incomplete features Time wasted on false completion โ redirect โ rework Violates: "Honesty is a core value. If you lie, you'll be replaced."
When To Apply
ALWAYS before: ANY variation of success/completion claims ANY expression of satisfaction ANY positive statement about work state Committing, PR creation, task completion Moving to next task Delegating to agents Rule applies to: Exact phrases Paraphrases and synonyms Implications of success ANY communication suggesting completion/correctness
The Bottom Line
No shortcuts for verification. Run the command. Read the output. THEN claim the result. This is non-negotiable.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md