skills.rest
luongldptit
luongldptitCOMMUNITY
Explore all skills by this author →
GitHub

workspace-surface-audit

Map repository, environment, and connected tool capabilities against Claude plugins.

Updated Mar 26, 2026
Search Tags:#workflow optimization#mcp servers#plugin audit#workspace audit#capability inventory#claude code setup#ecc skills
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill workspace-surface-audit-luongldptit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workspace-surface-audit
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/workspace-surface-audit
Command: npx skills add https://github.com/luongldptit/move-ticket --skill workspace-surface-audit-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the guesswork from setting up Claude Code or optimizing your workflow by mapping exactly what your current workspace, environment, and connected tools can do, and identifying the highest-value ECC-native capabilities you should add next.

Core Features & Use Cases

  • Read-Only Capability Inventory: Scans your repo files, MCP servers, plugins, environment variables, and existing ECC skills to build a complete list of all available tools and surfaces without modifying any files.
  • Gap Benchmarking: Compares your current setup against official Claude plugins and installed tools to clearly call out where ECC already has parity, where only primitive tools exist, and where full integrations are missing.
  • Prioritized ECC Recommendations: Suggests concrete, high-impact ECC-native additions (skills, hooks, agents, connectors) aligned with your workflow needs, such as billing ops, deployment control, or Google Workspace automation.
  • Use Case: If you are setting up Claude Code for a new SaaS project and want to know which billing or deployment automations you are missing, this skill will deliver an actionable, prioritized roadmap of ECC-native options to implement.

Quick Start

Request a full workspace surface audit to receive a prioritized list of high-impact ECC-native skills, hooks, and connectors tailored to your current setup and workflow goals.

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

A workspace surface audit scans your repository, MCP servers, and environment variables to inventory available tools and identify missing Claude Code integrations. It benchmarks current surfaces against official plugins to reveal parity and primitive-only gaps.

What is the best way to optimize Claude Code setup for an existing SaaS repository?▼

To optimize Claude Code setup, you should map your repository's current capabilities against official plugins. This benchmarking process highlights fully missing integrations and suggests prioritized, high-impact ECC-native skills and connectors for your SaaS workflow.

Does a workspace surface audit modify my existing repository files or environment variables?▼

No, a workspace surface audit operates as a read-only capability inventory. It scans your repo files, MCP servers, and environment variables to build a complete list of available tools without modifying any existing files.

Can I use a plugin audit to identify which ECC-native hooks I need for deployment control?▼

Yes, a plugin audit benchmarks your current setup against official tools to identify missing integrations. It generates prioritized, actionable recommendations for high-impact ECC-native hooks and agents aligned with specific needs like deployment control.

Why does my Claude Code workflow only have primitive tools instead of full integrations?▼

Your Claude Code workflow has primitive-only gaps because your current environment lacks full integrations compared to official plugins. A workspace surface audit identifies these specific gaps and recommends actionable ECC-native skills to achieve parity.

When do I need a capability inventory for my MCP servers and connected tools?▼

You need a capability inventory when setting up Claude Code or optimizing workflows for a new project. It maps exactly what your connected tools and MCP servers can do, eliminating guesswork by identifying high-value ECC-native capabilities to add next.

Related Skills

Explore More Software Engineering Skills→
Clean1inesClean1ines

workspace-surface-audit

Audit repository workspace surfaces and MCP configurations to generate gap-driven recommendations.

Community
Advanced
sakamoto-family-smilesakamoto-family-smile

workspace-surface-audit

Audit workspace surfaces and recommend ECC-native skills, hooks, and agents.

Community
Advanced
henmessihenmessi
1

MCP Integration

Configure MCP servers for Claude Code plugins with environment expansion.

Community
Advanced
mostafa-ismail-2004mostafa-ismail-2004

workspace-surface-audit

Audit Codex workspace surfaces and identify missing workflow coverage.

Community
Advanced