[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M771BQK8RX84WSZ034G37CCP":3,"skill-same:01M771BQK8RX84WSZ034G37CCP":54},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M771BQK8RX84WSZ034G37CCP","swamp",null,"Model any API with Swamp, test it, and enrich *Claw with new capabilities — full lifecycle from idea to working integration","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\u002Fumag\u002Fswamp\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: swamp\ndescription: Model any API with Swamp, test it, and enrich *Claw with new capabilities — full lifecycle from idea to working integration\nversion: 0.2.0\nmetadata:\n  openclaw:\n    requires:\n      bins:\n        - swamp\n    emoji: \"🐊\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsysteminit\u002Fswamp\n---\n\n# Swamp — API Modeling & *Claw Enrichment\n\nYou are an AI agent that uses Swamp to model any API, test it, and turn it into a reusable *Claw capability. Swamp is an AI-native automation CLI that represents external resources (APIs, CLIs, cloud services) as typed models with executable methods and composable workflows.\n\n## Repository Setup\n\nBefore any operation, check if the current directory is a swamp repository. If not, initialize one:\n\n```bash\nswamp repo init --tool claude\n```\n\nThis creates a `.swamp\u002F` directory with the necessary structure. Use `--tool claude` to set up the AI agent integration for Claude\u002FOpenClaw.\n\n## API Modeling Workflow\n\n### Step 1: Discover Model Types\n\nFind available model types to understand what kinds of resources can be modeled:\n\n```bash\nswamp model type search\nswamp model type describe \u003Ctype>\n```\n\nThe `command\u002Fshell` type is the most versatile — it can model any API via shell commands (curl, httpie, CLI tools).\n\n### Step 2: Create a Model\n\nCreate a new model definition for the API:\n\n```bash\nswamp model create \u003Ctype> \u003Cname>\n```\n\nExample: `swamp model create command\u002Fshell github-issues`\n\n### Step 3: Edit the Model Definition\n\nOpen and edit the model's YAML definition to configure endpoints, authentication, parameters, and methods:\n\n```bash\nswamp model edit \u003Cname>\n```\n\nWhen editing, define:\n- **Methods**: The operations this API supports (list, create, update, delete)\n- **Inputs**: Parameters each method accepts\n- **Authentication**: Reference vault secrets via CEL expressions\n- **Commands**: The actual shell commands (curl calls, CLI invocations) that execute each method\n\n### Step 4: Validate\n\nEnsure the model definition is well-formed:\n\n```bash\nswamp model validate \u003Cname>\n```\n\nFix any validation errors before proceeding.\n\n## Testing & Execution\n\n### Run a Method\n\nExecute a method on your model to test it:\n\n```bash\nswamp model method run \u003Cmodel_name> \u003Cmethod_name>\n```\n\n### Inspect Results\n\nCheck outputs, logs, and data from the execution:\n\n```bash\nswamp model output get \u003Coutput_id_or_model_name>\nswamp model output logs \u003Coutput_id>\nswamp model output data \u003Coutput_id>\n```\n\n### Review History\n\nSee past executions:\n\n```bash\nswamp model method history search\nswamp model method history get \u003Coutput_id_or_model_name>\n```\n\nIterate on the model definition until methods return the expected results.\n\n## Workflow Orchestration\n\nChain multiple model methods into automated workflows with dependency ordering:\n\n```bash\nswamp workflow create \u003Cname>\nswamp workflow edit \u003Cname>\nswamp workflow validate \u003Cname>\nswamp workflow run \u003Cname>\n```\n\nWorkflows support:\n- Parallel job execution\n- Dependency ordering between jobs\n- Trigger conditions via CEL expressions\n- Cross-model references (one model's output feeds into another)\n\nCheck workflow results:\n\n```bash\nswamp workflow history get \u003Cname>\nswamp workflow history logs \u003Crun_id>\n```\n\n## Vault & Credentials\n\nStore API keys and secrets securely — never hardcode them:\n\n```bash\nswamp vault create \u003Ctype> \u003Cname>\nswamp vault put \u003Cvault_name> \u003CKEY=value>\nswamp vault list-keys \u003Cvault_name>\n```\n\nReference secrets in model definitions using CEL expressions like `vault.get(\"my-vault\", \"API_KEY\")`.\n\n## Data Management\n\nInspect outputs and artifacts across models:\n\n```bash\nswamp data list \u003Cmodel_name>\nswamp data get \u003Cmodel_name> \u003Cdata_name>\nswamp data search \u003Cquery>\n```\n\n## Swamp-Club Authentication\n\nSwamp-club is the community registry and collaboration layer. Authenticate to push\u002Fpull extensions and share work:\n\n```bash\nswamp auth login\nswamp auth login --server \u003Curl>\nswamp auth whoami\nswamp auth logout\n```\n\n- `swamp auth login` opens a browser-based login flow by default\n- Use `--no-browser` with `--username` and `--password` for headless\u002FCI environments\n- Set `SWAMP_CLUB_URL` env var to target a custom server\n- Always verify identity with `swamp auth whoami` after login\n\nAuthentication is required before pushing extensions to the registry.\n\n## Extensions\n\nExtensions expand Swamp's model types and capabilities. Use the extension registry to share and reuse custom models:\n\n### Pull an Extension\n\nInstall a community or team extension from the registry:\n\n```bash\nswamp extension pull \u003Cextension_name>\nswamp extension pull \u003Cextension_name> --force\n```\n\nUse `--force` to overwrite existing files without prompting.\n\n### List Installed Extensions\n\nSee what extensions are currently installed:\n\n```bash\nswamp extension list\n```\n\n### Push an Extension\n\nPublish your own extension to the swamp registry (requires `swamp auth login` first):\n\n```bash\nswamp extension push \u003Cmanifest-path>\nswamp extension push \u003Cmanifest-path> --dry-run\n```\n\nUse `--dry-run` to build the archive locally and verify it without actually publishing. Use `-y` to skip confirmation prompts.\n\n### Remove an Extension\n\nUninstall a pulled extension and clean up its files:\n\n```bash\nswamp extension remove \u003Cextension_name>\n```\n\n### Extension Workflow\n\nThe typical flow for extending Swamp with new model types:\n\n1. Create custom TypeScript model definitions in `extensions\u002Fmodels\u002F`\n2. Test locally with `swamp model create \u003Cyour-type> \u003Cname>`\n3. Package with a manifest file\n4. Dry-run: `swamp extension push .\u002Fmanifest.yaml --dry-run`\n5. Publish: `swamp extension push .\u002Fmanifest.yaml`\n6. Others install: `swamp extension pull \u003Cyour-extension>`\n\n## Enriching *Claw with New Capabilities\n\nOnce a Swamp model is validated and working, turn it into a standalone *Claw skill:\n\n1. **Export the model**: Use `swamp model get \u003Cname> --json` to extract the full definition\n2. **Generate a SKILL.md**: Create a new skill file that wraps the Swamp model's methods as agent instructions\n3. **Include setup instructions**: Document the required env vars, binaries, and vault configuration\n4. **Publish to ClawHub**: Share the skill with the community via `clawhub publish`\n\nThe generated skill should:\n- Require `swamp` in its `bins` dependency\n- Reference the swamp repo and model by name\n- Map each model method to a clear agent instruction\n- Include examples of typical invocations\n\n### Sharing via Extensions\n\nFor reusable model types (not just individual models), publish as a Swamp extension:\n\n1. Build the custom model type in `extensions\u002Fmodels\u002F`\n2. Push to the Swamp registry: `swamp extension push .\u002Fmanifest.yaml`\n3. Create a *Claw skill that pulls the extension and uses it: `swamp extension pull \u003Cname>`\n\nThis creates a two-layer sharing model: extensions for model types (Swamp registry), skills for agent workflows (ClawHub).\n\n## Examples\n\n### Model a REST API\n\n> \"Model the JSONPlaceholder API so I can list and create posts\"\n\n1. `swamp model create command\u002Fshell jsonplaceholder`\n2. Edit to add methods: `list-posts` (GET \u002Fposts), `create-post` (POST \u002Fposts)\n3. `swamp model method run jsonplaceholder list-posts`\n4. Verify output, iterate\n\n### Set Up a Weather Integration\n\n> \"Create a weather model that fetches forecasts by city\"\n\n1. `swamp model create command\u002Fshell weather`\n2. Edit to add a `forecast` method using `curl -s \"wttr.in\u002F{city}?format=j1\"`\n3. Test with `swamp model method run weather forecast`\n\n### Chain APIs in a Workflow\n\n> \"Create a workflow that fetches GitHub issues, summarizes them, and posts to Slack\"\n\n1. Create models: `github-issues`, `slack-webhook`\n2. Create workflow: `swamp workflow create issue-digest`\n3. Define jobs with dependencies: fetch issues -> format summary -> post to Slack\n4. `swamp workflow run issue-digest`\n\n### Graduate to a *Claw Skill\n\n> \"Turn my working weather model into a skill others can install\"\n\n1. `swamp model get weather --json` to export\n2. Create a new `SKILL.md` wrapping the weather model commands\n3. `clawhub publish .\u002Fweather-skill`\n\n### Share a Custom Extension\n\n> \"Publish my custom Stripe model type so the team can use it\"\n\n1. `swamp auth login` to authenticate with swamp-club\n2. `swamp extension push .\u002Fstripe-models\u002Fmanifest.yaml --dry-run` to verify\n3. `swamp extension push .\u002Fstripe-models\u002Fmanifest.yaml` to publish\n4. Team members install: `swamp extension pull stripe-models`\n\n## Important Notes\n\n- Always use `--json` flag when you need to parse Swamp output programmatically\n- Use `swamp model validate` before running to catch definition errors early\n- Store all credentials in vaults, never in model definitions\n- Use `-v` (verbose) flag when debugging unexpected behavior\n- All Swamp operations run locally — credentials stay on the user's machine\n- Authenticate with `swamp auth login` before pushing extensions to the registry\n- Use `swamp extension push --dry-run` to verify an extension before publishing\n- Use `swamp auth whoami` to confirm your identity before registry operations\n","# Swamp — API Modeling & *Claw Enrichment\n\nYou are an AI agent that uses Swamp to model any API, test it, and turn it into a reusable *Claw capability. Swamp is an AI-native automation CLI that represents external resources (APIs, CLIs, cloud services) as typed models with executable methods and composable workflows.\n\n## Repository Setup\n\nBefore any operation, check if the current directory is a swamp repository. If not, initialize one:\n\n```bash\nswamp repo init --tool claude\n```\n\nThis creates a `.swamp\u002F` directory with the necessary structure. Use `--tool claude` to set up the AI agent integration for Claude\u002FOpenClaw.\n\n## API Modeling Workflow\n\n### Step 1: Discover Model Types\n\nFind available model types to understand what kinds of resources can be modeled:\n\n```bash\nswamp model type search\nswamp model type describe \u003Ctype>\n```\n\nThe `command\u002Fshell` type is the most versatile — it can model any API via shell commands (curl, httpie, CLI tools).\n\n### Step 2: Create a Model\n\nCreate a new model definition for the API:\n\n```bash\nswamp model create \u003Ctype> \u003Cname>\n```\n\nExample: `swamp model create command\u002Fshell github-issues`\n\n### Step 3: Edit the Model Definition\n\nOpen and edit the model's YAML definition to configure endpoints, authentication, parameters, and methods:\n\n```bash\nswamp model edit \u003Cname>\n```\n\nWhen editing, define:\n- **Methods**: The operations this API supports (list, create, update, delete)\n- **Inputs**: Parameters each method accepts\n- **Authentication**: Reference vault secrets via CEL expressions\n- **Commands**: The actual shell commands (curl calls, CLI invocations) that execute each method\n\n### Step 4: Validate\n\nEnsure the model definition is well-formed:\n\n```bash\nswamp model validate \u003Cname>\n```\n\nFix any validation errors before proceeding.\n\n## Testing & Execution\n\n### Run a Method\n\nExecute a method on your model to test it:\n\n```bash\nswamp model method run \u003Cmodel_name> \u003Cmethod_name>\n```\n\n### Inspect Results\n\nCheck outputs, logs, and data from the execution:\n\n```bash\nswamp model output get \u003Coutput_id_or_model_name>\nswamp model output logs \u003Coutput_id>\nswamp model output data \u003Coutput_id>\n```\n\n### Review History\n\nSee past executions:\n\n```bash\nswamp model method history search\nswamp model method history get \u003Coutput_id_or_model_name>\n```\n\nIterate on the model definition until methods return the expected results.\n\n## Workflow Orchestration\n\nChain multiple model methods into automated workflows with dependency ordering:\n\n```bash\nswamp workflow create \u003Cname>\nswamp workflow edit \u003Cname>\nswamp workflow validate \u003Cname>\nswamp workflow run \u003Cname>\n```\n\nWorkflows support:\n- Parallel job execution\n- Dependency ordering between jobs\n- Trigger conditions via CEL expressions\n- Cross-model references (one model's output feeds into another)\n\nCheck workflow results:\n\n```bash\nswamp workflow history get \u003Cname>\nswamp workflow history logs \u003Crun_id>\n```\n\n## Vault & Credentials\n\nStore API keys and secrets securely — never hardcode them:\n\n```bash\nswamp vault create \u003Ctype> \u003Cname>\nswamp vault put \u003Cvault_name> \u003CKEY=value>\nswamp vault list-keys \u003Cvault_name>\n```\n\nReference secrets in model definitions using CEL expressions like `vault.get(\"my-vault\", \"API_KEY\")`.\n\n## Data Management\n\nInspect outputs and artifacts across models:\n\n```bash\nswamp data list \u003Cmodel_name>\nswamp data get \u003Cmodel_name> \u003Cdata_name>\nswamp data search \u003Cquery>\n```\n\n## Swamp-Club Authentication\n\nSwamp-club is the community registry and collaboration layer. Authenticate to push\u002Fpull extensions and share work:\n\n```bash\nswamp auth login\nswamp auth login --server \u003Curl>\nswamp auth whoami\nswamp auth logout\n```\n\n- `swamp auth login` opens a browser-based login flow by default\n- Use `--no-browser` with `--username` and `--password` for headless\u002FCI environments\n- Set `SWAMP_CLUB_URL` env var to target a custom server\n- Always verify identity with `swamp auth whoami` after login\n\nAuthentication is required before pushing extensions to the registry.\n\n## Extensions\n\nExtensions expand Swamp's model types and capabilities. Use the extension registry to share and reuse custom models:\n\n### Pull an Extension\n\nInstall a community or team extension from the registry:\n\n```bash\nswamp extension pull \u003Cextension_name>\nswamp extension pull \u003Cextension_name> --force\n```\n\nUse `--force` to overwrite existing files without prompting.\n\n### List Installed Extensions\n\nSee what extensions are currently installed:\n\n```bash\nswamp extension list\n```\n\n### Push an Extension\n\nPublish your own extension to the swamp registry (requires `swamp auth login` first):\n\n```bash\nswamp extension push \u003Cmanifest-path>\nswamp extension push \u003Cmanifest-path> --dry-run\n```\n\nUse `--dry-run` to build the archive locally and verify it without actually publishing. Use `-y` to skip confirmation prompts.\n\n### Remove an Extension\n\nUninstall a pulled extension and clean up its files:\n\n```bash\nswamp extension remove \u003Cextension_name>\n```\n\n### Extension Workflow\n\nThe typical flow for extending Swamp with new model types:\n\n1. Create custom TypeScript model definitions in `extensions\u002Fmodels\u002F`\n2. Test locally with `swamp model create \u003Cyour-type> \u003Cname>`\n3. Package with a manifest file\n4. Dry-run: `swamp extension push .\u002Fmanifest.yaml --dry-run`\n5. Publish: `swamp extension push .\u002Fmanifest.yaml`\n6. Others install: `swamp extension pull \u003Cyour-extension>`\n\n## Enriching *Claw with New Capabilities\n\nOnce a Swamp model is validated and working, turn it into a standalone *Claw skill:\n\n1. **Export the model**: Use `swamp model get \u003Cname> --json` to extract the full definition\n2. **Generate a SKILL.md**: Create a new skill file that wraps the Swamp model's methods as agent instructions\n3. **Include setup instructions**: Document the required env vars, binaries, and vault configuration\n4. **Publish to ClawHub**: Share the skill with the community via `clawhub publish`\n\nThe generated skill should:\n- Require `swamp` in its `bins` dependency\n- Reference the swamp repo and model by name\n- Map each model method to a clear agent instruction\n- Include examples of typical invocations\n\n### Sharing via Extensions\n\nFor reusable model types (not just individual models), publish as a Swamp extension:\n\n1. Build the custom model type in `extensions\u002Fmodels\u002F`\n2. Push to the Swamp registry: `swamp extension push .\u002Fmanifest.yaml`\n3. Create a *Claw skill that pulls the extension and uses it: `swamp extension pull \u003Cname>`\n\nThis creates a two-layer sharing model: extensions for model types (Swamp registry), skills for agent workflows (ClawHub).\n\n## Examples\n\n### Model a REST API\n\n> \"Model the JSONPlaceholder API so I can list and create posts\"\n\n1. `swamp model create command\u002Fshell jsonplaceholder`\n2. Edit to add methods: `list-posts` (GET \u002Fposts), `create-post` (POST \u002Fposts)\n3. `swamp model method run jsonplaceholder list-posts`\n4. Verify output, iterate\n\n### Set Up a Weather Integration\n\n> \"Create a weather model that fetches forecasts by city\"\n\n1. `swamp model create command\u002Fshell weather`\n2. Edit to add a `forecast` method using `curl -s \"wttr.in\u002F{city}?format=j1\"`\n3. Test with `swamp model method run weather forecast`\n\n### Chain APIs in a Workflow\n\n> \"Create a workflow that fetches GitHub issues, summarizes them, and posts to Slack\"\n\n1. Create models: `github-issues`, `slack-webhook`\n2. Create workflow: `swamp workflow create issue-digest`\n3. Define jobs with dependencies: fetch issues -> format summary -> post to Slack\n4. `swamp workflow run issue-digest`\n\n### Graduate to a *Claw Skill\n\n> \"Turn my working weather model into a skill others can install\"\n\n1. `swamp model get weather --json` to export\n2. Create a new `SKILL.md` wrapping the weather model commands\n3. `clawhub publish .\u002Fweather-skill`\n\n### Share a Custom Extension\n\n> \"Publish my custom Stripe model type so the team can use it\"\n\n1. `swamp auth login` to authenticate with swamp-club\n2. `swamp extension push .\u002Fstripe-models\u002Fmanifest.yaml --dry-run` to verify\n3. `swamp extension push .\u002Fstripe-models\u002Fmanifest.yaml` to publish\n4. Team members install: `swamp extension pull stripe-models`\n\n## Important Notes\n\n- Always use `--json` flag when you need to parse Swamp output programmatically\n- Use `swamp model validate` before running to catch definition errors early\n- Store all credentials in vaults, never in model definitions\n- Use `-v` (verbose) flag when debugging unexpected behavior\n- All Swamp operations run locally — credentials stay on the user's machine\n- Authenticate with `swamp auth login` before pushing extensions to the registry\n- Use `swamp extension push --dry-run` to verify an extension before publishing\n- Use `swamp auth whoami` to confirm your identity before registry operations\n",{"name":5,"version":24,"metadata":25,"description":7},"0.2.0",{"openclaw":26},{"emoji":27,"homepage":28,"requires":29},"🐊","https:\u002F\u002Fgithub.com\u002Fsysteminit\u002Fswamp",{"bins":30},[5],"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fumag\u002Fswamp",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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill swamp",{"tool":46,"command":47},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill swamp",{"tool":49,"command":50},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill swamp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fumag\u002Fswamp\u002FSKILL.md",true,[],[55,63,70,77,84,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"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":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":62},"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":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":62},"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":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":62},"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":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":62},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":62},"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",[],[]]