workspace-surface-audit

Audit Codex workspace surfaces and identify missing workflow coverage.

Updated Jun 24, 2026

Search Tags:#hooks #codex #skills #mcp #integration analysis #workspace audit

Ready to run

npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill workspace-surface-audit-mostafa-ismail-2004

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workspace-surface-audit
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/workspace-surface-audit
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill workspace-surface-audit-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you figure out what capabilities are actually available in your Codex workspace, which surfaces are already connected, and where important workflow gaps still exist.

Core Features & Use Cases

Workspace inventory: Reviews repo and environment surfaces such as manifests, hooks, MCP configs, env-backed services, and existing Codex skills.
Parity analysis: Compares current capabilities against installed plugins and connected apps to identify where Codex already has coverage versus only primitive support.
Gap-to-skill mapping: Recommends the right Codex-native shape for missing workflows, such as a skill, hook, agent, or connector.
Use case: Use it before setting up a new workspace to decide which workflows Codex should own and which integrations are still missing.

Quick Start

Ask for a read-only audit of the current workspace and have it recommend the highest-value Codex-native skills, hooks, agents, and integrations.

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 Codex workspace for available surfaces and connected tools?▼

To audit your Codex workspace, inspect manifests, configuration files, MCP configs, hooks, and existing skill libraries to inventory connected tools and identify workflow coverage gaps.

What is a Codex workspace surface audit and when do I need one?▼

A workspace surface audit reviews your repos, plugins, MCP servers, hooks, and env-backed services to map available capabilities. You need one before setting up a new workspace or benchmarking your environment.

How do I find missing workflow coverage and map gaps to Codex skills?▼

To find missing workflow coverage, perform a parity analysis comparing current capabilities against installed plugins. The audit then recommends the right Codex-native shape, such as a skill, hook, agent, or connector, for those gaps.

Can I check if my connected MCP servers and hooks provide full parity for my Codex workflows?▼

Yes, a workspace parity analysis compares your current capabilities against installed plugins and connected apps to identify where Codex already has coverage versus only primitive support.

What's the best way to determine which Codex-native integrations are missing from my environment?▼

The best way to find missing integrations is to run a read-only audit of your workspace to inspect manifests and env-backed services, which produces workflow-level recommendations for missing skills, hooks, and agents.