Workspace surface audit: read-only inventory of your agent setup and what to add next
Read-only audit of active repos, MCP servers, plugins, connectors, env surface and tool setup — recommends the highest-value ECC-native skills, hooks, agents and operator workflows
- What
- Read-only audit of active repos, MCP servers, plugins, connectors, env surface and tool setup — recommends the highest-value ECC-native skills, hooks, agents and operator workflows
- Cost
- Free
- Needs
- nothing to install — the skill is a read-only audit methodology your agent follows; no accounts, keys, or runtime dependencies
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's read-only audit for your agent workspace and machine: it answers "what can this workspace actually do right now, and what should I add or enable next?" in three phases — inventory everything (repo surface: package.json, `.mcp.json`, `.claude/settings*.json`, `AGENTS.md`; env surface showing only key names like `STRIPE_API_KEY`, never values; installed plugins, connected apps, MCP/LSP servers; existing ECC skills), benchmark against official and installed plugin surfaces (what each does, whether ECC matches it, has only a raw form of it, or fully lacks it), then convert each real gap into the right ECC-native form (repeatable workflow → skill, side effects → hook, delegated role → agent, external bridge → MCP server or connector). Outputs a five-section report: current surface, parity, raw-only gaps, missing integrations, and the top 3–5 next steps by impact. Non-negotiable rules: never print secret values (provider names, key names and file paths only), never modify files unless explicitly asked, and treat external plugins as inspiration — never as the authority. Honest caveats: **the skill is written in Japanese** (lives under `docs/ja-JP/`); it is an ECC-ecosystem skill, so parts of its vocabulary assume you use that setup. MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing to install — the skill is a read-only audit methodology your agent follows; no accounts, keys, or runtime dependencies Install "Workspace surface audit: read-only inventory of your agent setup and what to add next" for me. It gives my agent @affaan-m's audit workflow: inventory the repo surface (package.json, .mcp.json, .claude/settings*.json, AGENTS.md), the env surface (key names only, never values), installed plugins, connected apps, MCP/LSP servers, and existing ECC skills; benchmark the workspace against official and installed plugin surfaces; convert each real gap into the right ECC-native form (skill, hook, agent, MCP server or connector); and deliver a five-section report with the top 3-5 next steps by impact. Never prints secret values and never modifies files unless asked. Written in Japanese; MIT-licensed. Repository: https://github.com/affaan-m/ecc/blob/main/docs/ja-JP/skills/workspace-surface-audit/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "workspace-surface-audit". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a methodology; ask the agent to audit your setup the next time you wonder what is actually available or what to add). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.