New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Agent Sort

by affaan-m in affaan-m/ECC

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.

MITAuto-check passed

Install Agent Sort

skills CLI
$ npx skills add affaan-m/ECC --skill agent-sort -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC agent-sort --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-sort .claude/skills/agent-sort && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-sort
GitHub stars
276k
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
667 words
Files
1
Skills in repo
673
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 6 steps: Read the repo → Build the evidence table → Decide DAILY vs LIBRARY → …
  • ECC should be trimmed to what a project actually needs instead of loading the full bundle
  • SKILL.md covers When to Use, Non-Negotiable Rules, Outputs and Classification Model, plus 5 more sections
  • Calls rg, supabase and flutter

What it does

Agent Sort is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • ECC should be trimmed to what a project actually needs instead of loading the full bundle

Example prompts

  • “/agent-sort”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit ef648e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • rg
    • supabase
    • flutter

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use supabase, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Sort loads about 1.5k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 667 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit ef648e0, republished under its MIT licence (© affaan-m). 667 words, ~1,481 tokens.

Download SKILL.mdSave it as .claude/skills/agent-sort/SKILL.md (or your agent's skills folder).
name
agent-sort
description
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.
metadata.origin
ECC

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:

bash
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

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. Rules
    • classify rules/*
  5. Hooks and scripts
    • classify hook surfaces, MCP health checks, helper scripts, and OS compatibility
  6. Extras
    • classify contexts, examples, MCP configs, templates, and guidance docs

If subagents are not available, run the same passes sequentially.

Core Workflow

1. Read the repo

Establish the real stack before classifying anything:

  • languages in use
  • frameworks in use
  • primary package manager
  • test stack
  • lint/format stack
  • deployment/runtime surface
  • operator integrations already present
2. Build the evidence table

For every candidate surface, record:

  • component path
  • component type
  • proposed bucket
  • repo evidence
  • short justification

Use this format:

text
skills/frontend-patterns | skill | DAILY | 84 .tsx files, next.config.ts present | core frontend stack
skills/django-patterns   | skill | LIBRARY | no .py files, no pyproject.toml       | not active in this repo
rules/typescript/*       | rules | DAILY | package.json + tsconfig.json            | active TS repo
rules/python/*           | rules | LIBRARY | zero Python source files             | keep accessible only
Show full SKILL.md (265 more words)Show less
3. Decide DAILY vs LIBRARY

Promote to DAILY when:

  • the repo clearly uses the matching stack
  • the component is general enough to help every session
  • the repo already depends on the corresponding runtime or workflow

Demote to LIBRARY when:

  • the component is off-stack
  • the repo might need it later, but not every day
  • it adds context overhead without immediate relevance
4. Build the install plan

Translate the classification into action:

  • DAILY skills -> install or keep in .claude/skills/
  • DAILY commands -> keep as explicit shims only if still useful
  • DAILY rules -> install only matching language sets
  • DAILY hooks/scripts -> keep only compatible ones
  • LIBRARY surfaces -> keep accessible through search or skill-library

If the repo already uses selective installs, update that plan instead of creating another system.

5. Create the optional library router

If the project wants a searchable library surface, create:

  • .claude/skills/skill-library/SKILL.md

That router should contain:

  • a short explanation of DAILY vs LIBRARY
  • grouped trigger keywords
  • where the library references live

Do not duplicate every skill body inside the router.

6. Verify the result

After the plan is applied, verify:

  • every DAILY file exists where expected
  • stale language rules were not left active
  • incompatible hooks were not installed
  • the resulting install actually matches the repo stack

Return a compact report with:

  • DAILY count
  • LIBRARY count
  • removed stale surfaces
  • open questions

Handoffs

If the next step is interactive installation or repair, hand off to:

  • configure-ecc

If the next step is overlap cleanup or catalog review, hand off to:

  • skill-stocktake

If the next step is broader context trimming, hand off to:

  • strategic-compact

Output Format

Return the result in this order:

text
STACK
- language/framework/runtime summary

DAILY
- always-loaded items with evidence

LIBRARY
- searchable/reference items with evidence

INSTALL PLAN
- what should be installed, removed, or routed

VERIFICATION
- checks run and remaining gaps

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/agent-sort of affaan-m/ECC.

Open the folder on GitHubat commit ef648e0

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Sort next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Sort compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Sort this skillaffaan-m/ECC276k1 repos~1.5kAutomated safety check: PassMIT
Sortedglebis/claude-skills390—~2kAutomated safety check: PassMIT
Card Sort AnalysisOwl-Listener/designer-skills2.9k1 repos~287Automated safety check: PassMIT
Sorting Parameter Handlerjeremylongshore/tons-of-skills-marketplace2.8k—~575Automated safety check: PassMIT
Configure Eccxu-xiang/everything-claude-code-zh2k1 repos~2.1kAutomated safety check: PassMIT
Configure Eccxu-xiang/everything-claude-code-zh2k—~1.8kAutomated safety check: PassMIT

Similar skills

  • Sorted

    glebis/claude-skills

    Automate getSorted.de (Sorted) for freelancer invoicing, expense tracking, and German tax submissions (VAT, ZM, annual returns).

    390 GitHub stars~2k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed

  • Card Sort Analysis

    Owl-Listener/designer-skills

    Analyse open or closed card sort results into a proposed grouping and label set.

    2.9k GitHub starsUsed in 1 repo~287 tokens
    Frontend & DesignAuto-check passed

  • Sorting Parameter Handler

    jeremylongshore/tons-of-skills-marketplace

    Manage sorting parameter handler operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~575 tokensUpdated today
    Backend & APIsAuto-check passed

  • Configure Ecc

    xu-xiang/everything-claude-code-zh

    Everything Claude Code 的交互式安装程序 — 引导用户选择并安装技能和规则到用户级或项目级目录，验证路径，并可选择优化已安装文件。

    2k GitHub starsUsed in 1 repo~2.1k tokens
    Backend & APIsAuto-check passed

  • Configure Ecc

    xu-xiang/everything-claude-code-zh

    Everything Claude Code 的交互式安装程序 —— 引导用户将技能（Skills）和规则（Rules）安装到用户级或项目级目录，验证路径，并在需要时优化已安装的文件。

    2k GitHub stars~1.8k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed

  • Configure Ecc

    xu-xiang/everything-claude-code-zh

    Everything Claude Code 的交互式安装程序 —— 引导用户选择并将技能（Skills）和规则（Rules）安装到用户级或项目级目录，验证路径，并可选地优化已安装的文件。

    2k GitHub stars~2k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed

More from affaan-m/ECC

All 673 skills in this repo

  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    276k GitHub starsUsed in 5 repos~1.9k tokens
    Auto-check passed

  • VideoDB Video Search and Editing

    affaan-m/ECC

    Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    276k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes

  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    276k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed

  • Master Agreement Generator

    affaan-m/ECC

    Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    276k GitHub stars~2.9k tokensUpdated 4 days ago
    Auto-check passed

  • Skill Compliance Checker

    affaan-m/ECC

    Measures whether agents actually follow a skill, rule or agent definition by generating scenarios at three strictness levels and scoring tool-call traces.

    276k GitHub starsUsed in 1 repo~623 tokens
    Auto-check passed

  • Continuous Learning V2

    affaan-m/ECC

    Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

    276k GitHub stars~3.5k tokensUpdated 4 days ago
    Auto-check passed

Questions about Agent Sort

What does Agent Sort 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. Agent Sort is an agent skill from affaan-m/ECC. 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.

When should I use Agent Sort?

Agent Sort fits situations like: ECC should be trimmed to what a project actually needs instead of loading the full bundle.

How do I install Agent Sort in Claude Code?

Run `npx skills add affaan-m/ECC --skill agent-sort -a claude-code`. Or copy the skill folder (skills/agent-sort in affaan-m/ECC) into .claude/skills/agent-sort in your project. Claude Code loads it when a task matches its description.

How do I install Agent Sort in Codex?

Run `npx skills add affaan-m/ECC --skill agent-sort -a codex`. Or copy the skill folder (skills/agent-sort in affaan-m/ECC) into .agents/skills/agent-sort in your project. Codex loads it when a task matches its description.

Can I use Agent Sort in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill agent-sort -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-sort, .gemini/skills/agent-sort, .github/skills/agent-sort and .opencode/skills/agent-sort in your project.

What does Agent Sort need to run?

Going by SKILL.md and its folder, Agent Sort needs the command-line tools its instructions call (rg, supabase and flutter). Our summary lists: Python 3.

Does Agent Sort access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Sort safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Sort use?

Agent Sort is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Sort use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Sort?

Skills that share tags, products or a category with Agent Sort: Sorted (glebis/claude-skills, 390 stars), Card Sort Analysis (Owl-Listener/designer-skills, 2.9k stars), Sorting Parameter Handler (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Configure Ecc (xu-xiang/everything-claude-code-zh, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Sort?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 275,546 GitHub stars. The repository holds 673 skills in this directory. The repository was last updated on October 5, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.