workspace-surface-audit
workspace surface audit
What it does
- 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
- Never print secret values. Surface only provider names, capability names, file paths, and whether a key or config exists.
- Prefer ECC-native workflows over generic "install another plugin" advice when ECC can reasonably own the surface.
Requirements & configuration
- not available and would require a new integration
- Existing skills, commands, hooks, agents, and install modules that already cover the need
- Default to user-facing skills that orchestrate existing tools when the need is operational rather than infrastructural.
Configuration: READMEAGENTSCLAUDESTRIPE_API_KEYTWILIO_AUTH_TOKENFAL_KEY
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
workspace-surface-audit FAQ
What does the workspace-surface-audit skill do?
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment. 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
What does workspace-surface-audit require?
not available and would require a new integration Existing skills, commands, hooks, agents, and install modules that already cover the need Default to user-facing skills that orchestrate existing tools when the need is operational rather than infrastructural. Configuration keys: README, AGENTS, CLAUDE, STRIPE_API_KEY, TWILIO_AUTH_TOKEN, FAL_KEY.
How do I install workspace-surface-audit?
Run: npx -y skills add https://github.com/affaan-m/everything-claude-code --skill workspace-surface-audit --agent claude-code — the source lives at github.com/affaan-m/everything-claude-code.
Maintain workspace-surface-audit?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[workspace-surface-audit on getagentictools](https://getagentictools.com/skills/affaan-m-everything-claude-code-workspace-surface-audit?ref=badge) npx agentictools info skills/affaan-m-everything-claude-code-workspace-surface-audit The second line is the CLI lookup for this page — handy in READMEs and docs.
