New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Workspace Surface Audit

by affaan-m in affaan-m/ECC

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.

MITAuto-check: notesAgent Workflows

Install Workspace Surface Audit

skills CLI
$ npx skills add affaan-m/ECC --skill workspace-surface-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install affaan-m/ECC workspace-surface-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/affaan-m/ECC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/workspace-surface-audit .claude/skills/workspace-surface-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workspace-surface-audit
GitHub stars
277k
Used in
3 other repos
Token cost
~1.3k tokens
SKILL.md length
652 words
Files
1
Skills in repo
683
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 3 steps: Inventory What Exists → Benchmark Against Official and Installed… → Turn Gaps Into ECC Decisions
  • The user wants help setting up Claude Code
  • SKILL.md covers When to Use, Non-Negotiable Rules, Audit Inputs and Audit Process, plus 3 more sections
  • Needs STRIPE_API_KEY and TWILIO_AUTH_TOKEN

What it does

Workspace Surface Audit is an agent skill from affaan-m/ECC. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond. The licence is MIT.

When your agent uses it

  • The user wants help setting up Claude Code
  • Understanding what capabilities are actually available in their environment

Example prompts

  • “/workspace-surface-audit”

Requirements

  • A credential in STRIPE_API_KEY
  • A credential in TWILIO_AUTH_TOKEN

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Inventory What Exists
  2. Benchmark Against Official and Installed Surfaces
  3. Turn Gaps Into ECC Decisions

What it can do on your machine

Read from SKILL.md and the folder at commit 2d515e4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • STRIPE_API_KEY
    • TWILIO_AUTH_TOKEN
    • FAL_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workspace Surface Audit loads about 1.3k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 652 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:19
    - Reviewing `.env`, `.mcp.json`, plugin settings, or connected-app surfaces to find missing workflow layers
  • NoteMentions a .env fileSKILL.md:41
    - `.env*` files in the active repo and obvious adjacent ECC workspaces

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from affaan-m/ECC at commit 2d515e4, republished under its MIT licence (© affaan-m). 652 words, ~1,291 tokens.

Download SKILL.mdSave it as .claude/skills/workspace-surface-audit/SKILL.md (or your agent's skills folder).
name
workspace-surface-audit
description
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.
metadata.origin
ECC

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.

When to Use

  • 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

Non-Negotiable Rules

  • 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 another plugin" advice when ECC can reasonably own the surface.
  • Treat external plugins as benchmarks and inspiration, not authoritative product boundaries.
  • Separate three things clearly:
    • already available now
    • available but not wrapped well in ECC
    • not available and would require a new integration

Audit Inputs

Inspect only the files and settings needed to answer the question well:

  1. Repo surface
    • package.json, lockfiles, language markers, framework config, README.md
    • .mcp.json, .lsp.json, .claude/settings*.json, .codex/*
    • AGENTS.md, CLAUDE.md, install manifests, hook configs
  2. Environment surface
    • .env* files in the active repo and obvious adjacent ECC workspaces
    • Surface only key names such as STRIPE_API_KEY, TWILIO_AUTH_TOKEN, FAL_KEY
  3. Connected tool surface
    • Installed plugins, enabled connectors, MCP servers, LSPs, and app integrations
  4. ECC surface
    • Existing skills, commands, hooks, agents, and install modules that already cover the need

Audit Process

Phase 1: Inventory What Exists

Produce a compact inventory:

  • active harness targets
  • installed plugins and connected apps
  • configured MCP servers
  • configured LSP servers
  • env-backed services implied by key names
  • existing ECC skills already relevant to the workspace

If a surface exists only as a primitive, call that out. Example:

  • "Stripe is available via connected app, but ECC lacks a billing-operator skill"
  • "Google Drive is connected, but there is no ECC-native Google Workspace operator workflow"
Phase 2: Benchmark Against Official and Installed Surfaces

Compare the workspace against:

  • official Claude plugins that overlap with setup, review, docs, design, or workflow quality
  • locally installed plugins in Claude or Codex
  • the user's currently connected app surfaces

Do not just list names. For each comparison, answer:

  1. what they actually do
  2. whether ECC already has parity
  3. whether ECC only has primitives
  4. whether ECC is missing the workflow entirely
Show full SKILL.md (229 more words)Show less
Phase 3: Turn Gaps Into ECC Decisions

For every real gap, recommend the correct ECC-native shape:

Gap TypePreferred ECC Shape
Repeatable operator workflowSkill
Automatic enforcement or side-effectHook
Specialized delegated roleAgent
External tool bridgeMCP server or connector
Install/bootstrap guidanceSetup or audit skill

Default to user-facing skills that orchestrate existing tools when the need is operational rather than infrastructural.

Output Format

Return five sections in this order:

  1. Current surface
    • what is already usable right now
  2. Parity
    • where ECC already matches or exceeds the benchmark
  3. Primitive-only gaps
    • tools exist, but ECC lacks a clean operator skill
  4. Missing integrations
    • capability not available yet
  5. Top 3-5 next moves
    • concrete ECC-native additions, ordered by impact

Recommendation Rules

  • Recommend at most 1-2 highest-value ideas per category.
  • Favor skills with obvious user intent and business value:
    • setup audit
    • billing/customer ops
    • issue/program ops
    • Google Workspace ops
    • deployment/ops control
  • If a connector is company-specific, recommend it only when it is genuinely available or clearly useful to the user's workflow.
  • If ECC already has a strong primitive, propose a wrapper skill instead of inventing a brand-new subsystem.

Good Outcomes

  • The user can immediately see what is connected, what is missing, and what ECC should own next.
  • Recommendations are specific enough to implement in the repo without another discovery pass.
  • The final answer is organized around workflows, not API brands.

© affaan-m, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/workspace-surface-audit of affaan-m/ECC.

Open the folder on GitHubat commit 2d515e4

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in affaan-m/ECC, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Workspace Surface Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workspace Surface Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workspace Surface Audit this skillaffaan-m/ECC277k3 repos~1.3kAutomated safety check: NotesMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Context Mode Output Sandboxmksglu/context-mode26k—~4.1kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Warp GUI to Agent CLI Migration

    warpdotdev/warp

    Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from affaan-m/ECC

All 682 skills in this repo

  • Skill Stocktake

    affaan-m/ECC

    Audits your installed Claude skills and commands for quality, with a quick mode for recently changed skills and a full mode that evaluates all of them through subagents.

    277k GitHub starsUsed in 5 repos~3.1k tokens
    Auto-check passed

  • VideoDB Video Search and Editing

    affaan-m/ECC

    Ingests, indexes, searches, edits and monitors video, audio and live streams through the VideoDB Python SDK, returning stream links, clips and timestamps.

    277k GitHub starsUsed in 3 repos~3.5k tokens
    Auto-check: notes

  • Docs Governance

    affaan-m/ECC

    Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references.

    277k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Rules Distillation

    affaan-m/ECC

    Scans installed skills for principles that recur across them and proposes rule-file changes: append, revise, add a section, create a file or leave as covered.

    277k GitHub starsUsed in 2 repos~2.3k tokens
    Auto-check passed

  • Master Agreement Generator

    affaan-m/ECC

    Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.

    277k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Frontend Design Direction

    affaan-m/ECC

    Set an ECC-specific frontend design direction for production UI work.

    277k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed

Works with

Categories

Questions about Workspace Surface Audit

What does Workspace Surface Audit do?

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. Workspace Surface Audit is an agent skill from affaan-m/ECC. 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.

When should I use Workspace Surface Audit?

Workspace Surface Audit fits situations like: the user wants help setting up Claude Code; understanding what capabilities are actually available in their environment.

How do I install Workspace Surface Audit in Claude Code?

Run `npx skills add affaan-m/ECC --skill workspace-surface-audit -a claude-code`. Or copy the skill folder (skills/workspace-surface-audit in affaan-m/ECC) into .claude/skills/workspace-surface-audit in your project. Claude Code loads it when a task matches its description.

How do I install Workspace Surface Audit in Codex?

Run `npx skills add affaan-m/ECC --skill workspace-surface-audit -a codex`. Or copy the skill folder (skills/workspace-surface-audit in affaan-m/ECC) into .agents/skills/workspace-surface-audit in your project. Codex loads it when a task matches its description.

Can I use Workspace Surface Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add affaan-m/ECC --skill workspace-surface-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workspace-surface-audit, .gemini/skills/workspace-surface-audit, .github/skills/workspace-surface-audit and .opencode/skills/workspace-surface-audit in your project.

What does Workspace Surface Audit need to run?

Going by SKILL.md and its folder, Workspace Surface Audit needs credentials named STRIPE_API_KEY, TWILIO_AUTH_TOKEN and FAL_KEY. Our summary lists: A credential in STRIPE_API_KEY; A credential in TWILIO_AUTH_TOKEN.

Does Workspace Surface Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workspace Surface Audit safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Workspace Surface Audit use?

Workspace Surface Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workspace Surface Audit use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workspace Surface Audit?

Skills that share tags, products or a category with Workspace Surface Audit: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workspace Surface Audit?

affaan-m (a GitHub user) maintains it in affaan-m/ECC, which has 276,673 GitHub stars. The repository holds 683 skills in this directory. The repository was last updated on October 11, 2026.

Source: affaan-m/ECC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.