agent-sort

Classifies ECC install components into DAILY/LIBRARY inventories and generates an evidence-backed install plan.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill agent-sort-khunglong-03
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/khunglong-03/Pathora_Version3/tree/main/.cursor/skills/agent-sort
Command: npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill agent-sort-khunglong-03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sort and classify ECC install components using repo-local evidence to minimize the active surface and tailor installs to a project's actual needs.

Core Features & Use Cases

  • Generate a DAILY inventory that reflects components actively needed for the current repo.
  • Build a LIBRARY inventory to retain searchable surfaces without loading by default.
  • Produce an install plan and verification report to enable repeatable, evidence-driven decisions.

Quick Start

Run the agent-sort skill against the target repository to produce DAILY and LIBRARY inventories and an 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 classify install components using repository evidence?▼

Classify install components by analyzing repository evidence to separate actively needed daily surfaces from accessible library references, producing a minimal, evidence-backed install plan tailored to the project.

What is the difference between daily and library surfaces in an install plan?▼

Daily surfaces are components actively needed for the current repository, while library surfaces remain searchable and accessible without loading by default, minimizing the active install footprint.

How do I generate a minimal install plan for a repository with varying stacks?▼

Generate a minimal install plan by identifying ECC-native surfaces and using concrete repository evidence to tailor the install workflow to the project's actual needs across varying stacks.

Can I use evidence-backed planning for repeatable repository reviews?▼

Yes, evidence-backed planning produces an install plan and verification report that enables repeatable, evidence-driven decisions for ongoing repository reviews.

Does the install workflow require concrete repo evidence for daily decisions?▼

Yes, daily decisions must cite concrete repository evidence to ensure the install plan accurately reflects the project's requirements without unnecessary components.