[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739S697NGSXTQ13Q69VB2MY":3,"skill-same:01M739S697NGSXTQ13Q69VB2MY":51},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M739S697NGSXTQ13Q69VB2MY","cbm-query",null,"Query the Yana AI codebase knowledge graph via codebase-memory-mcp. Use instead of grep\u002Fglob when exploring call chains, finding callers\u002Fcallees, understanding architecture, or tracing impact of changes. Triggers on: 'who calls X', 'trace path', 'find callers', 'search graph', 'cbm', 'knowledge graph', 'what calls', 'call chain', 'what uses', 'where is X defined', 'architecture overview', 'impact of changing'.","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\u002Fcbm-query\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: cbm-query\ndescription: \"Query the Yana AI codebase knowledge graph via codebase-memory-mcp. Use instead of grep\u002Fglob when exploring call chains, finding callers\u002Fcallees, understanding architecture, or tracing impact of changes. Triggers on: 'who calls X', 'trace path', 'find callers', 'search graph', 'cbm', 'knowledge graph', 'what calls', 'call chain', 'what uses', 'where is X defined', 'architecture overview', 'impact of changing'.\"\nsource: DeusData\u002Fcodebase-memory-mcp (MIT)\ntier: TIER 2 — CORRECTNESS\nproject: Users-vutam-Desktop-Yana-AI\n---\n\n# \u002Fcbm-query — Codebase Knowledge Graph\n\nQuery the Yana AI knowledge graph (35K nodes, 68K edges) instead of file-by-file grep.\nAnswers structural questions in \u003C1ms. 10× fewer tokens than grepping files.\n\n**When to use instead of grep\u002Fglob:**\n- \"Who calls `function_name`?\" → `trace_path` (callers)\n- \"What does this function call?\" → `trace_path` (callees)\n- \"Find anything named X\" → `search_graph`\n- \"What changed and what broke?\" → `detect_changes`\n- \"Overview of the codebase\" → `get_architecture`\n- \"Show me the actual code\" → `get_code_snippet` (after finding via search_graph)\n\n**Do NOT use for:** reading config files, editing, writing — graph is read-only structural index.\n\n---\n\n## Project name (always pass this)\n\n```\nproject: \"Users-vutam-Desktop-Yana-AI\"\n```\n\nIf the project is not found, re-index first:\n```\nindex_repository(repo_path=\"\u002FUsers\u002Fvutam\u002FDesktop\u002FYana-AI\", project_name=\"yana-ai\")\n```\n\n---\n\n## Tool Playbook\n\n### 1. Find a symbol — `search_graph`\n\n```\nsearch_graph(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  query=\"\u003Cname or keyword>\",\n  limit=10                    # default 10, max 50\n)\n```\n\nReturns: name, qualified_name, label (Function\u002FClass\u002FPackage), file_path, start_line.\n\n**Label filter examples:**\n- Functions only: add `label=\"Function\"`\n- Classes only: add `label=\"Class\"`\n\n---\n\n### 2. Trace call chains — `trace_path`\n\n```\ntrace_path(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  function_name=\"\u003Cexact name from search_graph>\",\n  direction=\"callers\",   # or \"callees\" or \"both\"\n  depth=3                # how many hops (default 3, max 10)\n)\n```\n\n**Workflow:** always `search_graph` first to get the exact `name`, then `trace_path`.\n\n---\n\n### 3. Get actual code — `get_code_snippet`\n\n```\nget_code_snippet(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  qualified_name=\"\u003Cqualified_name from search_graph result>\"\n)\n```\n\n**Use `qualified_name` (not `function_name`)** — copy from search_graph result field.\nExample: `Users-vutam-Desktop-Yana-AI.core.lib.hermes_adapted.context_compressor.ContextCompressor.compress`\n\n---\n\n### 4. Architecture overview — `get_architecture`\n\n```\nget_architecture(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  aspects=[\"languages\", \"clusters\"]   # or [\"all\"]\n)\n```\n\nReturns: language breakdown, package clusters, service boundaries.\n\n---\n\n### 5. Impact of git changes — `detect_changes`\n\n```\ndetect_changes(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  since=\"HEAD~1\"    # or a commit SHA, or \"HEAD~5\"\n)\n```\n\nReturns which functions changed and which callers are potentially affected.\nUse before a refactor to understand blast radius.\n\n---\n\n### 6. Text search (graph-augmented grep) — `search_code`\n\n```\nsearch_code(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  pattern=\"\u003Cregex or text>\",\n  file_filter=\"*.sh\"    # optional\n)\n```\n\nFaster than raw grep — filtered through graph context.\n\n---\n\n### 7. Complex structural query — `query_graph`\n\n```\nquery_graph(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  cypher=\"MATCH (f:Function)-[:CALLS]->(g:Function) WHERE f.name = 'X' RETURN g.name, g.file_path LIMIT 20\"\n)\n```\n\nUse when the other tools don't cover the exact relationship you need.\n\n---\n\n## Standard Workflow\n\n```\nUser: \"who calls check_egress_target?\"\n\n1. search_graph(query=\"check_egress_target\") → get exact name + file\n2. trace_path(function_name=\"check_egress_target\", direction=\"callers\", depth=3)\n3. If code needed: get_code_snippet(function_name=\"check_egress_target\")\n4. Report: callers list + file locations\n```\n\n---\n\n## Output Contract\n\n```\nSymbol found:   [name] at [file:line]\nCallers\u002Fcallees: [list with file paths]\nCode snippet:   [if requested]\nConfidence:     [95% if found in graph, 60% if not found — may need re-index]\n```\n\nIf symbol not found in graph:\n- Check spelling via `search_graph` with a broader query\n- If still missing: run `index_status` to check freshness, re-index if stale\n\n---\n\n## In-Skill Verification\n\nAfter every `trace_path` result:\n1. Spot-check 1 caller by reading the actual file — confirm the call exists\n2. If graph says \"no callers\" but you expect some → re-index and retry once\n\n---\n\n## Anti-patterns\n\n```\n❌ Using grep to find \"who calls X\" when cbm-query can do it in \u003C1ms\n❌ Passing a fuzzy name to trace_path without search_graph first (will fail)\n❌ Using query_graph for simple lookups — search_graph is faster\n❌ Forgetting to pass project= (required on every call)\n```\n","# \u002Fcbm-query — Codebase Knowledge Graph\n\nQuery the Yana AI knowledge graph (35K nodes, 68K edges) instead of file-by-file grep.\nAnswers structural questions in \u003C1ms. 10× fewer tokens than grepping files.\n\n**When to use instead of grep\u002Fglob:**\n- \"Who calls `function_name`?\" → `trace_path` (callers)\n- \"What does this function call?\" → `trace_path` (callees)\n- \"Find anything named X\" → `search_graph`\n- \"What changed and what broke?\" → `detect_changes`\n- \"Overview of the codebase\" → `get_architecture`\n- \"Show me the actual code\" → `get_code_snippet` (after finding via search_graph)\n\n**Do NOT use for:** reading config files, editing, writing — graph is read-only structural index.\n\n---\n\n## Project name (always pass this)\n\n```\nproject: \"Users-vutam-Desktop-Yana-AI\"\n```\n\nIf the project is not found, re-index first:\n```\nindex_repository(repo_path=\"\u002FUsers\u002Fvutam\u002FDesktop\u002FYana-AI\", project_name=\"yana-ai\")\n```\n\n---\n\n## Tool Playbook\n\n### 1. Find a symbol — `search_graph`\n\n```\nsearch_graph(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  query=\"\u003Cname or keyword>\",\n  limit=10                    # default 10, max 50\n)\n```\n\nReturns: name, qualified_name, label (Function\u002FClass\u002FPackage), file_path, start_line.\n\n**Label filter examples:**\n- Functions only: add `label=\"Function\"`\n- Classes only: add `label=\"Class\"`\n\n---\n\n### 2. Trace call chains — `trace_path`\n\n```\ntrace_path(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  function_name=\"\u003Cexact name from search_graph>\",\n  direction=\"callers\",   # or \"callees\" or \"both\"\n  depth=3                # how many hops (default 3, max 10)\n)\n```\n\n**Workflow:** always `search_graph` first to get the exact `name`, then `trace_path`.\n\n---\n\n### 3. Get actual code — `get_code_snippet`\n\n```\nget_code_snippet(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  qualified_name=\"\u003Cqualified_name from search_graph result>\"\n)\n```\n\n**Use `qualified_name` (not `function_name`)** — copy from search_graph result field.\nExample: `Users-vutam-Desktop-Yana-AI.core.lib.hermes_adapted.context_compressor.ContextCompressor.compress`\n\n---\n\n### 4. Architecture overview — `get_architecture`\n\n```\nget_architecture(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  aspects=[\"languages\", \"clusters\"]   # or [\"all\"]\n)\n```\n\nReturns: language breakdown, package clusters, service boundaries.\n\n---\n\n### 5. Impact of git changes — `detect_changes`\n\n```\ndetect_changes(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  since=\"HEAD~1\"    # or a commit SHA, or \"HEAD~5\"\n)\n```\n\nReturns which functions changed and which callers are potentially affected.\nUse before a refactor to understand blast radius.\n\n---\n\n### 6. Text search (graph-augmented grep) — `search_code`\n\n```\nsearch_code(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  pattern=\"\u003Cregex or text>\",\n  file_filter=\"*.sh\"    # optional\n)\n```\n\nFaster than raw grep — filtered through graph context.\n\n---\n\n### 7. Complex structural query — `query_graph`\n\n```\nquery_graph(\n  project=\"Users-vutam-Desktop-Yana-AI\",\n  cypher=\"MATCH (f:Function)-[:CALLS]->(g:Function) WHERE f.name = 'X' RETURN g.name, g.file_path LIMIT 20\"\n)\n```\n\nUse when the other tools don't cover the exact relationship you need.\n\n---\n\n## Standard Workflow\n\n```\nUser: \"who calls check_egress_target?\"\n\n1. search_graph(query=\"check_egress_target\") → get exact name + file\n2. trace_path(function_name=\"check_egress_target\", direction=\"callers\", depth=3)\n3. If code needed: get_code_snippet(function_name=\"check_egress_target\")\n4. Report: callers list + file locations\n```\n\n---\n\n## Output Contract\n\n```\nSymbol found:   [name] at [file:line]\nCallers\u002Fcallees: [list with file paths]\nCode snippet:   [if requested]\nConfidence:     [95% if found in graph, 60% if not found — may need re-index]\n```\n\nIf symbol not found in graph:\n- Check spelling via `search_graph` with a broader query\n- If still missing: run `index_status` to check freshness, re-index if stale\n\n---\n\n## In-Skill Verification\n\nAfter every `trace_path` result:\n1. Spot-check 1 caller by reading the actual file — confirm the call exists\n2. If graph says \"no callers\" but you expect some → re-index and retry once\n\n---\n\n## Anti-patterns\n\n```\n❌ Using grep to find \"who calls X\" when cbm-query can do it in \u003C1ms\n❌ Passing a fuzzy name to trace_path without search_graph first (will fail)\n❌ Using query_graph for simple lookups — search_graph is faster\n❌ Forgetting to pass project= (required on every call)\n```\n",{"name":5,"tier":24,"source":25,"project":26,"description":7},"TIER 2 — CORRECTNESS","DeusData\u002Fcodebase-memory-mcp (MIT)","Users-vutam-Desktop-Yana-AI","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fcbm-query",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill cbm-query",{"tool":43,"command":44},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill cbm-query",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill cbm-query","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcbm-query\u002FSKILL.md",true,[],[52,60,67,75,83,91],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"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},"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":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":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"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":94,"categories":95,"keywords":96,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]