CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-security-auditor

Security audit and vulnerability scanner for AI agent skills before installation. Use when: (1) evaluating a skill from an untrusted source, (2) auditing a skill directory or git repo URL for malicious code, (3) pre-install security gate for Claude Code plugins, OpenClaw skills, or Codex skills, (4) scanning Python scripts for dangerous patterns like os.system, eval, subprocess, network exfiltration, (5) detecting prompt injection in SKILL.md files, (6) checking dependency supply chain risks, (7) verifying file system access stays within skill boundaries. Triggers: "audit this skill", "is this skill safe", "scan skill for security", "check skill before install", "skill security check", "skill vulnerability scan".

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 is a well-structured, actionable overview backed by a real script and a single one-level reference file, with copy-paste CLI examples and a concrete report format. Its main weakness is workflow clarity: the batch and CI/CD integration paths perform install-gating decisions without an explicit validation checkpoint or review-before-install feedback loop, which the rubric caps at 3 for destructive/batch operations.

Suggestions

Add an explicit validation checkpoint to the Audit Workflow — e.g., a numbered step 'Review all CRITICAL/HIGH findings; only proceed to install when the report is PASS (or WARN with manual sign-off)' — so the install decision has a clear feedback loop.

In the Batch Audit and CI/CD Integration examples, show how to act on findings (e.g., fail the pipeline on FAIL and require explicit approval on WARN) rather than only producing output, closing the validation gap for these batch/destructive paths.

Consider trimming the decorative boxed ASCII report example to a plain-text sample to reduce token weight without losing the format reference.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — using compact tables for patterns rather than prose — but the four large detection tables plus a decorative boxed ASCII report example carry some density that could be trimmed. It sits noticeably above the 'mostly efficient' anchor but below the fully lean 'every token earns its place' anchor.

4 / 5

Actionability

Provides copy-paste-ready bash commands for every common case (local dir, git repo, strict, JSON, CI/CD, batch), references a real executable script (scripts/skill_security_auditor.py), and shows a concrete report format with file:line, pattern, risk, and fix fields — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

The Audit Workflow lists a numbered sequence with verdict interpretation and per-finding remediation, but it lacks an explicit validation/verification checkpoint before installing — and the Batch Audit and CI/CD examples perform destructive/gating install decisions with no 'review findings before install' feedback loop. Per the rubric, missing validation in batch/destructive operations caps workflow clarity at 3; it does not clearly fit the level-4 anchor's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections (Quick Start, What Gets Scanned, Audit Workflow, Reading the Report, Advanced Usage, Limitations) and a single one-level-deep reference to the real references/threat-model.md file for the complete threat model — matching the anchor for clear overview with well-signaled one-level references and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

100%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.

The description is comprehensive and well-structured, explicitly stating both what the skill does and when to use it with seven numbered use cases and six natural trigger phrases. It avoids verbosity while covering concrete capabilities, synonyms, and specific tool names. No improvements needed for the description field.

DimensionReasoningScore

Specificity

Names the domain (skill security auditing) and enumerates seven concrete actions — 'evaluating a skill from an untrusted source', 'auditing a skill directory or git repo URL', 'scanning Python scripts for dangerous patterns like os.system, eval, subprocess', 'detecting prompt injection', 'checking dependency supply chain risks', 'verifying file system access' — giving comprehensive coverage of concrete actions.

5 / 5

Completeness

Explicitly answers both 'what' ('Security audit and vulnerability scanner for AI agent skills before installation') and 'when' via a numbered 'Use when:' clause with seven cases plus a 'Triggers:' line of concrete phrases, matching the anchor that clearly answers both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger phrases users would actually say — 'audit this skill', 'is this skill safe', 'scan skill for security', 'check skill before install', 'skill security check', 'skill vulnerability scan' — alongside technical synonyms and tool names, matching the anchor's synonym-and-extension coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (pre-install security gate for AI agent skills) with distinct triggers unlikely to fire for other skills, matching the anchor for clear niche and minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.