workspace-surface-audit

To audit your workspace, inspect repository surfaces like package.json and .mcp.json to identify existing capabilities. This process benchmarks connected tools and recommends specific ECC-native skills, hooks, and agents to fill operational gaps.

A workspace surface audit evaluates repository configurations and connected tools to map current capabilities. It identifies missing ECC-native skills, hooks, agents, and workflows, offering targeted recommendations to enhance your development environment.

Yes, the workspace audit works with existing Claude plugins and .mcp.json configurations. It benchmarks installed applications and plugin settings against official capabilities to identify gaps and suggest ECC-native alternatives.

The best way to identify workflow gaps is running a comprehensive surface audit. It inspects environment configurations and repository surfaces to pinpoint missing ECC-native skills, agents, and operator workflows, providing specific improvement recommendations.

Limitations of auditing repository surfaces include dependency on visible configuration files like package.json and .mcp.json. If environment configurations or connected tools lack explicit surfaces, the audit cannot recommend ECC-native skills for undetected capabilities.