Automated summary
Audits an Agent Skills file for compliance with best practices, including pure XML structure and progressive disclosure.
Strengths
- Ensures skills follow required structure, tags, and formatting standards.
- Provides detailed findings with file:line locations and actionable recommendations.
- Automates quality review, reducing manual oversight.
Limitations
- Relies on up-to-date best practices documentation being correct and accessible.
- May produce false positives if rules misapply to edge cases.
- Requires correct subagent invocation and proper argument passing.
When creating or editing a skill and you need to validate its structure and compliance before usage or sharing.
If you are not working on Agent Skills files or need a general-purpose code linter for other languages.
Security analysis
SafeThe skill solely invokes a subagent for auditing, with no execution of system commands, network calls, or dangerous operations. No tools are declared, and it does not handle sensitive data.
No concerns found
How this analysis is madeExamples
Audit the skill at ./skills/deploy.mdRun skill auditor on /home/user/project/skills/my-skill.mddescription: Audit skill for YAML compliance, pure XML structure, progressive disclosure, and best practices argument-hint: <skill-path>
<objective> Invoke the skill-auditor subagent to audit the skill at $ARGUMENTS for compliance with Agent Skills best practices.This ensures skills follow proper structure (pure XML, required tags, progressive disclosure) and effectiveness patterns. </objective>
<process> 1. Invoke skill-auditor subagent 2. Pass skill path: $ARGUMENTS 3. Subagent will read updated best practices (including pure XML structure requirements) 4. Subagent evaluates XML structure quality, required/conditional tags, anti-patterns 5. Review detailed findings with file:line locations, compliance scores, and recommendations </process><success_criteria>
- Subagent invoked successfully
- Arguments passed correctly to subagent
- Audit includes XML structure evaluation </success_criteria>
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/skill-audit-for-yaml-xml-compliance-mrzxurl5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/skill-audit-for-yaml-xml-compliance-mrzxurl5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/skill-audit-for-yaml-xml-compliance-mrzxurl5/download' --output '.skill-downloads/skill-audit-for-yaml-xml-compliance-mrzxurl5/SKILL.md.part' && mv '.skill-downloads/skill-audit-for-yaml-xml-compliance-mrzxurl5/SKILL.md.part' '.skill-downloads/skill-audit-for-yaml-xml-compliance-mrzxurl5/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/skill-audit-for-yaml-xml-compliance-mrzxurl5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.