agent-sort

Classify repository ECC components into DAILY and LIBRARY install plans.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill agent-sort-sakamoto-family-smile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/sakamoto-family-smile/agent_monorepo/tree/main/.claude/skills/ecc/agent-sort
Command: npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill agent-sort-sakamoto-family-smile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This ECC decision tool reduces install bloat by sorting repo surfaces into DAILY vs LIBRARY, producing a minimal, evidence-backed plan.

Core Features & Use Cases

  • Classifies ECC components by repo evidence (languages, configs, dependencies) to decide daily rollout vs library references.
  • Generates an install plan that translates classifications into concrete actions for Skill loading, hook surfaces, and extras.
  • Supports repeatable, project-specific ECC tailoring across multiple repositories.

Quick Start

Analyze a repository and run the agent-sort to produce a DAILY and LIBRARY ECC partition with an actionable 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-backed install plan for repository components?

An evidence-backed install plan is generated by analyzing repository evidence like languages and configs to classify components into DAILY and LIBRARY partitions, translating them into concrete actions for Skill loading, hook surfaces, and extras.

What is the best way to reduce install bloat when sorting repo surfaces?

To reduce install bloat, an ECC decision tool sorts repository surfaces into DAILY versus LIBRARY partitions, producing a minimal and evidence-backed plan tailored to the specific repository's configurations and dependencies.

Can I use repository analysis to classify skills, commands, rules, and hooks?

Yes, repository analysis can classify multiple surface types including skills, commands, rules, hooks, and extras, sorting them into actionable DAILY and LIBRARY ECC partitions based on repo-local evidence.

How does repo evidence decide between daily rollout and library references?

Repo evidence such as detected languages, configurations, and dependencies is evaluated to determine whether components should be scheduled for daily rollout or maintained as library references within the install plan.

Does the install plan include verification-ready artifacts for the classified components?

Yes, the install plan includes verification-ready artifacts alongside DAILY and LIBRARY partitions, ensuring that the evidence-backed classifications across surfaces are repeatable and project-specific.