skills.rest
klu-dev
klu-devCOMMUNITY
Explore all skills by this author →
GitHub

agent-sort

Classify ECC components into DAILY and LIBRARY categories using repository evidence.

2|Updated Apr 14, 2026
Search Tags:#repository organization#component classification#ecc management#project-specific setup#ecc categorization
One-click install
npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill agent-sort-klu-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/klu-dev/porting-ecc-to-vscode/tree/main/.github/skills/agent-sort
Command: npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill agent-sort-klu-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps manage the complexity of the Everything Claude Code (ECC) by classifying ECC components into DAILY and LIBRARY buckets, ensuring that only necessary components are loaded into daily workflow.

Core Features & Use Cases

  • Component Classification: Automatically categorize ECC components like skills, commands, rules, and hooks based on repository-specific evidence.
  • Selective Install: Create a project-specific ECC install plan by separating components that are always needed (DAILY) from those that are only necessary for reference (LIBRARY).
  • Use Case: Use when a project requires a tailored ECC installation that aligns with the specific language, framework, and operational needs of the repository.

Quick Start

Run the agent-sort skill within your repository to automatically generate the DAILY and LIBRARY inventories.

Frequently Asked Questions about agent-sort

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

FAQPage Schema
How do I organize ECC components for repository management?▼

ECC components are classified into DAILY and LIBRARY categories based on repository-specific evidence, ensuring only necessary components are loaded into daily workflow while reference materials remain accessible.

How do I classify project components into daily and library categories?▼

Run the classification skill within your repository to automatically evaluate codebase evidence and generate DAILY and LIBRARY inventories for your components.

When do I need to categorize ECC components for a project-specific setup?▼

You need component categorization when a project requires a tailored ECC installation aligning with specific language, framework, and operational needs, preventing unnecessary components from loading into daily workflow.

Does component classification support parallel subagent execution?▼

Yes, component classification supports parallel subagent execution or sequential pass-through to process ECC component categorization, allowing flexible execution models based on available resources.

What is the difference between DAILY and LIBRARY buckets in repository organization?▼

DAILY buckets contain components always needed in daily workflow, while LIBRARY buckets store reference-only components, ensuring optimized repository management and reduced noise.

How do I create a selective install plan for ECC components?▼

Create a selective install plan by separating ECC components into DAILY and LIBRARY inventories based on codebase evidence, ensuring only necessary components are loaded for the specific repository.

Related Skills

Explore More Software Engineering Skills→
zero3041zero3041
1

agent-sort

Classify ECC components into daily and library categories from repository evidence.

Community
Advanced
rivaldiekaptrrrrivaldiekaptrrr

agent-sort

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

Community
Advanced
ammonfifeammonfife

clawhub

Manage agent skill lifecycles with search, install, update, and publish operations.

Community
Intermediate
luongldptitluongldptit

agent-sort

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

Community
Advanced