Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Security & Compliance
Solidity Guardian
Smart contract security analysis skill. Detect vulnerabilities, suggest fixes, generate audit reports. Supports Hardhat/Foundry projects. Uses pattern matchi...
skill openclawclawhub Free
Smart contract security analysis skill. Detect vulnerabilities, suggest fixes, generate audit reports. Supports Hardhat/Foundry projects. Uses pattern matchi...
โฌ 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
- BEST_PRACTICES.md, SKILL.md, analyzer.js, package.json, slither-integration.js
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.3
Provenance
- Publisher
- aviclaw
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Solidity Guardian ๐ก๏ธ
Security analysis for Solidity smart contracts. Find vulnerabilities, get fix suggestions, follow best practices.
Quick Start
# Analyze a single contract node skills/solidity-guardian/analyze.js contracts/MyContract.sol # Analyze entire project node skills/solidity-guardian/analyze.js ./contracts/ # Generate markdown report node skills/solidity-guardian/analyze.js ./contracts/ --format markdown > AUDIT.md
Critical (Must Fix)
IDVulnerabilityDescriptionSG-001ReentrancyExternal calls before state updatesSG-002Unprotected selfdestructMissing access control on selfdestructSG-003Delegatecall to untrustedDelegatecall with user-controlled addressSG-004Uninitialized storage pointerStorage pointer overwrites slotsSG-005Signature replayecrecover without nonce/chainIdSG-006Arbitrary jumpFunction type from user input
High (Should Fix)
IDVulnerabilityDescriptionSG-010Missing access controlPublic functions that should be restrictedSG-011Unchecked transferERC20 transfer without return checkSG-012Integer overflowArithmetic without SafeMath (pre-0.8)SG-013tx.origin authUsing tx.origin for authenticationSG-014Weak randomnessblock.timestamp/blockhash for randomnessSG-015Unprotected withdrawalWithdrawal without ownership checkSG-016Unchecked low-level call.call() without success checkSG-017Dangerous equalityStrict balance check (manipulable)SG-018Deprecated functionssuicide, sha3, throw, callcodeSG-019Wrong constructorFunction name matches contract
Medium (Consider Fixing)
IDVulnerabilityDescriptionSG-020Floating pragmaNon-pinned Solidity versionSG-021Missing zero checkNo validation for zero addressSG-022Timestamp dependenceLogic depends on block.timestampSG-023DoS with revertLoop with external call can revertSG-024Front-running riskPredictable state changes
Low (Best Practice)
IDVulnerabilityDescriptionSG-030Missing eventsState changes without eventsSG-031Magic numbersHardcoded values without constantsSG-032Implicit visibilityFunctions without explicit visibilitySG-033Large contractContract exceeds size recommendationsSG-034Missing NatSpecPublic functions without documentation
Basic Analysis
const { analyzeContract } = require('./analyzer'); const results = await analyzeContract('contracts/Token.sol'); console.log(results.findings);
With Fix Suggestions
const results = await analyzeContract('contracts/Vault.sol', { includeFixes: true, severity: ['critical', 'high'] }); for (const finding of results.findings) { console.log(`[${finding.severity}] ${finding.title}`); console.log(` Line ${finding.line}: ${finding.description}`); console.log(` Fix: ${finding.suggestion}`); }
Generate Report
const { generateReport } = require('./reporter'); const report = await generateReport('./contracts/', { format: 'markdown', includeGas: true, includeBestPractices: true }); fs.writeFileSync('SECURITY_AUDIT.md', report);
Best Practices Checklist
When writing secure contracts, follow these guidelines:
Access Control
Use OpenZeppelin's Ownable or AccessControl Apply onlyOwner or role checks to sensitive functions Implement two-step ownership transfer Consider timelocks for critical operations
Reentrancy Prevention
Use ReentrancyGuard on all external-facing functions Follow checks-effects-interactions pattern Update state BEFORE external calls Use pull over push for payments
Input Validation
Validate all external inputs Check for zero addresses Validate array lengths match Use SafeERC20 for token transfers
Arithmetic Safety
Use Solidity 0.8+ or SafeMath Check for division by zero Validate percentage calculations (โค100) Be careful with token decimals
Upgradeability (if applicable)
Use initializer instead of constructor Protect initialize from re-initialization Follow storage layout rules Test upgrade paths
Slither Integration
Guardian can run alongside Slither for comprehensive analysis: # Combined analysis (auto-installs Slither if missing) node skills/solidity-guardian/slither-integration.js ./contracts/ --install-slither # Generate combined report node skills/solidity-guardian/slither-integration.js . --format markdown --output AUDIT.md # Guardian only (faster, no Slither dependency) node skills/solidity-guardian/slither-integration.js ./contracts/ --guardian-only # Slither only node skills/solidity-guardian/slither-integration.js ./contracts/ --slither-only Why both? Guardian: Fast pattern matching, custom rules, no compilation needed Slither: Deep dataflow analysis, CFG-based detection, more comprehensive
Hardhat
// hardhat.config.js require('./skills/solidity-guardian/hardhat-plugin'); // Run: npx hardhat guardian
Foundry
# Add to CI forge build node skills/solidity-guardian/analyze.js ./src/
References
Trail of Bits - Building Secure Contracts OpenZeppelin - Security Best Practices Consensys - Smart Contract Best Practices SWC Registry Built by Avi ๐ | Security-first, ship always.
Category context
Identity, auth, scanning, governance, audit, and operational guardrails.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs2 Scripts1 Config
- SKILL.md
- BEST_PRACTICES.md
- analyzer.js
- slither-integration.js
- package.json