agent-sort

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

Updated Apr 6, 2026

Search Tags:#repository analysis #ecc #skill classification #install plan #codebase evidence

Ready to run

npx skills add https://github.com/thangvawn/agent_financial --skill agent-sort-thangvawn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/thangvawn/agent_financial/tree/main/.cursor/.agents/skills/agent-sort
Command: npx skills add https://github.com/thangvawn/agent_financial --skill agent-sort-thangvawn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of selecting the right components for an ECC (Enhanced Component Collection) install by sorting them into DAILY and LIBRARY buckets based on evidence from the repository.

Core Features & Use Cases

Evidence-Based Sorting: Classifies ECC components into DAILY (always loaded) and LIBRARY (searchable) based on repository evidence.
Repo-Aware Review: Uses repository-specific data to make informed decisions about component usage.
Use Case: When a project requires a customized ECC install that aligns with its specific needs and usage patterns.

Quick Start

Run the agent-sort skill to generate a tailored ECC install plan for your project.

Frequently Asked Questions about agent-sort

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

FAQPage Schema

How do I sort repository components into daily and library buckets?▼

To sort repository components into daily and library buckets, analyze repository evidence like file extensions, package managers, and framework configurations to classify ECC components into DAILY or LIBRARY categories for a customized install plan.

What is evidence-based component classification for an install plan?▼

Evidence-based component classification is a sorting method that categorizes ECC components into DAILY and LIBRARY buckets by analyzing repository-specific data, ensuring the install plan aligns with the project's specific usage patterns.

How do I customize an ECC install plan based on repository analysis?▼

You customize an ECC install plan by running a repository analysis that extracts evidence from file extensions and framework configurations, sorting components into DAILY or LIBRARY buckets to match your project needs.

Can I use repository evidence to decide which components to always load?▼

Yes, you can use repository evidence such as package manager configurations and file extensions to decide which components are classified as DAILY for always loading versus LIBRARY for searchable access.

What do I need to generate a tailored ECC install plan?▼

To generate a tailored ECC install plan, you need a repository containing evidence such as file extensions, package managers, and framework configurations to inform the sorting of components into DAILY and LIBRARY buckets.

Are there limitations to classifying components using repository evidence?▼

Classifying components using repository evidence is limited to the accuracy of the detected file extensions, package managers, and framework configurations, meaning incomplete repository data may result in an inaccurate DAILY versus LIBRARY sorting.