[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75D33QVHS6HMFN3V4KHNSPX":3,"skill-same:01M75D33QVHS6HMFN3V4KHNSPX":59},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M75D33QVHS6HMFN3V4KHNSPX","airtable-participants",null,"Read and query retreat participant data from the Ceremonia Airtable base. Use this skill when asked about participants, subscriber counts, retreat attendance, contact segments, phone numbers, emails, or donation status. Also used by other skills (email-newsletter, sms-outreach) to retrieve recipient lists. Read-only by default.","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\u002Faustinmao\u002Fairtable-participants\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: airtable-participants\ndescription: >\n  Read and query retreat participant data from the Ceremonia Airtable base.\n  Use this skill when asked about participants, subscriber counts, retreat\n  attendance, contact segments, phone numbers, emails, or donation status.\n  Also used by other skills (email-newsletter, sms-outreach) to retrieve\n  recipient lists. Read-only by default.\nversion: 1.0.0\nmetadata:\n  openclaw:\n    requires:\n      env:\n        - AIRTABLE_API_KEY\n      bins:\n        - curl\n        - jq\n    primaryEnv: AIRTABLE_API_KEY\n    emoji: \"contacts\"\n    homepage: https:\u002F\u002Fairtable.com\u002Fdevelopers\u002Fweb\u002Fapi\u002Fintroduction\n---\n\n# Airtable Participants Skill\n\n## Purpose\n\nQuery retreat participant data from the Ceremonia Airtable base. This is the\nauthoritative source of truth for who receives emails and SMS messages.\nAccess is read-only by default — record modifications require Austin's\nexplicit instruction per change.\n\n## Required Setup\n\nEnsure AIRTABLE_API_KEY is set in .env.\n\nYou will also need:\n- **Base ID:** [VERIFY — find in Airtable API docs at airtable.com\u002Fdevelopers or ask Austin]\n- **Table name:** [VERIFY — confirm the participant table name with Austin]\n\nStore confirmed values in TOOLS.md and MEMORY.md once verified.\n\n## Expected Data Structure\n\nParticipant records are expected to have at minimum these fields:\n\n| Field | Type | Description |\n|-------|------|-------------|\n| name | Text | Full name |\n| email | Email | Primary email address |\n| phone | Phone | E.164 format preferred (+1XXXXXXXXXX) |\n| retreat_status | Select | e.g., active, alumni, prospective, unsubscribed |\n| tags | Multi-select | e.g., february-2026, guide-circle, donor |\n| last_contact | Date | Most recent outreach date |\n| donation_status | Select | e.g., donor, non-donor |\n\n[VERIFY actual field names with Austin on first use — update this section when confirmed]\n\n## Common Query Patterns\n\n### Get all active participants (for newsletter sends)\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?filterByFormula={retreat_status}='active'&fields[]=name&fields[]=email\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '.records[].fields'\n```\n\n### Get participants with phone numbers (for SMS campaigns)\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?filterByFormula=AND({retreat_status}='active',{phone}!='')&fields[]=name&fields[]=phone\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '.records[].fields'\n```\n\n### Get participant count by status\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?fields[]=retreat_status\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '[.records[].fields.retreat_status] | group_by(.) | map({status: .[0], count: length})'\n```\n\n### Get participants by tag\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?filterByFormula=FIND('february-2026',ARRAYJOIN({tags}))\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '.records[].fields'\n```\n\nNote: Airtable paginates at 100 records. Use the offset parameter from the response to fetch subsequent pages:\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?offset={OFFSET_TOKEN}\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq .\n```\nAlways paginate fully before reporting totals or building recipient lists.\n\n## Behavior Rules\n\n- Read-only by default — never PATCH, POST, or DELETE Airtable records without Austin's explicit instruction per operation\n- When building a recipient list for email or SMS: always filter out records where retreat_status is 'unsubscribed'\n- Never include email addresses or phone numbers in Slack messages — summarize counts and segments only\n- If a query returns 0 results unexpectedly: report the issue to Austin rather than sending to an empty list\n- Paginate all list queries fully — do not report partial counts or build partial recipient lists\n- If Airtable API returns an error: surface it to Austin immediately with the error code and message\n\n## Record Modification (Requires Austin Approval)\n\nWhen Austin instructs a record change (e.g., marking someone unsubscribed, updating last_contact):\n1. Confirm the specific change with Austin before executing\n2. Execute the PATCH request\n3. Log the change in memory\u002Flogs\u002Fcrm-writes\u002FYYYY-MM-DD.md with: record name\u002Femail, field changed, old value, new value, Austin's instruction timestamp\n\n## Example Invocations\n\n- \"How many active participants do we have?\"\n- \"Get the email list for the February retreat attendees\"\n- \"Who attended the last three retreats?\"\n- \"How many people have phone numbers in the system?\"\n- \"Mark [name] as unsubscribed\" (requires Austin approval)\n- \"Pull the full active participant list for the newsletter\"\n- \"How many people joined since January?\"\n","# Airtable Participants Skill\n\n## Purpose\n\nQuery retreat participant data from the Ceremonia Airtable base. This is the\nauthoritative source of truth for who receives emails and SMS messages.\nAccess is read-only by default — record modifications require Austin's\nexplicit instruction per change.\n\n## Required Setup\n\nEnsure AIRTABLE_API_KEY is set in .env.\n\nYou will also need:\n- **Base ID:** [VERIFY — find in Airtable API docs at airtable.com\u002Fdevelopers or ask Austin]\n- **Table name:** [VERIFY — confirm the participant table name with Austin]\n\nStore confirmed values in TOOLS.md and MEMORY.md once verified.\n\n## Expected Data Structure\n\nParticipant records are expected to have at minimum these fields:\n\n| Field | Type | Description |\n|-------|------|-------------|\n| name | Text | Full name |\n| email | Email | Primary email address |\n| phone | Phone | E.164 format preferred (+1XXXXXXXXXX) |\n| retreat_status | Select | e.g., active, alumni, prospective, unsubscribed |\n| tags | Multi-select | e.g., february-2026, guide-circle, donor |\n| last_contact | Date | Most recent outreach date |\n| donation_status | Select | e.g., donor, non-donor |\n\n[VERIFY actual field names with Austin on first use — update this section when confirmed]\n\n## Common Query Patterns\n\n### Get all active participants (for newsletter sends)\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?filterByFormula={retreat_status}='active'&fields[]=name&fields[]=email\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '.records[].fields'\n```\n\n### Get participants with phone numbers (for SMS campaigns)\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?filterByFormula=AND({retreat_status}='active',{phone}!='')&fields[]=name&fields[]=phone\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '.records[].fields'\n```\n\n### Get participant count by status\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?fields[]=retreat_status\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '[.records[].fields.retreat_status] | group_by(.) | map({status: .[0], count: length})'\n```\n\n### Get participants by tag\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?filterByFormula=FIND('february-2026',ARRAYJOIN({tags}))\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq '.records[].fields'\n```\n\nNote: Airtable paginates at 100 records. Use the offset parameter from the response to fetch subsequent pages:\n```bash\ncurl -s \"https:\u002F\u002Fapi.airtable.com\u002Fv0\u002F{BASE_ID}\u002F{TABLE_NAME}?offset={OFFSET_TOKEN}\" \\\n  -H \"Authorization: Bearer $AIRTABLE_API_KEY\" | jq .\n```\nAlways paginate fully before reporting totals or building recipient lists.\n\n## Behavior Rules\n\n- Read-only by default — never PATCH, POST, or DELETE Airtable records without Austin's explicit instruction per operation\n- When building a recipient list for email or SMS: always filter out records where retreat_status is 'unsubscribed'\n- Never include email addresses or phone numbers in Slack messages — summarize counts and segments only\n- If a query returns 0 results unexpectedly: report the issue to Austin rather than sending to an empty list\n- Paginate all list queries fully — do not report partial counts or build partial recipient lists\n- If Airtable API returns an error: surface it to Austin immediately with the error code and message\n\n## Record Modification (Requires Austin Approval)\n\nWhen Austin instructs a record change (e.g., marking someone unsubscribed, updating last_contact):\n1. Confirm the specific change with Austin before executing\n2. Execute the PATCH request\n3. Log the change in memory\u002Flogs\u002Fcrm-writes\u002FYYYY-MM-DD.md with: record name\u002Femail, field changed, old value, new value, Austin's instruction timestamp\n\n## Example Invocations\n\n- \"How many active participants do we have?\"\n- \"Get the email list for the February retreat attendees\"\n- \"Who attended the last three retreats?\"\n- \"How many people have phone numbers in the system?\"\n- \"Mark [name] as unsubscribed\" (requires Austin approval)\n- \"Pull the full active participant list for the newsletter\"\n- \"How many people joined since January?\"\n",{"name":5,"version":24,"metadata":25,"description":35},"1.0.0",{"openclaw":26},{"emoji":27,"homepage":28,"requires":29,"primaryEnv":31},"contacts","https:\u002F\u002Fairtable.com\u002Fdevelopers\u002Fweb\u002Fapi\u002Fintroduction",{"env":30,"bins":32},[31],"AIRTABLE_API_KEY",[33,34],"curl","jq","Read and query retreat participant data from the Ceremonia Airtable base. Use this skill when asked about participants, subscriber counts, retreat attendance, contact segments, phone numbers, emails, or donation status. Also used by other skills (email-newsletter, sms-outreach) to retrieve recipient lists. Read-only by default.\n","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Faustinmao\u002Fairtable-participants",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill airtable-participants",{"tool":51,"command":52},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill airtable-participants",{"tool":54,"command":55},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill airtable-participants","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Faustinmao\u002Fairtable-participants\u002FSKILL.md",true,[],[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":67},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":67},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":67},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":67},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":67},"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",[],[]]