[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PBVNKTF7KZS08NZ54PCYA":3,"skill-same:01M75PBVNKTF7KZS08NZ54PCYA":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M75PBVNKTF7KZS08NZ54PCYA","nas-agent-sync",null,"Synology NAS integration for OpenClaw — centralized file storage for multi-agent teams via SSH","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\u002Fneal-collab\u002Fnas-agent-sync\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: nas-agent-sync\nversion: 1.1.0\ndescription: Synology NAS integration for OpenClaw — centralized file storage for multi-agent teams via SSH\nemoji: 📦\ntags:\n  - nas\n  - synology\n  - file-storage\n  - ssh\n  - multi-agent\n  - backup\n---\n\n# NAS Agent Sync — Synology File Storage for OpenClaw Agents\n\nCentralize file storage across your multi-agent team using a Synology NAS (or any SSH-accessible storage). One agent acts as **File Master** — all others route file requests through it.\n\n## The Problem\n\nMulti-agent setups generate files across multiple workspaces. Without centralized storage:\n- Files get lost between agent sessions\n- No backup strategy\n- Agents duplicate work\n- No single source of truth\n\n## The Solution\n\nDesignate one agent as **File Master**. All file operations go through this agent via `sessions_send`. The File Master manages:\n- SSH connection to NAS\n- Folder structure per agent\n- File storage and retrieval\n- Cross-agent file sharing\n\n## Architecture\n\n```\n┌──────────┐    sessions_send     ┌────────────┐     SSH      ┌─────────┐\n│ Agent A  │ ──────────────────► │ FILE MASTER │ ──────────► │   NAS   │\n│ (Finance)│ \"store invoice.pdf\" │ (Tech Lead) │             │         │\n└──────────┘                     └────────────┘             └─────────┘\n                                       │\n┌──────────┐    sessions_send          │  SSH\n│ Agent B  │ ──────────────────►       │\n│ (Sales)  │ \"get sales report\"        ▼\n└──────────┘                     ┌─────────────┐\n                                 │ _agents\u002F     │\n                                 │ ├── agent-a\u002F │\n                                 │ ├── agent-b\u002F │\n                                 │ ├── agent-c\u002F │\n                                 │ └── _shared\u002F │\n                                 └─────────────┘\n```\n\n## Setup\n\n### 1. NAS Prerequisites\n\n- Synology NAS (any model) or any Linux server with SSH\n- SSH access with key-based auth\n- VPN or Tailnet (recommended) for secure remote access\n\n### 2. Create Folder Structure\n\n```bash\nSSH_HOST=\"user@your-nas-ip\"\n\n# Create agent folders (customize agent names to match your team)\nssh $SSH_HOST \"mkdir -p ~\u002F_agents\u002F{coordinator,techops,finance,sales,marketing}\"\n\n# Create shared folders\nssh $SSH_HOST \"mkdir -p ~\u002F_shared\u002F{config,templates}\"\n\n# Create agent directory file\nssh $SSH_HOST 'cat > ~\u002F_shared\u002Fconfig\u002Fagent-directory.json \u003C\u003C EOF\n{\n  \"agents\": {\n    \"coordinator\": { \"role\": \"Coordinator\", \"path\": \"~\u002F_agents\u002Fcoordinator\u002F\" },\n    \"techops\": { \"role\": \"File Master\", \"path\": \"~\u002F_agents\u002Ftechops\u002F\" },\n    \"finance\": { \"role\": \"Finance\", \"path\": \"~\u002F_agents\u002Ffinance\u002F\" }\n  },\n  \"shared\": \"~\u002F_shared\u002F\",\n  \"basePath\": \"~\u002F\"\n}\nEOF'\n```\n\n### 3. Configure File Master Agent\n\nAdd to your File Master agent's `AGENTS.md`:\n\n```markdown\n## FILE MASTER — Incoming Requests\n\nWhen another agent sends a file request via sessions_send:\n\n### Store a file:\nssh USER@NAS-IP \"mkdir -p ~\u002F_agents\u002F[agent]\u002F[subfolder]\u002F\"\n# Copy\u002Fcreate file there\n\n### Retrieve a file:\nssh USER@NAS-IP \"cat ~\u002F_agents\u002F[agent]\u002F[file]\"\n# Send content back to requesting agent\n\n### Confirm back:\nsessions_send(sessionKey=\"agent:[requester]:main\", message=\"Done! File at [path]\")\n```\n\n### 4. Configure Other Agents\n\nAdd to each agent's `AGENTS.md`:\n\n```markdown\n## File Operations → File Master\n\nI do NOT access files directly. ALL file ops go through the File Master:\n\nsessions_send(sessionKey=\"agent:techops:main\", message=\"Store: [details]\")\nsessions_send(sessionKey=\"agent:techops:main\", message=\"Retrieve: [path]\")\n```\n\n## NAS Folder Structure (Recommended)\n\n```\n~\u002F\n├── _agents\u002F\n│   ├── coordinator\u002F     # Coordinator files\n│   │   ├── journal\u002F     # Daily journals\n│   │   └── tracking\u002F    # Task tracking\n│   ├── techops\u002F         # Tech docs, scripts\n│   │   ├── scripts\u002F\n│   │   └── configs\u002F\n│   ├── finance\u002F         # Finance\n│   │   ├── invoices\u002F\n│   │   ├── contracts\u002F\n│   │   └── reports\u002F\n│   ├── sales\u002F           # Sales\n│   │   ├── leads\u002F\n│   │   └── proposals\u002F\n│   └── [your-agent]\u002F    # Per-agent storage\n├── _shared\u002F\n│   ├── config\u002F          # Shared configs\n│   │   └── agent-directory.json\n│   └── templates\u002F       # Shared templates\n└── _backups\u002F\n    └── memory\u002F          # Memory file backups\n```\n\n## SSH via VPN\u002FTailnet (Recommended)\n\n```bash\n# Connect via secure tunnel IP (e.g. WireGuard, ZeroTier, or similar)\nSSH_HOST=\"user@10.x.x.x\"  # Your VPN\u002FTailnet IP\n\n# Test connection\nssh $SSH_HOST \"echo 'NAS connected!'\"\n```\n\n## Security\n\n- ✅ SSH key-based auth (no passwords in configs)\n- ✅ VPN\u002FTailnet for encrypted tunnel (no port forwarding needed)\n- ✅ File Master pattern limits SSH access to one agent\n- ✅ Other agents never get SSH credentials\n- ❌ Never store SSH keys in agent SOUL.md or memory files\n\n## Why File Master Pattern?\n\n1. **Security**: Only one agent has NAS credentials\n2. **Consistency**: Single point of truth for file locations\n3. **Audit trail**: All file ops logged through one agent\n4. **Simplicity**: Other agents don't need to know SSH commands\n\n## Backup Strategy\n\n### Daily Backup Cron (via OpenClaw)\nSet up a cron job that backs up agent workspaces to NAS:\n\n```json5\n\u002F\u002F Cron job config\n{\n  \"schedule\": { \"kind\": \"cron\", \"expr\": \"0 3 * * *\", \"tz\": \"UTC\" },\n  \"payload\": {\n    \"kind\": \"agentTurn\",\n    \"message\": \"Backup all agent workspaces to NAS. For each agent: rsync workspace memory\u002F folder to NAS _agents\u002F{agent}\u002Fmemory-backup\u002F. Report any failures.\"\n  },\n  \"sessionTarget\": \"isolated\"\n}\n```\n\n### Manual Backup Command\n```bash\n# Backup specific agent\nrsync -avz ~\u002F.openclaw\u002Fworkspace-finance\u002Fmemory\u002F user@nas-ip:~\u002F_agents\u002Ffinance\u002Fmemory-backup\u002F\n\n# Backup all agents (customize list to your team)\nfor agent in coordinator techops finance sales marketing; do\n  rsync -avz ~\u002F.openclaw\u002Fworkspace-$agent\u002Fmemory\u002F user@nas-ip:~\u002F_agents\u002F$agent\u002Fmemory-backup\u002F\ndone\n```\n\n## Troubleshooting\n\n**SSH connection refused:**\n→ Check VPN\u002FTailnet status — is NAS online and connected?\n→ Verify SSH service running on NAS (Synology: DSM → Control Panel → Terminal & SNMP)\n\n**Permission denied:**\n→ SSH key not added: `ssh-copy-id user@nas-ip`\n→ NAS home folder not enabled (Synology: DSM → User → Advanced → Enable home service)\n\n**Slow transfers:**\n→ Use direct VPN connection (not relayed)\n→ Consider compression: `rsync -avz --compress`\n\n## Compatible NAS Models\n\n- ✅ Synology (any model with DSM 7+)\n- ✅ QNAP (QTS 5+)\n- ✅ TrueNAS \u002F FreeNAS\n- ✅ Any Linux server with SSH access\n- ✅ Raspberry Pi with external storage\n\n## Changelog\n\n### v1.1.0\n- Removed all specific agent\u002Fsetup references\n- Generalized folder structure and examples\n- Added backup strategy with cron\n\n### v1.0.0\n- Initial release\n","# NAS Agent Sync — Synology File Storage for OpenClaw Agents\n\nCentralize file storage across your multi-agent team using a Synology NAS (or any SSH-accessible storage). One agent acts as **File Master** — all others route file requests through it.\n\n## The Problem\n\nMulti-agent setups generate files across multiple workspaces. Without centralized storage:\n- Files get lost between agent sessions\n- No backup strategy\n- Agents duplicate work\n- No single source of truth\n\n## The Solution\n\nDesignate one agent as **File Master**. All file operations go through this agent via `sessions_send`. The File Master manages:\n- SSH connection to NAS\n- Folder structure per agent\n- File storage and retrieval\n- Cross-agent file sharing\n\n## Architecture\n\n```\n┌──────────┐    sessions_send     ┌────────────┐     SSH      ┌─────────┐\n│ Agent A  │ ──────────────────► │ FILE MASTER │ ──────────► │   NAS   │\n│ (Finance)│ \"store invoice.pdf\" │ (Tech Lead) │             │         │\n└──────────┘                     └────────────┘             └─────────┘\n                                       │\n┌──────────┐    sessions_send          │  SSH\n│ Agent B  │ ──────────────────►       │\n│ (Sales)  │ \"get sales report\"        ▼\n└──────────┘                     ┌─────────────┐\n                                 │ _agents\u002F     │\n                                 │ ├── agent-a\u002F │\n                                 │ ├── agent-b\u002F │\n                                 │ ├── agent-c\u002F │\n                                 │ └── _shared\u002F │\n                                 └─────────────┘\n```\n\n## Setup\n\n### 1. NAS Prerequisites\n\n- Synology NAS (any model) or any Linux server with SSH\n- SSH access with key-based auth\n- VPN or Tailnet (recommended) for secure remote access\n\n### 2. Create Folder Structure\n\n```bash\nSSH_HOST=\"user@your-nas-ip\"\n\n# Create agent folders (customize agent names to match your team)\nssh $SSH_HOST \"mkdir -p ~\u002F_agents\u002F{coordinator,techops,finance,sales,marketing}\"\n\n# Create shared folders\nssh $SSH_HOST \"mkdir -p ~\u002F_shared\u002F{config,templates}\"\n\n# Create agent directory file\nssh $SSH_HOST 'cat > ~\u002F_shared\u002Fconfig\u002Fagent-directory.json \u003C\u003C EOF\n{\n  \"agents\": {\n    \"coordinator\": { \"role\": \"Coordinator\", \"path\": \"~\u002F_agents\u002Fcoordinator\u002F\" },\n    \"techops\": { \"role\": \"File Master\", \"path\": \"~\u002F_agents\u002Ftechops\u002F\" },\n    \"finance\": { \"role\": \"Finance\", \"path\": \"~\u002F_agents\u002Ffinance\u002F\" }\n  },\n  \"shared\": \"~\u002F_shared\u002F\",\n  \"basePath\": \"~\u002F\"\n}\nEOF'\n```\n\n### 3. Configure File Master Agent\n\nAdd to your File Master agent's `AGENTS.md`:\n\n```markdown\n## FILE MASTER — Incoming Requests\n\nWhen another agent sends a file request via sessions_send:\n\n### Store a file:\nssh USER@NAS-IP \"mkdir -p ~\u002F_agents\u002F[agent]\u002F[subfolder]\u002F\"\n# Copy\u002Fcreate file there\n\n### Retrieve a file:\nssh USER@NAS-IP \"cat ~\u002F_agents\u002F[agent]\u002F[file]\"\n# Send content back to requesting agent\n\n### Confirm back:\nsessions_send(sessionKey=\"agent:[requester]:main\", message=\"Done! File at [path]\")\n```\n\n### 4. Configure Other Agents\n\nAdd to each agent's `AGENTS.md`:\n\n```markdown\n## File Operations → File Master\n\nI do NOT access files directly. ALL file ops go through the File Master:\n\nsessions_send(sessionKey=\"agent:techops:main\", message=\"Store: [details]\")\nsessions_send(sessionKey=\"agent:techops:main\", message=\"Retrieve: [path]\")\n```\n\n## NAS Folder Structure (Recommended)\n\n```\n~\u002F\n├── _agents\u002F\n│   ├── coordinator\u002F     # Coordinator files\n│   │   ├── journal\u002F     # Daily journals\n│   │   └── tracking\u002F    # Task tracking\n│   ├── techops\u002F         # Tech docs, scripts\n│   │   ├── scripts\u002F\n│   │   └── configs\u002F\n│   ├── finance\u002F         # Finance\n│   │   ├── invoices\u002F\n│   │   ├── contracts\u002F\n│   │   └── reports\u002F\n│   ├── sales\u002F           # Sales\n│   │   ├── leads\u002F\n│   │   └── proposals\u002F\n│   └── [your-agent]\u002F    # Per-agent storage\n├── _shared\u002F\n│   ├── config\u002F          # Shared configs\n│   │   └── agent-directory.json\n│   └── templates\u002F       # Shared templates\n└── _backups\u002F\n    └── memory\u002F          # Memory file backups\n```\n\n## SSH via VPN\u002FTailnet (Recommended)\n\n```bash\n# Connect via secure tunnel IP (e.g. WireGuard, ZeroTier, or similar)\nSSH_HOST=\"user@10.x.x.x\"  # Your VPN\u002FTailnet IP\n\n# Test connection\nssh $SSH_HOST \"echo 'NAS connected!'\"\n```\n\n## Security\n\n- ✅ SSH key-based auth (no passwords in configs)\n- ✅ VPN\u002FTailnet for encrypted tunnel (no port forwarding needed)\n- ✅ File Master pattern limits SSH access to one agent\n- ✅ Other agents never get SSH credentials\n- ❌ Never store SSH keys in agent SOUL.md or memory files\n\n## Why File Master Pattern?\n\n1. **Security**: Only one agent has NAS credentials\n2. **Consistency**: Single point of truth for file locations\n3. **Audit trail**: All file ops logged through one agent\n4. **Simplicity**: Other agents don't need to know SSH commands\n\n## Backup Strategy\n\n### Daily Backup Cron (via OpenClaw)\nSet up a cron job that backs up agent workspaces to NAS:\n\n```json5\n\u002F\u002F Cron job config\n{\n  \"schedule\": { \"kind\": \"cron\", \"expr\": \"0 3 * * *\", \"tz\": \"UTC\" },\n  \"payload\": {\n    \"kind\": \"agentTurn\",\n    \"message\": \"Backup all agent workspaces to NAS. For each agent: rsync workspace memory\u002F folder to NAS _agents\u002F{agent}\u002Fmemory-backup\u002F. Report any failures.\"\n  },\n  \"sessionTarget\": \"isolated\"\n}\n```\n\n### Manual Backup Command\n```bash\n# Backup specific agent\nrsync -avz ~\u002F.openclaw\u002Fworkspace-finance\u002Fmemory\u002F user@nas-ip:~\u002F_agents\u002Ffinance\u002Fmemory-backup\u002F\n\n# Backup all agents (customize list to your team)\nfor agent in coordinator techops finance sales marketing; do\n  rsync -avz ~\u002F.openclaw\u002Fworkspace-$agent\u002Fmemory\u002F user@nas-ip:~\u002F_agents\u002F$agent\u002Fmemory-backup\u002F\ndone\n```\n\n## Troubleshooting\n\n**SSH connection refused:**\n→ Check VPN\u002FTailnet status — is NAS online and connected?\n→ Verify SSH service running on NAS (Synology: DSM → Control Panel → Terminal & SNMP)\n\n**Permission denied:**\n→ SSH key not added: `ssh-copy-id user@nas-ip`\n→ NAS home folder not enabled (Synology: DSM → User → Advanced → Enable home service)\n\n**Slow transfers:**\n→ Use direct VPN connection (not relayed)\n→ Consider compression: `rsync -avz --compress`\n\n## Compatible NAS Models\n\n- ✅ Synology (any model with DSM 7+)\n- ✅ QNAP (QTS 5+)\n- ✅ TrueNAS \u002F FreeNAS\n- ✅ Any Linux server with SSH access\n- ✅ Raspberry Pi with external storage\n\n## Changelog\n\n### v1.1.0\n- Removed all specific agent\u002Fsetup references\n- Generalized folder structure and examples\n- Added backup strategy with cron\n\n### v1.0.0\n- Initial release\n",{"name":5,"tags":24,"emoji":31,"version":32,"description":7},[25,26,27,28,29,30],"nas","synology","file-storage","ssh","multi-agent","backup","📦","1.1.0","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fneal-collab\u002Fnas-agent-sync",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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill nas-agent-sync",{"tool":48,"command":49},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill nas-agent-sync",{"tool":51,"command":52},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill nas-agent-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fneal-collab\u002Fnas-agent-sync\u002FSKILL.md",true,[],[57,65,72,79,86,93],{"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":64},"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":64},"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":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":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":64},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":64},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":64},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":64},"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",[],[]]