[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BQCQK8JSTTWD8C0F3BCG2":3,"skill-same:01M73BQCQK8JSTTWD8C0F3BCG2":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M73BQCQK8JSTTWD8C0F3BCG2","gitnexus-debugging",null,"Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\"","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\u002Fgitnexus-debugging\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: gitnexus-debugging\ndescription: \"Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \\\"Why is X failing?\\\", \\\"Where does this error come from?\\\", \\\"Trace this bug\\\"\"\n---\n\n# Debugging with GitNexus\n\n## When to Use\n\n- \"Why is this function failing?\"\n- \"Trace where this error comes from\"\n- \"Who calls this method?\"\n- \"This endpoint returns 500\"\n- Investigating bugs, errors, or unexpected behavior\n\n## Workflow\n\n```\n1. gitnexus_query({query: \"\u003Cerror or symptom>\"})            → Find related execution flows\n2. gitnexus_context({name: \"\u003Csuspect>\"})                    → See callers\u002Fcallees\u002Fprocesses\n3. READ gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocess\u002F{name}                → Trace execution flow\n4. gitnexus_cypher({query: \"MATCH path...\"})                 → Custom traces if needed\n```\n\n> If \"Index is stale\" → run `npx gitnexus analyze` in terminal.\n\n## Checklist\n\n```\n- [ ] Understand the symptom (error message, unexpected behavior)\n- [ ] gitnexus_query for error text or related code\n- [ ] Identify the suspect function from returned processes\n- [ ] gitnexus_context to see callers and callees\n- [ ] Trace execution flow via process resource if applicable\n- [ ] gitnexus_cypher for custom call chain traces if needed\n- [ ] Read source files to confirm root cause\n```\n\n## Debugging Patterns\n\n| Symptom              | GitNexus Approach                                          |\n| -------------------- | ---------------------------------------------------------- |\n| Error message        | `gitnexus_query` for error text → `context` on throw sites |\n| Wrong return value   | `context` on the function → trace callees for data flow    |\n| Intermittent failure | `context` → look for external calls, async deps            |\n| Performance issue    | `context` → find symbols with many callers (hot paths)     |\n| Recent regression    | `detect_changes` to see what your changes affect           |\n\n## Tools\n\n**gitnexus_query** — find code related to error:\n\n```\ngitnexus_query({query: \"payment validation error\"})\n→ Processes: CheckoutFlow, ErrorHandling\n→ Symbols: validatePayment, handlePaymentError, PaymentException\n```\n\n**gitnexus_context** — full context for a suspect:\n\n```\ngitnexus_context({name: \"validatePayment\"})\n→ Incoming calls: processCheckout, webhookHandler\n→ Outgoing calls: verifyCard, fetchRates (external API!)\n→ Processes: CheckoutFlow (step 3\u002F7)\n```\n\n**gitnexus_cypher** — custom call chain traces:\n\n```cypher\nMATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: \"validatePayment\"})\nRETURN [n IN nodes(path) | n.name] AS chain\n```\n\n## Example: \"Payment endpoint returns 500 intermittently\"\n\n```\n1. gitnexus_query({query: \"payment error handling\"})\n   → Processes: CheckoutFlow, ErrorHandling\n   → Symbols: validatePayment, handlePaymentError\n\n2. gitnexus_context({name: \"validatePayment\"})\n   → Outgoing calls: verifyCard, fetchRates (external API!)\n\n3. READ gitnexus:\u002F\u002Frepo\u002Fmy-app\u002Fprocess\u002FCheckoutFlow\n   → Step 3: validatePayment → calls fetchRates (external)\n\n4. Root cause: fetchRates calls external API without proper timeout\n```\n","# Debugging with GitNexus\n\n## When to Use\n\n- \"Why is this function failing?\"\n- \"Trace where this error comes from\"\n- \"Who calls this method?\"\n- \"This endpoint returns 500\"\n- Investigating bugs, errors, or unexpected behavior\n\n## Workflow\n\n```\n1. gitnexus_query({query: \"\u003Cerror or symptom>\"})            → Find related execution flows\n2. gitnexus_context({name: \"\u003Csuspect>\"})                    → See callers\u002Fcallees\u002Fprocesses\n3. READ gitnexus:\u002F\u002Frepo\u002F{name}\u002Fprocess\u002F{name}                → Trace execution flow\n4. gitnexus_cypher({query: \"MATCH path...\"})                 → Custom traces if needed\n```\n\n> If \"Index is stale\" → run `npx gitnexus analyze` in terminal.\n\n## Checklist\n\n```\n- [ ] Understand the symptom (error message, unexpected behavior)\n- [ ] gitnexus_query for error text or related code\n- [ ] Identify the suspect function from returned processes\n- [ ] gitnexus_context to see callers and callees\n- [ ] Trace execution flow via process resource if applicable\n- [ ] gitnexus_cypher for custom call chain traces if needed\n- [ ] Read source files to confirm root cause\n```\n\n## Debugging Patterns\n\n| Symptom              | GitNexus Approach                                          |\n| -------------------- | ---------------------------------------------------------- |\n| Error message        | `gitnexus_query` for error text → `context` on throw sites |\n| Wrong return value   | `context` on the function → trace callees for data flow    |\n| Intermittent failure | `context` → look for external calls, async deps            |\n| Performance issue    | `context` → find symbols with many callers (hot paths)     |\n| Recent regression    | `detect_changes` to see what your changes affect           |\n\n## Tools\n\n**gitnexus_query** — find code related to error:\n\n```\ngitnexus_query({query: \"payment validation error\"})\n→ Processes: CheckoutFlow, ErrorHandling\n→ Symbols: validatePayment, handlePaymentError, PaymentException\n```\n\n**gitnexus_context** — full context for a suspect:\n\n```\ngitnexus_context({name: \"validatePayment\"})\n→ Incoming calls: processCheckout, webhookHandler\n→ Outgoing calls: verifyCard, fetchRates (external API!)\n→ Processes: CheckoutFlow (step 3\u002F7)\n```\n\n**gitnexus_cypher** — custom call chain traces:\n\n```cypher\nMATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: \"validatePayment\"})\nRETURN [n IN nodes(path) | n.name] AS chain\n```\n\n## Example: \"Payment endpoint returns 500 intermittently\"\n\n```\n1. gitnexus_query({query: \"payment error handling\"})\n   → Processes: CheckoutFlow, ErrorHandling\n   → Symbols: validatePayment, handlePaymentError\n\n2. gitnexus_context({name: \"validatePayment\"})\n   → Outgoing calls: verifyCard, fetchRates (external API!)\n\n3. READ gitnexus:\u002F\u002Frepo\u002Fmy-app\u002Fprocess\u002FCheckoutFlow\n   → Step 3: validatePayment → calls fetchRates (external)\n\n4. Root cause: fetchRates calls external API without proper timeout\n```\n",{"name":5,"description":7},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fgitnexus-debugging",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill gitnexus-debugging",{"tool":40,"command":41},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill gitnexus-debugging",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill gitnexus-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fgitnexus-debugging\u002FSKILL.md",true,[],[49,57,64,72,80,88],{"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":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":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},"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":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":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"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":91,"categories":92,"keywords":93,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]