Skip to main content

Quality Gate

A proposed skill must pass all gates before PR.

Gate 1: Relevance​

  • Clear user problem
  • Practical and repeatable workflow
  • Suitable for AL Copilot Skill Collection

Gate 2: Clarity​

  • Scope boundaries explicitly stated
  • Step-by-step flow is unambiguous
  • Failure and fallback paths defined

Gate 3: Reusability​

  • Generic examples instead of customer data
  • No private network details
  • No organization-specific hardcoded names

Gate 4: Maintainability​

  • SKILL.md stays compact
  • Long technical content moved to references/scripts
  • File structure follows repository conventions

Gate 5: Governance​

  • Release plan entry added
  • Changelog entry included
  • Author metadata complete