workspace-surface-audit

Audit repository, MCP servers, plugins, and environment variables for capability gaps.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill workspace-surface-audit-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-surface-audit
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/workspace-surface-audit
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill workspace-surface-audit-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of not knowing what capabilities your current workspace, connected tools, and environment have available, and which ECC-native skills, hooks, agents, or connectors you should add to improve your workflow without installing redundant or overlapping plugins.

Core Features & Use Cases

  • Read-Only Workspace Audit: Scans your repository, MCP servers, installed plugins, environment variables, and existing ECC setup to catalog all available capabilities without modifying any files.
  • Benchmark Gap Analysis: Compares your current setup against official Claude plugins and installed tools to identify where ECC already has parity, where only primitive tools exist, and where full integrations are missing.
  • Tailored ECC Recommendations: Delivers prioritized, actionable suggestions for ECC-native additions aligned with your workflow needs, such as setup audit skills, billing operators, or deployment control tools.
  • Use Case: For example, if you are setting up Claude Code for your AI research project, this Skill will tell you which existing ECC tools you can leverage, what workflow layers are missing, and exactly what to add next to automate your research and deployment tasks.

Quick Start

Use the workspace-surface-audit skill to review your AI Research Agent repository and environment setup, then receive a prioritized list of ECC-native tools and workflows to add for maximum productivity.

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 workspace to find missing Claude Code integrations?

An environment audit scans connected MCP servers, installed plugins, and environment variables to catalog all available capabilities. It then compares your setup against benchmarks to identify primitive-only gaps and missing integrations for ECC adoption.

What is the best way to evaluate which ECC workflows to add to my development environment?

ECC workflow recommendations are generated by comparing your active repository and connected tools against official benchmarks. The audit highlights where ECC already has parity, where only primitive tools exist, and what full integrations are missing.

Does a workspace surface audit modify my repository files during the scan?

No, the workspace audit is completely read-only and does not modify existing files. It safely reviews your repository, MCP servers, installed plugins, and environment variables to deliver a structured output of current capabilities and gaps.

Can I identify primitive-only gaps in my MCP server setup?

Yes, an MCP audit identifies primitive-only gaps by comparing your connected servers against official plugin benchmarks. This reveals exactly where your environment relies on basic primitives instead of possessing full ECC-native integrations.

How do I check if my installed plugins overlap with existing ECC-native skills?

A plugin audit catalogs your installed tools and compares them against ECC-native skills to identify parity. This prevents installing redundant or overlapping plugins by highlighting where your environment already possesses equivalent capabilities.