[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BKA861NZ5NTV10GEGCECC":3,"skill-same:01M75BKA861NZ5NTV10GEGCECC":47},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75BKA861NZ5NTV10GEGCECC","bug-audit",null,"Comprehensive bug audit for Node.js web projects. Activate when user asks to audit, review, check bugs, find vulnerabilities, or do security\u002Fquality review on a project. Works by dissecting the project's actual code to build project-specific check matrices, then exhaustively verifying each item — not by running a generic checklist. Supports games, data tools, WeChat apps, API services, bots, and dashboards.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fabczsl520\u002Fbug-audit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: bug-audit\ndescription: Comprehensive bug audit for Node.js web projects. Activate when user asks to audit, review, check bugs, find vulnerabilities, or do security\u002Fquality review on a project. Works by dissecting the project's actual code to build project-specific check matrices, then exhaustively verifying each item — not by running a generic checklist. Supports games, data tools, WeChat apps, API services, bots, and dashboards.\n---\n\n# Bug Audit — Dissect, Then Verify\n\nDo NOT run a generic checklist. Instead: read the code, extract every auditable entity, then exhaustively question each one.\n\n## Phase 1: Dissect (10-15 min)\n\nRead all project files. Build 7 tables. These tables ARE the audit — everything found here gets verified in Phase 2.\n\n### Table 1: API Endpoints\n\nFor every route in server-side code:\n\n```\n| # | Method | Path | Auth? | Params validated? | Precondition | Returns | Attack vector |\n```\n\nFor each endpoint, ask:\n- Can I call this without authentication?\n- Can I pass 0, negative, NaN, huge numbers, arrays, objects?\n- Can I skip a prerequisite API and call this directly?\n- What happens if I call this 100 times per second?\n- Does the response leak sensitive data (openid, internal IDs, full user objects)?\n\n### Table 2: State Machines\n\nFor every boolean\u002Fenum state variable (isGameOver, battleState, Game.running, phase, mode...):\n\n```\n| # | Variable | Set by | Read by | Init value | Reset when? | Can it leak across lifecycles? |\n```\n\nFor each variable, ask:\n- If the game\u002Fsession ends, does this get reset?\n- If I start a new round immediately, will stale state from the previous round affect it?\n- Are there race conditions between setters?\n\n### Table 3: Timers\n\nFor every setTimeout\u002FsetInterval:\n\n```\n| # | Type | Delay | Created in | Cleared in | What if lifecycle ends before it fires? |\n```\n\nFor each timer, ask:\n- Is the handle stored for cleanup?\n- If the game ends \u002F user disconnects \u002F page navigates, does this still fire?\n- If it fires after cleanup, does it reference destroyed objects?\n\n### Table 4: Numeric Values\n\nFor every user-influenceable number (cost, score, damage, lootValue, kills, quantity...):\n\n```\n| # | Name | Source (client\u002Fserver\u002Fconfig) | Validated? | Min | Max | What if 0? | What if negative? |\n```\n\nFor each value, ask:\n- Is the server-side cap realistic? (kills cap 200 but max enemies is 50?)\n- Can the client send a value the server trusts without verification?\n- Float precision issues? (accumulated math → 290402.0000000001)\n\n### Table 5: Data Flows (Critical!)\n\nFor every pair of related APIs (buy→use, start→complete, pay→deliver, login→action):\n\n```\n| # | Step 1 API | Step 2 API | Token\u002Flink between them? | Can skip Step 1? | Can replay Step 1? |\n```\n\nThis is where the biggest bugs hide. For each flow, ask:\n- Can I call Step 2 without ever calling Step 1? (raid-result without buy)\n- Can I call Step 1 once but Step 2 many times? (buy once, submit results 10 times)\n- Is there a one-time token linking them? If not, this is a critical vulnerability.\n- Can I call Step 1 with cost=0 then Step 2 with high reward?\n\n### Table 6: Resource Ledger\n\nFor every in-game resource (coins, gems, items, XP, energy...):\n\n```\n| # | Resource | All INFLOWS (APIs\u002Fevents that add) | All OUTFLOWS (APIs\u002Fevents that subtract) | Daily limits? | Can any inflow be infinite? |\n```\n\nFor each resource, ask:\n- Is there any inflow without a corresponding cost? (free coins from quest with no cooldown)\n- Can any outflow go negative? (sell item → coins, but what if coins overflow?)\n- Are items in safe-box excluded from ALL outflows? (trade, sell, merge, fuse, gift)\n- Is there a loop? (buy item A → sell for more than cost → repeat)\n\n### Table 7: Concurrency Hotspots (TOCTOU)\n\nFor every operation that reads-then-writes shared state (balance check→deduct, stock check→reserve, coupon check→redeem):\n\n```\n| # | Operation | Read step | Write step | Atomic? | What if 2 requests hit simultaneously? |\n```\n\nThis catches race conditions that single-request testing misses. For each operation, ask:\n- Is the read-then-write atomic? (SQL `UPDATE x=x-1 WHERE x>=1` is atomic; `SELECT` then `UPDATE` is NOT)\n- Can two concurrent requests both pass the check and both execute the write? (double-spend)\n- Is there a mutex\u002Flock\u002Ftransaction? If using SQLite, is WAL mode enabled for concurrent reads?\n- For multi-step flows: can request A be between steps while request B starts the same flow?\n\n## Phase 2: Verify (main audit)\n\nGo through every row in every table. For each row, determine:\n- 🔴 Critical: exploitable security hole, data loss, crash\n- 🟡 Medium: logic error, inconsistency, performance issue  \n- 🟢 Minor: code quality, edge case, UX issue\n- ✅ OK: verified correct\n\nOutput format:\n```\nBug N: [🔴\u002F🟡\u002F🟢] Brief description\n- Row: Table X, #Y\n- Cause: ...\n- Fix: ...\n- File: ...\n```\n\n**Do NOT stop when you run out of \"inspiration\".** You stop when every row in every table has been verified ✅ or flagged 🔴\u002F🟡\u002F🟢. This is exhaustive, not heuristic.\n\n## Phase 3: Red Team \u002F Blue Team\n\nAfter verifying all tables, switch to adversarial mode. Read `references\u002Fredblue.md` for the full playbook.\n\n### Structure\nThe playbook has 4 parts:\n1. **Universal Chains (5)** — apply to ALL projects: Auth Bypass, Injection, Rate Abuse, Data Leakage, Concurrency\u002FRace Conditions\n2. **Type-Specific Chains** — pick sections matching the project:\n   - 🎮 Game: Skip-Pay-Collect, Economic Loop, State Manipulation, Anti-Cheat Bypass\n   - 📊 Data Tool: Data Access Control, Data Integrity, Scheduled Task Abuse\n   - 🔌 API Service: Key\u002FToken Abuse, Upstream Dependency, Response Manipulation\n   - 🤖 Bot: Message Injection, Bot State Abuse\n   - 🔧 WeChat: OAuth & Identity, WebView Compatibility, H5 Hybrid\n   - 📈 Platform: Cross-Service Trust, Multi-Tenant Isolation\n3. **Blue Team Defense** — for each finding, verify 4 layers: Prevention → Detection → Containment → Recovery\n4. **Execution Guide** — step-by-step for the auditor\n\n### How to Run\n1. From Phase 1 dissection, identify project type(s) — a project can match multiple types\n2. Run ALL 5 Universal Chains\n3. Run type-specific chains matching the project\n4. For each 🔴 finding: verify all 4 Blue Team layers\n5. For each 🟡 finding: verify Layer 1 (Prevention) at minimum\n\n## Phase 4: Supplement\n\nAfter red\u002Fblue team, run generic checks as a final safety net. Read `references\u002Fmodules.md` and pick sections matching the project:\n\n- 🔒 Security (S1-S3): CORS, XSS, SQLi, brute force — if project has users\n- 🔐 Crypto (C1): Hardcoded secrets, weak hashing, plaintext storage, insecure random — all projects\n- 📊 Data (D1-D3): Timezone, atomic ops, float precision — if project has DB\n- ⚡ Performance (P1-P2): Memory leaks, hot paths — if project is large\u002Frealtime\n- 🎮 Game (G1-G4): State guards, rendering, config — if project is a game\n- 🔧 WeChat (W1-W3): ES6 compat, CDN, debugging — if runs in WeChat WebView\n- 🔌 API (A1-A3): Interface standards, rate limiting — if project is an API service\n- 🤖 Bot (B1): Timeout, dedup, sensitive words — if project is a bot\n- 🚀 Deploy (R1-R2): PM2, nginx, SSL, SDK overwrite — all projects\n- 🧪 Error Handling (E1-E2): Network errors, server errors, graceful degradation — all projects\n- 📱 UX Robustness (U1-U2): Error states, edge case UX — all projects with UI\n- 📦 Supply Chain (SC1): npm audit, dependency vulnerabilities, lockfile integrity — all Node.js projects\n- 📝 Logging (L1): Security event logging, audit trail completeness — all projects with users\n\n## Phase 5: Regression + Verify\n\n- Check that fixes didn't introduce new bugs\n- After modular split: verify cross-file variable\u002Ffunction reachability\n- Live smoke test: homepage 200, key APIs return JSON, login works, core feature functional\n\n## Phase 6: Archive\n\nUpdate project docs with: date, tables built, bugs found\u002Ffixed, key pitfalls for next audit.\n\n## Key Principles\n\n1. **Tables first, checking second.** Building the tables IS the hard work. Once you have them, verification is mechanical.\n2. **Exhaustive, not heuristic.** Don't stop when you \"feel done.\" Stop when every row is verified.\n3. **Think like an attacker.** For every API: \"How would I exploit this?\" For every value: \"What if I send garbage?\"\n4. **Data flows are where critical bugs hide.** The link (or lack thereof) between related APIs is the #1 source of exploitable vulnerabilities.\n5. **Generic checklists are supplements, not the main event.** They catch known patterns; the tables catch project-specific logic bugs.\n\n## Reference Files\n\n- `references\u002Fmodules.md` — Generic audit modules (Security, Crypto, Data, Performance, Game, WeChat, API, Bot, Deploy, Error Handling, UX, Supply Chain, Logging) for Phase 4 supplementary checks.\n- `references\u002Fredblue.md` — Red team attack chains (universal + 6 project types) and blue team defense verification playbook for Phase 3.\n- `references\u002Fpitfalls.md` — Real-world pitfall lookup table from 200+ bugs, plus WeChat WebView remote debugging techniques.\n","# Bug Audit — Dissect, Then Verify\n\nDo NOT run a generic checklist. Instead: read the code, extract every auditable entity, then exhaustively question each one.\n\n## Phase 1: Dissect (10-15 min)\n\nRead all project files. Build 7 tables. These tables ARE the audit — everything found here gets verified in Phase 2.\n\n### Table 1: API Endpoints\n\nFor every route in server-side code:\n\n```\n| # | Method | Path | Auth? | Params validated? | Precondition | Returns | Attack vector |\n```\n\nFor each endpoint, ask:\n- Can I call this without authentication?\n- Can I pass 0, negative, NaN, huge numbers, arrays, objects?\n- Can I skip a prerequisite API and call this directly?\n- What happens if I call this 100 times per second?\n- Does the response leak sensitive data (openid, internal IDs, full user objects)?\n\n### Table 2: State Machines\n\nFor every boolean\u002Fenum state variable (isGameOver, battleState, Game.running, phase, mode...):\n\n```\n| # | Variable | Set by | Read by | Init value | Reset when? | Can it leak across lifecycles? |\n```\n\nFor each variable, ask:\n- If the game\u002Fsession ends, does this get reset?\n- If I start a new round immediately, will stale state from the previous round affect it?\n- Are there race conditions between setters?\n\n### Table 3: Timers\n\nFor every setTimeout\u002FsetInterval:\n\n```\n| # | Type | Delay | Created in | Cleared in | What if lifecycle ends before it fires? |\n```\n\nFor each timer, ask:\n- Is the handle stored for cleanup?\n- If the game ends \u002F user disconnects \u002F page navigates, does this still fire?\n- If it fires after cleanup, does it reference destroyed objects?\n\n### Table 4: Numeric Values\n\nFor every user-influenceable number (cost, score, damage, lootValue, kills, quantity...):\n\n```\n| # | Name | Source (client\u002Fserver\u002Fconfig) | Validated? | Min | Max | What if 0? | What if negative? |\n```\n\nFor each value, ask:\n- Is the server-side cap realistic? (kills cap 200 but max enemies is 50?)\n- Can the client send a value the server trusts without verification?\n- Float precision issues? (accumulated math → 290402.0000000001)\n\n### Table 5: Data Flows (Critical!)\n\nFor every pair of related APIs (buy→use, start→complete, pay→deliver, login→action):\n\n```\n| # | Step 1 API | Step 2 API | Token\u002Flink between them? | Can skip Step 1? | Can replay Step 1? |\n```\n\nThis is where the biggest bugs hide. For each flow, ask:\n- Can I call Step 2 without ever calling Step 1? (raid-result without buy)\n- Can I call Step 1 once but Step 2 many times? (buy once, submit results 10 times)\n- Is there a one-time token linking them? If not, this is a critical vulnerability.\n- Can I call Step 1 with cost=0 then Step 2 with high reward?\n\n### Table 6: Resource Ledger\n\nFor every in-game resource (coins, gems, items, XP, energy...):\n\n```\n| # | Resource | All INFLOWS (APIs\u002Fevents that add) | All OUTFLOWS (APIs\u002Fevents that subtract) | Daily limits? | Can any inflow be infinite? |\n```\n\nFor each resource, ask:\n- Is there any inflow without a corresponding cost? (free coins from quest with no cooldown)\n- Can any outflow go negative? (sell item → coins, but what if coins overflow?)\n- Are items in safe-box excluded from ALL outflows? (trade, sell, merge, fuse, gift)\n- Is there a loop? (buy item A → sell for more than cost → repeat)\n\n### Table 7: Concurrency Hotspots (TOCTOU)\n\nFor every operation that reads-then-writes shared state (balance check→deduct, stock check→reserve, coupon check→redeem):\n\n```\n| # | Operation | Read step | Write step | Atomic? | What if 2 requests hit simultaneously? |\n```\n\nThis catches race conditions that single-request testing misses. For each operation, ask:\n- Is the read-then-write atomic? (SQL `UPDATE x=x-1 WHERE x>=1` is atomic; `SELECT` then `UPDATE` is NOT)\n- Can two concurrent requests both pass the check and both execute the write? (double-spend)\n- Is there a mutex\u002Flock\u002Ftransaction? If using SQLite, is WAL mode enabled for concurrent reads?\n- For multi-step flows: can request A be between steps while request B starts the same flow?\n\n## Phase 2: Verify (main audit)\n\nGo through every row in every table. For each row, determine:\n- 🔴 Critical: exploitable security hole, data loss, crash\n- 🟡 Medium: logic error, inconsistency, performance issue  \n- 🟢 Minor: code quality, edge case, UX issue\n- ✅ OK: verified correct\n\nOutput format:\n```\nBug N: [🔴\u002F🟡\u002F🟢] Brief description\n- Row: Table X, #Y\n- Cause: ...\n- Fix: ...\n- File: ...\n```\n\n**Do NOT stop when you run out of \"inspiration\".** You stop when every row in every table has been verified ✅ or flagged 🔴\u002F🟡\u002F🟢. This is exhaustive, not heuristic.\n\n## Phase 3: Red Team \u002F Blue Team\n\nAfter verifying all tables, switch to adversarial mode. Read `references\u002Fredblue.md` for the full playbook.\n\n### Structure\nThe playbook has 4 parts:\n1. **Universal Chains (5)** — apply to ALL projects: Auth Bypass, Injection, Rate Abuse, Data Leakage, Concurrency\u002FRace Conditions\n2. **Type-Specific Chains** — pick sections matching the project:\n   - 🎮 Game: Skip-Pay-Collect, Economic Loop, State Manipulation, Anti-Cheat Bypass\n   - 📊 Data Tool: Data Access Control, Data Integrity, Scheduled Task Abuse\n   - 🔌 API Service: Key\u002FToken Abuse, Upstream Dependency, Response Manipulation\n   - 🤖 Bot: Message Injection, Bot State Abuse\n   - 🔧 WeChat: OAuth & Identity, WebView Compatibility, H5 Hybrid\n   - 📈 Platform: Cross-Service Trust, Multi-Tenant Isolation\n3. **Blue Team Defense** — for each finding, verify 4 layers: Prevention → Detection → Containment → Recovery\n4. **Execution Guide** — step-by-step for the auditor\n\n### How to Run\n1. From Phase 1 dissection, identify project type(s) — a project can match multiple types\n2. Run ALL 5 Universal Chains\n3. Run type-specific chains matching the project\n4. For each 🔴 finding: verify all 4 Blue Team layers\n5. For each 🟡 finding: verify Layer 1 (Prevention) at minimum\n\n## Phase 4: Supplement\n\nAfter red\u002Fblue team, run generic checks as a final safety net. Read `references\u002Fmodules.md` and pick sections matching the project:\n\n- 🔒 Security (S1-S3): CORS, XSS, SQLi, brute force — if project has users\n- 🔐 Crypto (C1): Hardcoded secrets, weak hashing, plaintext storage, insecure random — all projects\n- 📊 Data (D1-D3): Timezone, atomic ops, float precision — if project has DB\n- ⚡ Performance (P1-P2): Memory leaks, hot paths — if project is large\u002Frealtime\n- 🎮 Game (G1-G4): State guards, rendering, config — if project is a game\n- 🔧 WeChat (W1-W3): ES6 compat, CDN, debugging — if runs in WeChat WebView\n- 🔌 API (A1-A3): Interface standards, rate limiting — if project is an API service\n- 🤖 Bot (B1): Timeout, dedup, sensitive words — if project is a bot\n- 🚀 Deploy (R1-R2): PM2, nginx, SSL, SDK overwrite — all projects\n- 🧪 Error Handling (E1-E2): Network errors, server errors, graceful degradation — all projects\n- 📱 UX Robustness (U1-U2): Error states, edge case UX — all projects with UI\n- 📦 Supply Chain (SC1): npm audit, dependency vulnerabilities, lockfile integrity — all Node.js projects\n- 📝 Logging (L1): Security event logging, audit trail completeness — all projects with users\n\n## Phase 5: Regression + Verify\n\n- Check that fixes didn't introduce new bugs\n- After modular split: verify cross-file variable\u002Ffunction reachability\n- Live smoke test: homepage 200, key APIs return JSON, login works, core feature functional\n\n## Phase 6: Archive\n\nUpdate project docs with: date, tables built, bugs found\u002Ffixed, key pitfalls for next audit.\n\n## Key Principles\n\n1. **Tables first, checking second.** Building the tables IS the hard work. Once you have them, verification is mechanical.\n2. **Exhaustive, not heuristic.** Don't stop when you \"feel done.\" Stop when every row is verified.\n3. **Think like an attacker.** For every API: \"How would I exploit this?\" For every value: \"What if I send garbage?\"\n4. **Data flows are where critical bugs hide.** The link (or lack thereof) between related APIs is the #1 source of exploitable vulnerabilities.\n5. **Generic checklists are supplements, not the main event.** They catch known patterns; the tables catch project-specific logic bugs.\n\n## Reference Files\n\n- `references\u002Fmodules.md` — Generic audit modules (Security, Crypto, Data, Performance, Game, WeChat, API, Bot, Deploy, Error Handling, UX, Supply Chain, Logging) for Phase 4 supplementary checks.\n- `references\u002Fredblue.md` — Red team attack chains (universal + 6 project types) and blue team defense verification playbook for Phase 3.\n- `references\u002Fpitfalls.md` — Real-world pitfall lookup table from 200+ bugs, plus WeChat WebView remote debugging techniques.\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fabczsl520\u002Fbug-audit",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill bug-audit",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill bug-audit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill bug-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fabczsl520\u002Fbug-audit\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]