[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KNFAQSFB8ZWGQS7C5ESEC":3,"skill-same:01M75KNFAQSFB8ZWGQS7C5ESEC":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75KNFAQSFB8ZWGQS7C5ESEC","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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":23,"description":7},"ECC","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fworkspace-surface-audit",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill workspace-surface-audit",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill workspace-surface-audit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill workspace-surface-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]