Name: skill-vetter
Author: LeoYeAI

Output preview skill-vetter-leoyeai.preview

---
name: skill-vetter
description: Security vetting protocol before installing any AI agent skill. Red flag detection for credentia…
category: security
runtime: no special runtime
---

# skill-vetter output preview

## PART A: Task fit
- Use case: Security vetting protocol before installing any AI agent skill. Red flag detection for credential theft, obfuscated code, exfiltration. Risk classification LOW/MEDIUM/HIGH/EXTREME. Produces structured vetting reports. Never install untrusted skills without running this first..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Problem Solved / When to Use / Vetting Protocol” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Security vetting protocol before installing any AI agent skill. Red flag detection for credential theft, obfuscated code, exfiltration. Risk classification LOW/MEDIUM/HIGH/EXTREME. Produces structured vetting reports. Never install untrusted skills without running this first.”.
- **02** When the source has headings, the agent prioritizes “Problem Solved / When to Use / Vetting Protocol” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands, read environment variables; may access external network resources; requires Vendor-specific API keys.

## Running Rules
- read files, write/modify files, run shell commands, read environment variables; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

Choose the trigger

The source mentions slash commands such as `/tmp`; use them first when your agent supports command triggers.

Provide inputs and boundaries

Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands, read environment variables.

Validate with a small run

Start with a small task and check whether the result follows “Problem Solved / When to Use / Vetting Protocol”. Inspect diffs, logs, previews, or tests before expanding scope.

Review before delivery

Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.

SKILL.md SKILL.md

---
name: skill-vetter
description: Security vetting protocol before installing any AI agent skill. Red flag detection for credentia…
category: security
source: LeoYeAI/openclaw-master-skills
---

# skill-vetter

## When to use
- Security vetting protocol before installing any AI agent skill. Red flag detection for credential theft, obfuscated co…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Problem Solved / When to Use / Vetting Protocol” and keep inference separate from source facts.
- read files, write/modify files, run shell commands, read environment variables; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "skill-vetter" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Problem Solved / When to Use / Vetting Protocol
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files, run shell commands, read environment variables | may access external network resources
  guardrails -> requires Vendor-specific API keys + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Risk Level	Examples	Action
🟢 LOW	Notes, weather, formatting	Basic review, install OK
🟡 MEDIUM	File ops, browser, APIs	Full code review required
🔴 HIGH	Credentials, trading, system	User approval required
⛔ EXTREME	Security configs, root access	Do NOT install

Source	Trust Level	Action
Official ClawHub (verified badge)	Medium	Full vet still recommended
ClawHub (unverified)	Low	Full vet required
GitHub (known author)	Medium	Full vet required
GitHub (unknown author)	Very Low	Full vet + extra scrutiny
Random URL / DM link	None	Refuse unless user insists

skill-vetter

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

Skill Vetter 🔒

Problem Solved

When to Use

Vetting Protocol

Step 1: Source Check

Step 2: Code Review (MANDATORY)

Step 3: Permission Scope

Step 4: Risk Classification

Vetting Checklist (Copy & Use)

Vetting Report Template

Quick Vet Commands

Source Trust Levels

Trust Hierarchy

Example: Vetting a ClawHub Skill

Red Flag Examples

⛔ EXTREME: Credential Theft

🔴 HIGH: Obfuscated Code

🟡 MEDIUM: External API (Legitimate Use)

🟢 LOW: Local File Operations Only

Companion Skills

Integration with Other Skills

Remember

Discussion