[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GJSCAP9YYTTYDK1DFP5K0":3,"skill-same:01M73GJSCAP9YYTTYDK1DFP5K0":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},"01M73GJSCAP9YYTTYDK1DFP5K0","venice--venice-crypto-rpc",null,"Use Venice as a pay-per-call JSON-RPC proxy to 20+ EVM and Starknet networks. Covers GET \u002Fcrypto\u002Frpc\u002Fnetworks, POST \u002Fcrypto\u002Frpc\u002F{network}, the 1×\u002F2×\u002F4× method-tier pricing model, per-minute + 24-hour credit rate limits, idempotency keys for safe retries, single vs batch requests, and the unsupported","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fvenice--venice-crypto-rpc\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: venice--venice-crypto-rpc\ndescription: >-\n  Use Venice as a pay-per-call JSON-RPC proxy to 20+ EVM and Starknet networks. Covers GET \u002Fcrypto\u002Frpc\u002Fnetworks, POST \u002Fcrypto\u002Frpc\u002F{network}, the 1×\u002F2×\u002F4× method-tier pricing model, per-minute + 24-hour credit rate limits, idempotency keys for safe retries, single vs batch requests, and the unsupported\norigin: \"github.com\u002Fveniceai\u002Fskills (skill: venice-crypto-rpc)\"\nlicense: MIT\nversion: \"1.0.0\"\ncompatibility: \"yana-ai >= 0.14.0\"\n---\n\n# Venice Crypto RPC (JSON-RPC proxy)\n\nVenice exposes a **multi-chain JSON-RPC proxy** billed per call. Same request shape as Alchemy \u002F Infura — just change the base URL and pay per credit.\n\n| Endpoint | Auth | Notes |\n|---|---|---|\n| `GET \u002Fcrypto\u002Frpc\u002Fnetworks` | Bearer or SIWE | Returns `{ \"networks\": [...] }` (sorted). |\n| `POST \u002Fcrypto\u002Frpc\u002F{network}` | Bearer or SIWE (x402) | Forward a JSON-RPC 2.0 request (single or batch). |\n\n## Supported networks\n\nCall `GET \u002Fcrypto\u002Frpc\u002Fnetworks` for the current list. It currently returns 23 slugs (always verify — the catalog grows):\n\n```\narbitrum-mainnet    arbitrum-sepolia\navalanche-mainnet   avalanche-fuji\nbase-mainnet        base-sepolia\nblast-mainnet       blast-sepolia\nbsc-mainnet         bsc-testnet\nethereum-mainnet    ethereum-sepolia    ethereum-holesky\nlinea-mainnet       linea-sepolia\noptimism-mainnet    optimism-sepolia\npolygon-mainnet     polygon-amoy\nstarknet-mainnet    starknet-sepolia\nzksync-mainnet      zksync-sepolia\n```\n\nUse the slug as `:network` in the proxy path.\n\n## Send a JSON-RPC request\n\n### Single call\n\n```bash\ncurl -X POST https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fethereum-mainnet \\\n  -H \"Authorization: Bearer $VENICE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"method\":\"eth_chainId\",\"params\":[],\"id\":1}'\n```\n\n```json\n{ \"jsonrpc\": \"2.0\", \"id\": 1, \"result\": \"0x1\" }\n```\n\n### Batch (up to 100 calls)\n\n```bash\ncurl -X POST https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fbase-mainnet \\\n  -H \"Authorization: Bearer $VENICE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '[\n    {\"jsonrpc\":\"2.0\",\"method\":\"eth_chainId\",\"params\":[],\"id\":1},\n    {\"jsonrpc\":\"2.0\",\"method\":\"eth_blockNumber\",\"params\":[],\"id\":2}\n  ]'\n```\n\nA single unsupported method in a batch ⇒ the **entire batch** fails with `400`.\n\n### Drop-in with `viem` \u002F `ethers`\n\n```ts\nimport { createPublicClient, http } from 'viem'\nimport { mainnet } from 'viem\u002Fchains'\n\nconst client = createPublicClient({\n  chain: mainnet,\n  transport: http('https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fethereum-mainnet', {\n    fetchOptions: { headers: { Authorization: `Bearer ${process.env.VENICE_API_KEY}` } },\n  }),\n})\n```\n\n## Pricing\n\nCredits per call = `baseCredits[chain] × methodTier`.\n\n| Base credits | Chains |\n|---|---|\n| `20` | Ethereum, Base, Optimism, Arbitrum, Polygon, Linea, Avalanche, BSC, Blast, Starknet. |\n| `30` | zkSync Era. |\n\n| Tier | Multiplier | Methods |\n|---|---|---|\n| **Standard** | `1×` | `eth_call`, `eth_getBalance`, `eth_blockNumber`, `eth_sendRawTransaction`, `eth_getLogs`, `net_version`, `web3_clientVersion`, ERC-4337 bundler (`eth_sendUserOperation`, …), chain-family extensions (`zks_*`, `linea_*`, `bor_*`, `starknet_*`). |\n| **Advanced** | `2×` | `trace_*`, `debug_*`, `txpool_inspect`, `txpool_status`, `arbtrace_*`. |\n| **Large** | `4×` | `trace_replayBlockTransactions`, `trace_replayTransaction`, `txpool_content`, `arbtrace_replay*`. |\n\nAt `~$7e-7` per credit:\n\n- Standard EVM call (20 × 1) ≈ **$0.000014**\n- Advanced trace on Ethereum (20 × 2) ≈ **$0.000028**\n- Large trace replay (20 × 4) ≈ **$0.000056**\n- zkSync standard call (30 × 1) ≈ **$0.000021**\n\nRPC-level errors (HTTP 200 with `error` object inside — e.g. method unsupported on that chain, bad params) are billed at a flat **5 credits** regardless of tier.\n\nResponse headers on `200`:\n\n| Header | Meaning |\n|---|---|\n| `X-Venice-RPC-Credits` | Total credits charged (sum over batch). |\n| `X-Venice-RPC-Cost-USD` | Dollar cost to 8 decimal places. |\n| `X-Balance-Remaining` | Remaining x402 USD — set on routes whose middleware refreshes balance headers. The `\u002Fcrypto\u002Frpc\u002F*` handler currently emits credits\u002Fcost\u002Frequest headers; treat `X-Balance-Remaining` here as best-effort (may be absent on RPC). Use `GET \u002Fx402\u002Fbalance\u002F{walletAddress}` for an authoritative read. |\n| `X-Request-ID` | 32-char correlation ID — include in support tickets. |\n| `Idempotent-Replayed` | `\"true\"` when served from the idempotency cache. |\n\n## Unsupported methods\n\nThese always return `400`:\n\n- **Stateful filter methods** — `eth_newFilter`, `eth_newBlockFilter`, `eth_getFilterChanges`, `eth_getFilterLogs`, `eth_uninstallFilter`. Filter state is pinned to a single backend and a load-balanced HTTP proxy can't maintain it. Use `eth_getLogs` instead.\n- **WebSocket-only methods** — `eth_subscribe`, `eth_unsubscribe`. This proxy is HTTP only. Run your own WS endpoint for subscriptions.\n- **Cross-family methods** — calling `starknet_*` on an EVM chain (or vice versa) ⇒ `400`.\n- **Unmapped methods** — anything not in the Standard\u002FAdvanced\u002FLarge lists.\n\n## Idempotency\n\nSet the `Idempotency-Key` header to any `[A-Za-z0-9_-]{1,255}` string for safe retries:\n\n```bash\ncurl -X POST https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fethereum-mainnet \\\n  -H \"Authorization: Bearer $VENICE_API_KEY\" \\\n  -H \"Idempotency-Key: send-tx-2026-04-21-nonce-42\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"method\":\"eth_sendRawTransaction\",\"params\":[\"0x...\"] ,\"id\":1}'\n```\n\n- Cached for **24 hours** keyed on `(user, idempotency-key)`.\n- Replay returns the cached response with `Idempotent-Replayed: true` and is **not billed again**.\n- Same key + **different body** ⇒ `400` (prevents silent corruption).\n\nUse this for any state-mutating method (`eth_sendRawTransaction`, `eth_sendUserOperation`) to survive flaky networks without double-broadcasting.\n\n## Rate limits\n\nTwo caps per caller, both enforced independently:\n\n| Tier | Per-minute requests | Credits \u002F rolling 24h |\n|---|---|---|\n| Paid | 100 | 10,000,000 |\n| Staff | 1,000 | 100,000,000 |\n\n`429` response `customMessage` identifies which cap tripped. Per-minute cap also sets `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset` headers.\n\nConcurrent-call collisions on the per-user mutex also return `429`. Retry with jitter.\n\n## Errors\n\n| Status | Typical cause |\n|---|---|\n| `400` | Unsupported network slug, empty body, batch > 100, unsupported\u002FWebSocket\u002Ffilter method, cross-family call, idempotency-key reuse with a different body. |\n| `401` | Missing or invalid Bearer \u002F SIWE. The `\u002Fnetworks` listing is public but the proxy endpoint requires auth. |\n| `402` | Insufficient balance. x402 wallet users get a `PAYMENT-REQUIRED` header with structured top-up instructions (see [`venice-x402`](..\u002Fvenice-x402\u002FSKILL.md)). |\n| `429` | Per-minute, 24-hour credit, or concurrency cap tripped. |\n| `500` | Upstream fetch failed \u002F timeout. Safe to retry with the same `Idempotency-Key`. |\n\n## Patterns\n\n- **Multi-chain dashboards** — Single API key unlocks all networks. No per-chain keys to rotate.\n- **High-throughput indexing** — Batch up to 100 calls per request; each sub-call is still billed individually, but the network round-trip is amortized.\n- **Wallet-based (x402) RPC** — Pay per RPC call with USDC on Base. Use the SIWE header; a `402` indicates low credit and carries structured top-up instructions.\n- **Cost tracking** — Log `X-Venice-RPC-Credits` and `X-Venice-RPC-Cost-USD` per request; aggregate by `method` to see where credits go.\n- **Safe transaction submission** — Always include an `Idempotency-Key` on `eth_sendRawTransaction`. The proxy then guarantees exactly-once semantics within 24 hours.\n","# Venice Crypto RPC (JSON-RPC proxy)\n\nVenice exposes a **multi-chain JSON-RPC proxy** billed per call. Same request shape as Alchemy \u002F Infura — just change the base URL and pay per credit.\n\n| Endpoint | Auth | Notes |\n|---|---|---|\n| `GET \u002Fcrypto\u002Frpc\u002Fnetworks` | Bearer or SIWE | Returns `{ \"networks\": [...] }` (sorted). |\n| `POST \u002Fcrypto\u002Frpc\u002F{network}` | Bearer or SIWE (x402) | Forward a JSON-RPC 2.0 request (single or batch). |\n\n## Supported networks\n\nCall `GET \u002Fcrypto\u002Frpc\u002Fnetworks` for the current list. It currently returns 23 slugs (always verify — the catalog grows):\n\n```\narbitrum-mainnet    arbitrum-sepolia\navalanche-mainnet   avalanche-fuji\nbase-mainnet        base-sepolia\nblast-mainnet       blast-sepolia\nbsc-mainnet         bsc-testnet\nethereum-mainnet    ethereum-sepolia    ethereum-holesky\nlinea-mainnet       linea-sepolia\noptimism-mainnet    optimism-sepolia\npolygon-mainnet     polygon-amoy\nstarknet-mainnet    starknet-sepolia\nzksync-mainnet      zksync-sepolia\n```\n\nUse the slug as `:network` in the proxy path.\n\n## Send a JSON-RPC request\n\n### Single call\n\n```bash\ncurl -X POST https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fethereum-mainnet \\\n  -H \"Authorization: Bearer $VENICE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"method\":\"eth_chainId\",\"params\":[],\"id\":1}'\n```\n\n```json\n{ \"jsonrpc\": \"2.0\", \"id\": 1, \"result\": \"0x1\" }\n```\n\n### Batch (up to 100 calls)\n\n```bash\ncurl -X POST https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fbase-mainnet \\\n  -H \"Authorization: Bearer $VENICE_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '[\n    {\"jsonrpc\":\"2.0\",\"method\":\"eth_chainId\",\"params\":[],\"id\":1},\n    {\"jsonrpc\":\"2.0\",\"method\":\"eth_blockNumber\",\"params\":[],\"id\":2}\n  ]'\n```\n\nA single unsupported method in a batch ⇒ the **entire batch** fails with `400`.\n\n### Drop-in with `viem` \u002F `ethers`\n\n```ts\nimport { createPublicClient, http } from 'viem'\nimport { mainnet } from 'viem\u002Fchains'\n\nconst client = createPublicClient({\n  chain: mainnet,\n  transport: http('https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fethereum-mainnet', {\n    fetchOptions: { headers: { Authorization: `Bearer ${process.env.VENICE_API_KEY}` } },\n  }),\n})\n```\n\n## Pricing\n\nCredits per call = `baseCredits[chain] × methodTier`.\n\n| Base credits | Chains |\n|---|---|\n| `20` | Ethereum, Base, Optimism, Arbitrum, Polygon, Linea, Avalanche, BSC, Blast, Starknet. |\n| `30` | zkSync Era. |\n\n| Tier | Multiplier | Methods |\n|---|---|---|\n| **Standard** | `1×` | `eth_call`, `eth_getBalance`, `eth_blockNumber`, `eth_sendRawTransaction`, `eth_getLogs`, `net_version`, `web3_clientVersion`, ERC-4337 bundler (`eth_sendUserOperation`, …), chain-family extensions (`zks_*`, `linea_*`, `bor_*`, `starknet_*`). |\n| **Advanced** | `2×` | `trace_*`, `debug_*`, `txpool_inspect`, `txpool_status`, `arbtrace_*`. |\n| **Large** | `4×` | `trace_replayBlockTransactions`, `trace_replayTransaction`, `txpool_content`, `arbtrace_replay*`. |\n\nAt `~$7e-7` per credit:\n\n- Standard EVM call (20 × 1) ≈ **$0.000014**\n- Advanced trace on Ethereum (20 × 2) ≈ **$0.000028**\n- Large trace replay (20 × 4) ≈ **$0.000056**\n- zkSync standard call (30 × 1) ≈ **$0.000021**\n\nRPC-level errors (HTTP 200 with `error` object inside — e.g. method unsupported on that chain, bad params) are billed at a flat **5 credits** regardless of tier.\n\nResponse headers on `200`:\n\n| Header | Meaning |\n|---|---|\n| `X-Venice-RPC-Credits` | Total credits charged (sum over batch). |\n| `X-Venice-RPC-Cost-USD` | Dollar cost to 8 decimal places. |\n| `X-Balance-Remaining` | Remaining x402 USD — set on routes whose middleware refreshes balance headers. The `\u002Fcrypto\u002Frpc\u002F*` handler currently emits credits\u002Fcost\u002Frequest headers; treat `X-Balance-Remaining` here as best-effort (may be absent on RPC). Use `GET \u002Fx402\u002Fbalance\u002F{walletAddress}` for an authoritative read. |\n| `X-Request-ID` | 32-char correlation ID — include in support tickets. |\n| `Idempotent-Replayed` | `\"true\"` when served from the idempotency cache. |\n\n## Unsupported methods\n\nThese always return `400`:\n\n- **Stateful filter methods** — `eth_newFilter`, `eth_newBlockFilter`, `eth_getFilterChanges`, `eth_getFilterLogs`, `eth_uninstallFilter`. Filter state is pinned to a single backend and a load-balanced HTTP proxy can't maintain it. Use `eth_getLogs` instead.\n- **WebSocket-only methods** — `eth_subscribe`, `eth_unsubscribe`. This proxy is HTTP only. Run your own WS endpoint for subscriptions.\n- **Cross-family methods** — calling `starknet_*` on an EVM chain (or vice versa) ⇒ `400`.\n- **Unmapped methods** — anything not in the Standard\u002FAdvanced\u002FLarge lists.\n\n## Idempotency\n\nSet the `Idempotency-Key` header to any `[A-Za-z0-9_-]{1,255}` string for safe retries:\n\n```bash\ncurl -X POST https:\u002F\u002Fapi.venice.ai\u002Fapi\u002Fv1\u002Fcrypto\u002Frpc\u002Fethereum-mainnet \\\n  -H \"Authorization: Bearer $VENICE_API_KEY\" \\\n  -H \"Idempotency-Key: send-tx-2026-04-21-nonce-42\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"method\":\"eth_sendRawTransaction\",\"params\":[\"0x...\"] ,\"id\":1}'\n```\n\n- Cached for **24 hours** keyed on `(user, idempotency-key)`.\n- Replay returns the cached response with `Idempotent-Replayed: true` and is **not billed again**.\n- Same key + **different body** ⇒ `400` (prevents silent corruption).\n\nUse this for any state-mutating method (`eth_sendRawTransaction`, `eth_sendUserOperation`) to survive flaky networks without double-broadcasting.\n\n## Rate limits\n\nTwo caps per caller, both enforced independently:\n\n| Tier | Per-minute requests | Credits \u002F rolling 24h |\n|---|---|---|\n| Paid | 100 | 10,000,000 |\n| Staff | 1,000 | 100,000,000 |\n\n`429` response `customMessage` identifies which cap tripped. Per-minute cap also sets `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset` headers.\n\nConcurrent-call collisions on the per-user mutex also return `429`. Retry with jitter.\n\n## Errors\n\n| Status | Typical cause |\n|---|---|\n| `400` | Unsupported network slug, empty body, batch > 100, unsupported\u002FWebSocket\u002Ffilter method, cross-family call, idempotency-key reuse with a different body. |\n| `401` | Missing or invalid Bearer \u002F SIWE. The `\u002Fnetworks` listing is public but the proxy endpoint requires auth. |\n| `402` | Insufficient balance. x402 wallet users get a `PAYMENT-REQUIRED` header with structured top-up instructions (see [`venice-x402`](..\u002Fvenice-x402\u002FSKILL.md)). |\n| `429` | Per-minute, 24-hour credit, or concurrency cap tripped. |\n| `500` | Upstream fetch failed \u002F timeout. Safe to retry with the same `Idempotency-Key`. |\n\n## Patterns\n\n- **Multi-chain dashboards** — Single API key unlocks all networks. No per-chain keys to rotate.\n- **High-throughput indexing** — Batch up to 100 calls per request; each sub-call is still billed individually, but the network round-trip is amortized.\n- **Wallet-based (x402) RPC** — Pay per RPC call with USDC on Base. Use the SIWE header; a `402` indicates low credit and carries structured top-up instructions.\n- **Cost tracking** — Log `X-Venice-RPC-Credits` and `X-Venice-RPC-Cost-USD` per request; aggregate by `method` to see where credits go.\n- **Safe transaction submission** — Always include an `Idempotency-Key` on `eth_sendRawTransaction`. The proxy then guarantees exactly-once semantics within 24 hours.\n",{"name":5,"origin":24,"license":15,"version":25,"description":7,"compatibility":26},"github.com\u002Fveniceai\u002Fskills (skill: venice-crypto-rpc)","1.0.0","yana-ai >= 0.14.0","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fvenice--venice-crypto-rpc",1,"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-11 23:56:26",{"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 venice--venice-crypto-rpc",{"tool":43,"command":44},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill venice--venice-crypto-rpc",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill venice--venice-crypto-rpc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fvenice--venice-crypto-rpc\u002FSKILL.md",true,[],[52,59,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":15,"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`.","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":63,"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.","Apache-2.0","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":63,"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":63,"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":63,"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":63,"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",[],[]]