CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-supply-chain-audit

Audit the extensions AI coding agents load and trust (skills, plugins, marketplaces, hooks, settings, MCP servers, and instruction files like CLAUDE.md, AGENTS.md, GEMINI.md, .cursor/rules and copilot-instructions.md) across Claude Code, Cursor, Codex, Gemini CLI and GitHub Copilot. Read-only: inventories each item with its source and pin, greps for hidden instructions, exfiltration, credential reads, persistence, curl|bash and over-broad tool grants, reviews hooks and MCP pinning and tool poisoning, and gives each item a SAFE / CAUTION / DO-NOT-INSTALL verdict. Use when the user mentions 'audit my skills,' 'is this skill malicious,' 'is this skill safe,' 'is this MCP server safe,' 'review CLAUDE.md,' 'review AGENTS.md,' 'plugin security,' 'check my hooks,' 'audit my MCP servers,' 'agent supply chain,' 'SkillSpector,' 'tool poisoning,' 'rug pull,' 'audit my IDE extensions,' 'is this VS Code extension safe,' or is about to install a skill, plugin, MCP server, or IDE extension.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, operational audit playbook: concrete grep commands and per-agent path tables, a clearly sequenced Step 0–6 workflow with a findings validator and explicit triage and closure rules, and disciplined offloading of full detail to real, well-signaled reference files. The only deduction is minor token overhead in the motivating intro, the cross-reference paragraph, and the partially duplicated headline location table.

Suggestions

Trim the opening statistics ('of 31,132 public skills analysed, 26.1% had a vulnerability and 5.2% looked malicious') to a single clause or move them to a reference file — the model does not need motivating data to execute the audit.

Compress the Step 1 headline location table, which overlaps references/locations.md, to agent names plus a pointer, or keep only the columns (source, pin, runtime) not already tabulated there.

Shorten the cross-references paragraph (ten sibling skills) to the three most likely handoffs (prompt-injection, secrets-audit, incident-triage) and move the full map to a reference file.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (it never explains what MCP servers or hooks are), but a few passages could be trimmed: the motivating statistics ('of 31,132 public skills analysed, 26.1% had a vulnerability and 5.2% looked malicious'), the long sibling-skill cross-reference paragraph, and the Step 1 headline location table that partially duplicates references/locations.md. This matches 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than 5, whose every token must earn its place; it is clearly above 3, which requires genuinely unnecessary explanation or padding.

4 / 5

Actionability

Fully executable guidance throughout: the Step 2 grep table gives concrete `rg` patterns (with 'Set `T` to the inventoried paths first' and a note on unescaping `\|`), Steps 3–4 give copy-paste bash blocks over named settings files, and the skill specifies the exact SkillSpector invocation (`skillspector scan --no-llm .claude/skills -f json -o skillspector.json`), the pinned MCP Inspector snapshot command, the full findings.json record fields, and the validator command `node references/validate-findings.mjs findings.json`. Matches the 5 anchor; 4 would tolerate missing key details, and none are missing.

5 / 5

Workflow Clarity

Steps 0–6 are clearly sequenced (authorization/scope → inventory → content checks → hooks and settings → MCP servers → optional scan → verdicts and output) with explicit validation checkpoints: 'Fix every error before writing prose' after running the findings validator, explicit hit-triage rules ('Directive vs documentation,' 'Concealment is the signal'), and a confirmed / needs_validation / rejected closure model with per-item validation plans. Matches the 5 anchor (explicit validation, feedback loops, checklists); the missing-validation cap at 3 does not apply because validation is present and the skill is read-only.

5 / 5

Progressive Disclosure

Each section keeps only headline detail inline and clearly signals its one-level-deep reference — 'The per-agent path tables and a one-shot discovery command are in references/locations.md,' 'the full set, with portable grep / perl equivalents, is in references/content-checks.md,' plus browser-runtimes.md, launch-directories.md, ide-extensions.md, findings-format.md, and severity-calibration.md — and all referenced files exist in references/. The two bundle files not named in the body (findings.schema.json, to-sarif.mjs) are documented in findings-format.md, so nothing is orphaned. Matches the 5 anchor (clear overview, well-signaled one-level-deep references, appropriate split); 4 would show organization gaps, and none are evident.

5 / 5

Total

19

/

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 long but every clause is functional: it names the covered agents and item types, enumerates concrete read-only audit actions in third person, states the output verdicts, and closes with an explicit 'Use when' clause quoting natural trigger phrases including filenames. It fully meets the top anchor on all four dimensions with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'inventories each item with its source and pin, greps for hidden instructions, exfiltration, credential reads, persistence, curl|bash and over-broad tool grants, reviews hooks and MCP pinning and tool poisoning, and gives each item a SAFE / CAUTION / DO-NOT-INSTALL verdict' — comprehensive coverage of the whole audit workflow, in third person. Matches the 5 anchor (multiple specific concrete actions, comprehensive coverage), not 4, which expects minor gaps in coverage.

5 / 5

Completeness

Explicitly answers both parts: what ('Read-only: inventories each item with its source and pin, greps for …, reviews …, and gives each item a SAFE / CAUTION / DO-NOT-INSTALL verdict') and when ('Use when the user mentions … or is about to install a skill, plugin, MCP server, or IDE extension') with concrete trigger phrases — the 5 anchor. A 4 would have a 'when' clause that is present but less explicit.

5 / 5

Trigger Term Quality

Quotes natural user phrasings verbatim — 'audit my skills,' 'is this skill malicious,' 'is this MCP server safe,' 'check my hooks,' 'is this VS Code extension safe' — plus practitioner jargon ('tool poisoning,' 'rug pull,' 'SkillSpector') and concrete filenames (CLAUDE.md, AGENTS.md, GEMINI.md, .cursor/rules, copilot-instructions.md). Comprehensive synonym and filename coverage matches the 5 anchor; 4 would leave natural terms missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — auditing the extensions and instruction files AI coding agents load — with distinctive triggers ('agent supply chain,' 'audit my MCP servers,' 'plugin security') unlikely to fire for a generic security-review or document skill. Minimal conflict risk matches 5; 4 ('minor overlap risk with closely related skills') is not a better fit since the enumerated triggers all point uniquely at this skill.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/agent-supply-chain-audit/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.