AIPM
Theme

AIPM package

Workspace Surface Audit

@affaan-m/workspace-surface-audit@1.0.0

Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents,…

Scanned · no issues · Nov 8, 2026

GitHub stars: ★ 299K

LinkedInPost

Install Skill

Pins this version in aipm.package.json and aipm-lock.json.

aipm add @affaan-m/workspace-surface-audit@1.0.0

Without project tracking

Writes the skill files only. Add --no-init to skip aipm.package.json and the lockfile.

aipm add @affaan-m/workspace-surface-audit@1.0.0 --no-init

How to use

Install the skill above, then run this in your AI tool:

/workspace-surface-audit <your description>

About

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?"

Source

What gets added to your project

Preview every file this package writes on install before you run the command above.

Summary

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 u...

Skill instructions

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

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.

Loading package files…

Share this package

Add an Install with AIPM badge

Add this badge to a GitHub README so readers can open the package page and install the same version.

Install with AIPM
[![Install with AIPM](https://www.aipm-registry.com/install-with-aipm.svg)](https://www.aipm-registry.com/skills/affaan-m/workspace-surface-audit/1.0.0?utm_source=github&utm_medium=readme&utm_campaign=package_badge)

Publisher

Affaan Mustafa

This imported publisher has not claimed its AIPM account. A connected account confirms account control, but it does not guarantee that a package is safe.

AI assistant context

What this skill is for

@affaan-m/workspace-surface-audit@1.0.0 is an AIPM skill package for All tools. Use it when a project needs the reusable AI behavior described as: 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 u...

Install
aipm add @affaan-m/workspace-surface-audit@1.0.0
Use after install
/workspace-surface-audit <your description>

Tool targets

Install command by target

Add --no-init to any of these when you want the skill files without aipm.package.json or aipm-lock.json.

cursor

Run this variant when you want to install the package into cursor.

aipm add @affaan-m/workspace-surface-audit@1.0.0 --target cursor --ci

claude

Run this variant when you want to install the package into claude.

aipm add @affaan-m/workspace-surface-audit@1.0.0 --target claude --ci

Discussion

Comments (0)

Loading comments…

Keep exploring

Affaan Mustafa/ui-canvas

Preview a UI component mockup in a local browser canvas where the human directly edits it (move, resize, edit text, delete, restyle), switches mobile/desktop/custom viewports, tests it, chats with you, and clicks Save and Finish. You the...

Published by Affaan Mustafa

skillScanned · no issues★ 308KImported · UnverifiedAll toolsNov 21, 2026, 1:11 AM6.61 KBMIT

Affaan Mustafa/yoruba-localization-testing

Test Yoruba (yo) and English bilingual interfaces for tone marks, underdots, Unicode normalization, translation fallback, and accessibility.

Published by Affaan Mustafa

skillScanned · no issues★ 306KImported · UnverifiedAll toolsNov 18, 2026, 1:19 AM3.43 KBMIT

Affaan Mustafa/web-perimeter-owasp-2025-audit

Passive, non-destructive web perimeter security auditing mapped to OWASP Top 10:2025 surface leads, CDN Unkeyed Header Web Cache Poisoning (X-Forwarded-Host), supply chain manifest exposure, git object dumping prevention (/.git/HEAD), cr...

Published by Affaan Mustafa

skillScanned · flagged★ 305KImported · UnverifiedAll toolsNov 17, 2026, 1:13 AM8.86 KBMIT

Package FAQ

Install and compatibility

How to install
Run aipm add @affaan-m/workspace-surface-audit@1.0.0 in a project that has AIPM initialized.
Supported tools
@affaan-m/workspace-surface-audit@1.0.0 supports All tools.

Before installing

AIPM skills can add files to your project. Review the package name, target, description, license, and publisher before installing. Use a clean branch when trying a new skill.