skill vetter

Security Community

Skill notes

When to Use

Before installing any skill from the platform skill market Before installing external skills from skillhub Before running skills from GitHub repositories When evaluating skills shared by other agents Anytime you are asked to install unknown code

Step 1: Source Check

Questions to answer: Where did this skill come from? (platform market / skillhub / GitHub / other) Is the author known or reputable? How many downloads or stars does it have? When was it last updated?

Step 2: Preview Install to Temp Dir, Then Read All Files

Do not install to the real skills directory yet. Install to a temp directory first for inspection. Choose the preview method based on the source: skillhub source (supports --dir for temp directory): After install, use shell_exec to list and read all files: If approved, run the normal install without --dir. Either way, clean up the temp dir:

Step 3: Code Review (MANDATORY)

Read ALL files in the skill. Reject immediately if any of the following are present:

Step 4: Permission Scope

Evaluate: What files does it need to read? What files does it need to write? What commands does it run? Does it need network access? To where?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@dtyq · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Source Check

Questions to answer: Where did this skill come from? (platform market / skillhub / GitHub / other) Is the author known or reputable? How many downloads or stars does it have? When was it last updated?

02
Step 2: Preview Install to Temp Dir, Then Read All Files

Do not install to the real skills directory yet. Install to a temp directory first for inspection. Choose the preview method based on the source: skillhub source (supports `--dir` for temp directory): After install, use `shell_exec` to list and read all files: If approved, run the normal install without `--dir`. Either way, clean up the temp dir:

03
Step 3: Code Review (MANDATORY)

Read ALL files in the skill. Reject immediately if any of the following are present:

04
Step 4: Permission Scope

Evaluate: What files does it need to read? What files does it need to write? What commands does it run? Does it need network access? To where?

05
Step 5: Risk Classification

Risk Level · Examples · Action LOW · Notes, weather, formatting · Basic review, install OK MEDIUM · File ops, browser, external APIs · Full code review required HIGH · Credentials, trading, system commands · Human approval required EXTREME · Security configs, root access · Do NOT install

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.