agent-sort
/agent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
- Author
- ginaservice ↗
- Repository
- ginaservice-skills ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Original author description
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
How it works
- When to Use
- Non-Negotiable Rules
- Outputs
- Classification Model
- Evidence Sources
- Parallel Review Passes
- Core Workflow
- Handoffs
- Output Format
SKILL.md preview
--- name: agent-sort description: "Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle." category: architecture allowed-tools: "Read, Grep, Glob, Bash, Edit, Write" file_names: ["SKILL.md"] metadata: origin: ECC architecture: GINA-Sovereign-Multi-Agent security_charter: GINA-SEC-7L-2026 memory_topology: 3-tier-L1-L2-L3 sandbox_policy: "--cap-drop=ALL" dlp_leakage_score: "0.00" --- # Agent Sort Use this skill when a repo needs a project-specific ECC surface instead of the default full install. The goal is not to guess what "feels useful." The goal is to classify ECC components with evidence from the actual codebase. ## When to Use - A project only needs a subset of ECC and full installs are too noisy - The repo stack is clear, but nobody wants to hand-curate skills one by one - A team wants a repeatable install decision backed by grep evidence instead of opinion - You need to separate always-loaded daily workflow surfaces from searchable library/reference surfaces - A repo has drifted into the wrong language, rule, or hook set and needs cleanup ## Non-Negotiable Rules - Use the current repository as the source of truth, not generic preferences - Every DAILY decision must cite concrete repo evidence - LIBRARY does not mean "delete"; it means "keep accessible without loading by default" - Do not install hooks, rules, or scripts that the current repo cannot use - Prefer ECC-native surfaces; do not introduce a second install system ## Outputs Produce these artifacts in order: 1. DAILY inventory 2. LIBRARY inventory 3. install plan 4. verification report 5. optional `skill-library` router if the project wants one ## Classification Model Use two buckets only: - `DAILY` - should load every session for this repo - strongly matched to the repo's language, framework, workflow, or operator surface - `LIBRARY` - useful to retain, but not worth loading by default - should remain reachable through search, router skill, or selective manual use ## Evidence Sources Use repo-local evidence before making any classification: - file extensions - package managers and lockfiles - framework configs - CI and hook configs - build/test scripts - imports and dependency manifests - repo docs that explicitly describe the stack Useful commands include: ```bash rg --files rg -n "typescript|react|next|supabase|django|spring|flutter|swift" cat package.json cat pyproject.toml cat Cargo.toml cat pubspec.yaml cat go.mod ``` ## Parallel Review Passes If parallel subagents are available, split the review into these passes: 1. Agents - classify `agents/*` 2. Skills - classify `skills/*` 3. Commands - classify `commands/*` 4. Rules - classify `rules/*` 5. Hooks and scripts - classify hook surfaces, MCP health checks, helper scripts, and OS compatibility 6. Extras - classify contexts, examples, MCP configs, templates, and guidance docs If subagents are not available, run the same passes sequentially. ## Core Workflow ### 1. Read the repo Establish the real stack before classifying anything: - languages in use - frameworks in use - primary package manager - test stack - lint/format stack - deployment/runtime surface - operator integrations already present ### 2. Build the evidence table For every candidate surface, record: - component path - component type - proposed bucket - repo evidence - short justification Use this format: ```text skills/frontend-patterns | skill | DAILY | 84 .tsx files, next.config.ts present | core frontend stack skills/django-patterns | skill | LIBRARY | no .py files, no pyproject.toml | not active in this repo rules/typescript/* | rules | DAILY | package.json + tsconfig.json | active TS repo rules/python/* | rules | LIBRARY | zero Python source files | keep accessible only ``` ### 3. Decide DAILY vs LIBRARY Promote to `DAILY` when: - the repo clearly uses the matching stack - the component is general enough to help every session - the repo already depends on the corresponding runtime or workflow Demote to `LIBRARY` when: - the component is off-stack - the repo might need it later, but not every day - it adds context overhead without immediate relevance ### 4. Build the install plan Translate the classification into action: - DAILY skills -> install or keep in `.gina/skills/` - DAILY commands -> keep as explicit shims only if still useful - DAILY rules -> install only matching language sets - DAILY hooks/scripts -> keep only compatible ones - LIBRARY surfaces -> keep accessible through search or `skill-library` If the repo already uses selective installs, update that plan instead of creating another system. ### 5. Create the optional library router If the project wants a searchable library surface, create: - `.gina/skills/skill-library/SKILL.md` That router should contain: - a short explanation of DAILY vs LIBRARY - grouped trigger keywords - where the library references live Do not duplicate every skill body inside the router. ### 6. Verify the result After the plan is applied, verify: - every DAILY file exists where expected - stale language rules were not left active - incompatible hooks were not installed - the resulting install actually matches the repo stack Return a compact report with: - DAILY count - LIBRARY count - removed stale surfaces - open questions ## Handoffs If the next step is interactive installation or repair, hand off to: - `configure-ecc` If the next step is overlap cleanup or catalog review, hand off to: - `skill-stocktake` If the next step is broader context trimming, hand off to: - `strategic-compact` ## Output Format Return the result in this order: ```text STACK - language/framework/runtime summary DAILY - always-loaded items with evidence LIBRARY - searchable/reference items with evidence INSTALL PLAN - what should be installed, removed, or routed VERIFICATION - checks run and remaining gaps ```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ginaservice/ginaservice-skills | 100 | MIT |
| affaan-m/ECC | 100 | MIT |
| affaan-m/ECC | 100 | MIT |
| affaan-m/ECC | 100 | MIT |
| SHRIJANAGAIN/Nemo-Cli | 100 | Apache-2.0 |
| aaione/everything-claude-code-zh | 100 | MIT |
| aaione/everything-claude-code-zh | 100 | MIT |
| mturac/everything-openai-codex | 100 | MIT |
| mturac/everything-openai-codex | 100 | MIT |
Database snapshot: 13.11.2026 · package version 1dedecdc6f40 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ecc-guide
Answer questions about ECC by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works. - 100ecc-guide
Answer questions about ECC by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works. - 96ecc-guide
在回答之前先读取仓库的实时状态,引导用户了解 ECC 当前的 agents、skills、命令、hooks、规则、安装配置档案以及项目接入流程。 - 100ecc
ECC (Everything Claude Code) is an open-source toolkit that adds agents, skills, slash commands, rules, hooks and a shared memory vault to coding agents such as Claude Code and Codex. Use it when a user asks to "install ECC", "set up ecc-universal", "add a planning, TDD and… - 100ecc
Install, configure, verify, update, or recover affaan-m/ECC, the MIT-licensed agent harness with native Claude Code and Codex plugins plus selective adapters for other supported clients. Use when the user names ECC, Everything Claude Code, ecc-universal, ecc@ecc, `ecc setup`, or… - 96ecc-guide
通过读取实时仓库内容,引导用户了解 ECC 当前的智能体、技能、命令、钩子、规则、安装配置文件和项目入门。