workspace-surface-audit

What problem does it solve?

Provides a read-only, structured audit of a repository, machine, and connected surfaces so users understand what capabilities are actually available, what is missing, and which MCC-native workflows or integrations to add without modifying files or exposing secrets.

Core Features & Use Cases

• Inventory: Enumerates repo markers (package.json, lockfiles, README), MCC manifests, installed plugins, MCP servers, LSPs, and env-backed keys to show what is usable now.
• Benchmarking: Compares local surfaces to official plugins and connected apps and assesses parity versus MCC-native capabilities.
• Gap Analysis & Recommendations: Classifies gaps as primitive-only, missing integrations, or candidates for skills/hooks/agents and proposes the top 3-5 next MCC-native moves.
• Safety-first: Explicitly avoids printing secret values and only surfaces provider names, capability names, and existence of keys or files.
• Use Case: Run before installing Claude Code or when asking "what am I missing?" to get an actionable, implementable plan for MCC adoption.

Quick Start

Ask the workspace-surface-audit skill to inventory this repository and connected machine and recommend MCC skills, hooks, or connectors to add next.