skill-auditor

Audit Claude Code skills for quality, security, and portability standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of auditing other Claude Code skills, ensuring they meet high standards for quality, security, portability, and documentation, thereby preventing common issues and improving overall reliability.

Core Features & Use Cases

  • Automated Checks: Scans SKILL.md for critical issues like hardcoded paths, missing security/error handling sections, and ambiguous language.
  • Scoring System: Assigns a production readiness score based on weighted categories.
  • Use Case: Before sharing a newly developed skill with your team, run the Skill Auditor to get a comprehensive report highlighting any critical flaws or areas for improvement, ensuring it's safe and ready for collaboration.

Quick Start

Run the skill auditor on the 'my-skill' directory.

Frequently Asked Questions about skill-auditor

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

FAQPage Schema
How do I audit Claude Code skills for security and quality standards?

Auditing Claude Code skills involves scanning SKILL.md files and associated scripts to identify hardcoded paths, missing security sections, and ambiguous terminology, generating a scored report with actionable recommendations for improvement.

What is the best way to check a skill for hardcoded paths before sharing it?

Checking a skill for hardcoded paths involves scanning the SKILL.md file and associated scripts to detect absolute file references, replacing them with portable alternatives to ensure the skill runs reliably across different environments and team setups.

How does scoring work for skill production readiness?

Scoring for skill production readiness works by assigning a weighted score across critical categories like quality, security, portability, and documentation, evaluating the presence of error handling sections and code review best practices to calculate a final readiness metric.

Do I need to manually review error handling sections in my skill documentation?

Manual review of error handling sections is not strictly necessary, as automated auditing tools can scan your SKILL.md files to detect missing critical sections and output a comprehensive report highlighting exactly where error handling documentation needs to be added.

Can I audit multiple scripts associated with a single SKILL.md file?

You can audit multiple scripts associated with a SKILL.md file by running the auditor on the skill directory, which analyzes both the main documentation and the associated scripts to ensure comprehensive code review and quality assurance across all components.

Why does my custom skill fail portability checks?

Custom skills often fail portability checks due to hardcoded paths or ambiguous terminology within the SKILL.md file or scripts, which an automated audit identifies by analyzing the files against established best practices and providing actionable recommendations.