agent-sort

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill agent-sort-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/.agents/skills/agent-sort
Command: npx skills add https://github.com/luongldptit/move-ticket --skill agent-sort-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Default full ECC installs often include irrelevant components that add noise and context overhead to repository workflows, and hand-curating a project-specific ECC set is tedious and subjective. This Skill solves that by classifying all ECC components using concrete evidence from the actual codebase, ensuring only relevant components are loaded by default.

Core Features & Use Cases

  • Evidence-Based Classification: Sorts ECC skills, commands, rules, hooks, scripts, and extras into DAILY (always loaded) and LIBRARY (searchable reference) buckets using repo-local data like file extensions, lockfiles, framework configs, and dependency manifests.
  • Flexible Review Workflow: Supports both parallel subagent passes and sequential review for all ECC component types, adapting to available tooling.
  • Complete Output Artifacts: Generates a full DAILY/LIBRARY inventory, actionable install plan, verification report, and optional searchable skill-library router for off-stack components.
  • Use Case: For a TypeScript Next.js repository, this Skill will promote TypeScript rules and frontend workflow skills to DAILY, demote unused Python or Django components to LIBRARY, and produce a ready-to-apply install plan that matches the repo's actual stack.

Quick Start

Use the agent-sort skill to analyze the current repository's codebase and generate an evidence-based ECC install plan that separates daily workflow components from library reference components.

Frequently Asked Questions about agent-sort

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

FAQPage Schema
How do I avoid noisy context overhead from default ECC installs in my repository?

Evidence-based ECC sorting classifies ECC components by analyzing repo-local data such as file extensions, framework configs, and dependency manifests to separate daily workflow components from searchable library reference components.

How do I generate a project-specific ECC install plan for a TypeScript Next.js repository?

To generate a project-specific ECC install plan for a TypeScript Next.js repository, analyze the codebase to promote TypeScript rules to DAILY, demote unused Python components to LIBRARY, and output a ready-to-apply stack-aligned install plan.

Does ECC component classification support parallel review passes for multiple framework configs?

Yes, ECC component classification supports parallel subagent passes alongside sequential review workflows, allowing flexible review of skills, rules, hooks, and scripts across multiple framework configs based on available tooling.

What is the best way to separate daily workflow skills from library reference components?

The best way to separate daily workflow skills from library reference components is using evidence-based classification that analyzes repository lockfiles and dependency manifests to produce a complete DAILY/LIBRARY inventory and install plan.

What output artifacts are generated when sorting ECC components for stack alignment?

Sorting ECC components for stack alignment generates a full DAILY/LIBRARY inventory, an actionable install plan, a verification report, and an optional searchable skill-library router for off-stack components.