[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M731GKBHH5EC06CCDYQGTMAG":3,"skill-same:01M731GKBHH5EC06CCDYQGTMAG":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M731GKBHH5EC06CCDYQGTMAG","workspace-surface-audit",null,"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 understanding what capabilities are actually available in their environment.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: workspace-surface-audit\ndescription: 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 understanding what capabilities are actually available in their environment.\norigin: ECC\n---\n\n# Workspace Surface Audit\n\nRead-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?\"\n\nThis is the ECC-native answer to setup-audit plugins. It does not modify files unless the user explicitly asks for follow-up implementation.\n\n## When to Use\n\n- User says \"set up Claude Code\", \"recommend automations\", \"what plugins or MCPs should I use?\", or \"what am I missing?\"\n- Auditing a machine or repo before installing more skills, hooks, or connectors\n- Comparing official marketplace plugins against ECC-native coverage\n- Reviewing `.env`, `.mcp.json`, plugin settings, or connected-app surfaces to find missing workflow layers\n- Deciding whether a capability should be a skill, hook, agent, MCP, or external connector\n\n## Non-Negotiable Rules\n\n- Never print secret values. Surface only provider names, capability names, file paths, and whether a key or config exists.\n- Prefer ECC-native workflows over generic \"install another plugin\" advice when ECC can reasonably own the surface.\n- Treat external plugins as benchmarks and inspiration, not authoritative product boundaries.\n- Separate three things clearly:\n  - already available now\n  - available but not wrapped well in ECC\n  - not available and would require a new integration\n\n## Audit Inputs\n\nInspect only the files and settings needed to answer the question well:\n\n1. Repo surface\n   - `package.json`, lockfiles, language markers, framework config, `README.md`\n   - `.mcp.json`, `.lsp.json`, `.claude\u002Fsettings*.json`, `.codex\u002F*`\n   - `AGENTS.md`, `CLAUDE.md`, install manifests, hook configs\n2. Environment surface\n   - `.env*` files in the active repo and obvious adjacent ECC workspaces\n   - Surface only key names such as `STRIPE_API_KEY`, `TWILIO_AUTH_TOKEN`, `FAL_KEY`\n3. Connected tool surface\n   - Installed plugins, enabled connectors, MCP servers, LSPs, and app integrations\n4. ECC surface\n   - Existing skills, commands, hooks, agents, and install modules that already cover the need\n\n## Audit Process\n\n### Phase 1: Inventory What Exists\n\nProduce a compact inventory:\n\n- active harness targets\n- installed plugins and connected apps\n- configured MCP servers\n- configured LSP servers\n- env-backed services implied by key names\n- existing ECC skills already relevant to the workspace\n\nIf a surface exists only as a primitive, call that out. Example:\n\n- \"Stripe is available via connected app, but ECC lacks a billing-operator skill\"\n- \"Google Drive is connected, but there is no ECC-native Google Workspace operator workflow\"\n\n### Phase 2: Benchmark Against Official and Installed Surfaces\n\nCompare the workspace against:\n\n- official Claude plugins that overlap with setup, review, docs, design, or workflow quality\n- locally installed plugins in Claude or Codex\n- the user's currently connected app surfaces\n\nDo not just list names. For each comparison, answer:\n\n1. what they actually do\n2. whether ECC already has parity\n3. whether ECC only has primitives\n4. whether ECC is missing the workflow entirely\n\n### Phase 3: Turn Gaps Into ECC Decisions\n\nFor every real gap, recommend the correct ECC-native shape:\n\n| Gap Type | Preferred ECC Shape |\n|----------|---------------------|\n| Repeatable operator workflow | Skill |\n| Automatic enforcement or side-effect | Hook |\n| Specialized delegated role | Agent |\n| External tool bridge | MCP server or connector |\n| Install\u002Fbootstrap guidance | Setup or audit skill |\n\nDefault to user-facing skills that orchestrate existing tools when the need is operational rather than infrastructural.\n\n## Output Format\n\nReturn five sections in this order:\n\n1. **Current surface**\n   - what is already usable right now\n2. **Parity**\n   - where ECC already matches or exceeds the benchmark\n3. **Primitive-only gaps**\n   - tools exist, but ECC lacks a clean operator skill\n4. **Missing integrations**\n   - capability not available yet\n5. **Top 3-5 next moves**\n   - concrete ECC-native additions, ordered by impact\n\n## Recommendation Rules\n\n- Recommend at most 1-2 highest-value ideas per category.\n- Favor skills with obvious user intent and business value:\n  - setup audit\n  - billing\u002Fcustomer ops\n  - issue\u002Fprogram ops\n  - Google Workspace ops\n  - deployment\u002Fops control\n- If a connector is company-specific, recommend it only when it is genuinely available or clearly useful to the user's workflow.\n- If ECC already has a strong primitive, propose a wrapper skill instead of inventing a brand-new subsystem.\n\n## Good Outcomes\n\n- The user can immediately see what is connected, what is missing, and what ECC should own next.\n- Recommendations are specific enough to implement in the repo without another discovery pass.\n- The final answer is organized around workflows, not API brands.\n","# Workspace Surface Audit\n\nRead-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?\"\n\nThis is the ECC-native answer to setup-audit plugins. It does not modify files unless the user explicitly asks for follow-up implementation.\n\n## When to Use\n\n- User says \"set up Claude Code\", \"recommend automations\", \"what plugins or MCPs should I use?\", or \"what am I missing?\"\n- Auditing a machine or repo before installing more skills, hooks, or connectors\n- Comparing official marketplace plugins against ECC-native coverage\n- Reviewing `.env`, `.mcp.json`, plugin settings, or connected-app surfaces to find missing workflow layers\n- Deciding whether a capability should be a skill, hook, agent, MCP, or external connector\n\n## Non-Negotiable Rules\n\n- Never print secret values. Surface only provider names, capability names, file paths, and whether a key or config exists.\n- Prefer ECC-native workflows over generic \"install another plugin\" advice when ECC can reasonably own the surface.\n- Treat external plugins as benchmarks and inspiration, not authoritative product boundaries.\n- Separate three things clearly:\n  - already available now\n  - available but not wrapped well in ECC\n  - not available and would require a new integration\n\n## Audit Inputs\n\nInspect only the files and settings needed to answer the question well:\n\n1. Repo surface\n   - `package.json`, lockfiles, language markers, framework config, `README.md`\n   - `.mcp.json`, `.lsp.json`, `.claude\u002Fsettings*.json`, `.codex\u002F*`\n   - `AGENTS.md`, `CLAUDE.md`, install manifests, hook configs\n2. Environment surface\n   - `.env*` files in the active repo and obvious adjacent ECC workspaces\n   - Surface only key names such as `STRIPE_API_KEY`, `TWILIO_AUTH_TOKEN`, `FAL_KEY`\n3. Connected tool surface\n   - Installed plugins, enabled connectors, MCP servers, LSPs, and app integrations\n4. ECC surface\n   - Existing skills, commands, hooks, agents, and install modules that already cover the need\n\n## Audit Process\n\n### Phase 1: Inventory What Exists\n\nProduce a compact inventory:\n\n- active harness targets\n- installed plugins and connected apps\n- configured MCP servers\n- configured LSP servers\n- env-backed services implied by key names\n- existing ECC skills already relevant to the workspace\n\nIf a surface exists only as a primitive, call that out. Example:\n\n- \"Stripe is available via connected app, but ECC lacks a billing-operator skill\"\n- \"Google Drive is connected, but there is no ECC-native Google Workspace operator workflow\"\n\n### Phase 2: Benchmark Against Official and Installed Surfaces\n\nCompare the workspace against:\n\n- official Claude plugins that overlap with setup, review, docs, design, or workflow quality\n- locally installed plugins in Claude or Codex\n- the user's currently connected app surfaces\n\nDo not just list names. For each comparison, answer:\n\n1. what they actually do\n2. whether ECC already has parity\n3. whether ECC only has primitives\n4. whether ECC is missing the workflow entirely\n\n### Phase 3: Turn Gaps Into ECC Decisions\n\nFor every real gap, recommend the correct ECC-native shape:\n\n| Gap Type | Preferred ECC Shape |\n|----------|---------------------|\n| Repeatable operator workflow | Skill |\n| Automatic enforcement or side-effect | Hook |\n| Specialized delegated role | Agent |\n| External tool bridge | MCP server or connector |\n| Install\u002Fbootstrap guidance | Setup or audit skill |\n\nDefault to user-facing skills that orchestrate existing tools when the need is operational rather than infrastructural.\n\n## Output Format\n\nReturn five sections in this order:\n\n1. **Current surface**\n   - what is already usable right now\n2. **Parity**\n   - where ECC already matches or exceeds the benchmark\n3. **Primitive-only gaps**\n   - tools exist, but ECC lacks a clean operator skill\n4. **Missing integrations**\n   - capability not available yet\n5. **Top 3-5 next moves**\n   - concrete ECC-native additions, ordered by impact\n\n## Recommendation Rules\n\n- Recommend at most 1-2 highest-value ideas per category.\n- Favor skills with obvious user intent and business value:\n  - setup audit\n  - billing\u002Fcustomer ops\n  - issue\u002Fprogram ops\n  - Google Workspace ops\n  - deployment\u002Fops control\n- If a connector is company-specific, recommend it only when it is genuinely available or clearly useful to the user's workflow.\n- If ECC already has a strong primitive, propose a wrapper skill instead of inventing a brand-new subsystem.\n\n## Good Outcomes\n\n- The user can immediately see what is connected, what is missing, and what ECC should own next.\n- Recommendations are specific enough to implement in the repo without another discovery pass.\n- The final answer is organized around workflows, not API brands.\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Fworkspace-surface-audit",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill workspace-surface-audit",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill workspace-surface-audit",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill workspace-surface-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]