plugin-audit

Name: plugin-audit
Availability: InStock
Author: global-os

Analyze Claude Code logs to audit Vercel-plugin performance and cache staleness.

Updated Dec 12, 2025

Search Tags:#code review #performance analysis #performance audit #tool usage #Vercel-plugin

Ready to run

npx skills add https://github.com/global-os/gproxy --skill plugin-audit-global-os

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plugin-audit
Source: https://github.com/global-os/gproxy/tree/main/.agents/skills/plugin-audit
Command: npx skills add https://github.com/global-os/gproxy --skill plugin-audit-global-os

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the audit of Vercel-plugin performance on real-world projects, identifying gaps, coverage, and plugin cache staleness issues.

Core Features & Use Cases

Performance Audit: Analyze Vercel-plugin performance on actual projects.
Tool Call Extraction: Extracts tool calls from Claude Code conversation logs.
Pattern Matching: Matches hook inputs against tool calls and identifies coverage gaps.
Cache Staleness Check: Validates plugin cache against the latest version.
Use Case: When you need to audit a plugin's performance on a project, this skill can automatically analyze tool usage, identify mismatched patterns, and check for outdated cache entries.

Quick Start

Run the plugin-audit skill on your project to automatically analyze the performance of your Vercel-plugin setup.

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 performance on real projects?▼

To audit Vercel-plugin performance, you can use an automated tool that analyzes Claude Code conversation logs, extracts tool calls, matches hook inputs, and checks cache staleness to generate a structured report of performance metrics and gaps.

What does a plugin performance audit analyze in Claude Code logs?▼

A plugin performance audit analyzes Claude Code conversation logs to extract tool calls, match hook inputs against those calls, identify coverage gaps, and validate plugin cache staleness against the latest version.

Do I need Claude Code project logs to run a Vercel-plugin performance audit?▼

Yes, you need Claude Code project logs and an existing Vercel-plugin setup, as the audit process relies on parsing these conversation logs to extract tool usage data and identify performance coverage gaps.

How do I identify Vercel-plugin coverage gaps and mismatched patterns?▼

You identify Vercel-plugin coverage gaps by matching hook inputs against extracted tool calls within conversation logs, which highlights mismatched patterns and uncovers missing tool usage in your project.

How do I check Vercel-plugin cache staleness against the latest version?▼

You check Vercel-plugin cache staleness by validating the existing plugin cache against the latest version, allowing the audit process to detect and report outdated cache entries that may impact performance.

What is the best way to automate tool usage analysis for Vercel-plugin?▼

The best way to automate tool usage analysis is running an audit skill that parses Claude Code logs, extracts tool calls, and automatically generates a structured report of performance metrics and plugin coverage gaps.