[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76WNX4AFZGXAT5EP6BXKJZD":3,"skill-same:01M76WNX4AFZGXAT5EP6BXKJZD":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M76WNX4AFZGXAT5EP6BXKJZD","water-coach",null,"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\u002Foristides\u002Fwater-coach\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: water-coach\ndescription: \"Hydration tracking and coaching skill. Use when user wants to track water intake, get reminders to drink water, log body metrics, or get analytics on hydration habits.\"\ncompatibility: \"Requires python3, openclaw cron feature, heartbeat feature\"\nmetadata: {\"clawdbot\":{\"emoji\":\"💧\"} \n  author: oristides\n---\n\n# 💧 Water Coach\n\n\n\n## First-time Setup \n\nFollow the first setup here [references\u002Fsetup.md](references\u002Fsetup.md)\n\n---\n\n## 🤖 How Other Agents Should Interact\n\n### First-time Setup Check\n```bash\nwater setup\n```\n\n| is_setup | What to do |\n|----------|-------------|\n| **false** | Ask: weight OR desired goal. Also ask: \"What times do you want water reminders?\" (let user configure their schedule). Then use `water set_body_weight 80` or `water set_goal 3000`. Don't assume hardcoded times! |\n| **true** | Skip setup. Just log water or show status. |\n\n### ❌ Don't Ask\n- Reminder schedules after first setup (user already configured)\n\n### ✅ Do Ask  \n- \"How much water did you drink?\"\n- Only weight\u002Fgoal (first time)\n\n---\n\n## CLI Structure\n\n```bash\nwater_coach.py \u003Cnamespace> \u003Ccommand> [options]\n```\n\nNamespaces: `water` | `body` | `analytics`\n\n---\n\n## Data Format \n\n### CSV Format\n```\nlogged_at,drank_at,date,slot,ml_drank,goal_at_time,message_id\n```\n\n| Column | Description |\n|--------|-------------|\n| logged_at | When user told you (NOW) |\n| drank_at | When user actually drank (user can specify past time) |\n| date | Derived from drank_at |\n| slot | morning\u002Flunch\u002Fafternoon\u002Fevening\u002Fmanual |\n| ml_drank | Amount in ml |\n| goal_at_time | Goal at that moment |\n| message_id | Audit trail - link to conversation |\n\n**Key Rules:**\n- **drank_at is MANDATORY** - always required\n- If user doesn't specify drank_at → assume drank_at = logged_at\n- **Cumulative is calculated at query time** (not stored)\n- Use drank_at to determine which day counts\n\nDetails at  [references\u002Flog_format.md](references\u002Flog_format.md)\n\n### Audit Trail\n\nEvery water log entry captures:\n- **message_id**: Links to the conversation message where user requested the log\n- **Auto-capture**: CLI automatically gets message_id from session transcript\n- **Proof**: Use `water audit \u003Cmessage_id>` to get entry + conversation context\n\n```bash\n# Check proof of a water entry\nwater audit msg_123\n# Returns: entry data + surrounding messages for context\n```\n\n> ⚠️ **Privacy Notice**: The audit feature can read your conversation transcripts, but **only when you explicitly run `water audit \u003Cmessage_id>`**. This is off by default (`audit_auto_capture: false`).\n>\n> ```bash\n> # Edit water_config.json and set:\n> \"audit_auto_capture\": true\n> ```\n>\n> **How it works:**\n> - Water log **always** saves the `message_id` (regardless of this setting) ✅\n> - When you run `water audit \u003Cmessage_id>`:\n>   - If `false`: Shows entry data only (message_id saved, but no context read)\n>   - If `true`: Also reads transcript to show conversation context (\"User said: I drank 500ml\")\n>\n> **Why disable it?** If you discuss sensitive topics and don't need proof of intake, leave it off.\n\n---\n\n## Daily Commands\n\n```bash\n# Water\nwater status                                      # Current progress (calculated from drank_at)\nwater log 500                                    # Log intake (drank_at = now)\nwater log 500 --drank-at=2026-02-18T18:00:00Z  # Log with past time\nwater log 500 --drank-at=2026-02-18T18:00:00Z --message-id=msg_123\nwater dynamic                                    # Check if extra notification needed\nwater threshold                                  # Get expected % for current hour\nwater set_body_weight 80                        # Update weight + logs to body_metrics\nwater set_body_weight 80 --update-goal          # + update goal\nwater audit \u003Cmessage_id>                        # Get entry + conversation context\n\n# Body\nbody log --weight=80 --height=1.75 --body-fat=18\nbody latest          # Get latest metrics\nbody history 30     # Get history\n\n# Analytics\nanalytics week       # Weekly briefing (Sunday 8pm)\nanalytics month     # Monthly briefing (2nd day 8pm)\n```\n\n---\n\n## Rules (MUST FOLLOW)\n\n1. **ALWAYS use CLI** - never calculate manually\n2. **LLM interprets first** - \"eu tomei 2 copos\" → 500ml → water log 500\n3. **Threshold from CLI** - run `water threshold`, don't hardcode\n4. **GOAL is USER'S CHOICE** - weight × 35 is just a DEFAULT suggestion:\n   - At setup: Ask weight → suggest goal → **CONFIRM with user**\n   - On weight update: Ask \"Want to update your goal to the new suggested amount?\"\n   - User can set any goal (doctor's orders, preference, etc.)\n\n---\n\n## Config Tree\n\n```\nwater-coach\u002F\n├── SKILL.md              ← You are here\n├── scripts\u002F\n│   ├── water_coach.py   ← Unified CLI\n│   └── water.py         ← Core functions\n├── data\u002F                 ← DO NOT USE - keep skill code separate from user data\n└── references\u002F\n    ├── setup.md\n    ├── dynamic.md\n    └── log_format.md\n```\n\n### ⚠️ IMPORTANT: Data Location\n**User data is stored in the AGENT WORKSPACE, NOT in the skill folder!**\n\n| Data | Location |\n|------|----------|\n| water_log.csv | `\u003Cagent-workspace>\u002Fmemory\u002Fdata\u002Fwater_log.csv` |\n| water_config.json | `\u003Cagent-workspace>\u002Fmemory\u002Fdata\u002Fwater_config.json` |\n| body_metrics.csv | `\u003Cagent-workspace>\u002Fmemory\u002Fdata\u002Fbody_metrics.csv |\n\nExample path: `\u002Fhome\u002Foriel\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Fdata\u002F`\n\n**Why?** Keeps user data separate from skill code — makes backups, migrations, and skill updates easier.\n\n---\n\n## Notifications Schedule\n\n| Type | When | Command |\n|------|------|---------|\n| User Configured | Per user's schedule | water status |\n| Default Suggestion | 9am, 12pm, 3pm, 6pm, 9pm | water status |\n| Dynamic | Every ~30 min (heartbeat) | water dynamic |\n| Weekly | Sunday 8pm | analytics week |\n| Monthly | 2nd day 8pm | analytics month |\n\n### Notification Rules (MUST FOLLOW)\n- **USER CONFIGURES THEIR SCHEDULE** — Agent should ask user: \"What times do you want water reminders?\" and respect that\n- **NO \"no log\" skip logic** — Always send notifications when scheduled, don't skip because user hasn't logged water\n- **Notifications STIMULATE logging** — That's the point! Don't assume user will log on their own\n\n---\n\n## Quick Reference\n\n| Task | Command |\n|------|---------|\n| Check progress | `water_coach.py water status` |\n| Log water | `water_coach.py water log 500` |\n| Need extra? | `water_coach.py water dynamic` |\n| Body metrics | `water_coach.py body log --weight=80` |\n| Weekly report | `water_coach.py analytics week` |\n| Monthly report | `water_coach.py analytics month` |\n\n## Dynamic Scheduling details\n→ [references\u002Fdynamic.md](references\u002Fdynamic.md)\n\n### ⚠️ Bug Fix (Feb 2026)\nThe `water dynamic` command had a bug where the hourly notification counter wouldn't reset when the hour changed. This is now fixed:\n- The script now checks if the current hour differs from `last_extra_hour` and resets the counter accordingly\n- This ensures notifications work correctly after hour boundaries (e.g., 4PM)\n\n### ⚠️ Bug Fix (Feb 2026) - Analytics\nThe `analyticsPM → 5 week` and `analytics month` commands had a bug:\n- Was looking for non-existent `cumulative_ml` column in CSV\n- Fixed to sum `ml_drank` per day instead\n\n### ✅ How to Build Good Weekly\u002FMonthly Reports\n\n**Use these functions (don't reinvent):**\n\n| Report | Script | Function |\n|--------|--------|----------|\n| Weekly | `water_coach.py analytics week` | `analytics_week()` in `water_coach.py` |\n| Monthly | `water_coach.py analytics month` | `analytics_month()` in `water_coach.py` |\n\nThese call `get_week_stats()` and `get_month_stats()` in `water.py`.\n\n**When updating analytics functions, follow these rules:**\n\n**1. Include ALL days, even with 0ml**\n```python\n# In get_week_stats() \u002F get_month_stats()\n# Include every day in the range, not just days with data\nfor i in range(days):\n    d = (date.today() - timedelta(days=i)).strftime(\"%Y-%m-%d\")\n    ml = by_date.get(d, {}).get(\"ml\", 0)  # Default to 0, not skip\n```\n\n**2. Calculate true average**\n```python\n# Average = total_ml \u002F ALL days (including zeros), not just tracked days\navg_ml = total_ml \u002F days  # e.g., 15440ml \u002F 7 days = 2205ml\u002Fday\n```\n\n**3. Show all days in table format**\n```python\n| Dia | ML | % | Status |\n| Sab 22 | 2250ml | 67.7% | ⚠️ |\n| Seg 17 | 0ml | 0.0% | ❌ |\n```\n\nThis gives users an accurate picture of their habits!\n\n\n\n## Tests\n\n```bash\npython3 -m pytest skills\u002Fwater-coach\u002Fscripts\u002Ftest\u002Ftest_water.py -v\n```\n\n## Example\n\n```\nUser: \"eu tomei 2 copos\"\nAgent: (LLM interprets: 2 copos ≈ 500ml)\nAgent: exec(\"water_coach.py water log 500\")\n→ Python logs to CSV\n```\n\n\n\nAgent Evaluations → [evaluation\u002FAGENT.md](evaluation\u002FAGENT.md)\n\n","# 💧 Water Coach\n\n\n\n## First-time Setup \n\nFollow the first setup here [references\u002Fsetup.md](references\u002Fsetup.md)\n\n---\n\n## 🤖 How Other Agents Should Interact\n\n### First-time Setup Check\n```bash\nwater setup\n```\n\n| is_setup | What to do |\n|----------|-------------|\n| **false** | Ask: weight OR desired goal. Also ask: \"What times do you want water reminders?\" (let user configure their schedule). Then use `water set_body_weight 80` or `water set_goal 3000`. Don't assume hardcoded times! |\n| **true** | Skip setup. Just log water or show status. |\n\n### ❌ Don't Ask\n- Reminder schedules after first setup (user already configured)\n\n### ✅ Do Ask  \n- \"How much water did you drink?\"\n- Only weight\u002Fgoal (first time)\n\n---\n\n## CLI Structure\n\n```bash\nwater_coach.py \u003Cnamespace> \u003Ccommand> [options]\n```\n\nNamespaces: `water` | `body` | `analytics`\n\n---\n\n## Data Format \n\n### CSV Format\n```\nlogged_at,drank_at,date,slot,ml_drank,goal_at_time,message_id\n```\n\n| Column | Description |\n|--------|-------------|\n| logged_at | When user told you (NOW) |\n| drank_at | When user actually drank (user can specify past time) |\n| date | Derived from drank_at |\n| slot | morning\u002Flunch\u002Fafternoon\u002Fevening\u002Fmanual |\n| ml_drank | Amount in ml |\n| goal_at_time | Goal at that moment |\n| message_id | Audit trail - link to conversation |\n\n**Key Rules:**\n- **drank_at is MANDATORY** - always required\n- If user doesn't specify drank_at → assume drank_at = logged_at\n- **Cumulative is calculated at query time** (not stored)\n- Use drank_at to determine which day counts\n\nDetails at  [references\u002Flog_format.md](references\u002Flog_format.md)\n\n### Audit Trail\n\nEvery water log entry captures:\n- **message_id**: Links to the conversation message where user requested the log\n- **Auto-capture**: CLI automatically gets message_id from session transcript\n- **Proof**: Use `water audit \u003Cmessage_id>` to get entry + conversation context\n\n```bash\n# Check proof of a water entry\nwater audit msg_123\n# Returns: entry data + surrounding messages for context\n```\n\n> ⚠️ **Privacy Notice**: The audit feature can read your conversation transcripts, but **only when you explicitly run `water audit \u003Cmessage_id>`**. This is off by default (`audit_auto_capture: false`).\n>\n> ```bash\n> # Edit water_config.json and set:\n> \"audit_auto_capture\": true\n> ```\n>\n> **How it works:**\n> - Water log **always** saves the `message_id` (regardless of this setting) ✅\n> - When you run `water audit \u003Cmessage_id>`:\n>   - If `false`: Shows entry data only (message_id saved, but no context read)\n>   - If `true`: Also reads transcript to show conversation context (\"User said: I drank 500ml\")\n>\n> **Why disable it?** If you discuss sensitive topics and don't need proof of intake, leave it off.\n\n---\n\n## Daily Commands\n\n```bash\n# Water\nwater status                                      # Current progress (calculated from drank_at)\nwater log 500                                    # Log intake (drank_at = now)\nwater log 500 --drank-at=2026-02-18T18:00:00Z  # Log with past time\nwater log 500 --drank-at=2026-02-18T18:00:00Z --message-id=msg_123\nwater dynamic                                    # Check if extra notification needed\nwater threshold                                  # Get expected % for current hour\nwater set_body_weight 80                        # Update weight + logs to body_metrics\nwater set_body_weight 80 --update-goal          # + update goal\nwater audit \u003Cmessage_id>                        # Get entry + conversation context\n\n# Body\nbody log --weight=80 --height=1.75 --body-fat=18\nbody latest          # Get latest metrics\nbody history 30     # Get history\n\n# Analytics\nanalytics week       # Weekly briefing (Sunday 8pm)\nanalytics month     # Monthly briefing (2nd day 8pm)\n```\n\n---\n\n## Rules (MUST FOLLOW)\n\n1. **ALWAYS use CLI** - never calculate manually\n2. **LLM interprets first** - \"eu tomei 2 copos\" → 500ml → water log 500\n3. **Threshold from CLI** - run `water threshold`, don't hardcode\n4. **GOAL is USER'S CHOICE** - weight × 35 is just a DEFAULT suggestion:\n   - At setup: Ask weight → suggest goal → **CONFIRM with user**\n   - On weight update: Ask \"Want to update your goal to the new suggested amount?\"\n   - User can set any goal (doctor's orders, preference, etc.)\n\n---\n\n## Config Tree\n\n```\nwater-coach\u002F\n├── SKILL.md              ← You are here\n├── scripts\u002F\n│   ├── water_coach.py   ← Unified CLI\n│   └── water.py         ← Core functions\n├── data\u002F                 ← DO NOT USE - keep skill code separate from user data\n└── references\u002F\n    ├── setup.md\n    ├── dynamic.md\n    └── log_format.md\n```\n\n### ⚠️ IMPORTANT: Data Location\n**User data is stored in the AGENT WORKSPACE, NOT in the skill folder!**\n\n| Data | Location |\n|------|----------|\n| water_log.csv | `\u003Cagent-workspace>\u002Fmemory\u002Fdata\u002Fwater_log.csv` |\n| water_config.json | `\u003Cagent-workspace>\u002Fmemory\u002Fdata\u002Fwater_config.json` |\n| body_metrics.csv | `\u003Cagent-workspace>\u002Fmemory\u002Fdata\u002Fbody_metrics.csv |\n\nExample path: `\u002Fhome\u002Foriel\u002F.openclaw\u002Fworkspace\u002Fmemory\u002Fdata\u002F`\n\n**Why?** Keeps user data separate from skill code — makes backups, migrations, and skill updates easier.\n\n---\n\n## Notifications Schedule\n\n| Type | When | Command |\n|------|------|---------|\n| User Configured | Per user's schedule | water status |\n| Default Suggestion | 9am, 12pm, 3pm, 6pm, 9pm | water status |\n| Dynamic | Every ~30 min (heartbeat) | water dynamic |\n| Weekly | Sunday 8pm | analytics week |\n| Monthly | 2nd day 8pm | analytics month |\n\n### Notification Rules (MUST FOLLOW)\n- **USER CONFIGURES THEIR SCHEDULE** — Agent should ask user: \"What times do you want water reminders?\" and respect that\n- **NO \"no log\" skip logic** — Always send notifications when scheduled, don't skip because user hasn't logged water\n- **Notifications STIMULATE logging** — That's the point! Don't assume user will log on their own\n\n---\n\n## Quick Reference\n\n| Task | Command |\n|------|---------|\n| Check progress | `water_coach.py water status` |\n| Log water | `water_coach.py water log 500` |\n| Need extra? | `water_coach.py water dynamic` |\n| Body metrics | `water_coach.py body log --weight=80` |\n| Weekly report | `water_coach.py analytics week` |\n| Monthly report | `water_coach.py analytics month` |\n\n## Dynamic Scheduling details\n→ [references\u002Fdynamic.md](references\u002Fdynamic.md)\n\n### ⚠️ Bug Fix (Feb 2026)\nThe `water dynamic` command had a bug where the hourly notification counter wouldn't reset when the hour changed. This is now fixed:\n- The script now checks if the current hour differs from `last_extra_hour` and resets the counter accordingly\n- This ensures notifications work correctly after hour boundaries (e.g., 4PM)\n\n### ⚠️ Bug Fix (Feb 2026) - Analytics\nThe `analyticsPM → 5 week` and `analytics month` commands had a bug:\n- Was looking for non-existent `cumulative_ml` column in CSV\n- Fixed to sum `ml_drank` per day instead\n\n### ✅ How to Build Good Weekly\u002FMonthly Reports\n\n**Use these functions (don't reinvent):**\n\n| Report | Script | Function |\n|--------|--------|----------|\n| Weekly | `water_coach.py analytics week` | `analytics_week()` in `water_coach.py` |\n| Monthly | `water_coach.py analytics month` | `analytics_month()` in `water_coach.py` |\n\nThese call `get_week_stats()` and `get_month_stats()` in `water.py`.\n\n**When updating analytics functions, follow these rules:**\n\n**1. Include ALL days, even with 0ml**\n```python\n# In get_week_stats() \u002F get_month_stats()\n# Include every day in the range, not just days with data\nfor i in range(days):\n    d = (date.today() - timedelta(days=i)).strftime(\"%Y-%m-%d\")\n    ml = by_date.get(d, {}).get(\"ml\", 0)  # Default to 0, not skip\n```\n\n**2. Calculate true average**\n```python\n# Average = total_ml \u002F ALL days (including zeros), not just tracked days\navg_ml = total_ml \u002F days  # e.g., 15440ml \u002F 7 days = 2205ml\u002Fday\n```\n\n**3. Show all days in table format**\n```python\n| Dia | ML | % | Status |\n| Sab 22 | 2250ml | 67.7% | ⚠️ |\n| Seg 17 | 0ml | 0.0% | ❌ |\n```\n\nThis gives users an accurate picture of their habits!\n\n\n\n## Tests\n\n```bash\npython3 -m pytest skills\u002Fwater-coach\u002Fscripts\u002Ftest\u002Ftest_water.py -v\n```\n\n## Example\n\n```\nUser: \"eu tomei 2 copos\"\nAgent: (LLM interprets: 2 copos ≈ 500ml)\nAgent: exec(\"water_coach.py water log 500\")\n→ Python logs to CSV\n```\n\n\n\nAgent Evaluations → [evaluation\u002FAGENT.md](evaluation\u002FAGENT.md)\n\n",{},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Foristides\u002Fwater-coach",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":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill water-coach",{"tool":38,"command":39},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill water-coach",{"tool":41,"command":42},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill water-coach","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Foristides\u002Fwater-coach\u002FSKILL.md",true,[],[47,55,62,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":54},"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":54},"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":54},"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":54},"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":54},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":54},"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",[],[]]