workspace-surface-audit

To audit your repository workspace, run a surface inventory to enumerate installed MCP servers, plugins, connectors, and environment variables. This process reveals available ECC-native capabilities and identifies configuration gaps for actionable recommendations.

A workspace surface audit identifies and summarizes active repository surfaces, MCP configurations, and harness setups. You need this audit when you want to benchmark your current environment against ECC-native surfaces to reveal capability gaps and generate recommended skills or agent workflows.

Yes, you can benchmark installed environment surfaces against known ECC-native capabilities. The audit compares your active repository configurations to standard surfaces, producing a gap-to-solution plan that recommends specific skills, hooks, or agent workflows to implement.

Generating gap-driven recommendations requires visibility into configured env files, installed plugins, and connected apps. The audit uses guardrails to surface only names, capabilities, paths, and existing configurations to safely map your workspace environment.

Map connected apps and harness setups by running an inventory of your active repository workspace. This surfaces existing configurations and connectors, allowing you to benchmark against ECC-native surfaces and generate targeted recommendations for operator workflows and agents.

No, the workspace audit applies strict guardrails to protect sensitive data. When scanning environment variables and configured env files, it surfaces only names, capabilities, paths, and existing configurations to ensure your workspace environment remains secure during the inventory process.