Guide · Agent skill
How to use the Agent Sort agent skill: install and run it
Updated · written with AI from the project's own documentation and checked against our catalogue data
Agent Sort is an agent skill from the ECC (Everything Claude Code) repository. It inspects a code repository and sorts ECC components into two groups: DAILY items that load every session and LIBRARY items that stay available but are not loaded by default. This guide explains what the skill does, how to install it, how to ask for it, and what to check before applying its changes.
Agent Sortaffaan-m/ECC · MIT Download the skill Quick start
- 1Get the ZIP. Download the agent-sort ZIP from this page.
- 2Unzip the skill. Unzip the folder so that it contains SKILL.md and agents/openai.yaml.
- 3Place it in a skills folder. Move the folder to ~/.claude/skills/ for personal use or to a project's .claude/skills/ folder for one repo.
- 4Make sure ECC is available. The skill needs the ECC repository as the source of the components it sorts.
- 5Ask for a sort in plain language. Describe that you want ECC trimmed to what the project needs, naming the repo.
- 6Review the output. Read the DAILY and LIBRARY inventories, the install plan and the verification report before changing any files.
What an agent skill is and what Agent Sort makes the agent do
An agent skill is a folder containing a SKILL.md file that tells an AI agent how to handle a particular task. When the skill is installed and a request matches its description, the agent follows its instructions.
Agent Sort is aimed at teams and developers who find the full ECC bundle too noisy for the project they are working on. The agent reads the repository, including its files, package manifests, configs and CI setup, and classifies ECC agents, skills, commands, rules, hooks and extras. The stated goal is to base each decision on evidence from the codebase rather than guesses, using items such as file counts, lockfiles and imports.
- DAILY: items that should load every session for this repo.
- LIBRARY: items kept accessible but not loaded by default. The skill says LIBRARY does not mean delete.
- Outputs: a DAILY inventory, a LIBRARY inventory, an install plan, a verification report, and optionally a searchable skill-library router skill.
Install the agent-sort skill
Download the ZIP for the skill from this page and unzip it. To make it available to Claude Code for all your projects, place the unzipped folder in ~/.claude/skills/. To use it only in one project, place it in that project's .claude/skills/ folder.
If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside the repository
- Claude apps: Settings → Capabilities → Skills
~/.claude/skills/Prerequisites: the ECC repository and shell tools
The skill sorts components from the ECC (Everything Claude Code) repository, so that repository must be available as the source of the components being classified. The instructions reference shell tools such as rg (ripgrep) and cat for gathering evidence.
Subagent support is optional. If parallel subagents are available, the review can be split into passes for agents, skills, commands, rules, hooks and scripts, and extras. If not, the same passes run one after another.
- ECC (Everything Claude Code) repository as the source of components
- Shell tools such as rg and cat
- Optional: subagent support for parallel review passes
Trigger the skill with a natural request
The skill is meant to be used when ECC should be trimmed to what a project actually needs instead of loading the full bundle. You do not need a special command. Describe that goal in plain language, and the agent can match it to the skill's description.
Good requests name the repo and the outcome you want, for example asking for a DAILY vs LIBRARY split of ECC for a specific project. Mention if you want a searchable router skill, since the skill can create one as an optional output.
- "Sort the ECC components for this repo into DAILY and LIBRARY so I only load what this project uses."
- "Build an evidence-backed ECC install plan for this repo and tell me what to keep loaded."
- "Trim ECC to this project's stack and create a skill-library router for the rest."
What to review before applying the plan
The skill proposes changes to installed files and hooks. The source warns that these changes should be checked before they are applied, so treat the output as a proposal rather than a finished configuration. The skill also states that it runs no scripts and uses no network access.
The skill's own rules say hooks, rules or scripts that the current repo cannot use should not be installed, and that ECC-native surfaces should be preferred over introducing a second install system. Its verification step checks that DAILY files exist where expected, stale language rules were removed, and incompatible hooks were not installed.
- Do not run it unreviewed on production repos.
- Check the DAILY evidence table against the repo yourself.
- Confirm the verification report lists the remaining open questions before you apply changes.
What people use it for
- Keeping only the language rules that match a TypeScript or Python project instead of loading every rule set.
- Cleaning up a repo that has picked up the wrong language rules or hooks.
- Producing a repeatable install decision for a team, backed by repo evidence instead of opinion.
- Creating a searchable skill-library router so that LIBRARY items stay reachable without loading by default.
Frequently asked questions
Is the agent-sort skill free to use?
The skill is listed under the MIT licence. The source does not mention pricing for the skill itself, so check the ECC repository for any terms that apply to its components.
Where do I put the agent-sort folder to install it?
Place the unzipped folder in ~/.claude/skills/ to use it across projects, or in a project's .claude/skills/ folder to use it in one repo. In the Claude apps, upload it under Settings → Capabilities → Skills.
What does agent-sort need to run?
It needs the ECC (Everything Claude Code) repository as the source of the components being sorted, plus shell tools such as rg (ripgrep) and cat as referenced in its instructions. Subagent support is optional and only used for parallel review passes.
Does agent-sort delete ECC components?
No. The skill states that LIBRARY does not mean delete. LIBRARY items remain accessible through search or a router skill but are not loaded by default.
Is agent-sort safe to run on a production repo?
The skill proposes changes to installed files and hooks, so the source advises checking them before applying. Review the proposed plan on a copy or in a non-production repo first.
Who should not use agent-sort?
People who want to install the whole ECC bundle as-is should not use it, since the skill is designed to trim the bundle. Non-developers, and repos with no clear stack, may get weak results because classification depends on reading the codebase.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Agent Sort suits developers and teams whose projects use only part of the ECC toolkit and who want a repeatable, evidence-based install decision. It is a poor fit if you want the full ECC bundle unchanged, or if your repo has no clear stack. Review every proposed change to installed files and hooks before applying it.
Download the skill