agent-sort

Classify ECC surfaces into daily and library categories with repo evidence.

2|Updated Mar 3, 2026

Search Tags:#automation #classification #repo-evidence #ecc #install-plan #daily-vs-library

Ready to run

npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill agent-sort-momodaviluke

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/ecc/agent-sort
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill agent-sort-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ECC surfaces in a repository can lead to unnecessary bloat if loaded all at once; this skill helps trim and categorize components so only daily-use items load by default while others remain accessible as library references.

Core Features & Use Cases

Classifies ECC surfaces into DAILY vs LIBRARY buckets using repo-aware review passes.
Produces a coherent DAILY inventory, a LIBRARY reference inventory, an install plan, and a verification report.
Enables evidence-driven, reproducible installs across different project stacks and team contexts.

Quick Start

Run the agent-sort skill on your repository to produce a DAILY install plan and a LIBRARY reference by sorting components.

Frequently Asked Questions about agent-sort

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

FAQPage Schema

How do I classify ECC surfaces in a repository to separate daily-use components from library references?▼

The skill classifies ECC surfaces by applying repo-aware review passes to categorize components into DAILY and LIBRARY buckets, generating a daily inventory and a searchable library reference list.

What is the best way to generate a reproducible install plan for mixed ECC components across diverse stacks?▼

A reproducible install plan across diverse stacks is generated through evidence-driven filtering of ECC components, separating always-loaded surfaces from searchable references to yield a concrete installation blueprint.

Can I use repo evidence to filter which ECC components load daily versus remain as library references?▼

Yes, repo evidence filters ECC components by applying evidence-driven categorization to decide which surfaces load daily by default and which remain accessible as library references.

How do I verify an install plan for ECC surfaces after categorizing them into daily and library buckets?▼

Verifying an ECC surface install plan involves generating a verification report alongside the daily inventory and library reference outputs to ensure reproducible installs across project stacks.

Does this classification approach work for projects with mixed ECC components across different team contexts?▼

This classification approach supports projects with mixed ECC components by enabling evidence-driven, reproducible installs across different project stacks and team contexts.