workspace-surface-audit

Read-only audit skill for answering the question "what can this workspace and machine actually do right now, and what should we add or enable next?" This is the ECC-native answer to setup-audit plugins. It does not modify files unless the user explicitly asks for follow-up implementation. Inspect only the files and settings needed to answer the question well: Produce a compact inventory: If a surface exists only as a primitive, call that out. Example: Compare the workspace against: Do not just list names. For each comparison, answer: For every real gap, recommend the correct ECC-native shape: Default to user-facing skills that orchestrate existing tools when the need is operational rather than infrastructural. Return five sections in this order: - 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...