Agent skill · Security

workspace-surface-audit

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 OpenAI Codex or understanding what capabilities are actually available in their environment.

mturacgithub.com/mturacGitHub ↗
codexcopilotcursorMIT
Install
npx skills add mturac/everything-openai-codex --skill workspace-surface-audit --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/workspace-surface-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 84
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 OpenAI Codex", "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: - alrea

What's inside
Steps it walks through
  1. When to Use
  2. Non-Negotiable Rules
  3. Audit Inputs
  4. Audit Process
  5. Phase 1: Inventory What Exists
  6. Phase 2: Benchmark Against Official and Installed Surfaces
  7. Phase 3: Turn Gaps Into ecc Decisions
  8. Output Format
  9. Recommendation Rules
  10. Good Outcomes
More from everything-openai-codex
All skills →
About this skill
What does the workspace-surface-audit skill 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. Use when the user wants help setting up OpenAI Codex or understanding what capabilities are actually available in their environment.

How do I install it?

Run `npx skills add mturac/everything-openai-codex --skill workspace-surface-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going