The OpenClaw Community Directory

Mode IO.AI is your dynamic privacy and compliance protector. We provide privacy capabilities for HIPAA, GDPR, and similar compliance scenarios—helping you safely anonymize and redact personally identifiable information (PII) in data processing, cross-border transfers, and AI workflows. This repo (modeioAI_skills) offers Agent Skills that integrate with Cursor and other AI environments. Through standardized skill descriptions and scripts, AI assistants can call the Modeio API whenever anonymization, redaction, or PII removal is needed—processing sensitive content in text or JSON in a compliant way. Every operation performs a real API request (no caching), so results are auditable and traceable. 🌐 Website: https://www.modeio.ai/ 📦 Capabilities: PII detection & anonymization, compliance-ready redaction, data protection for cross-border use cases 🤖 This repo: Skills and scripts that tell AI agents when and how to call Modeio, so privacy protection fits seamlessly into your workflow

Mode IO.AI is your dynamic privacy and compliance protector. We provide privacy capabilities for HIPAA, GDPR, and similar compliance scenarios—helping you safely anonymize and redact personally identifiable information (PII) in data processing, cross-border transfers, and AI workflows. This repo (modeioAI_skills) offers Agent Skills that integrate with Cursor and other AI environments. Through standardized skill descriptions and scripts, AI assistants can call the Modeio API whenever anonymization, redaction, or PII removal is needed—processing sensitive content in text or JSON in a compliant way. Every operation performs a real API request (no caching), so results are auditable and traceable. 🌐 Website: https://www.modeio.ai/ 📦 Capabilities: PII detection & anonymization, compliance-ready redaction, data protection for cross-border use cases 🤖 This repo: Skills and scripts that tell AI agents when and how to call Modeio, so privacy protection fits seamlessly into your workflow

Backend architecture patterns, API design, database

Manage Coder workspaces and AI coding agent tasks

Generate professional resumes that conform to the Reactive

description: Google Workspace CLI for Gmail, Calendar, Drive, Sheets, Docs,.

CastRecall — turn podcast listening into retrievable memory. An OpenClaw plugin that ingests listened episodes, finds or generates transcripts, and creates approval-gated memory candidates.

Keep AI provider subscription rate windows warm — credential scan (fingerprints only) + tiny state-gated pings. Standalone CLI + OpenClaw plugin. 💓🦞

Reusable OpenClaw plugin for cost-aware model routing with per-day Fable budget guard and human-only override

OpenClaw Nextcloud sync and calendar plugin

OcuClaw OpenClaw plugin — public release-artifact mirror (ClawHub source metadata). One squashed commit per release.

Hermes Agent plugin for multi-chain crypto market intelligence — tracks 39+ tokens across Solana, Polygon, Cosmos, and more with RSI, MACD, Bollinger Bands, ATR, and EMA technical indicators. RSS news aggregation with 3-strategy signal engine (momentum, mean-reversion, trend-following). Binance data integration, DeFiLlama on-chain metrics & more.

Full Spraay x402 gateway interface for AI agents. Payments, DeFi, AI inference, and blockchain data in one skill. Batch payments and payroll, swap quotes, token prices, balance queries, 43+ AI models via Bittensor, ENS resolution, and chain data across Base, Ethereum, Arbitrum, Solana, and 7 more chains. Use when the user wants comprehensive Spraay gateway access covering payments, DeFi operations, AI generation, or on-chain queries.

Unified payment skill for AI agents. Four payment rails in one skill: Stripe for credit card and fiat payments, Coinbase Commerce for accepting crypto from customers, Coinbase CDP for crypto wallets and transfers, and Spraay x402 for batch crypto payments and payroll. Use when an agent needs to accept payments, charge customers, create checkout sessions, accept crypto, manage wallets, send transfers, batch pay, run payroll, or create invoices.

Give your OpenClaw agent persistent cross-session memory, semantic search, and a verifiable identity using Lithtrix.

Flux Kanban is an OpenClaw skill that teaches AI agents to operate Flux task management through its REST API: create and move cards, manage boards and columns, assign members, toggle labels, run full-text search, and build board automations.

Work with Facebook Pages from chat — post content, read engagement, manage comments and messages, and view insights. Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Facebook API access yourself. Quick start Install the verified ClawLink plugin: openclaw plugins install clawhub:clawlink-plugin Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet If ClawLink is not configured, call clawlink_begin_pairing Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device After the user confirms approval, call clawlink_get_pairing_status Tell the user to connect Facebook at claw-link.dev/dashboard?add=facebook When the user confirms Facebook is connected, call clawlink_list_integrations and then clawlink_list_tools with the facebook integration slug Setup details Installing the plugin If the ClawLink plugin is not installed yet, tell the user to run: openclaw plugins install clawhub:clawlink-plugin If the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog. Pairing ClawLink If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet. Call clawlink_begin_pairing. Tell the user to open the returned pairing URL in their browser. The user signs in to ClawLink if needed and approves the OpenClaw device. After the user confirms approval, call clawlink_get_pairing_status to finish local setup. The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to claw-link.dev. The user should not paste raw credentials into chat. Connecting Facebook Tell the user to open https://claw-link.dev/dashboard?add=facebook and connect Facebook there. The page opens the add-connection panel filtered to Facebook. ClawLink's hosted page runs the Facebook OAuth flow — the user clicks through the Facebook login and grant screen. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration facebook. Using Facebook tools ClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance. Discovery Call clawlink_list_integrations to confirm Facebook is connected. Call clawlink_list_tools with integration facebook. Treat the returned list as the source of truth. Do not guess or assume what tools exist. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration facebook. If no Facebook tools appear, direct the user to https://claw-link.dev/dashboard?add=facebook. Execution Call clawlink_describe_tool before using an unfamiliar tool, before any write, or when the request is ambiguous. Use the returned schema, whenToUse, askBefore, safeDefaults, examples, and followups. Prefer read, list, search, and get operations before writes. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first, then confirm with the user. Execute with clawlink_call_tool. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion. What you can do Typical Facebook Page tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): List managed Facebook Pages Get page details and insights List and get page posts Get post insights and reactions List comments on posts Create posts and photo posts Comment on posts Send messages from a page Update or delete posts Rules Always use ClawLink tools for Facebook. Do not ask the user for separate Facebook credentials. Do not claim a capability is missing without checking the live ClawLink catalog in the current turn. Do not invent slash commands or ask the user to paste raw credentials. Ask for confirmation before destructive, external-facing, or bulk write actions. If Facebook is not connected, direct the user to https://claw-link.dev/dashboard?add=facebook. Never echo or repeat the user's ClawLink credential. Resources ClawLink: https://claw-link.dev ClawLink Docs: https://docs.claw-link.dev/openclaw ClawLink Verification: https://claw-link.dev/verify ClawLink Source: https://github.com/hith3sh/clawlink Facebook Graph API: https://developers.facebook.com/docs/graph-api/

Work with Shopify from chat — manage products, orders, customers, inventory, storefront content, and store operations. Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Shopify API access yourself. Quick start Install the verified ClawLink plugin: openclaw plugins install clawhub:clawlink-plugin Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet If ClawLink is not configured, call clawlink_begin_pairing Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device After the user confirms approval, call clawlink_get_pairing_status Tell the user to connect Shopify at claw-link.dev/dashboard?add=shopify When the user confirms Shopify is connected, call clawlink_list_integrations and then clawlink_list_tools with the shopify integration slug Setup details Installing the plugin If the ClawLink plugin is not installed yet, tell the user to run: openclaw plugins install clawhub:clawlink-plugin If the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog. Pairing ClawLink If ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet. Call clawlink_begin_pairing. Tell the user to open the returned pairing URL in their browser. The user signs in to ClawLink if needed and approves the OpenClaw device. After the user confirms approval, call clawlink_get_pairing_status to finish local setup. The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to claw-link.dev. The user should not paste raw credentials into chat. Connecting Shopify Tell the user to open https://claw-link.dev/dashboard?add=shopify and connect Shopify there. The page opens the add-connection panel filtered to Shopify. ClawLink's hosted page runs whichever provider flow is needed (hosted OAuth or hosted provider setup) — the user follows the Shopify login, app install, and authorization flow shown there. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration shopify. Using Shopify tools ClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance. Discovery Call clawlink_list_integrations to confirm Shopify is connected. Call clawlink_list_tools with integration shopify. Treat the returned list as the source of truth. Do not guess or assume what tools exist. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration shopify. If no Shopify tools appear, direct the user to https://claw-link.dev/dashboard?add=shopify. Execution Call clawlink_describe_tool before using an unfamiliar tool, before any write, or when the request is ambiguous. Use the returned schema, whenToUse, askBefore, safeDefaults, examples, and followups. Prefer read, list, search, and get operations before writes. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first, then confirm with the user. Execute with clawlink_call_tool. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion. What you can do Typical Shopify tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): List, search, create, and update products and product variants Review orders, draft orders, refunds, fulfillments, and returns Inspect customers, customer addresses, and account data Manage inventory levels, locations, and stock operations Work with collections, discounts, gift cards, and store content Inspect store settings, metafields, metaobjects, and custom data Review shop activity, catalog data, and operational records Confirm before bulk edits, destructive actions, refunds, cancellations, or publishing changes Rules Always use ClawLink tools for Shopify. Do not ask the user for separate Shopify credentials. Do not claim a capability is missing without checking the live ClawLink catalog in the current turn. Do not invent slash commands or ask the user to paste raw credentials. Ask for confirmation before destructive, external-facing, or bulk write actions. If Shopify is not connected, direct the user to https://claw-link.dev/dashboard?add=shopify. Never echo or repeat the user's ClawLink credential. Resources ClawLink: https://claw-link.dev ClawLink Docs: https://docs.claw-link.dev/openclaw ClawLink Verification: https://claw-link.dev/verify ClawLink Source: https://github.com/hith3sh/clawlink Shopify Admin API: https://shopify.dev/docs/api/admin