agent-sort

Classify and rank ECC install components using codebase evidence.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/ldk-hub/broke-shopping --skill agent-sort-ldk-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/ldk-hub/broke-shopping/tree/main/.agent/.agents/skills/agent-sort
Command: npx skills add https://github.com/ldk-hub/broke-shopping --skill agent-sort-ldk-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sorts and prioritizes ECC install components for a repository by collecting evidence from the codebase, enabling lean, project-specific deployments.

Core Features & Use Cases

  • Evidence-driven classification of agents, skills, commands, rules, hooks, and extras based on actual repo signals.
  • Parallel review passes that separate DAILY workflow surfaces from LIBRARY/reference surfaces.
  • Generates an install plan that trims unnecessary components while preserving essential capabilities.
  • Validates decisions against the repository structure to prevent drift.

Quick Start

Run the agent-sort skill against your repository to produce daily and library ECC surfaces guided by codebase evidence.

Frequently Asked Questions about agent-sort

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

FAQPage Schema
How do I classify repository components for an install plan using codebase evidence?

To classify repository components for an install plan using codebase evidence, run parallel review passes against your stack to separate DAILY workflow surfaces from LIBRARY reference surfaces. This generates a rejection-safe install plan that trims unnecessary components while preserving essential capabilities.

What is the best way to trim ECC install components to what a repository actually needs?

Trimming ECC install components to what a repository actually needs involves applying evidence-driven classification across agents, skills, commands, rules, hooks, and extras based on actual repo signals. This approach prioritizes project-specific deployments and prevents drift by validating decisions against the repository structure.

How do I separate daily workflow surfaces from library surfaces in my repository?

Separate daily workflow surfaces from library surfaces by performing parallel review passes that rank ECC install components according to concrete codebase evidence. This distinguishes active project stack requirements from reference-only materials.

Does evidence-driven repository classification validate install plans against the project structure?

Evidence-driven repository classification validates install plans against the project structure to prevent configuration drift. It ranks ECC install components using concrete codebase evidence, ensuring the final deployment is lean and project-specific.

Why does my repository install plan include unnecessary components and how can I generate a rejection-safe one?

A repository install plan includes unnecessary components when it lacks evidence-driven classification. Generate a rejection-safe install plan by collecting concrete codebase evidence to separate DAILY surfaces from LIBRARY surfaces, validating all decisions against the repository structure.