agent-sort

Builds an evidence-backed ECC install plan classifying repository components as DAILY or LIBRARY.

2|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/CDO-07-New/TF4-AIO-03-foresight-lens-final --skill agent-sort-cdo-07-new
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/CDO-07-New/TF4-AIO-03-foresight-lens-final/tree/main/.agents/skills/agent-sort
Command: npx skills add https://github.com/CDO-07-New/TF4-AIO-03-foresight-lens-final --skill agent-sort-cdo-07-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams decide which ECC components should be loaded by default and which should remain searchable, using the repository itself as evidence instead of personal preference.

Core Features & Use Cases

  • Evidence-backed classification: Sort skills, commands, rules, hooks, scripts, and extras into DAILY or LIBRARY buckets based on file structure, manifests, and docs.
  • Repo-aware install planning: Build a practical load plan that fits the project stack and avoids installing surfaces the repository cannot use.
  • Verification and cleanup support: Produce a compact report that shows what stays active, what becomes reference-only, and what stale surfaces should be removed.
  • Use case: A repo has drifted across multiple languages and toolchains, and you need a repeatable way to trim the active ECC surface without losing useful references.

Quick Start

Use the agent-sort skill to analyze this repository and return an evidence-backed DAILY versus LIBRARY 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 repository components into daily and library buckets using repo evidence?

Evidence-backed classification sorts skills, commands, rules, hooks, scripts, and extras into DAILY or LIBRARY buckets by analyzing file patterns, manifests, CI configs, and documentation to justify every classification.

What's the best way to build an ECC install plan for a repository that has drifted across multiple toolchains?

Build a repo-aware ECC install plan by analyzing the repository's own evidence to create a practical load plan that fits the project stack, keeping incompatible surfaces out of the install.

Can I use repo file patterns and manifests to justify which ECC components should stay active?

Yes, repo-local evidence from file patterns, manifests, CI configs, and documentation is required to justify every classification, determining what stays active versus what becomes reference-only.

How do I clean up stale ECC surfaces without losing useful references during stack-aware cleanup?

Produce a compact report during stack-aware cleanup that identifies what stays active, what becomes reference-only, and what stale surfaces should be removed, preserving useful references while trimming the active surface.

Do I need specific repository files to generate a DAILY versus LIBRARY sorting plan?

Yes, generating a DAILY versus LIBRARY install plan requires repo-local evidence from file patterns, manifests, CI configs, and documentation to ensure incompatible surfaces are kept out of the install.