Overview

Gate skill quality automatically and define your organisation's standard for what a good skill looks like.

Takeaway Keep poor-quality skills out of your repository. Set the bar for what "good" means, then gate it in CI so skills that fall short do not get merged.

When a team shares skills, quality stops being a personal matter. A weak skill that one person tolerates becomes everyone's problem once it is in the shared repository, shaping how every agent on the team behaves. This section is about holding a quality line automatically, so you do not depend on everyone remembering to check.

There are two parts to it:

• Gate on a review score. Run a review in CI and fail the build when a skill scores below your bar, so substandard skills never merge. See Gate skill quality in CI.
• Define your own bar. The default rubric scores against general best practices. Fork it to encode what your organisation cares about, and apply it to every review. See Define your own quality standards.

This section covers protecting a repository from low-quality skills. It does not cover managing your wider skill estate, surveying what is installed across your organisation, or org-level policy; those are separate capabilities.

Next

• Gate skill quality in CI - run reviews on pull requests and block merges below your threshold.
• Define your own quality standards - build a custom rubric and apply it to every review.