agent-sort

Classifies ECC components into DAILY and LIBRARY buckets using repo evidence.

Updated May 7, 2026
One-click install
npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill agent-sort-mirzadham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/mirzadham/trainingroombookingsystem2/tree/main/.agent/.agents/skills/agent-sort
Command: npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill agent-sort-mirzadham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Full ECC installs load every skill, rule, and hook regardless of what a project actually uses, creating noisy context and stale configurations. This Skill builds an evidence-backed install plan so a repo only loads the components that match its real stack. ## Core Features & Use Cases - Evidence-Based Classification: Sorts skills, commands, rules, hooks, and extras into DAILY (always loaded) or LIBRARY (searchable on demand) buckets, with every DAILY decision citing concrete repo evidence such as file extensions, lockfiles, and framework configs. - Parallel Review Passes: Splits the audit into six passes (agents, skills, commands, rules, hooks/scripts, extras) that can run as parallel subagents or sequentially. - Install Plan and Verification: Produces a DAILY inventory, LIBRARY inventory, install plan, and verification report, plus an optional skill-library router for searchable access to demoted components. - Use Case: A TypeScript/Next.js repo inherited the full ECC bundle including Python and Django rules. Run this Skill to demote off-stack surfaces to LIBRARY, keep TypeScript rules in DAILY, and verify no incompatible hooks remain installed. ## Quick Start Use agent-sort to audit this repository and produce a DAILY versus LIBRARY install plan for the ECC components.

Frequently Asked Questions about agent-sort

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trim an ECC install to match my project's stack?▼

Run the agent-sort workflow against your repository. It reads file extensions, lockfiles, and framework configs, then classifies each ECC component as DAILY or LIBRARY and outputs an install plan with evidence for every decision.

What is the difference between DAILY and LIBRARY buckets?▼

DAILY components load every session because they match the repo's active language, framework, or workflow. LIBRARY components stay accessible through search or a router skill but are not loaded by default, reducing context overhead.

Does agent-sort delete components that are not needed?▼

No. Demoting a component to LIBRARY keeps it accessible through search or the optional skill-library router. The skill explicitly states LIBRARY does not mean delete, only that the component is not loaded by default.

What repo evidence does the classification use?▼

Classification relies on file extensions, package managers and lockfiles, framework configs, CI and hook configs, build and test scripts, dependency manifests, and repo documentation describing the stack.

Can the review passes run in parallel?▼

Yes. If parallel subagents are available, the six review passes (agents, skills, commands, rules, hooks/scripts, extras) run concurrently. Without subagents, the same passes execute sequentially with identical results.

When should I not use agent-sort?▼

Skip it when a project genuinely needs the full ECC bundle or when the repo stack is still undecided. For interactive installation or repair after classification, hand off to configure-ecc instead.