agent-sort

Sort ECC components into DAILY and LIBRARY buckets using local repository evidence.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/TymorIbrahim/UniPilot --skill agent-sort-tymoribrahim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/TymorIbrahim/UniPilot/tree/main/.cursor/.agents/skills/agent-sort
Command: npx skills add https://github.com/TymorIbrahim/UniPilot --skill agent-sort-tymoribrahim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The agent-sort skill solves the issue of determining the appropriate evidence-backed ECC (Everything Configurable) install plan for a specific repository, sorting skills, commands, rules, hooks, and extras into 'DAILY' vs 'LIBRARY' buckets for a project-specific ECC surface.

Core Features & Use Cases

  • Repository-aware Review: Utilizes evidence from the actual codebase for sorting.
  • Parallel Review Passes: Allows classification of different components like agents, skills, commands, rules, hooks, and extras in parallel passes if available.
  • Output Artifacts: Produces daily inventory, library inventory, install plan, verification report, and optional skill-library router.
  • Classification Model: Categorizes components into 'DAILY' (always loaded) or 'LIBRARY' (accessible but not loaded by default).
  • Evidence Sources: Uses local evidence from file extensions, package managers, framework configs, and CI/hook/configs.

Quick Start

Run the agent-sort skill with a specific repository to build a project-specific 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 create an evidence-based install plan for a specific codebase?

To create an evidence-based install plan, you analyze local repository evidence like file extensions, package managers, and CI configs to sort components into daily or library categories for project-specific setup.

What is repository-aware sorting for ECC components?

Repository-aware sorting classifies ECC components into daily or library buckets by analyzing local codebase evidence such as framework configs, file extensions, package managers, and CI hooks.

How do I categorize repository components into daily versus library buckets?

You categorize repository components by analyzing local codebase evidence including file extensions, package managers, and CI configs to determine which components are always loaded or accessible by default.

Can I use file extensions and CI configs to classify project configurations?

Yes, you can classify project configurations by using local evidence sources including file extensions, package managers, framework configs, and CI/hook configurations to back your categorization.

What artifacts are generated when building an ECC install plan?

Building an ECC install plan generates output artifacts including a daily inventory, a library inventory, an install plan, a verification report, and an optional skill-library router.

Does repository analysis support parallel review passes for multiple component types?

Yes, repository analysis supports parallel review passes to classify different component types like agents, skills, commands, rules, hooks, and extras simultaneously when processing a codebase.