[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GPMPDYD2FWCPYVWZ4SFZF":3,"skill-same:01M73GPMPDYD2FWCPYVWZ4SFZF":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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73GPMPDYD2FWCPYVWZ4SFZF","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.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\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","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fworkspace-surface-audit",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill workspace-surface-audit",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill workspace-surface-audit",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill workspace-surface-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"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":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\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":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]