audit-skill-type

To determine if a marketplace plugin should be a skill or a command, analyze its SKILL.md file to count workflow steps, evaluate allowed-tools, assess context needs, and score output complexity.

The difference between a skill and a command involves workflow depth; skills require richer context and multi-step processing, while commands are lightweight executables suited for simpler output complexity and fewer tool requirements.

You audit plugin SKILL.md files by globbing the plugins directory to parse YAML frontmatter, evaluating bundled resources, and generating a recommendation table with confidence levels for each item.

Metrics used to evaluate whether a plugin needs richer context include the count of workflow steps, the allowed-tools specified, output complexity, and the presence of bundled resources within the SKILL.md metadata.

Yes, you can automate the classification of marketplace items by systematically reading every SKILL.md to apply signal-based evaluation, producing actionable recommendations for maintainers and marketplace curators.

You should not use a skill classification when a plugin lacks multi-step workflows, requires minimal allowed-tools, or produces low output complexity, indicating a lightweight command is the appropriate implementation.