agent-sort

Topics in the source

• Agent Sort
• When to Use
• Non-Negotiable Rules
• Outputs
• Classification Model
• Evidence Sources
• Parallel Review Passes
• Core Workflow

Use this skill when a repo needs a project-specific ECC surface instead of the default full install. The goal is not to guess what "feels useful." The goal is to classify ECC components with evidence from the actual codebase. A project only needs a subset of ECC and full installs are too noisy The repo stack is clear, but nobody wants to hand-curate skills one by one A team wants a repeatable install decision backed by grep evidence instead of opinion You need to separate always-loaded daily workflow surfaces from searchable library/reference surfaces A repo has drifted into the wrong language, rule, or hook set and needs cleanup Use the current repository as the source of truth, not generic preferences Every DAILY decision must cite concrete repo evidence LIBRARY does not mean "delete"; it means "keep accessible without loading by default" Do not install hooks, rules, or scripts that the current repo cannot use Prefer ECC-native surfaces; do not introduce a second install system Produce these artifacts in order: 1. DAILY inventory 2. LIBRARY inventory 3. install plan 4. verification report 5. optional skill-library router if the project wants one Use two buckets only: DAILY should

This is an excerpt. Refer to the complete source and its current requirements.