[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77YAFQ75704M6SESYH4B2C2":3,"skill-same:01M77YAFQ75704M6SESYH4B2C2":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M77YAFQ75704M6SESYH4B2C2","workspace-surface-audit",null,"Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value HCP-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.","503496348-ops\u002Fmischief-production","503496348-ops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266905914?v=4","01M77X5J7XQWWZGT8998HDGXQM","AtomCollide","01M77X5J8V78Y3NXMY6BBC75X9",2,"MIT","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-workspace-surface-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: workspace-surface-audit\ndescription: Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value HCP-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.\nmetadata:\n  origin: HCP\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 HCP-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 HCP-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 HCP-native workflows over generic \"install another plugin\" advice when HCP 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 HCP\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 HCP 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. HCP 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 HCP 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 HCP lacks a billing-operator skill\"\n- \"Google Drive is connected, but there is no HCP-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 HCP already has parity\n3. whether HCP only has primitives\n4. whether HCP is missing the workflow entirely\n\n### Phase 3: Turn Gaps Into HCP Decisions\n\nFor every real gap, recommend the correct HCP-native shape:\n\n| Gap Type | Preferred HCP 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 HCP already matches or exceeds the benchmark\n3. **Primitive-only gaps**\n   - tools exist, but HCP lacks a clean operator skill\n4. **Missing integrations**\n   - capability not available yet\n5. **Top 3-5 next moves**\n   - concrete HCP-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 HCP 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 HCP 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 HCP-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 HCP-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 HCP-native workflows over generic \"install another plugin\" advice when HCP 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 HCP\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 HCP 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. HCP 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 HCP 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 HCP lacks a billing-operator skill\"\n- \"Google Drive is connected, but there is no HCP-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 HCP already has parity\n3. whether HCP only has primitives\n4. whether HCP is missing the workflow entirely\n\n### Phase 3: Turn Gaps Into HCP Decisions\n\nFor every real gap, recommend the correct HCP-native shape:\n\n| Gap Type | Preferred HCP 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 HCP already matches or exceeds the benchmark\n3. **Primitive-only gaps**\n   - tools exist, but HCP lacks a clean operator skill\n4. **Missing integrations**\n   - capability not available yet\n5. **Top 3-5 next moves**\n   - concrete HCP-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 HCP 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 HCP 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,"metadata":24,"description":7},{"origin":25},"HCP","main","c9103dbad48ef3005f163584d0f2abd4591217f6","skills\u002Fecc-workspace-surface-audit",1,"https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production","https:\u002F\u002Fgithub.com\u002F503496348-ops","https:\u002F\u002F503496348-ops.github.io\u002Fatomcollide-product-matrix\u002F#tree","元素碰撞-AtomCollide-AI 智能体实验室 测试人专属成长社群 正式招募\r\n我们的目标很纯粹：连接每一位测试工程师\u002FAI使用探索与爱好者，让你在这里既能扎实打磨技术硬实力，也能打通职业晋升的新通路，这是一个专注于AI领域的开源组","2026-07-30 00:35:42",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add 503496348-ops\u002Fmischief-production --skill workspace-surface-audit",{"tool":41,"command":42},"bunx","bunx skills add 503496348-ops\u002Fmischief-production --skill workspace-surface-audit",{"tool":44,"command":45},"pnpm","pnpm dlx skills add 503496348-ops\u002Fmischief-production --skill workspace-surface-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fecc-workspace-surface-audit\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M77YG7NPZHE751W9QGK3H9ED","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-skills\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77YG4HPYH0GJP974DZ6KCPQ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-plans\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77YFZW1FZ1GVC5C89NPE5M8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77YFVPWANT5VE5GWBTKHPA2","using-智械工程","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-superpowers\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77YFQJAW5PX3QYSBCD3B24S","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77YFMSTB70VX8W2QHNJWYB0","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-test-driven-development\u002FSKILL.md",[],[]]