This is the ECC operator's answer to "what can I actually do in this workspace and what should I wire up next?" It reads your repo config, MCP servers, plugins, environment keys, and existing skills, then tells you what's connected, what's just primitives without a clean workflow wrapper, and what's missing entirely. The output separates three buckets: already available, available but needs an ECC skill layer, and not available yet. Use it when setting up Claude Code in a new repo or deciding whether a capability should be a skill, hook, agent, or MCP integration. It won't print secret values and defaults to recommending user-facing operator skills over generic "install another plugin" advice when ECC can reasonably own the surface.
npx -y skills add affaan-m/everything-claude-code --skill workspace-surface-audit --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills