auditing-commands

To audit slash command Markdown files, the Skill examines YAML metadata, argument usage, dynamic context loading, and tool restrictions to identify defects and report structured findings with file:line locations for remediation.

Security checks for custom slash commands include verifying YAML compliance, validating argument references, enforcing tool restrictions to prevent unsafe operations, and detecting prompt injection patterns across typical plugin workflows.

Validating YAML metadata and argument usage involves checking command structure, confirming required parameters and references, and enforcing evaluation criteria to ensure command files meet safety and quality standards before publishing.

Yes, you can review dynamic context loading and tool restrictions by verifying state-aware prompts, checking environment configurations, and enforcing tool restriction rules to prevent unsafe operations within the command file.

The best way to find defects in slash command configurations is to run a comprehensive audit that examines command structure, context usage, and security patterns, then outputs structured findings with file:line locations to facilitate remediation.

Slash commands fail safety and quality standards due to non-compliant YAML metadata, missing argument validations, improper dynamic context loading, or unenforced tool restrictions that allow unsafe operations or ambiguous prompts.