skills.rest
Jamkris
JamkrisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agent-sort

Classify ECC components into DAILY and LIBRARY buckets using repo evidence.

86|21|Updated Feb 9, 2026
Search Tags:#library#repository#evidence#classification#daily#ecc#install-plan
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill agent-sort-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-sort
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/agent-sort
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill agent-sort-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the ECC surface by selecting only the components a project actually uses, backed by repo evidence.

Core Features & Use Cases

  • Evidence-driven classification of surfaces into DAILY and LIBRARY
  • Parallel review passes across Agents, Skills, Commands, Rules, Hooks, and Extras
  • Generates an install plan and verification artifacts to audit decisions
  • Optional library router to expose DAILY decisions for search and reuse

Quick Start

Invoke the agent-sort process on a repository to produce a project-specific DAILY vs 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 reduce my repository's component install surface to only what the project uses?▼

Evidence-based install planning classifies repository components into DAILY and LIBRARY buckets using repo-local evidence, selecting only the active surface for installation.

What is evidence-based classification for repository install plans?▼

Evidence-based classification reviews repository usage data to sort components into DAILY and LIBRARY buckets, producing a lean, project-specific install plan with verification artifacts.

How do I generate an install plan and verification artifacts for auditing repo components?▼

Run parallel review passes across Agents, Skills, Commands, Rules, Hooks, and Extras to produce a deterministic install plan and verification artifacts for audit and deployment.

Can I preserve access to non-loaded repository components after creating a lean install surface?▼

Yes, the classification process reduces the loaded install surface while preserving access to non-loaded LIBRARY components via an optional library router for search and reuse.

What's the best way to deterministically select ECC components across multiple categories for a project?▼

Apply parallel review passes across skills, commands, rules, hooks, and extras to generate deterministic, project-specific selections backed by repo-local evidence.

When should I not use a lean, project-specific ECC install surface?▼

Avoid lean ECC install surfaces when a repository lacks sufficient usage evidence to accurately classify components into DAILY and LIBRARY buckets for deterministic selection.

Related Skills

Explore More Software Engineering Skills→
ldk-hubldk-hub

agent-sort

Classify and rank ECC install components using codebase evidence.

Community
Advanced
sakamoto-family-smilesakamoto-family-smile

agent-sort

Classify repository ECC components into DAILY and LIBRARY install plans.

Community
Advanced
luongldptitluongldptit

agent-sort

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

Community
Advanced
CDO-07-NewCDO-07-New

agent-sort

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

Official
Advanced