plugin-audit

Audits vercel-plugin skill injection by testing hook matching against Claude Code conversation logs.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sharad07072007/paras --skill plugin-audit-sharad07072007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-audit
Source: https://github.com/sharad07072007/paras/tree/main/.agents/plugins/vercel/.claude/skills/plugin-audit
Command: npx skills add https://github.com/sharad07072007/paras --skill plugin-audit-sharad07072007

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When a Claude Code plugin injects skills based on tool-call patterns, it is hard to know whether the right skills fire on real projects. This Skill audits vercel-plugin performance by replaying actual conversation logs through the hook matching pipeline, exposing coverage gaps, dedup behavior, and stale plugin caches. ## Core Features & Use Cases - Log-based replay: Extracts tool_use entries (Bash, Read, Write, Edit) from JSONL conversation logs and replays them through the hook's loadSkills/matchSkills functions. - Gap and dedup analysis: Produces a match matrix, dedup timeline, and list of unmatched tool calls so you can identify missing path or Bash patterns and budget/cap drops. - Cache staleness checks: Compares the installed plugin cache against the dev version using installed_plugins.json and content diffs. - Use Case: After noticing a skill never fired during a Next.js session, run the batch-match script against that session's JSONL log to see exactly which tool calls matched, which were deduped, and which patterns need to be added. ## Quick Start Ask the AI to audit vercel-plugin skill injection on your project by analyzing the conversation log at ~/.claude/projects/ for your project directory.

Frequently Asked Questions about plugin-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test Claude Code hook matching against real sessions?

Extract tool_use entries from the JSONL conversation log, then call loadSkills once and matchSkills for each tool input using the plugin's hook module. The batch-match.mjs script automates this and outputs a match matrix and dedup timeline.

Where are Claude Code conversation logs stored?

Logs are stored as JSONL files under ~/.claude/projects/<encoded-project-path>/<session-id>.jsonl, where the encoded path replaces slashes with hyphens and prepends a hyphen. Each line is a JSON object containing message content with tool_use blocks.

Why is a skill not being injected for a matching file or command?

Common causes are path or Bash pattern gaps, deduplication of an already-injected skill, or drops from the 12KB budget and 3-skill ceiling. Replay the session log through matchSkills to see exactly which case applies.

How do I check if the installed plugin cache is stale?

Compare the cache at ~/.claude/plugins/cache/vercel-labs-vercel-plugin/vercel-plugin/<version>/ against the dev version by diffing skill files. Check ~/.claude/plugins/installed_plugins.json for the installed version and git SHA.

Can I test the hook without running the full hook script each time?

Yes. Import loadSkills and matchSkills directly from hooks/pretooluse-skill-inject.mjs instead of shelling out per test. This runs the exact matching logic in-process and is much faster for batch analysis.