workspace-surface-audit

Audit repo and environment surfaces for ECC capability gaps.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill workspace-surface-audit-llmh333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-surface-audit
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/workspace-surface-audit
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill workspace-surface-audit-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A workspace or Gemini/ECC setup often has hidden capability gaps, so teams waste time installing plugins or building workflows without verifying what’s already available and properly configured.

Core Features & Use Cases

  • Workspace capability inventory: Audits repo and environment surfaces (configs, connected tools, MCP/LSP/LSP settings, and existing ECC coverage) to summarize what works right now.
  • Parity benchmarking: Compares what’s available in the workspace and against overlapping official or installed surfaces to identify where ECC already matches versus where it only has primitives.
  • Gap-to-workflow recommendations: Converts real gaps into the correct ECC-native shape (skill, hook, agent, MCP, or connector) and orders the top next moves by impact.

Quick Start

Ask for a workspace capability audit by saying: "Run a workspace-surface-audit for this repo and my current Gemini/ECC environment, then list current surface, ECC parity, primitive-only gaps, missing integrations, and your top next moves."

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 Gemini CLI workspace to find available MCP servers and capabilities?

A workspace surface audit inventories your repo, environment surfaces, connected apps, and MCP server configurations to summarize what works right now. It performs a read-only review of your Gemini CLI setup to separate existing, weakly wrapped, and missing capabilities.

What is the best way to identify capability gaps in my ECC-native workflows and connected tools?

To identify capability gaps in ECC-native workflows, run a parity benchmarking audit. This compares your workspace's available surfaces against overlapping official installations to pinpoint where ECC fully matches versus where it only has basic primitives.

Can I review my workspace configuration to decide which ECC-native workflow to build next?

Yes, you can review your workspace configuration to prioritize next moves. The audit converts real capability gaps into the correct ECC-native shape—whether a skill, hook, agent, MCP, or connector—and orders recommendations by operational impact.

Does the workspace configuration review expose secret values from my environment surfaces?

No, the workspace configuration review strictly enforces safety by never printing secret values. It performs a read-only inventory of your connected apps and environment surfaces to assess operational automation capabilities without compromising credentials.

How do I inventory existing ECC coverage and plugin configurations across my machine?

You can inventory existing ECC coverage by auditing your repo and machine environment. This read-only process evaluates plugin, MCP, and LSP settings to output a structured assessment separating properly configured surfaces from primitive-only gaps.