skills-audit

Audit agent skill directories for guideline compliance and portability standards.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aufrank/agent-skills --skill skills-audit-aufrank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-audit
Source: https://github.com/aufrank/agent-skills/tree/main/skills/skills-audit
Command: npx skills add https://github.com/aufrank/agent-skills --skill skills-audit-aufrank

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of checking your agent skills against established development guidelines, ensuring consistency, portability, and adherence to best practices.

Core Features & Use Cases

  • Guideline Compliance: Verifies SKILL.md files for correct frontmatter, naming conventions, and content length.
  • Portability Checks: Identifies hard-coded paths, non-portable commands, and incorrect fence usage.
  • Structure Validation: Ensures references are correctly organized and flags unexpected documentation files.
  • Use Case: Before merging a new skill, run this audit to catch potential issues that could hinder its deployment or cause unexpected behavior in different environments.

Quick Start

Run the audit_skills.py script from the repository root, pointing it to the skills directory.

Frequently Asked Questions about skills-audit

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

FAQPage Schema
How do I audit agent skills for compliance and portability issues?

Auditing agent skills for compliance involves checking SKILL.md files for correct frontmatter, naming conventions, and content length. This skill also validates scripts and references for hard-coded paths and structural integrity to ensure cross-environment reliability.

What are common portability issues when deploying agent skills across environments?

Common portability issues in agent skills include hard-coded paths, non-portable commands, and incorrect fence usage in scripts. Running an audit identifies these problems to ensure skills execute reliably across different deployment environments.

How do I validate SKILL.md frontmatter and naming conventions before merging?

To validate SKILL.md frontmatter and naming conventions before merging, run an audit script against your skills directory. This verifies guideline compliance by checking frontmatter correctness, content length, and structural organization of references.

Do I need any dependencies to run a skills audit on my repository?

No dependencies are required to run this skills audit. The tool operates independently to analyze your agent skill directories, requiring only the audit script and your skills repository structure to verify compliance and portability standards.

When should I run a skills compliance audit during development?

You should run a skills compliance audit before merging a new skill into your repository. This catches potential guideline violations, non-portable commands, and structural issues early, preventing unexpected behavior during deployment across different environments.

What is the best way to check agent skills for hard-coded paths and non-portable commands?

The best way to check agent skills for hard-coded paths and non-portable commands is to run an automated audit script. It analyzes your skills directory structure, verifying that scripts and references meet portability standards for cross-environment execution.