Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vercel-labs avatar

Plugin Audit

  • 1.1k installs
  • 229 repo stars
  • Updated July 27, 2026
  • vercel-labs/vercel-plugin

plugin-audit provides documented workflows for Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, ident

About

The plugin-audit skill audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache staleness. Use when asked to audit, test, or investigate plugin skill injection on a real project. # Plugin Audit Audit how well vercel-plugin skill injection performs on real-world Claude Code sessions. Locate conversation logs Find JSONL conversation logs for a target project: ```bash ls -lt ~/.claude/projects/-Users-*-<project-name>/*.jsonl ``` The path uses the project's absolute path with slashes replaced by hyphens and a leading hyphen. Extract tool calls Parse the JSONL log to extract all tool_use entries. Each line is a JSON object with `message.content[]` containing `type: "tool_use"` blocks. Extract `name` and `input` fields. Group by tool type (Bash, Read, Write, Edit). Test hook matching Use the exported pipeline functions directly - do NOT shell out to the hook script for each test.

  • **Path pattern gaps**: Files that should trigger a skill but don't (e.g., `src/db/schema.ts` not matching `vercel-storag
  • **Bash pattern gaps**: Commands that should trigger but don't (e.g., missing package manager variants)
  • **Dedup masking**: Skills that matched but were deduped before injection
  • **Budget/cap drops**: Skills matched but dropped by the 12KB budget or 3-skill ceiling
  • **Session summary**: Project, date, tool call count, model

Plugin Audit by the numbers

  • 1,116 all-time installs (skills.sh)
  • Ranked #940 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

plugin-audit capabilities & compatibility

Capabilities
**path pattern gaps**: files that should trigger · **bash pattern gaps**: commands that should trig · **dedup masking**: skills that matched but were · **budget/cap drops**: skills matched but dropped · **session summary**: project, date, tool call co
Use cases
documentation
From the docs

What plugin-audit says it does

# Plugin Audit Audit how well vercel-plugin skill injection performs on real-world Claude Code sessions.
SKILL.md
Extract tool calls Parse the JSONL log to extract all tool_use entries.
SKILL.md
npx skills add https://github.com/vercel-labs/vercel-plugin --skill plugin-audit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.1k
repo stars229
Security audit2 / 3 scanners passed
Last updatedJuly 27, 2026
Repositoryvercel-labs/vercel-plugin

How do I use plugin-audit for the task described in its SKILL.md triggers?

Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks.

Who is it for?

Teams invoking plugin-audit when the user request matches documented triggers and prerequisites.

Skip if: Skip when cached docs are missing, the request is a negative trigger, or another sibling skill owns the workflow.

When should I use this skill?

Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache stalene

What you get

Step-by-step guidance grounded in plugin-audit documentation and reference files.

  • Hook coverage gap report
  • Tool-call extraction summary
  • Cache staleness findings

By the numbers

  • Workflow steps: locate JSONL logs, extract tool calls, replay hook matcher, report gaps

Files

SKILL.mdMarkdownGitHub ↗

Plugin Audit

Audit how well vercel-plugin skill injection performs on real-world Claude Code sessions.

Workflow

1. Locate conversation logs

Find JSONL conversation logs for a target project:

ls -lt ~/.claude/projects/-Users-*-<project-name>/*.jsonl

The path uses the project's absolute path with slashes replaced by hyphens and a leading hyphen.

2. Extract tool calls

Parse the JSONL log to extract all tool_use entries. Each line is a JSON object with message.content[] containing type: "tool_use" blocks. Extract name and input fields. Group by tool type (Bash, Read, Write, Edit).

3. Test hook matching

Use the exported pipeline functions directly — do NOT shell out to the hook script for each test. Import from the hooks directory:

import { loadSkills, matchSkills } from "./hooks/pretooluse-skill-inject.mjs";
import { createLogger } from "./hooks/logger.mjs";

Call loadSkills() once, then matchSkills(toolName, toolInput, compiledSkills) for each tool call. This is fast and gives exact match results.

4. Identify gaps

Compare matched skills against what SHOULD have matched based on the project's technology stack. Common gap categories:

  • Path pattern gaps: Files that should trigger a skill but don't (e.g., src/db/schema.ts not matching vercel-storage)
  • Bash pattern gaps: Commands that should trigger but don't (e.g., missing package manager variants)
  • Dedup masking: Skills that matched but were deduped before injection
  • Budget/cap drops: Skills matched but dropped by the 12KB budget or 3-skill ceiling

5. Check plugin cache staleness

Compare the installed plugin cache against the dev version:

# Cache location
~/.claude/plugins/cache/vercel-labs-vercel-plugin/vercel-plugin/<version>/

# Compare skill content
diff <(grep 'pattern' skills/<skill>/SKILL.md) <(grep 'pattern' ~/.claude/plugins/cache/.../skills/<skill>/SKILL.md)

Check ~/.claude/plugins/installed_plugins.json for version and git SHA.

Report Format

Produce a structured report with:

1. Session summary: Project, date, tool call count, model 2. Match matrix: Table of tool calls × matched skills (with match type) 3. Coverage gaps: Unmatched tool calls that should have matched, with suggested pattern additions 4. Dedup timeline: Order of skill injections and what got deduped 5. Cache status: Whether installed version matches dev, with specific diffs

References

  • Log format details
  • Test script for batch matching

Related skills

How it compares

Pick plugin-audit for retrospective JSONL coverage analysis; pick benchmark-agents for forward interactive eval scenarios on new Vercel features.

FAQ

What does plugin-audit do?

Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache stalene

When should I use plugin-audit?

Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache stalene

What are common prerequisites?

--- name: plugin-audit description: Audit vercel-plugin performance on real-world projects.

Is Plugin Audit safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.