Agent skill · software engineering · affaan-m
agent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Why this skill is useful
Adds a structured process for classifying and installing ECC components based on specific repo evidence, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Agent Sort 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. When to Use 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 Non-Negotiable Rules 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 Outputs 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 Classification Model Use two buckets only: DAILY should load every session for this repo strongly matched to the repo's language, framework, workflow, or operator surface LIBRARY useful to retain, but not worth loading by default should remain reachable through search, router skill, or selective manual use Evidence Sources Use repo-local evidence before making any classification: file extensions package managers and lockfiles framework configs CI and hook configs build/test scripts imports and dependency manifests repo docs that explicitly describe the stack Useful commands include: Parallel Review Passes If parallel subagents are available, split the review into these passes: 1. Agents classify agents/ 2. Skills classify skills/ 3. Commands classify commands/ 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/agent-sort--000165