to-skill-or-not-to-skill

To decide if you need a new automation skill, apply a formal 13-point decision tree evaluating triggers, context, and alternatives. This checklist determines whether to proceed with skill creation, reformulate the request, or use a simpler workflow rule instead.

The go-no-go decision process for skill creation is a formal 13-point checklist that evaluates requested capabilities across specific discriminants. It outputs a structured verdict of Go, Reformuler, or Pas de skill based on official evaluation methods.

You should not create a skill when the decision tree verdict is negative, in which case the process outputs an actionable alternative. This alternative provides a concrete rule, instruction, guide, or runbook to address your documentation needs without a new skill.

You validate a skill-creation request by running it through a multi-step decision tree loaded from official truth sources. This evaluation method checks specific discriminants to ensure the requested capability genuinely warrants a new skill.

The criteria used to evaluate whether a capability needs a skill involve a 13-point decision checklist. It assesses the request across formal discriminants derived from official decision-tree documentation to output a structured Go or No-Go verdict.