workspace-surface-audit

Audit workspace surfaces and benchmark against official ECC-native capabilities.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/contentbugvideoediting/cb-project-assistant --skill workspace-surface-audit-contentbugvideoediting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-surface-audit
Source: https://github.com/contentbugvideoediting/cb-project-assistant/tree/main/services/cb-s-claude/vendor/s-claude/skills-library/workspace-surface-audit
Command: npx skills add https://github.com/contentbugvideoediting/cb-project-assistant --skill workspace-surface-audit-contentbugvideoediting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Inventory active harness targets, installed plugins and connected apps, configured MCP servers, and key env surfaces to surface a complete landscape.
  • Benchmark the workspace against official Claude plugin surfaces and locally installed ECC primitives to identify parity and gaps.
  • Turn gaps into ECC-native decisions by recommending the appropriate shape (skill, hook, or agent) to close the loop and accelerate adoption.

Quick Start

Run the workspace-surface-audit skill against your active workspace to generate a surface inventory and a prioritized ECC-native improvement plan.

Frequently Asked Questions about workspace-surface-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my workspace surfaces for Claude Code capabilities?

To audit workspace surfaces, this skill inventories active repos, MCP servers, installed plugins, connectors, env surfaces, and harness setups, then benchmarks them against official Claude plugin surfaces to identify parity gaps and recommend ECC-native improvements.

What is an ECC-native workspace surface inventory?

An ECC-native workspace surface inventory maps your active repo configurations, installed plugins, connected MCP servers, and env files to reveal existing Claude Code capabilities and highlight gaps where native skills, hooks, or agents are missing.

How do I identify gaps in my MCP server and plugin configurations?

To identify gaps in MCP server and plugin configurations, the audit benchmarks your locally installed ECC primitives and connected apps against official Claude plugin surfaces, producing a prioritized set of recommendations to close capability loops.

Can I use this audit to set up Claude Code for my active repository?

Yes, you can use this audit to set up Claude Code by evaluating your active repo surfaces, env files, and harness setups to generate a prioritized ECC-native improvement plan recommending the appropriate skills, hooks, or agents for your environment.

What do I need to inventory before recommending ECC-native skills and hooks?

Before recommending ECC-native skills and hooks, you need accessible repo surfaces, env files, MCP server settings, and installed plugins so the audit can assemble a complete surface inventory and benchmark it against official Claude surfaces.

Are there limitations to benchmarking workspace surfaces against official Claude plugins?

Limitations of benchmarking workspace surfaces include requiring full access to repo surfaces, env files, MCP settings, and installed plugins; without complete environment visibility, the audit cannot accurately assemble inventory or produce reliable ECC-native recommendations.