workspace-surface-audit

Audit repo, MCP servers, plugins, and env surfaces to recommend ECC-native skills and workflows.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill workspace-surface-audit-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workspace-surface-audit
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/workspace-surface-audit
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill workspace-surface-audit-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When setting up Claude Code or an AI coding environment, it is hard to know what capabilities are already available, which plugins or MCP servers overlap, and what is genuinely missing. This Skill performs a read-only audit of your workspace and machine surfaces, then turns the findings into concrete recommendations. ## Core Features & Use Cases - Surface Inventory: Inspects repo files (package.json, .mcp.json, .claude/settings, AGENTS.md), env key names, installed plugins, MCP servers, and LSPs to map what is usable right now. - Gap Benchmarking: Compares your setup against official marketplace plugins and installed connectors, classifying each capability as available, primitive-only, or missing. - ECC-Native Recommendations: Converts gaps into the right shape—skill, hook, agent, MCP server, or connector—and outputs a prioritized top 3-5 next moves. - Use Case: You just cloned a new SaaS repo and ask what automations to add. The audit reveals Stripe is connected but has no billing-operator skill, and recommends a wrapper skill plus a deployment-ops hook. ## Quick Start Ask the assistant to audit this workspace and recommend which skills, hooks, and MCP servers to add next.

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 Claude Code workspace setup?▼

Run a workspace surface audit that inventories your repo config files, MCP servers, plugins, connectors, and env key names. It classifies each capability as available, primitive-only, or missing, then recommends the highest-value skills, hooks, and agents to add.

What MCP servers or plugins should I install for my repo?▼

The answer depends on what your workspace already exposes. The audit compares installed plugins and connected apps against official marketplace offerings, then recommends only integrations that fill real gaps rather than duplicating existing coverage.

Does the workspace audit expose my API keys or secrets?▼

No. The audit never prints secret values. It surfaces only provider names, capability names, file paths, and whether a key or config exists, such as noting that STRIPE_API_KEY is present without revealing its contents.

When should a capability be a skill versus a hook or agent?▼

Repeatable operator workflows become skills, automatic enforcement or side-effects become hooks, specialized delegated roles become agents, and external tool bridges become MCP servers or connectors. The audit maps each identified gap to the correct shape.

Will the audit modify my repository files?▼

No. The audit is read-only and does not modify files unless you explicitly ask for follow-up implementation. It only inspects configuration surfaces and returns a structured report with prioritized next moves.