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.
npx skills add mturac/everything-openai-codex --skill agent-sort --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. option
- When to Use
- Non-Negotiable Rules
- Outputs
- Classification Model
- Evidence Sources
- Parallel Review Passes
- Core Workflow
- 1. Read the repo
- 2. Build the evidence table
- 3. Decide DAILY vs LIBRARY
- 4. Build the install plan
- 5. Create the optional library router
- 6. Verify the result
- Handoffs
rg --files rg -n "typescript|react|next|supabase|django|spring|flutter|swift" cat package.json cat pyproject.toml cat Cargo.toml cat pubspec.yaml cat go.mod
What does the agent-sort skill do?
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.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill agent-sort --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.