agent-sort

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams trim ECC installs to the actual repo needs by sorting and prioritizing components with evidence.

Core Features & Use Cases

  • Classifies ECC components into DAILY and LIBRARY buckets using repository evidence.
  • Produces an install plan and verification report to guide minimal, effective deployments.
  • Reusable for any repo to reduce bloat and align with project scope.

Quick Start

Run this skill on a repository to generate a DAILY vs LIBRARY install plan backed by concrete evidence.

Frequently Asked Questions about agent-sort

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

FAQPage Schema
What is an evidence-backed ECC install plan?

Classify ECC components into DAILY and LIBRARY buckets by analyzing concrete repository evidence, generating a minimal install plan and verification report for safe deployments.

How do I generate a minimal ECC deployment plan for a multi-stack repository?

Run the skill on your repository to classify ECC components into DAILY and LIBRARY inventories using repo evidence, producing a minimal install plan and verification report for deployment.

Can I use this ECC install planning approach for repositories with varying tech stacks?

Yes, the classification mechanism is reusable for any repository with varying stacks, sorting ECC components into DAILY and LIBRARY buckets to reduce bloat and align with project scope.

What is the difference between DAILY and LIBRARY ECC component buckets?

DAILY and LIBRARY buckets classify ECC components based on concrete repository evidence to separate daily operational needs from library dependencies, guiding minimal and effective deployments.

Why does my ECC install include unnecessary components?

Unnecessary ECC components often occur when installs are not tailored to actual repository needs; classifying components using concrete repo evidence trims the deployment to minimal requirements.