Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Validator Agent
Validates project pre-deployment by running comprehensive security, testing, quality, documentation, CI/CD, privacy, maintainability, usability, marketabilit...
skill openclawclawhub Free
Validates project pre-deployment by running comprehensive security, testing, quality, documentation, CI/CD, privacy, maintainability, usability, marketabilit...
โฌ 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, skill.json
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.1.0
Provenance
- Publisher
- up2itnow
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Validator Agent
Multi-round automated validation pipeline for TypeScript/Solidity projects. Runs 8 rounds of checks before any publish or deploy: compile gate, lint, test suite, security audit, type coverage, docs, changelog, and final review. The gold standard โ catches what manual review misses. Originally built to validate the agent-wallet-sdk before every npm publish. Now available as a reusable skill for any project.
When to Use
Before npm publish โ run the full 8-round validation Before merging a PR โ run as a quality gate After a dependency update โ verify nothing regressed On any TypeScript or Solidity project in the workspace
Quick Start
Run the Validator Agent on skills/agent-nexus-2/agent-wallet-sdk Or trigger specific rounds: Run Validator Agent round 0 (compile gate) on projects/mastra-plugin
Round 0 โ Compile Gate (BLOCKING)
cd <project> && npx tsc --noEmit 2>&1 If this fails, ALL subsequent rounds are BLOCKED. Nothing proceeds until compile is clean. This was added after a Feb 20 incident where broken types were published to npm.
Round 1 โ Lint
cd <project> && npm run lint 2>&1 | tail -20 Check for lint errors. Warnings are noted but don't block. Errors block.
Round 2 โ Test Suite
cd <project> && npm test 2>&1 Capture: total tests, passing, failing, skipped. Compare against baseline in ops/test-baselines.md if it exists. Any test count drop = regression = BLOCK.
Round 3 โ Security Audit
cd <project> && npm audit 2>&1 | tail -15 0 vulnerabilities โ โ PASS Moderate only (transitive) โ โ ๏ธ WARN (note but don't block) HIGH or CRITICAL โ ๐จ BLOCK
Round 4 โ Type Coverage
cd <project> && npx type-coverage 2>&1 || echo "type-coverage not installed โ skip" If available, report percentage. Target: >95%. Below 90% = WARN.
Round 5 โ Documentation Check
Does README.md exist and reference current version? Does CHANGELOG.md have an entry for the version being published? Are all exported functions documented?
Round 6 โ Changelog Verification
Read package.json version field Read CHANGELOG.md โ does it have an entry matching that version? If no changelog entry for current version โ BLOCK publish
Round 7 โ Final Review Summary
Aggregate all rounds into a single verdict: # Validator Agent Report โ [project] โ [timestamp] ## Verdict: [โ PASS / โ ๏ธ WARN / ๐จ BLOCK] | Round | Check | Result | |-------|-------|--------| | 0 | Compile | โ /โ | | 1 | Lint | โ /โ ๏ธ/โ | | 2 | Tests | โ X/X passing / โ regression | | 3 | Security | โ /โ ๏ธ/๐จ | | 4 | Type Coverage | โ X% / โ ๏ธ / skipped | | 5 | Docs | โ /โ ๏ธ | | 6 | Changelog | โ /โ | | 7 | Summary | [verdict] | ## Blocking Issues [list or "None"] ## Warnings [list or "None"] ## Recommendation [PUBLISH / FIX FIRST / DO NOT PUBLISH] Save report to: ops/reports/validator-YYYY-MM-DD-HH-[project].md
Configuration
The skill auto-detects project type from: package.json โ TypeScript/Node project foundry.toml โ Solidity/Forge project For Solidity projects, Round 0 uses forge build instead of tsc, Round 2 uses forge test, and Round 3 uses forge audit (if slither is available).
Authority
This skill is read-only โ it checks and reports, never modifies code It produces a recommendation, never auto-publishes Max or Bill must approve the publish after reviewing the report
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 Docs1 Config
- SKILL.md
- skill.json