agent-sort

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

Updated Jan 30, 2026

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

Ready to run

npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill agent-sort-thejanajayalath

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/ThejanaJayalath/Niolla-PM-system/tree/main/.cursor/.agents/skills/agent-sort
Command: npx skills add https://github.com/ThejanaJayalath/Niolla-PM-system --skill agent-sort-thejanajayalath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of bloated, generic environment configurations by creating a project-specific, evidence-backed install plan for ECC components.

Core Features & Use Cases

Evidence-Based Classification: Sorts skills, rules, and hooks into DAILY or LIBRARY buckets based on actual repository contents like lockfiles and framework configs.
Automated Install Planning: Generates a clear, actionable plan to trim unnecessary surfaces and keep only what the project requires.
Use Case: When starting work on a new repository, use this skill to automatically determine which rules and hooks are relevant to the current tech stack, ensuring a clean and performant workspace.

Quick Start

Use the agent-sort skill to analyze the current repository and generate an evidence-backed ECC install plan.

Frequently Asked Questions about agent-sort

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

FAQPage Schema

How do I optimize environment configuration for a new repository?▼

To optimize environment configuration, you can classify ECC components into DAILY and LIBRARY buckets based on actual repository contents like lockfiles and framework configs. This generates an evidence-backed install plan that trims unnecessary surfaces, keeping only what the project requires.

What is evidence-based ECC component classification?▼

Evidence-based ECC component classification is the process of sorting skills, rules, and hooks into DAILY or LIBRARY buckets. It verifies language, framework, and dependency manifests within a repository to ensure a clean and performant workspace tailored to the current tech stack.

Do I need repository-level file access to generate an ECC install plan?▼

Yes, you need repository-level file access to generate an ECC install plan. The classification process requires access to verify language, framework, and dependency manifests, ensuring the resulting DAILY and LIBRARY buckets accurately reflect the project's specific tech stack.

When should I automate ECC component sorting for project initialization?▼

You should automate ECC component sorting during project initialization and environment cleanup tasks. It is specifically designed for situations where context-loading must be optimized by eliminating bloated, generic configurations in favor of a project-specific setup.

How does automated install planning handle bloated generic configurations?▼

Automated install planning handles bloated generic configurations by analyzing repository-specific evidence to create a targeted setup. It automatically determines which rules and hooks are relevant to the current tech stack, generating an actionable plan to trim unnecessary surfaces.