Build an evidence-backed ECC install plan from repository files and configuration.
npx skills add https://github.com/WUIX69/e-lock --skill agent-sort-wuix69
Please help me install this Agent Skill. Skill: agent-sort Source: https://github.com/WUIX69/e-lock/tree/main/.agent/.agents/skills/agent-sort Command: npx skills add https://github.com/WUIX69/e-lock --skill agent-sort-wuix69
This Skill helps teams avoid loading a generic ECC bundle when a repository only needs a narrower, project-specific set of agents, skills, commands, rules, hooks, and extras.
Ask the agent to inspect the repository and build an evidence-backed DAILY and LIBRARY ECC install plan.
High-intent search queries and answers about installing and using this skill.
Sort repository components into daily versus library buckets by using an evidence-backed classification plan that inspects actual repo files and configuration to determine what to keep loaded, keep searchable, or remove as incompatible.
The best way to plan an ECC install is to build an evidence-backed plan from the repository's actual files, verifying that the final surface matches the repo stack and that stale or off-stack components are not left active.
Clean up a mixed ECC setup by inspecting the repository to sort agents, skills, commands, rules, hooks, and extras into daily or library buckets, trimming noise and keeping only the surfaces the project actually uses.
You can route workflow components without loading off-stack extras by verifying compatible surfaces through stack-aware classification, ensuring that only project-specific components are kept active while incompatible ones are removed.
You need an evidence-backed ECC install plan when a repository only requires a narrower, project-specific set of components instead of a generic ECC bundle, allowing selective installation and routing based on actual repo evidence.
Stale or off-stack components are left active when a verification workflow is not applied; running an evidence-backed classification checks the final surface against the repo stack to identify and remove incompatible components.
pragsmikeInspect repositories and produce inventory, classification, and migration reports for agent-facing files.
JamkrisClassify ECC components into DAILY and LIBRARY buckets using repo evidence.
CDO-07-NewBuilds an evidence-backed ECC install plan classifying repository components as DAILY or LIBRARY.
MomoDavilukeClassify ECC surfaces into daily and library categories with repo evidence.
