Sorts ECC skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using repo evidence like file extensions and configs. Creates trimmed install plan for project-specific needs.
From eccnpx claudepluginhub affaan-m/everything-claude-code --plugin everything-claude-codeThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
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.
Produce these artifacts in order:
skill-library router if the project wants oneUse two buckets only:
DAILY
LIBRARY
Use repo-local evidence before making any classification:
Useful commands include:
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
If parallel subagents are available, split the review into these passes:
agents/*skills/*commands/*rules/*If subagents are not available, run the same passes sequentially.
Establish the real stack before classifying anything:
For every candidate surface, record:
Use this format:
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
Promote to DAILY when:
Demote to LIBRARY when:
Translate the classification into action:
.claude/skills/skill-libraryIf the repo already uses selective installs, update that plan instead of creating another system.
If the project wants a searchable library surface, create:
.claude/skills/skill-library/SKILL.mdThat router should contain:
Do not duplicate every skill body inside the router.
After the plan is applied, verify:
Return a compact report with:
If the next step is interactive installation or repair, hand off to:
configure-eccIf the next step is overlap cleanup or catalog review, hand off to:
skill-stocktakeIf the next step is broader context trimming, hand off to:
strategic-compactReturn the result in this order:
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