skill-audit

Analyze SKILL.md frontmatter and content for security risk patterns.

19|4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/anysiteio/agent-skills --skill skill-audit-anysiteio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-audit
Source: https://github.com/anysiteio/agent-skills/tree/main/skills/skill-audit
Command: npx skills add https://github.com/anysiteio/agent-skills --skill skill-audit-anysiteio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Read, Grep, Glob, WebFetch.

What problem does it solve?

This Skill Audit helps security teams and developers ensure Claude Code skills, commands, and plugins are safe before deployment by performing read-only static analysis of SKILL.md frontmatter, body, and supporting files.

Core Features & Use Cases

  • Static analysis of frontmatter fields such as allowed-tools, hooks, and permissions to surface potential risk patterns
  • Discovery and evaluation of dangerous patterns in skill bodies, scripts, and hooks
  • Supports local skill directories and remote GitHub audits with a strict read-only approach
  • Use case: vet a new skill from a repository before enabling it to prevent unintended side effects
  • Use case: conduct ongoing security reviews of installed skills and plugins

Quick Start

For local audits, run: /skill-audit skills/skill-audit For GitHub audits, run: /skill-audit https://github.com/owner/repo

Frequently Asked Questions about skill-audit

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

FAQPage Schema
How do I perform a static security audit on a Claude Code skill from a GitHub repository?

Run a static security audit by passing the GitHub repository URL to the skill-audit command. It performs a read-only analysis of SKILL.md frontmatter, scripts, and hooks to surface risk patterns.

What does a static security audit check for in Claude Code skills?

A static security audit reviews SKILL.md frontmatter, body content, scripts, and hooks to identify dangerous patterns and calculate risk scores. You need it before deploying new plugins to prevent unintended side effects.

Can I audit locally installed Claude Code skills and plugins?

Yes, you can audit locally installed skills by passing the local directory path to the skill-audit command. It performs a strict read-only analysis of the SKILL.md file and supporting components.

What are the limitations of read-only static analysis for skill risk assessment?

Read-only static analysis is limited to evaluating hardcoded patterns in frontmatter, scripts, and hooks. It cannot detect runtime vulnerabilities or dynamic execution issues, providing only risk scoring and hardening recommendations.

Does the security audit modify or execute the Claude Code skills being analyzed?

No, the security audit applies a strict read-only approach using tools like Read, Grep, and Glob to analyze files. It never executes or modifies the Claude Code skills being reviewed.

How does a 5-phase security audit surface risk patterns in skill hooks?

The 5-phase analysis enumerates frontmatter, body content, scripts, references, and hooks to surface risk patterns. It assigns a risk score and provides hardening recommendations to guide safe skill enablement.