Workspace Surface Audit

This is the skill you run when someone asks "what should I set up?" or "what can Claude Code actually do here?" It inventories your repo, MCP servers, plugins, environment variables, and existing ECC surfaces, then tells you what's already working, what's just primitives without a clean operator layer, and what's missing entirely. The output separates parity from gaps and recommends the next three to five ECC-native additions as skills, hooks, agents, or connectors based on actual impact. It's read-only by default and never prints secrets. Use it before installing more tooling or when you want to understand whether a workflow should live in ECC or stay external.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill workspace-surface-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

Workspace Surface Audit

Read-only audit skill for answering the question "what can this workspace and machine actually do right now, and what should we add or enable next?"

This is the ECC-native answer to setup-audit plugins. It does not modify files unless the user explicitly asks for follow-up implementation.

When to Use

User says "set up Claude Code", "recommend automations", "what plugins or MCPs should I use?", or "what am I missing?"
Auditing a machine or repo before installing more skills, hooks, or connectors
Comparing official marketplace plugins against ECC-native coverage
Reviewing .env, .mcp.json, plugin settings, or connected-app surfaces to find missing workflow layers
Deciding whether a capability should be a skill, hook, agent, MCP, or external connector