Agent Sort

This does one thing well: it looks at your actual repo and decides which ECC components you need loaded daily versus tucked away in a searchable library. Instead of guessing or manually curating, it greps for evidence like file extensions, package managers, framework configs, and build scripts, then classifies skills, rules, hooks, and commands into DAILY or LIBRARY buckets. The parallel review passes are clean if you have subagents available. Use it when full ECC installs are too noisy for a focused project, or when a repo has drifted into the wrong language ruleset. The evidence table format keeps decisions auditable instead of vibes based.

skills.sh installs: 3.6K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill agent-sort --agent claude-code

Installs into .claude/skills of the current project.

Files

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