[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DGR5DCGPV889H57302BKD":3,"skill-same:01M73DGR5DCGPV889H57302BKD":50},{"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":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M73DGR5DCGPV889H57302BKD","latency-critical-systems",null,"Use for latency-sensitive systems such as realtime dashboards, market data, streaming agents, execution gateways, queues, caches, or HFT-like infrastructure where freshness and p95 latency matter.","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\u002Flatency-critical-systems\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: latency-critical-systems\ndescription: Use for latency-sensitive systems such as realtime dashboards, market data, streaming agents, execution gateways, queues, caches, or HFT-like infrastructure where freshness and p95 latency matter.\norigin: ECC\ntools: Read, Write, Edit, Bash, Grep, Glob\n---\n\n# Latency Critical Systems\n\nUse this skill when the user cares about realtime behavior, hot paths, streaming\nfreshness, or execution speed. This includes HFT-like infrastructure, but the\nskill is engineering-focused. It does not authorize live trading or financial\nadvice.\n\n## Split The Metrics\n\nDo not collapse everything into \"fast.\" Track:\n\n- p50, p95, and p99 latency;\n- throughput;\n- freshness age;\n- queue depth;\n- cache hit rate;\n- provider\u002FAPI response time;\n- browser render time;\n- correctness under load;\n- failure and retry behavior.\n\n## Map The Hot Path\n\nWrite the path from user\u002Fevent to final visible state:\n\n```text\nsource event -> provider API -> ingest worker -> queue -> cache -> edge route\n-> client stream -> browser render -> user-visible state\n```\n\nThen measure each segment separately.\n\n## Optimization Order\n\n1. Remove unnecessary round trips.\n2. Cache stable reads with freshness metadata.\n3. Batch small calls and writes.\n4. Move compute closer to the data or the user.\n5. Split hot and cold paths.\n6. Apply backpressure before queues grow unbounded.\n7. Use streaming only when it improves freshness or user experience.\n8. Add canaries for stale data, degraded providers, and bad cache state.\n\n## Verification\n\nUse live readbacks when a deployed surface exists:\n\n- HTTP timing and response headers;\n- provider freshness timestamp;\n- queue or job state;\n- edge\u002Fcache state;\n- browser verification for actual UI freshness;\n- logs around retries and degraded mode.\n\nFor market-data or execution-adjacent paths, also verify orderbook age, VWAP\nassumptions, provider status, and kill-switch behavior before calling the path\nready.\n\n## Guardrails\n\n- Do not optimize latency by dropping required validation.\n- Do not hide stale data behind fast cache hits.\n- Do not claim millisecond behavior from client labels without measurement.\n- Do not run live orders, destructive migrations, or customer-impacting deploys\n  without an explicit approval gate.\n- Keep secrets and private payloads out of logs and benchmark artifacts.\n","# Latency Critical Systems\n\nUse this skill when the user cares about realtime behavior, hot paths, streaming\nfreshness, or execution speed. This includes HFT-like infrastructure, but the\nskill is engineering-focused. It does not authorize live trading or financial\nadvice.\n\n## Split The Metrics\n\nDo not collapse everything into \"fast.\" Track:\n\n- p50, p95, and p99 latency;\n- throughput;\n- freshness age;\n- queue depth;\n- cache hit rate;\n- provider\u002FAPI response time;\n- browser render time;\n- correctness under load;\n- failure and retry behavior.\n\n## Map The Hot Path\n\nWrite the path from user\u002Fevent to final visible state:\n\n```text\nsource event -> provider API -> ingest worker -> queue -> cache -> edge route\n-> client stream -> browser render -> user-visible state\n```\n\nThen measure each segment separately.\n\n## Optimization Order\n\n1. Remove unnecessary round trips.\n2. Cache stable reads with freshness metadata.\n3. Batch small calls and writes.\n4. Move compute closer to the data or the user.\n5. Split hot and cold paths.\n6. Apply backpressure before queues grow unbounded.\n7. Use streaming only when it improves freshness or user experience.\n8. Add canaries for stale data, degraded providers, and bad cache state.\n\n## Verification\n\nUse live readbacks when a deployed surface exists:\n\n- HTTP timing and response headers;\n- provider freshness timestamp;\n- queue or job state;\n- edge\u002Fcache state;\n- browser verification for actual UI freshness;\n- logs around retries and degraded mode.\n\nFor market-data or execution-adjacent paths, also verify orderbook age, VWAP\nassumptions, provider status, and kill-switch behavior before calling the path\nready.\n\n## Guardrails\n\n- Do not optimize latency by dropping required validation.\n- Do not hide stale data behind fast cache hits.\n- Do not claim millisecond behavior from client labels without measurement.\n- Do not run live orders, destructive migrations, or customer-impacting deploys\n  without an explicit approval gate.\n- Keep secrets and private payloads out of logs and benchmark artifacts.\n",{"name":5,"tools":24,"origin":25,"description":7},"Read, Write, Edit, Bash, Grep, Glob","ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Flatency-critical-systems",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill latency-critical-systems",{"tool":42,"command":43},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill latency-critical-systems",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill latency-critical-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Flatency-critical-systems\u002FSKILL.md",true,[],[51,59,66,74,82,90],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"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":93,"categories":94,"keywords":95,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]