artifact-advisor

Choosing the right artifact type depends on invocation pattern, complexity, and automation level. This Skill provides a decision framework with clarifying questions, scoring criteria, and anti-pattern checks to guide you to the optimal artifact—whether automatic detection, explicit triggering, event-driven, or isolated reasoning—based on your specific workflow requirements.

Artifact selection for code reviews and deployment pipelines depends on whether you need automatic event-triggered execution (Hook), explicit user invocation (Command or Skill), or isolated complex reasoning (Subagent). This Skill evaluates your workflow pattern against each artifact's strengths to recommend the optimal choice with justification.

A Skill suits user-triggered, frequently-reused analysis workflows, while a Command handles simpler, one-off executions. This Skill analyzes your task's complexity, reusability, and invocation frequency to recommend whether a Skill, Command, Subagent, or Hook best fits your data analysis needs.

Yes. This Skill applies its decision framework—clarifying questions, requirement analysis, and anti-pattern detection—to evaluate existing workflows and recommend whether refactoring to a different artifact type (Skill, Command, Subagent, or Hook) would improve automation effectiveness and design coherence.

Hooks trigger automatically on events with lightweight, scoped logic; Subagents handle complex, isolated reasoning tasks triggered explicitly or by events. This Skill compares these and other artifact types across invocation patterns, complexity scope, and automation context to clarify when each excels.