skills.rest
inuishan
inuishanCOMMUNITY
Explore all skills by this author →
GitHub

agent-sort

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

Updated Apr 7, 2026
Search Tags:#skill management#classification#ecc#repo analysis#context trimming#install plan
One-click install
npx skills add https://github.com/inuishan/mac-storage-organiser --skill agent-sort-inuishan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/inuishan/mac-storage-organiser/tree/main/.codex/skills/agent-sort
Command: npx skills add https://github.com/inuishan/mac-storage-organiser --skill agent-sort-inuishan

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 surfaces. This Skill builds an evidence-backed install plan so a repo only loads the ECC components matched to its real stack. ## Core Features & Use Cases - Evidence-Based Classification: Greps the repo for file extensions, lockfiles, framework configs, and dependency manifests to justify every DAILY vs LIBRARY decision. - Parallel Review Passes: Splits classification across agents, skills, commands, rules, hooks, and extras when subagents are available. - Install Plan and Verification: Produces a DAILY inventory, LIBRARY inventory, install plan, and verification report, plus an optional skill-library router. - Use Case: A TypeScript/Next.js repo with a full ECC install runs this Skill to keep TypeScript rules and frontend skills loaded daily while demoting Python and Django surfaces to a searchable library. ## Quick Start Analyze this repository and sort the ECC components into DAILY and LIBRARY buckets with an install plan based on the actual stack.

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 classification workflow to inspect your repo's languages, frameworks, and package managers, then sort each ECC component into DAILY or LIBRARY buckets. The result is an install plan that keeps only stack-matched surfaces loaded by default.

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.

What evidence is used to classify ECC components?▼

Classification relies on repo-local evidence such as file extensions, lockfiles, framework configs, CI and hook configs, build scripts, and dependency manifests. Every DAILY decision must cite concrete evidence from the current repository.

Can the classification run in parallel with subagents?▼

Yes, the review can be split into parallel passes covering agents, skills, commands, rules, hooks and scripts, and extras. If subagents are unavailable, the same passes run sequentially with identical results.

Does LIBRARY classification delete unused ECC components?▼

No, LIBRARY means the component remains installed and reachable through search or a skill-library router, just not loaded by default. Nothing is deleted; the goal is reducing default context load, not removing capability.

Related Skills

Explore More Software Engineering Skills→
arbisoftarbisoft
4

agent-sort

Classify ECC components into DAILY and LIBRARY buckets with repository evidence.

Official
Advanced
mirzadhammirzadham

agent-sort

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

Community
Intermediate
zero3041zero3041
1

automation-audit-ops

Audit ECC automation inventory and classify components as live, broken, redundant, or missing.

Community
Advanced
himanshu231204himanshu231204
2

agent-sort

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

Community
Intermediate