CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-vetter

Security-first skill vetting protocol for AI agents. Use before publishing a skill project or installing any skill from the platform skill market, skillhub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns to determine whether a skill is safe to install.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./backend/super-magic/agents/skills/skill-vetter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a genuinely actionable vetting workflow with concrete commands, a strong reject checklist, and validation gates before any real install. Its main weaknesses are duplication (the file-reading/cleanup block repeated across source branches) and an uncovered GitHub-source preview path.

Suggestions

Deduplicate the preview workflow: state the shared "list and read all files" block (find/cat/cleanup) once, and only show the source-specific install commands per branch.

Add a concrete preview/inspection procedure for GitHub-sourced skills, since 'Choose the preview method based on the source' currently leaves that branch without executable commands.

Tighten the lowest-scoring dimension (conciseness) by folding the 'Principles' section into the Risk Classification and Trust Hierarchy sections, which already express the same rules.

DimensionReasoningScore

Conciseness

Mostly efficient — commands and checklists dominate — but the "After install, use shell_exec to list and read all files" block is duplicated verbatim across the skillhub and platform-market branches (find/cat/cleanup repeated twice), and the "Principles" section ("No skill is worth compromising security", "When in doubt, do not install") restates the risk table and trust hierarchy. Fits 'mostly efficient but could be tightened'; not 2 because there is no padding that teaches concepts Claude already knows.

3 / 5

Actionability

Concrete, executable guidance throughout: `skillhub --dir /tmp/skillhub-preview/ install <slug>`, `find ... -type f | sort`, `cat` per file, `rm -rf` cleanup, a reject-immediately checklist, and a copy-paste report template. Minor gaps: the GitHub source path says "Choose the preview method based on the source" but provides no concrete command, and shell_exec(command=...) wrappers assume a specific tool interface. Not 5 for those gaps; well above the pseudocode-only level.

4 / 5

Workflow Clarity

Five clearly sequenced steps (Source Check → Preview Install → Code Review → Permission Scope → Risk Classification) with real validation checkpoints: install to a temp dir before the real skills directory, a "REJECT IMMEDIATELY IF YOU SEE" gate, and install-only-if-approved with a structured verdict. This satisfies the validation requirement for the system-modifying install operation. Minor gaps — no explicit error-recovery/escalation loop beyond "Escalate high-risk decisions to the user" — keep it at 4 rather than 5.

4 / 5

Progressive Disclosure

A single-file skill with clean section headers, a risk table, a checklist, and a report template — no nested or buried references, and navigation is easy. At ~187 lines, content such as the report template and trust hierarchy could arguably live in separate reference files, so it does not fully meet the 'appropriately split' bar of 5, but structure and placement are solidly at the 4 anchor.

4 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concise, with an explicit 'Use before...' trigger clause naming concrete sources and several specific capabilities. Trigger coverage is good though not exhaustive of natural synonyms, and the publishing context creates minor overlap with authoring-focused skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Checks for red flags, permission scope, and suspicious patterns" and "determine whether a skill is safe to install" — but does not comprehensively enumerate what the vetting covers. Fits the 'several specific actions; minor gaps' anchor rather than the 5's comprehensive coverage, and is clearly above the 1-2-action level.

4 / 5

Completeness

Clearly answers both parts: the 'what' is the vetting protocol ("Checks for red flags, permission scope, and suspicious patterns to determine whether a skill is safe to install") and the 'when' is explicit with concrete trigger phrases ("Use before publishing a skill project or installing any skill from the platform skill market, skillhub, GitHub, or other sources"). Matches the 5 anchor exactly; the 4 anchor requires a less explicit 'when', which is not the case here.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "platform skill market", "skillhub", "GitHub", "publishing a skill", "installing any skill", "safe to install" — phrases a user would plausibly say. A few natural variants (e.g., "review a skill", "audit a skill", "is this skill safe") are missing, keeping it below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (pre-install security vetting) with source-specific triggers unlikely to fire for unrelated skills. Minor overlap risk with skill-authoring/publishing skills around the "before publishing a skill project" clause, so it sits at 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dtyq/magic

Path

backend/super-magic/agents/skills/skill-vetter/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.