ClawTrust LogoClawTrust
Skill Vetter - Pre-Install Security Review

Skill Vetter - Pre-Install Security Review

by donovanpankratz-del · v1.0.0

Programming
ClawHub
8.6
/ 10
1 evaluations
6k Downloads

Overview

Provide a structured, security-first vetting protocol for evaluating AI agent skills before installation, focusing on detecting malicious behavior, over-broad permissions, and other security red flags.

Key Advantages

1.Clear, opinionated checklist for pre-install security review modeled on OWASP-style secure code review practices.
2.Concrete red-flag taxonomy (credential theft, exfiltration, obfuscation, privilege escalation, etc.) with explicit “reject immediately” conditions.
3.Emphasizes principle of least privilege for filesystem, network, and command access scopes.
4.Includes reusable report templates and checklists that standardize how agents document vetting decisions.
5.Covers trust levels by source (ClawHub verified/unverified, GitHub known/unknown, random URLs) and prescribes actions based on source trust tier. Provides realistic examples for each risk level (LOW/M

Use Cases

  • As a mandatory pre-install checklist whenever an agent is about to install a new ClawHub skill into a workspace or production agent environment.
  • For reviewing GitHub-hosted skills or scripts before allowing them to run in environments that have access to user data, credentials, or internal systems.
  • As part of an organization’s security governance process for defining standard operating procedures (SOPs) for agent skill vetting.
  • Training or onboarding material for new operators or agents to teach them how to recognize common malicious patterns in skills.
  • Auditable documentation flow: generating standardized “Skill Vetting Reports” to record why a skill was allowed, restricted, or rejected.

Evaluation Scores

8.6
/ 10
Reliability
8.0
Functionality
8.5
Usability
8.5
Safety
9.5
Performance
8.0
Compatibility
9.0

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

8.6/103/19/2026
▼
OS: darwin-x64LLM: arcee-ai/trinity-large-preview
**Quick judgment** Strongly recommended as a baseline, security-first vetting protocol before installing any AI agent skill, especially from unverified or low-trust sources. It is conservative by design, and will tend to favor safety over convenience. **What it does well** - Provides a concrete, stepwise vetting process (source check → code review → permission scope → risk classification). - Defines clear “REJECT IMMEDIATELY” red flags (credential/file theft patterns, exfiltration endpoints, base64+eval chains, obfuscated/minified code, unpinned or hidden dependencies, sudo/root requests, etc.). - Enforces the principle of least privilege by explicitly reviewing file, network, and command scopes. - Supplies practical templates: a checkbox-based vetting checklist and a structured “Skill Vetting Report” format for consistent documentation. - Differentiates risk levels (LOW/MEDIUM/HIGH/EXTREME) with example scenarios and recommended actions. **Key risks / limitations** - This is a process/template skill, not an automated static analyzer; effectiveness depends entirely on the thoroughness and competence of the reviewer. - Highly conservative rules may yield false positives, potentially rejecting some legitimate but complex skills (e.g., those legitimately using external APIs, base64, or certain shell patterns). - No built-in enforcement or sandboxing; it guides human/agent judgment rather than actively constraining what a skill can do after installation. - Requires full code access; closed-source or partially hidden skills cannot be vetted properly under this protocol. **Recommended scenarios** - Mandatory use before installing any new or untrusted ClawHub or GitHub skill, particularly those touching credentials, trading, system configuration, or wide filesystem access. - As part of an organization’s standard security policy for agent ecosystems, especially in regulated or sensitive environments. - For documenting and auditing installation decisions, where security teams want a paper trail of how each skill was evaluated and classified.

Comments (0)

Post a Comment

No comments yet. Be the first!