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

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

Generate professional resumes that conform to the Reactive

Manage Coder workspaces and AI coding agent tasks

Backend architecture patterns, API design, database

An autonomous AI software engineering platform that combines OpenClaw, Hermes, MCP servers, plugins, skills, sub-agents, and long-term memory to build complex applications from a single prompt.

OpenClaw plugin: customizable per-response usage footer rendered by a local command (model, context, usage, provider limits). Channel-agnostic.

Zig MCP agent for computer control - shell, a11y, vision, file ops via stdio transport

OpenClaw plugin that provides an independent OpenRouter Perplexity Search tool.

Exabase M-1 memory-provider integration for OpenClaw.

Openclaw Streaming Amazon Transcribe Plugin

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

Work with Google Maps from chat - search places, geocode addresses, calculate routes, and inspect location data. Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Google Maps 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 Google Maps at claw-link.dev/dashboard?add=google-maps When the user confirms Google Maps is connected, call clawlink_list_integrations and then clawlink_list_tools with the google-maps 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 Google Maps Tell the user to open https://claw-link.dev/dashboard?add=google-maps and connect Google Maps there. The page opens the add-connection panel filtered to Google Maps. ClawLink's hosted page runs the provider connection flow. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration google-maps. Using Google Maps 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 Google Maps is connected. Call clawlink_list_tools with integration google-maps. 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 google-maps. If no Google Maps tools appear, direct the user to https://claw-link.dev/dashboard?add=google-maps. 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 Google Maps tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): Search places and points of interest Geocode or reverse geocode addresses Calculate routes, directions, and distances Inspect place details and location metadata Use map data for planning and lookup workflows Rules Always use ClawLink tools for Google Maps. Do not ask the user for separate Google Maps 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 Google Maps is not connected, direct the user to https://claw-link.dev/dashboard?add=google-maps. 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 Google Maps API: https://developers.google.com/maps/documentation

Work with Calendly from chat — view events, check invitees, inspect availability schedules, manage webhooks, and create scheduling links when supported. Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Calendly 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 Calendly at claw-link.dev/dashboard?add=calendly When the user confirms Calendly is connected, call clawlink_list_integrations and then clawlink_list_tools with the calendly 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 Calendly Tell the user to open https://claw-link.dev/dashboard?add=calendly and connect Calendly there. The page opens the add-connection panel filtered to Calendly. ClawLink's hosted page runs the Calendly connection flow — the user clicks through Calendly sign-in and consent. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration calendly. Using Calendly 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 Calendly is connected. Call clawlink_list_tools with integration calendly. 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 calendly. If no Calendly tools appear, direct the user to https://claw-link.dev/dashboard?add=calendly. 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 inspection operations before writes. For scheduling links, no-show changes, webhook changes, 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 Calendly tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): View event details List invitees for an event Show upcoming or recent events Check availability schedules List webhook subscriptions Create scheduling links when supported Mark invitees as no-shows when requested Rules Always use ClawLink tools for Calendly. Do not ask the user for separate Calendly 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 writes such as creating links, marking no-shows, or changing webhooks. If Calendly is not connected, direct the user to https://claw-link.dev/dashboard?add=calendly. 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 Calendly API: https://developer.calendly.com/

Work with Airtable from chat — browse bases and tables, read and create records, manage fields, comments, and table operations when supported. Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Airtable 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 Airtable at claw-link.dev/dashboard?add=airtable When the user confirms Airtable is connected, call clawlink_list_integrations and then clawlink_list_tools with the airtable 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 Airtable Tell the user to open https://claw-link.dev/dashboard?add=airtable and connect Airtable there. The page opens the add-connection panel filtered to Airtable. ClawLink's hosted page runs the Airtable connection flow — the user clicks through Airtable sign-in and consent. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration airtable. Using Airtable 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 Airtable is connected. Call clawlink_list_tools with integration airtable. 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 airtable. If no Airtable tools appear, direct the user to https://claw-link.dev/dashboard?add=airtable. 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 creating records, updating fields or tables, comments, deletes, 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 Airtable tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): List bases and tables Browse records in a table or view Fetch a record by ID Create records, including bulk creation when supported Add or update comments on a record Create or update fields and tables Inspect base structure before changing data Rules Always use ClawLink tools for Airtable. Do not ask the user for separate Airtable 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 Airtable is not connected, direct the user to https://claw-link.dev/dashboard?add=airtable. 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 Airtable API: https://airtable.com/developers/web/api/introduction

Work with OneDrive from chat — browse files, search folders, inspect details, create folders, share links, and upload files when supported. Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Microsoft Graph 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 OneDrive at claw-link.dev/dashboard?add=onedrive When the user confirms OneDrive is connected, call clawlink_list_integrations and then clawlink_list_tools with the onedrive 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 OneDrive Tell the user to open https://claw-link.dev/dashboard?add=onedrive and connect OneDrive there. The page opens the add-connection panel filtered to OneDrive. ClawLink's hosted page runs the Microsoft account connection flow — the user clicks through Microsoft sign-in and consent. When they confirm it is done, call clawlink_list_integrations to verify, then call clawlink_list_tools with integration onedrive. Using OneDrive 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 OneDrive is connected. Call clawlink_list_tools with integration onedrive. 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 onedrive. If no OneDrive tools appear, direct the user to https://claw-link.dev/dashboard?add=onedrive. 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 uploads, folder creation, sharing, deletes, moves, 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 OneDrive tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog): List drives and browse folders Search files by name or metadata Get file or folder details Read supported workbook or table data Create folders Upload, download, move, or copy files when supported Create or inspect sharing links after confirmation Rules Always use ClawLink tools for OneDrive. Do not ask the user for separate Microsoft credentials or access tokens. 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 writes such as uploads, folder creation, sharing, moves, or deletes. If OneDrive is not connected, direct the user to https://claw-link.dev/dashboard?add=onedrive. 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 Microsoft Graph OneDrive: https://learn.microsoft.com/en-us/graph/api/resources/onedrive