plugin-audit

Analyze Claude Code logs to validate vercel-plugin hook injections.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ChristineTham/lp --skill plugin-audit-christinetham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-audit
Source: https://github.com/ChristineTham/lp/tree/main/.agents/skills/plugin-audit
Command: npx skills add https://github.com/ChristineTham/lp --skill plugin-audit-christinetham

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Audit vercel-plugin performance on real-world projects by analyzing Claude Code conversation logs, validating hook matching, and ensuring plugin cache freshness.

Core Features & Use Cases

  • Extracts tool_use entries from real conversation logs to quantify plugin interactions.
  • Tests hook matching against actual inputs using the provided pretooluse-skill-inject.mjs workflow.
  • Identifies pattern coverage gaps (path, command, dedup) and checks plugin cache staleness for consistency.
  • Use case: Audit a live project to ensure plugin injections align with technology stack and security policies.

Quick Start

Run the batch audit against your Claude Code project log to generate a structured report of matches, gaps, and dedup events.

Frequently Asked Questions about plugin-audit

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

FAQPage Schema
How do I audit vercel plugin hook injections in Claude Code logs?

To audit vercel plugin hook injections, you analyze Claude Code conversation logs to extract tool_use entries and validate hook matching using deterministic test hooks. This generates a structured report of matches, coverage gaps, and dedup timeline events.

What is vercel plugin cache freshness and why does it matter for security reviews?

Vercel plugin cache freshness measures whether cached plugin injections align with the current technology stack. Checking cache staleness during security reviews ensures tool-use patterns remain consistent and prevents outdated hook matching on real projects.

How do I identify pattern coverage gaps in Claude Code hook matching?

You identify pattern coverage gaps by testing hook matching against actual inputs using the pretooluse-skill-inject workflow. The audit validates path, command, and dedup patterns to detect missing interactions and quantify plugin coverage.

Can I run a batch audit on real conversation logs to check tool-use patterns?

Yes, you can run a batch audit against real Claude Code conversation logs to extract tool_use entries. This validates plugin interactions and produces a dedup timeline report highlighting matches and gaps.

Does the audit require external dependencies to validate pretooluse hook matching?

No, the audit requires no external dependencies. It uses internal scripts and references to apply deterministic test hooks like loadSkills and matchSkills directly against your Claude Code project logs.