workspace-surface-audit
by affaan-mworkspace-surface-audit is a read-only audit skill for checking what a workspace and machine can do right now. It inspects the repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommends the best ECC-native skills, hooks, agents, and workflows for Workflow Automation.
This skill scores 78/100, which means it is a solid listing candidate for directory users who want a practical way to audit a workspace’s available surfaces and decide what to enable next. The repository gives enough operational guidance to support install decisions, though it is not backed by scripts or reference files, so users should expect a documented workflow rather than a tool-driven automation package.
- Clear use case for auditing Claude Code/workspace capability surfaces, with specific triggers like MCPs, plugins, env surfaces, and connected apps.
- Strong operational guardrails: read-only by default, no secret printing, and explicit separation of what is available now versus what should be added.
- Substantial skill content with valid frontmatter, a long body, and multiple workflow/constraint signals, making it understandable without much guesswork.
- No install command, scripts, or support files, so adoption depends on reading the SKILL.md rather than running packaged automation.
- The repository appears focused on audit and recommendation behavior, not on executing a full implementation workflow, so users looking for direct automation may need follow-up skills or tools.
Overview of workspace-surface-audit skill
What workspace-surface-audit does
The workspace-surface-audit skill is a read-only audit tool for answering a practical question: what can this workspace and machine actually do right now, and what should be added or enabled next? It inspects the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommends the most valuable ECC-native skills, hooks, agents, and operator workflows.
Who should use it
Use the workspace-surface-audit skill if you are setting up Claude Code, reviewing a workspace before adding more automation, or trying to understand why a capability is missing even though the repo looks “ready.” It is especially useful for people deciding between a skill, a hook, an agent, an MCP server, or an external connector.
Why it stands out
Unlike a generic prompt, workspace-surface-audit is designed to separate what is already available, what is partially configured, and what still needs implementation. That makes the output more decision-ready for Workflow Automation, especially when you want ECC-native coverage instead of scattered plugin advice.
How to Use workspace-surface-audit skill
Install workspace-surface-audit
Use the repo’s skill install flow, then point the skill at the workspace you want audited. A typical install command is:
npx skills add affaan-m/everything-claude-code --skill workspace-surface-audit
If your setup uses a different skill manager, keep the same slug: workspace-surface-audit install is about making the skill available in your local skill system, not changing the audit behavior.
Give the skill the right input
The best workspace-surface-audit usage starts with a concrete target, not a vague request. Good prompts name the repo, environment, and goal, for example: “Audit this workspace for Claude Code readiness, list what is already configured, and recommend the top three missing surfaces to add next.”
Stronger inputs usually include:
- the repo path or workspace name
- whether you care about MCP, plugins, env vars, hooks, or agent routing
- whether you want a read-only audit or a follow-up implementation plan
- any constraints, such as no secret disclosure or no external plugins
Read these files first
For workspace-surface-audit guide work, start with SKILL.md, then inspect README.md, AGENTS.md, metadata.json, and any rules/, resources/, references/, or scripts/ folders if they exist. In this repository, SKILL.md is the primary source, so the main value is in reading the audit rules, input expectations, and workflow boundaries before you ask for output.
Workflow that improves results
Use the skill in two passes: first ask for a surface inventory, then ask for recommendations. That keeps the audit from jumping too early into “install more stuff” before it has verified what is already present. If you are using workspace-surface-audit for Workflow Automation, ask it to classify each finding as already available, partially available, or missing, then rank the next actions by impact and effort.
workspace-surface-audit skill FAQ
Is workspace-surface-audit only for Claude Code setups?
No. It is strongest for Claude Code and ECC-native workflows, but the logic is broader: it helps audit any workspace where capabilities may come from repo config, connected services, env files, or automation layers.
How is this different from a normal prompt?
A normal prompt can ask “what plugins should I use,” but workspace-surface-audit is built to inspect the actual workspace surface and make bounded recommendations. That reduces guesswork and helps avoid over-recommending tools that the environment cannot support.
Is it beginner-friendly?
Yes, if you can describe your workspace and your goal. You do not need deep infrastructure knowledge; the skill is meant to translate a rough setup question into a practical inventory and next-step plan.
When should I not use it?
Do not use workspace-surface-audit when you want code changes immediately, secret values exposed, or a generic brainstorming answer detached from the workspace. It is most useful when the decision is “what do we have, what is missing, and what should we enable next?”
How to Improve workspace-surface-audit skill
Start with a narrower target
The fastest way to improve workspace-surface-audit results is to narrow the audit surface. “Audit my whole environment” is less useful than “audit repo config, MCP connections, and env surfaces for Claude Code readiness.” Specific scope makes the recommendations more actionable.
Provide evidence, not assumptions
If you already know some files, services, or connectors exist, mention them up front. That lets the skill verify and classify them instead of rediscovering them. Good input names actual surfaces like .mcp.json, .env, plugin settings, or connected apps, which improves the workspace-surface-audit guide quality.
Ask for ranked next steps
The best outputs from workspace-surface-audit are not just inventories; they are prioritized decisions. Ask for the top missing ECC-native skill, hook, agent, or MCP addition, plus the reason it matters and the tradeoff if you defer it. That keeps the audit tied to adoption value, not just coverage.
Iterate after the first pass
Use the first audit to find gaps, then rerun the skill with one gap at a time. For example: “Now audit only the MCP layer and tell me whether this should be a connector, a hook, or a skill.” This second pass is where workspace-surface-audit skill output becomes more precise and easier to implement.