agent-sort

Classify repository components into DAILY and LIBRARY buckets for ECC install plans.

Updated Jul 8, 2026

Search Tags:#automation #workflow #optimization #repository #classification #ecc

Ready to run

npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill agent-sort-nazrulsoftwaredev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork and bloat associated with installing full ECC (Extended Context Capability) bundles by creating a project-specific, evidence-backed install plan.

Core Features & Use Cases

Evidence-Based Classification: Uses actual repository contents like lockfiles, build scripts, and file extensions to determine which components are necessary.
Daily vs. Library Bucketing: Separates essential, always-loaded workflow surfaces from searchable, on-demand reference materials.
Use Case: A developer working on a TypeScript project can use this skill to automatically identify and install only the relevant TypeScript rules and hooks, while moving irrelevant Python or Go configurations to a searchable library.

Quick Start

Run the agent-sort skill to analyze the current repository and generate a tailored ECC install plan based on the detected project stack.

Frequently Asked Questions about agent-sort

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

FAQPage Schema

How do I optimize my repository context surface area to prevent context bloat?▼

To optimize repository context surface area, you classify components into DAILY and LIBRARY buckets. This minimizes context bloat by separating always-loaded workflow surfaces from searchable, on-demand reference materials.

What is evidence-based ECC install planning for project initialization?▼

Evidence-based ECC install planning is a method that uses actual repository contents like lockfiles and build scripts to determine necessary components. It creates a project-specific, evidence-backed install plan to eliminate guesswork.

How do I automatically identify and install only relevant TypeScript configurations?▼

You can automatically identify and install relevant TypeScript configurations by analyzing the current repository stack. This skill detects the project stack to generate a tailored install plan, moving irrelevant configurations to a searchable library.

Do I need repository-level file access to classify codebase components?▼

Yes, repository-level file access is required to classify codebase components. Access is necessary to verify language, framework, and dependency manifests for accurate classification into DAILY and LIBRARY buckets.

What's the best way to separate essential workflow surfaces from on-demand reference materials?▼

The best way to separate essential workflow surfaces from on-demand reference materials is through Daily vs. Library bucketing. This approach uses codebase evidence to categorize components, ensuring only necessary parts are actively loaded.

Why does installing full ECC bundles cause project bloat and how to avoid it?▼

Installing full ECC bundles causes project bloat by loading irrelevant configurations. Avoid it by generating a project-specific, evidence-backed install plan that classifies repository components into DAILY and LIBRARY buckets.