openclaw-skill-eeta-audit
by @281862066-a11y
OpenClaw Skill quality audit based on CORE-EEAT framework adapted for AI agent skills. Evaluates skill's utility (task completion efficiency) and security (s...
clawhub install openclaw-skill-eeta-auditπ About This Skill
name: eeat-openclaw-skill-audit description: OpenClaw Skill quality audit based on CORE-EEAT framework adapted for AI agent skills. Evaluates skill's utility (task completion efficiency) and security (safe execution). Features 80 standardized criteria, 8-dimension scoring, veto item detection for security vulnerabilities, and priority improvement recommendations. Applicable for skill selection, security vetting, and skill quality assessment.
EEAT OpenClaw Skill Audit
> AI Agent Skill Quality Assurance β This skill adapts the CORE-EEAT framework to evaluate OpenClaw Skills, ensuring they deliver meaningful utility while maintaining security and reliability.
Skill Overview
OpenClaw Skills are modular capability extensions for AI agents, defined by SKILL.md files with YAML frontmatter and prompt instructions. This skill evaluates skill quality through 80 standardized criteria across 8 core dimensions, generating comprehensive audit reports including utility scores, security assessments, and actionable improvement recommendations.
Core Transformation:
OpenClaw Skill Structure
Every OpenClaw Skill consists of:
my-skill/
βββ SKILL.md # Core definition (YAML + Markdown instructions)
βββ scripts/ # Optional executable scripts
β βββ main.py
βββ references/ # Optional configuration and resources
βββ config.json
Key Components:
Applicable Scenarios
Use this skill when users request:
Skill Selection
Security Vetting
Skill Development
Skill Maintenance
Core Capabilities
This skill can:
1. Complete 80-Item Audit: Score each CORE-EEAT item adapted for OpenClaw Skills
2. Utility Scoring: Evaluate task completion efficiency and comparative value
3. Security Assessment: Three-level security evaluation (Pass/Caution/Risk)
4. Gating Validation: Check conditional activation requirements (bins, env, os)
5. Veto Item Detection: Flag critical security violations (command injection, data leakage)
6. Priority Ranking: Identify top 5 improvements by impact
7. Comparative Analysis: Compare skills for same use case
Skill Categories
This skill supports 6 OpenClaw Skill types, each with different evaluation priorities:
Productivity Skills
Development Skills
Research Skills
Automation Skills
Content Skills
System Skills
8 Progressive Quality Gates
Gate 1: Metadata Validation (Pre-Installation)
When: Before installing any skill
Duration: 2-5 minutes
Items:
Deliverable: Metadata Validation Report
Failure: Do not install. Contact skill author or fix manually.
Gate 2: Gating Mechanism Check
When: After metadata validation, before activation
Duration: 1-2 minutes
Items:
Deliverable: Gating Compatibility Report
Failure: Skill will not activate. Fix environment or choose alternative.
Gate 3: Security Pre-Check
When: Before first execution
Duration: 3-5 minutes
Items:
Deliverable: Security Pre-Check Report
Failure: Do not execute. Review code or choose alternative.
Gate 4: Prompt Quality Review
When: During skill development or installation
Duration: 5-10 minutes
Items:
Deliverable: Prompt Quality Report
Failure: Skill may misbehave. Refine SKILL.md instructions.
Gate 5: Script Security Audit
When: For skills with executable scripts
Duration: 10-20 minutes
Items:
Deliverable: Script Security Audit
Failure: Security risk. Audit scripts or avoid skill.
Gate 6: Utility Testing
When: During skill evaluation
Duration: 15-30 minutes
Items:
Deliverable: Utility Test Report
Failure: Skill doesn't deliver value. Consider alternatives.
Gate 7: Comparative Analysis
When: Selecting between multiple skills for same task
Duration: 10-15 minutes
Items:
Deliverable: Comparative Analysis Report
Failure: Alternative skill may be better. Choose based on scores.
Gate 8: Full 80-Item Audit
When: Critical skills, major updates, security reviews
Duration: 30-60 minutes
Items: All 80 items across all 8 dimensions
Deliverable: Comprehensive EEAT Audit Report
Failure: Address critical issues before production use.
Usage Examples
Example 1: Pre-Installation Security Check
User Request:
Check if this skill is safe to install:
clawhub install agent-browser
Response:
## EEAT Skill Security Audit: agent-browserGate 1: Metadata Validation β
[x] YAML frontmatter valid
[x] Description clear: "Browser automation for web scraping"
[x] Version: 1.2.3
[x] Dependencies: playwright (verified safe) Gate 2: Gating Check β οΈ
[x] Bins: playwright installed
[x] Env: PLAYWRIGHT_BROWSERS_PATH set
[ ] OS: macOS/Windows only (Linux limited support) Gate 3: Security Pre-Check β
[x] T01: No command injection detected
[x] T02: No data leakage risks
[x] T03: Input validation on URLs
[x] T04: Minimal permissions (browser control only) Security Score: 92/100
Security Status: CAUTION β οΈ
Linux support limited
Requires browser installation (system-level change) Recommendation
β
Install with Caution
Safe for macOS/Windows users
Linux users should check compatibility
Review permissions before first use
Example 2: Compare Two Skills
User Request:
Compare tavily-search vs web-search for web search
Response:
## Skill Comparative Analysis: Web SearchSkill A: tavily-search
Utility Score: 85/100
C05: High accuracy search results β
C06: Clean, structured output β
Exp01: Excellent usage examples β
E01: AI-optimized for agents π― Security Score: 95/100
T01-T04: All checks pass β
T07: No external dependencies β
Overall: 88/100 (Very Good)
Skill B: web-search (bundled)
Utility Score: 70/100
C05: Basic search functionality β
C06: Output quality varies β οΈ
Exp01: Limited examples β οΈ
E01: Generic implementation β οΈ Security Score: 90/100
T01-T04: Safe but basic β
T07: Uses external APIs β οΈ Overall: 75/100 (Good)
Recommendation
β
Choose tavily-search
+18 points higher utility
AI-optimized for agent workflows
Better structured output for downstream processing
Higher security score Trade-off: Requires API key setup vs. no setup for web-search
Example 3: Full Skill Audit
User Request:
Audit my custom skill: email-automation
[Paste SKILL.md content]
Response:
## EEAT Skill Audit: email-automationOverview
Skill Type: Productivity
Total Score: 62/100 (Fair)
Utility Score: 75/100 (Good)
Security Score: 45/100 (CAUTION β οΈ)
Veto Item: β οΈ T02 Triggered (Data Leakage Risk) Dimension Scores
| Dimension | Score | Rating | Weight | Weighted Score |
|-----------|-------|--------|--------|----------------|
| C β Correctness | 70/100 | Good | 30% | 21 |
| O β Organization | 65/100 | Fair | 5% | 3.25 |
| R β Referenceability | 50/100 | Fair | 25% | 12.5 |
| Exp β Experience | 80/100 | Good | 20% | 16 |
| Ept β Expertise | 55/100 | Fair | 15% | 8.25 |
| E β Exclusivity | 40/100 | Poor | 0% | 0 |
| A β Authority | 60/100 | Fair | 5% | 3 |
| T β Trust | 45/100 | Poor | 0% | 0 |
| Weighted Total | | | | 64 |
Critical Issues (Veto Items)
β οΈ T02: Data Leakage Risk
Issue: Skill stores API credentials in plain text in SKILL.md
yaml
SKILL.md
credentials: smtp_password: "mypassword123" # β οΈ SECURITY RISKAction: Move credentials to environment variables
yaml
credentials:
smtp_password: "${SMTP_PASSWORD}" # β
SECURE
Top 5 Priority Improvements
1. T02 Data Leakage β Remove hardcoded credentials
- Current: Fail | Potential Gain: 8 weighted points
- Action: Use environment variables for all secrets
2. R02 Coverage β Add error handling examples
- Current: Fail | Potential Gain: 6.25 weighted points
- Action: Document error scenarios and recovery
3. Ept01 Documentation β Improve prompt instructions
- Current: Partial | Potential Gain: 4.5 weighted points
- Action: Add step-by-step usage examples
4. R03 Source Authority β Verify email library security
- Current: Partial | Potential Gain: 3.75 weighted points
- Action: Audit nodemailer dependency for vulnerabilities
5. O01 Structure β Add scripts/ directory for complex logic
- Current: Partial | Potential Gain: 2.5 weighted points
- Action: Move complex operations to Python scripts
Action Plan
#### Quick Wins (Fix immediately)
[ ] Move all credentials to environment variables
[ ] Add error handling documentation #### Medium Investment (This week)
[ ] Add comprehensive usage examples
[ ] Implement proper logging in scripts #### Strategic (Next sprint)
[ ] Add test suite with edge cases
[ ] Implement retry logic for failed sends
[ ] Add HTML email support Recommendation
β οΈ Do Not Install Until Fixed
Security risk (T02 veto) must be addressed
After fixes, expected score: 78/100 (Good)
Reference Documents
references/openclaw-skill-benchmark.md β Complete 80-item benchmark adapted for OpenClaw Skillsreferences/skill-security-checklist.md β Security-specific evaluation criteriareferences/utility-testing-guide.md β How to test skill utility and comparative valueworkflow-optimization-analysis.md β Adaptation strategy from code to skillsKey Differences: Code vs. Skill Audit
| Aspect | Code Audit | Skill Audit | |--------|-----------|-------------| | Primary Focus | Code correctness, maintainability | Utility, security, reliability | | Security Emphasis | SQL injection, XSS | Command injection, data leakage, permissions | | Evaluation Method | Static analysis + testing | Comparative utility + security probes | | Output Format | Code quality report | Utility score + security status label | | Key Metrics | Test coverage, complexity | Task completion, risk level | | Veto Items | Security bugs, logic errors | Security vulnerabilities, data risks | | Automation Level | High (linters, type checkers) | Medium (requires manual security review) | | Comparative Analysis | Code vs. requirements | Skill vs. baseline/skills |
Success Points
1. Security-First Approach β OpenClaw Skills have system-level access; security is non-negotiable
2. Comparative Utility β Evaluate skills relative to baseline, not in isolation
3. Gating Validation β Ensure skills only activate when dependencies are met
4. Prompt Quality β SKILL.md instructions determine skill behavior; quality matters
5. Minimal Permissions β Skills should only request necessary access
6. Active Maintenance β Prioritize skills with recent updates and community support
7. Real-World Testing β Test with actual use cases, not synthetic scenarios
Optimization Recommendations
Based on OpenClaw's architecture and community best practices:
1. Add Skill Registry Integration
2. Implement Automated Security Scanning
clawsec (ClawHub security scanner)