Verified:GitHub

agent-sort

Sort ECC components into DAILY versus LIBRARY buckets using repository evidence.

Updated Sep 13, 2025

Search Tags:#skill installation #ecc #repository audit #verification plan #evidence-based classification #daily vs library #hook filtering

Ready to run

npx skills add https://github.com/llmh333/employee_management_spring --skill agent-sort-llmh333

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/agent-sort
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill agent-sort-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of installing an oversized, noisy ECC set by producing a repo-specific evidence-backed split of DAILY vs LIBRARY components.

Core Features & Use Cases

Evidence-backed classification: sorts skills, commands, rules, hooks, and extras by directly inspecting the target repository rather than using generic preferences.
Daily vs searchable library surfaces: defines what should load every session (DAILY) versus what should remain available without default load (LIBRARY).
Repeatable install planning and verification: generates an install plan and a compact verification report to confirm the result matches the repo stack.

Quick Start

Use agent-sort for your repository when you want ECC trimmed to only the components supported by the codebase, based on grep and file-structure evidence.

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 oversized skill and commands installation for a specific repository?▼

Sort ECC components into DAILY versus LIBRARY buckets using evidence-based classification from direct repository inspection, then generate an install plan to trim your skill and commands set to only what your codebase supports.

What is evidence-based classification for daily vs library component sorting?▼

Evidence-based classification for daily vs library component sorting means inspecting the target repository's actual file structure and grep results to decide what loads every session versus what remains available without default load, replacing generic heuristics.

How do I plan a lean ECC install using repository-local evidence?▼

Plan a lean ECC install by performing parallel or sequential review passes to build an evidence table from repo-local inspection, then generate an install plan with a verification report confirming the trimmed component surface matches your stack.

Can I use hook filtering to reduce command surface for my project?▼

Yes, you can filter hooks alongside skills, commands, rules, and extras to reduce your command surface, sorting them into DAILY or LIBRARY buckets based on actual project needs rather than installing the full default set.

When should I run a repository audit for ECC component cleanup?▼

Run a repository audit for ECC component cleanup when your project needs a smaller, correct surface and you want to avoid installing an oversized, noisy set of skills, commands, rules, and hooks that do not match your codebase.

Does agent-sort work without generic heuristics for skill installation?▼

Agent-sort works without generic heuristics by requiring an evidence table from repo-local inspection, applying review passes to classify components, and outputting an install plan with a verification report to ensure correct defaults for your specific repository.