[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75F10TWE9ESA20PR9NHVRK9":3,"skill-same:01M75F10TWE9ESA20PR9NHVRK9":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M75F10TWE9ESA20PR9NHVRK9","agent-contact-card",null,"Discover and create Agent Contact Cards - a vCard-like format for AI agents. Use when you need to find how to contact someone's agent, or help a user set up their own agent contact info at \u002F.well-known\u002Fagent-card.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"CC0-1.0","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdavedean\u002Fagent-contact-card\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: agent-contact-card\ndescription: Discover and create Agent Contact Cards - a vCard-like format for AI agents. Use when you need to find how to contact someone's agent, or help a user set up their own agent contact info at \u002F.well-known\u002Fagent-card.\nlicense: CC0-1.0\nmetadata:\n  author: davedean\n  version: \"1.0\"\n  homepage: https:\u002F\u002Fgithub.com\u002Fdavedean\u002Fagent-contact-card\n---\n\n# Agent Contact Card\n\nA simple format for publishing how AI agents can be contacted. Like a vCard, but for agents.\n\n## When to Use This Skill\n\n- User asks how to let other agents contact their agent\n- User wants to discover how to reach someone else's agent\n- You need to contact another agent on behalf of your user\n- User mentions \"agent-card\", \"agent contact\", or agent-to-agent communication\n\n## Quick Reference\n\n### Discovering an Agent Contact Card\n\nTry fetching `\u002F.well-known\u002Fagent-card` on their domain:\n\n```\nhttps:\u002F\u002Fexample.com\u002F.well-known\u002Fagent-card\n```\n\nThe file is markdown with YAML frontmatter. Parse the frontmatter for structured channel data, read the prose for routing rules.\n\n### Creating an Agent Contact Card\n\nCreate a markdown file with YAML frontmatter:\n\n```markdown\n---\nversion: \"1\"\nhuman_contact: \"+1 555 123 4567\"\nchannels:\n  email: \"agent@example.com\"\n  discord: \"my-agent#1234\"\n  webhook:\n    url: \"https:\u002F\u002Fexample.com\u002Fagent\u002Fincoming\"\n    method: \"POST\"\n    format: \"JSON with 'message' field\"\ncapabilities:\n  - scheduling\n  - accepts_ical\n---\n\n# My Agent\n\nIf you're a human, call the number above.\n\nIf you're an agent:\n- For scheduling requests, use Discord\n- For urgent matters, email with \"URGENT\" in subject\n- Response time: within a few hours\n```\n\nHost this at `\u002F.well-known\u002Fagent-card` on the user's domain.\n\n## Format Details\n\n### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| `version` | Spec version. Currently `\"1\"` |\n\n### Recommended Fields\n\n| Field | Description |\n|-------|-------------|\n| `human_contact` | Phone\u002Femail for humans to reach the human |\n| `channels` | Contact channels for agents (see below) |\n\n### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| `name` | Display name for this agent configuration |\n| `last_updated` | ISO date when card was last modified |\n| `capabilities` | What this agent can do (e.g., `[\"scheduling\", \"accepts_ical\"]`) |\n| `agents` | Named agents if multiple (see Multi-Agent section) |\n\n### Channels\n\nChannel names are freeform. Common ones:\n\n- `email` - Email address\n- `discord` - Discord username\n- `webhook` - HTTP endpoint for structured messages\n- `signal` - Signal phone number\n- `telegram` - Telegram username\n\nFor webhooks, provide details:\n\n```yaml\nchannels:\n  webhook:\n    url: \"https:\u002F\u002Fexample.com\u002Fagent\u002Fincoming\"\n    method: \"POST\"\n    auth: \"Bearer token in Authorization header\"\n    format: \"JSON with 'message' and 'from' fields\"\n```\n\n### Multi-Agent Setups\n\nList multiple specialized agents:\n\n```yaml\nagents:\n  - name: \"Calendar Agent\"\n    handles: [\"scheduling\", \"availability\"]\n    channel: discord\n    id: \"cal-agent#1234\"\n  - name: \"Support Agent\"\n    handles: [\"technical questions\"]\n    channel: webhook\n    id: \"https:\u002F\u002Fexample.com\u002Fsupport\"\n```\n\nThe markdown body should explain routing between them.\n\n## Privacy Tiers\n\nDifferent URLs for different access levels:\n\n| Tier | URL Pattern | Access |\n|------|-------------|--------|\n| Public | `\u002F.well-known\u002Fagent-card` | Anyone |\n| Named | `\u002F.well-known\u002Fagent-card\u002F{name}` | Know the name |\n| Private | `\u002F{random-uuid}\u002Fagent-card.md` | Shared URL only |\n\nEach tier can expose different channels and capabilities.\n\n## Discovery Methods\n\n1. **Well-known URL**: Check `https:\u002F\u002Fdomain\u002F.well-known\u002Fagent-card`\n2. **vCard extension**: Look for `X-AGENT-CARD` field in contact cards\n3. **Ask the human**: Request the URL directly\n\n## Reading an Agent Card\n\nWhen you fetch an agent card:\n\n1. Parse YAML frontmatter for structured data\n2. Read markdown body for natural language routing rules\n3. Choose appropriate channel based on your purpose\n4. Follow any authentication requirements mentioned\n\n## Test It\n\nHere's a live demo you can test:\n\n```\nhttps:\u002F\u002Fcity-services-api.dave-dean.workers.dev\u002F.well-known\u002Fagent-card\n```\n\nThis is a fictional \"City of Millbrook\" tip line. Fetch the card, then try POSTing to the webhook endpoint. Your experience may vary depending on what you say.\n\n## Full Specification\n\nSee [references\u002FSPEC.md](references\u002FSPEC.md) for the complete specification.\n\n## Examples\n\nSee [references\u002FEXAMPLES.md](references\u002FEXAMPLES.md) for more complete examples.\n","# Agent Contact Card\n\nA simple format for publishing how AI agents can be contacted. Like a vCard, but for agents.\n\n## When to Use This Skill\n\n- User asks how to let other agents contact their agent\n- User wants to discover how to reach someone else's agent\n- You need to contact another agent on behalf of your user\n- User mentions \"agent-card\", \"agent contact\", or agent-to-agent communication\n\n## Quick Reference\n\n### Discovering an Agent Contact Card\n\nTry fetching `\u002F.well-known\u002Fagent-card` on their domain:\n\n```\nhttps:\u002F\u002Fexample.com\u002F.well-known\u002Fagent-card\n```\n\nThe file is markdown with YAML frontmatter. Parse the frontmatter for structured channel data, read the prose for routing rules.\n\n### Creating an Agent Contact Card\n\nCreate a markdown file with YAML frontmatter:\n\n```markdown\n---\nversion: \"1\"\nhuman_contact: \"+1 555 123 4567\"\nchannels:\n  email: \"agent@example.com\"\n  discord: \"my-agent#1234\"\n  webhook:\n    url: \"https:\u002F\u002Fexample.com\u002Fagent\u002Fincoming\"\n    method: \"POST\"\n    format: \"JSON with 'message' field\"\ncapabilities:\n  - scheduling\n  - accepts_ical\n---\n\n# My Agent\n\nIf you're a human, call the number above.\n\nIf you're an agent:\n- For scheduling requests, use Discord\n- For urgent matters, email with \"URGENT\" in subject\n- Response time: within a few hours\n```\n\nHost this at `\u002F.well-known\u002Fagent-card` on the user's domain.\n\n## Format Details\n\n### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| `version` | Spec version. Currently `\"1\"` |\n\n### Recommended Fields\n\n| Field | Description |\n|-------|-------------|\n| `human_contact` | Phone\u002Femail for humans to reach the human |\n| `channels` | Contact channels for agents (see below) |\n\n### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| `name` | Display name for this agent configuration |\n| `last_updated` | ISO date when card was last modified |\n| `capabilities` | What this agent can do (e.g., `[\"scheduling\", \"accepts_ical\"]`) |\n| `agents` | Named agents if multiple (see Multi-Agent section) |\n\n### Channels\n\nChannel names are freeform. Common ones:\n\n- `email` - Email address\n- `discord` - Discord username\n- `webhook` - HTTP endpoint for structured messages\n- `signal` - Signal phone number\n- `telegram` - Telegram username\n\nFor webhooks, provide details:\n\n```yaml\nchannels:\n  webhook:\n    url: \"https:\u002F\u002Fexample.com\u002Fagent\u002Fincoming\"\n    method: \"POST\"\n    auth: \"Bearer token in Authorization header\"\n    format: \"JSON with 'message' and 'from' fields\"\n```\n\n### Multi-Agent Setups\n\nList multiple specialized agents:\n\n```yaml\nagents:\n  - name: \"Calendar Agent\"\n    handles: [\"scheduling\", \"availability\"]\n    channel: discord\n    id: \"cal-agent#1234\"\n  - name: \"Support Agent\"\n    handles: [\"technical questions\"]\n    channel: webhook\n    id: \"https:\u002F\u002Fexample.com\u002Fsupport\"\n```\n\nThe markdown body should explain routing between them.\n\n## Privacy Tiers\n\nDifferent URLs for different access levels:\n\n| Tier | URL Pattern | Access |\n|------|-------------|--------|\n| Public | `\u002F.well-known\u002Fagent-card` | Anyone |\n| Named | `\u002F.well-known\u002Fagent-card\u002F{name}` | Know the name |\n| Private | `\u002F{random-uuid}\u002Fagent-card.md` | Shared URL only |\n\nEach tier can expose different channels and capabilities.\n\n## Discovery Methods\n\n1. **Well-known URL**: Check `https:\u002F\u002Fdomain\u002F.well-known\u002Fagent-card`\n2. **vCard extension**: Look for `X-AGENT-CARD` field in contact cards\n3. **Ask the human**: Request the URL directly\n\n## Reading an Agent Card\n\nWhen you fetch an agent card:\n\n1. Parse YAML frontmatter for structured data\n2. Read markdown body for natural language routing rules\n3. Choose appropriate channel based on your purpose\n4. Follow any authentication requirements mentioned\n\n## Test It\n\nHere's a live demo you can test:\n\n```\nhttps:\u002F\u002Fcity-services-api.dave-dean.workers.dev\u002F.well-known\u002Fagent-card\n```\n\nThis is a fictional \"City of Millbrook\" tip line. Fetch the card, then try POSTing to the webhook endpoint. Your experience may vary depending on what you say.\n\n## Full Specification\n\nSee [references\u002FSPEC.md](references\u002FSPEC.md) for the complete specification.\n\n## Examples\n\nSee [references\u002FEXAMPLES.md](references\u002FEXAMPLES.md) for more complete examples.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26,"homepage":27},"davedean","1.0","https:\u002F\u002Fgithub.com\u002Fdavedean\u002Fagent-contact-card","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fdavedean\u002Fagent-contact-card",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill agent-contact-card",{"tool":43,"command":44},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill agent-contact-card",{"tool":46,"command":47},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill agent-contact-card","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fdavedean\u002Fagent-contact-card\u002FSKILL.md",true,[],[52,61,68,75,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"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.","MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":60},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":60},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":60},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":60},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":60},"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",[],[]]