From 8c60204e19cdc3e01c747c3f51f9cb9ce1d3fc96 Mon Sep 17 00:00:00 2001 From: sohamganatra Date: Wed, 11 Feb 2026 14:13:27 -0800 Subject: [PATCH] Add automation skills for all 874 Composio toolkits - 832 new automation skills covering every toolkit on composio.dev - Updated 78 existing skills with composio.dev/toolkits links - Total: 910 automation skills - Each skill includes toolkit slug, connection flow, tool discovery pattern, and links to composio.dev toolkit docs - All skills include "Powered by Composio" attribution Co-Authored-By: Claude Opus 4.6 --- -21risk-automation/SKILL.md | 91 +++++++++++++++ -2chat-automation/SKILL.md | 91 +++++++++++++++ ably-automation/SKILL.md | 91 +++++++++++++++ abstract-automation/SKILL.md | 91 +++++++++++++++ abuselpdb-automation/SKILL.md | 91 +++++++++++++++ abyssale-automation/SKILL.md | 91 +++++++++++++++ accelo-automation/SKILL.md | 91 +++++++++++++++ accredible-certificates-automation/SKILL.md | 91 +++++++++++++++ acculynx-automation/SKILL.md | 91 +++++++++++++++ active-campaign-automation/SKILL.md | 91 +++++++++++++++ activecampaign-automation/SKILL.md | 5 + addresszen-automation/SKILL.md | 91 +++++++++++++++ adobe-automation/SKILL.md | 91 +++++++++++++++ adrapid-automation/SKILL.md | 91 +++++++++++++++ adyntel-automation/SKILL.md | 91 +++++++++++++++ aero-workflow-automation/SKILL.md | 91 +++++++++++++++ aeroleads-automation/SKILL.md | 91 +++++++++++++++ affinda-automation/SKILL.md | 91 +++++++++++++++ affinity-automation/SKILL.md | 91 +++++++++++++++ agencyzoom-automation/SKILL.md | 91 +++++++++++++++ agent-mail-automation/SKILL.md | 91 +++++++++++++++ agentql-automation/SKILL.md | 91 +++++++++++++++ agenty-automation/SKILL.md | 91 +++++++++++++++ agiled-automation/SKILL.md | 91 +++++++++++++++ agility-cms-automation/SKILL.md | 91 +++++++++++++++ ahrefs-automation/SKILL.md | 91 +++++++++++++++ ai-ml-api-automation/SKILL.md | 91 +++++++++++++++ airtable-automation/SKILL.md | 5 + aivoov-automation/SKILL.md | 91 +++++++++++++++ alchemy-automation/SKILL.md | 91 +++++++++++++++ algodocs-automation/SKILL.md | 91 +++++++++++++++ algolia-automation/SKILL.md | 91 +++++++++++++++ all-images-ai-automation/SKILL.md | 91 +++++++++++++++ alpha-vantage-automation/SKILL.md | 91 +++++++++++++++ altoviz-automation/SKILL.md | 91 +++++++++++++++ alttext-ai-automation/SKILL.md | 91 +++++++++++++++ amara-automation/SKILL.md | 91 +++++++++++++++ amazon-automation/SKILL.md | 91 +++++++++++++++ ambee-automation/SKILL.md | 91 +++++++++++++++ ambient-weather-automation/SKILL.md | 91 +++++++++++++++ amcards-automation/SKILL.md | 91 +++++++++++++++ amplitude-automation/SKILL.md | 5 + anchor-browser-automation/SKILL.md | 91 +++++++++++++++ anonyflow-automation/SKILL.md | 91 +++++++++++++++ anthropic-administrator-automation/SKILL.md | 91 +++++++++++++++ anthropic_administrator-automation/SKILL.md | 110 ++++++++++++++++++ apaleo-automation/SKILL.md | 91 +++++++++++++++ apex27-automation/SKILL.md | 91 +++++++++++++++ api-bible-automation/SKILL.md | 91 +++++++++++++++ api-labz-automation/SKILL.md | 91 +++++++++++++++ api-ninjas-automation/SKILL.md | 91 +++++++++++++++ api-sports-automation/SKILL.md | 91 +++++++++++++++ api2pdf-automation/SKILL.md | 91 +++++++++++++++ apiflash-automation/SKILL.md | 91 +++++++++++++++ apify-automation/SKILL.md | 91 +++++++++++++++ apilio-automation/SKILL.md | 91 +++++++++++++++ apipie-ai-automation/SKILL.md | 91 +++++++++++++++ apitemplate-io-automation/SKILL.md | 91 +++++++++++++++ apiverve-automation/SKILL.md | 91 +++++++++++++++ apollo-automation/SKILL.md | 91 +++++++++++++++ appcircle-automation/SKILL.md | 91 +++++++++++++++ appdrag-automation/SKILL.md | 91 +++++++++++++++ appointo-automation/SKILL.md | 91 +++++++++++++++ appsflyer-automation/SKILL.md | 91 +++++++++++++++ appveyor-automation/SKILL.md | 91 +++++++++++++++ aryn-automation/SKILL.md | 91 +++++++++++++++ asana-automation/SKILL.md | 5 + ascora-automation/SKILL.md | 91 +++++++++++++++ ashby-automation/SKILL.md | 91 +++++++++++++++ asin-data-api-automation/SKILL.md | 91 +++++++++++++++ astica-ai-automation/SKILL.md | 91 +++++++++++++++ async-interview-automation/SKILL.md | 91 +++++++++++++++ atlassian-automation/SKILL.md | 91 +++++++++++++++ attio-automation/SKILL.md | 91 +++++++++++++++ auth0-automation/SKILL.md | 91 +++++++++++++++ autobound-automation/SKILL.md | 91 +++++++++++++++ autom-automation/SKILL.md | 91 +++++++++++++++ axonaut-automation/SKILL.md | 91 +++++++++++++++ ayrshare-automation/SKILL.md | 91 +++++++++++++++ backendless-automation/SKILL.md | 91 +++++++++++++++ bamboohr-automation/SKILL.md | 5 + bannerbear-automation/SKILL.md | 91 +++++++++++++++ bart-automation/SKILL.md | 91 +++++++++++++++ basecamp-automation/SKILL.md | 5 + baselinker-automation/SKILL.md | 91 +++++++++++++++ baserow-automation/SKILL.md | 91 +++++++++++++++ basin-automation/SKILL.md | 91 +++++++++++++++ battlenet-automation/SKILL.md | 91 +++++++++++++++ beaconchain-automation/SKILL.md | 91 +++++++++++++++ beaconstac-automation/SKILL.md | 91 +++++++++++++++ beamer-automation/SKILL.md | 91 +++++++++++++++ beeminder-automation/SKILL.md | 91 +++++++++++++++ bench-automation/SKILL.md | 91 +++++++++++++++ benchmark-email-automation/SKILL.md | 91 +++++++++++++++ benzinga-automation/SKILL.md | 91 +++++++++++++++ bestbuy-automation/SKILL.md | 91 +++++++++++++++ better-proposals-automation/SKILL.md | 91 +++++++++++++++ better-stack-automation/SKILL.md | 91 +++++++++++++++ bidsketch-automation/SKILL.md | 91 +++++++++++++++ big-data-cloud-automation/SKILL.md | 91 +++++++++++++++ bigmailer-automation/SKILL.md | 91 +++++++++++++++ bigml-automation/SKILL.md | 91 +++++++++++++++ bigpicture-io-automation/SKILL.md | 91 +++++++++++++++ bitbucket-automation/SKILL.md | 5 + bitquery-automation/SKILL.md | 91 +++++++++++++++ bitwarden-automation/SKILL.md | 91 +++++++++++++++ blackbaud-automation/SKILL.md | 91 +++++++++++++++ blackboard-automation/SKILL.md | 91 +++++++++++++++ blocknative-automation/SKILL.md | 91 +++++++++++++++ boldsign-automation/SKILL.md | 91 +++++++++++++++ bolna-automation/SKILL.md | 91 +++++++++++++++ boloforms-automation/SKILL.md | 91 +++++++++++++++ bolt-iot-automation/SKILL.md | 91 +++++++++++++++ bonsai-automation/SKILL.md | 91 +++++++++++++++ bookingmood-automation/SKILL.md | 91 +++++++++++++++ booqable-automation/SKILL.md | 91 +++++++++++++++ borneo-automation/SKILL.md | 91 +++++++++++++++ botbaba-automation/SKILL.md | 91 +++++++++++++++ botpress-automation/SKILL.md | 91 +++++++++++++++ botsonic-automation/SKILL.md | 91 +++++++++++++++ botstar-automation/SKILL.md | 91 +++++++++++++++ bouncer-automation/SKILL.md | 91 +++++++++++++++ box-automation/SKILL.md | 5 + boxhero-automation/SKILL.md | 91 +++++++++++++++ braintree-automation/SKILL.md | 91 +++++++++++++++ brandfetch-automation/SKILL.md | 91 +++++++++++++++ breeze-automation/SKILL.md | 91 +++++++++++++++ breezy-hr-automation/SKILL.md | 91 +++++++++++++++ brevo-automation/SKILL.md | 5 + brex-automation/SKILL.md | 91 +++++++++++++++ brex-staging-automation/SKILL.md | 91 +++++++++++++++ brightdata-automation/SKILL.md | 91 +++++++++++++++ brightpearl-automation/SKILL.md | 91 +++++++++++++++ brilliant-directories-automation/SKILL.md | 91 +++++++++++++++ browseai-automation/SKILL.md | 91 +++++++++++++++ browser-tool-automation/SKILL.md | 91 +++++++++++++++ browserbase-tool-automation/SKILL.md | 91 +++++++++++++++ browserhub-automation/SKILL.md | 91 +++++++++++++++ browserless-automation/SKILL.md | 91 +++++++++++++++ btcpay-server-automation/SKILL.md | 91 +++++++++++++++ bubble-automation/SKILL.md | 91 +++++++++++++++ bugbug-automation/SKILL.md | 91 +++++++++++++++ bugherd-automation/SKILL.md | 91 +++++++++++++++ bugsnag-automation/SKILL.md | 91 +++++++++++++++ buildkite-automation/SKILL.md | 91 +++++++++++++++ builtwith-automation/SKILL.md | 91 +++++++++++++++ bunnycdn-automation/SKILL.md | 91 +++++++++++++++ byteforms-automation/SKILL.md | 91 +++++++++++++++ cabinpanda-automation/SKILL.md | 91 +++++++++++++++ cal-automation/SKILL.md | 91 +++++++++++++++ cal-com-automation/SKILL.md | 5 + calendarhero-automation/SKILL.md | 91 +++++++++++++++ calendly-automation/SKILL.md | 5 + callerapi-automation/SKILL.md | 91 +++++++++++++++ callingly-automation/SKILL.md | 91 +++++++++++++++ callpage-automation/SKILL.md | 91 +++++++++++++++ campaign-cleaner-automation/SKILL.md | 91 +++++++++++++++ campayn-automation/SKILL.md | 91 +++++++++++++++ canny-automation/SKILL.md | 91 +++++++++++++++ canva-automation/SKILL.md | 5 + canvas-automation/SKILL.md | 91 +++++++++++++++ capsule-crm-automation/SKILL.md | 91 +++++++++++++++ capsule_crm-automation/SKILL.md | 110 ++++++++++++++++++ carbone-automation/SKILL.md | 91 +++++++++++++++ cardly-automation/SKILL.md | 91 +++++++++++++++ castingwords-automation/SKILL.md | 91 +++++++++++++++ cats-automation/SKILL.md | 91 +++++++++++++++ cdr-platform-automation/SKILL.md | 91 +++++++++++++++ census-bureau-automation/SKILL.md | 91 +++++++++++++++ centralstationcrm-automation/SKILL.md | 91 +++++++++++++++ certifier-automation/SKILL.md | 91 +++++++++++++++ chaser-automation/SKILL.md | 91 +++++++++++++++ chatbotkit-automation/SKILL.md | 91 +++++++++++++++ chatfai-automation/SKILL.md | 91 +++++++++++++++ chatwork-automation/SKILL.md | 91 +++++++++++++++ chmeetings-automation/SKILL.md | 91 +++++++++++++++ cincopa-automation/SKILL.md | 91 +++++++++++++++ circleci-automation/SKILL.md | 5 + claid-ai-automation/SKILL.md | 91 +++++++++++++++ classmarker-automation/SKILL.md | 91 +++++++++++++++ clearout-automation/SKILL.md | 91 +++++++++++++++ clickmeeting-automation/SKILL.md | 91 +++++++++++++++ clickup-automation/SKILL.md | 5 + clockify-automation/SKILL.md | 91 +++++++++++++++ close-automation/SKILL.md | 5 + cloudcart-automation/SKILL.md | 91 +++++++++++++++ cloudconvert-automation/SKILL.md | 91 +++++++++++++++ cloudflare-api-key-automation/SKILL.md | 91 +++++++++++++++ cloudflare-automation/SKILL.md | 91 +++++++++++++++ .../SKILL.md | 91 +++++++++++++++ cloudinary-automation/SKILL.md | 91 +++++++++++++++ cloudlayer-automation/SKILL.md | 91 +++++++++++++++ cloudpress-automation/SKILL.md | 91 +++++++++++++++ coassemble-automation/SKILL.md | 91 +++++++++++++++ coda-automation/SKILL.md | 5 + codacy-automation/SKILL.md | 91 +++++++++++++++ codeinterpreter-automation/SKILL.md | 91 +++++++++++++++ codereadr-automation/SKILL.md | 91 +++++++++++++++ coinbase-automation/SKILL.md | 91 +++++++++++++++ coinmarketcal-automation/SKILL.md | 91 +++++++++++++++ coinmarketcap-automation/SKILL.md | 91 +++++++++++++++ coinranking-automation/SKILL.md | 91 +++++++++++++++ college-football-data-automation/SKILL.md | 91 +++++++++++++++ composio-automation/SKILL.md | 91 +++++++++++++++ composio-search-automation/SKILL.md | 91 +++++++++++++++ confluence-automation/SKILL.md | 5 + connecteam-automation/SKILL.md | 91 +++++++++++++++ contentful-automation/SKILL.md | 91 +++++++++++++++ contentful-graphql-automation/SKILL.md | 91 +++++++++++++++ control-d-automation/SKILL.md | 91 +++++++++++++++ conversion-tools-automation/SKILL.md | 91 +++++++++++++++ convertapi-automation/SKILL.md | 91 +++++++++++++++ convertkit-automation/SKILL.md | 5 + conveyor-automation/SKILL.md | 91 +++++++++++++++ convolo-ai-automation/SKILL.md | 91 +++++++++++++++ corrently-automation/SKILL.md | 91 +++++++++++++++ countdown-api-automation/SKILL.md | 91 +++++++++++++++ coupa-automation/SKILL.md | 91 +++++++++++++++ craftmypdf-automation/SKILL.md | 91 +++++++++++++++ crowdin-automation/SKILL.md | 91 +++++++++++++++ crustdata-automation/SKILL.md | 91 +++++++++++++++ cults-automation/SKILL.md | 91 +++++++++++++++ curated-automation/SKILL.md | 91 +++++++++++++++ currents-api-automation/SKILL.md | 91 +++++++++++++++ customerio-automation/SKILL.md | 91 +++++++++++++++ customgpt-automation/SKILL.md | 91 +++++++++++++++ customjs-automation/SKILL.md | 91 +++++++++++++++ cutt-ly-automation/SKILL.md | 91 +++++++++++++++ d2lbrightspace-automation/SKILL.md | 91 +++++++++++++++ dadata-ru-automation/SKILL.md | 91 +++++++++++++++ daffy-automation/SKILL.md | 91 +++++++++++++++ dailybot-automation/SKILL.md | 91 +++++++++++++++ datadog-automation/SKILL.md | 5 + datagma-automation/SKILL.md | 91 +++++++++++++++ datarobot-automation/SKILL.md | 91 +++++++++++++++ deadline-funnel-automation/SKILL.md | 91 +++++++++++++++ deel-automation/SKILL.md | 91 +++++++++++++++ deepgram-automation/SKILL.md | 91 +++++++++++++++ demio-automation/SKILL.md | 91 +++++++++++++++ desktime-automation/SKILL.md | 91 +++++++++++++++ detrack-automation/SKILL.md | 91 +++++++++++++++ dialmycalls-automation/SKILL.md | 91 +++++++++++++++ dialpad-automation/SKILL.md | 91 +++++++++++++++ dictionary-api-automation/SKILL.md | 91 +++++++++++++++ diffbot-automation/SKILL.md | 91 +++++++++++++++ digicert-automation/SKILL.md | 91 +++++++++++++++ digital-ocean-automation/SKILL.md | 91 +++++++++++++++ discord-automation/SKILL.md | 5 + discordbot-automation/SKILL.md | 91 +++++++++++++++ dnsfilter-automation/SKILL.md | 91 +++++++++++++++ dock-certs-automation/SKILL.md | 91 +++++++++++++++ docker-hub-automation/SKILL.md | 91 +++++++++++++++ docker_hub-automation/SKILL.md | 110 ++++++++++++++++++ docmosis-automation/SKILL.md | 91 +++++++++++++++ docnify-automation/SKILL.md | 91 +++++++++++++++ docsbot-ai-automation/SKILL.md | 91 +++++++++++++++ docsumo-automation/SKILL.md | 91 +++++++++++++++ docugenerate-automation/SKILL.md | 91 +++++++++++++++ documenso-automation/SKILL.md | 91 +++++++++++++++ documint-automation/SKILL.md | 91 +++++++++++++++ docupilot-automation/SKILL.md | 91 +++++++++++++++ docupost-automation/SKILL.md | 91 +++++++++++++++ docuseal-automation/SKILL.md | 91 +++++++++++++++ docusign-automation/SKILL.md | 5 + .../SKILL.md | 91 +++++++++++++++ doppler-secretops-automation/SKILL.md | 91 +++++++++++++++ dotsimple-automation/SKILL.md | 91 +++++++++++++++ dovetail-automation/SKILL.md | 91 +++++++++++++++ dpd2-automation/SKILL.md | 91 +++++++++++++++ draftable-automation/SKILL.md | 91 +++++++++++++++ dreamstudio-automation/SKILL.md | 91 +++++++++++++++ drip-jobs-automation/SKILL.md | 91 +++++++++++++++ dripcel-automation/SKILL.md | 91 +++++++++++++++ dromo-automation/SKILL.md | 91 +++++++++++++++ dropbox-automation/SKILL.md | 5 + dropbox-sign-automation/SKILL.md | 91 +++++++++++++++ dropcontact-automation/SKILL.md | 91 +++++++++++++++ dungeon-fighter-online-automation/SKILL.md | 91 +++++++++++++++ dynamics365-automation/SKILL.md | 91 +++++++++++++++ echtpost-automation/SKILL.md | 91 +++++++++++++++ elevenlabs-automation/SKILL.md | 91 +++++++++++++++ elorus-automation/SKILL.md | 91 +++++++++++++++ emailable-automation/SKILL.md | 91 +++++++++++++++ emaillistverify-automation/SKILL.md | 91 +++++++++++++++ emailoctopus-automation/SKILL.md | 91 +++++++++++++++ emelia-automation/SKILL.md | 91 +++++++++++++++ encodian-automation/SKILL.md | 91 +++++++++++++++ endorsal-automation/SKILL.md | 91 +++++++++++++++ enginemailer-automation/SKILL.md | 91 +++++++++++++++ enigma-automation/SKILL.md | 91 +++++++++++++++ entelligence-automation/SKILL.md | 91 +++++++++++++++ eodhd-apis-automation/SKILL.md | 91 +++++++++++++++ epic-games-automation/SKILL.md | 91 +++++++++++++++ esignatures-io-automation/SKILL.md | 91 +++++++++++++++ espocrm-automation/SKILL.md | 91 +++++++++++++++ esputnik-automation/SKILL.md | 91 +++++++++++++++ etermin-automation/SKILL.md | 91 +++++++++++++++ evenium-automation/SKILL.md | 91 +++++++++++++++ eventbrite-automation/SKILL.md | 91 +++++++++++++++ eventee-automation/SKILL.md | 91 +++++++++++++++ eventzilla-automation/SKILL.md | 91 +++++++++++++++ everhour-automation/SKILL.md | 91 +++++++++++++++ eversign-automation/SKILL.md | 91 +++++++++++++++ exa-automation/SKILL.md | 91 +++++++++++++++ excel-automation/SKILL.md | 91 +++++++++++++++ exist-automation/SKILL.md | 91 +++++++++++++++ expofp-automation/SKILL.md | 91 +++++++++++++++ extracta-ai-automation/SKILL.md | 91 +++++++++++++++ facebook-automation/SKILL.md | 91 +++++++++++++++ faceup-automation/SKILL.md | 91 +++++++++++++++ factorial-automation/SKILL.md | 91 +++++++++++++++ feathery-automation/SKILL.md | 91 +++++++++++++++ felt-automation/SKILL.md | 91 +++++++++++++++ fibery-automation/SKILL.md | 91 +++++++++++++++ fidel-api-automation/SKILL.md | 91 +++++++++++++++ figma-automation/SKILL.md | 5 + files-com-automation/SKILL.md | 91 +++++++++++++++ fillout-forms-automation/SKILL.md | 91 +++++++++++++++ fillout_forms-automation/SKILL.md | 110 ++++++++++++++++++ finage-automation/SKILL.md | 91 +++++++++++++++ findymail-automation/SKILL.md | 91 +++++++++++++++ finerworks-automation/SKILL.md | 91 +++++++++++++++ fingertip-automation/SKILL.md | 91 +++++++++++++++ finmei-automation/SKILL.md | 91 +++++++++++++++ fireberry-automation/SKILL.md | 91 +++++++++++++++ firecrawl-automation/SKILL.md | 91 +++++++++++++++ fireflies-automation/SKILL.md | 91 +++++++++++++++ firmao-automation/SKILL.md | 91 +++++++++++++++ fitbit-automation/SKILL.md | 91 +++++++++++++++ fixer-automation/SKILL.md | 91 +++++++++++++++ fixer-io-automation/SKILL.md | 91 +++++++++++++++ flexisign-automation/SKILL.md | 91 +++++++++++++++ flowiseai-automation/SKILL.md | 91 +++++++++++++++ flutterwave-automation/SKILL.md | 91 +++++++++++++++ fluxguard-automation/SKILL.md | 91 +++++++++++++++ folk-automation/SKILL.md | 91 +++++++++++++++ fomo-automation/SKILL.md | 91 +++++++++++++++ forcemanager-automation/SKILL.md | 91 +++++++++++++++ formbricks-automation/SKILL.md | 91 +++++++++++++++ formcarry-automation/SKILL.md | 91 +++++++++++++++ formdesk-automation/SKILL.md | 91 +++++++++++++++ formsite-automation/SKILL.md | 91 +++++++++++++++ foursquare-automation/SKILL.md | 91 +++++++++++++++ fraudlabs-pro-automation/SKILL.md | 91 +++++++++++++++ freshbooks-automation/SKILL.md | 91 +++++++++++++++ freshdesk-automation/SKILL.md | 5 + freshservice-automation/SKILL.md | 5 + front-automation/SKILL.md | 91 +++++++++++++++ fullenrich-automation/SKILL.md | 91 +++++++++++++++ gagelist-automation/SKILL.md | 91 +++++++++++++++ gamma-automation/SKILL.md | 91 +++++++++++++++ gan-ai-automation/SKILL.md | 91 +++++++++++++++ gatherup-automation/SKILL.md | 91 +++++++++++++++ gemini-automation/SKILL.md | 91 +++++++++++++++ gender-api-automation/SKILL.md | 91 +++++++++++++++ genderapi-io-automation/SKILL.md | 91 +++++++++++++++ genderize-automation/SKILL.md | 91 +++++++++++++++ geoapify-automation/SKILL.md | 91 +++++++++++++++ geocodio-automation/SKILL.md | 91 +++++++++++++++ geokeo-automation/SKILL.md | 91 +++++++++++++++ getform-automation/SKILL.md | 91 +++++++++++++++ gift-up-automation/SKILL.md | 91 +++++++++++++++ gigasheet-automation/SKILL.md | 91 +++++++++++++++ giphy-automation/SKILL.md | 91 +++++++++++++++ gist-automation/SKILL.md | 91 +++++++++++++++ github-automation/SKILL.md | 5 + gitlab-automation/SKILL.md | 5 + givebutter-automation/SKILL.md | 91 +++++++++++++++ gladia-automation/SKILL.md | 91 +++++++++++++++ gleap-automation/SKILL.md | 91 +++++++++++++++ globalping-automation/SKILL.md | 91 +++++++++++++++ gmail-automation/SKILL.md | 6 +- go-to-webinar-automation/SKILL.md | 91 +++++++++++++++ godial-automation/SKILL.md | 91 +++++++++++++++ gong-automation/SKILL.md | 91 +++++++++++++++ goodbits-automation/SKILL.md | 91 +++++++++++++++ goody-automation/SKILL.md | 91 +++++++++++++++ google-address-validation-automation/SKILL.md | 91 +++++++++++++++ google-admin-automation/SKILL.md | 91 +++++++++++++++ google-analytics-automation/SKILL.md | 5 + google-calendar-automation/SKILL.md | 5 + google-classroom-automation/SKILL.md | 91 +++++++++++++++ google-cloud-vision-automation/SKILL.md | 91 +++++++++++++++ google-drive-automation/SKILL.md | 5 + google-maps-automation/SKILL.md | 91 +++++++++++++++ google-search-console-automation/SKILL.md | 91 +++++++++++++++ google_admin-automation/SKILL.md | 110 ++++++++++++++++++ google_classroom-automation/SKILL.md | 110 ++++++++++++++++++ google_maps-automation/SKILL.md | 110 ++++++++++++++++++ google_search_console-automation/SKILL.md | 110 ++++++++++++++++++ googleads-automation/SKILL.md | 91 +++++++++++++++ googlebigquery-automation/SKILL.md | 91 +++++++++++++++ googlecalendar-automation/SKILL.md | 91 +++++++++++++++ googledocs-automation/SKILL.md | 91 +++++++++++++++ googledrive-automation/SKILL.md | 91 +++++++++++++++ googlemeet-automation/SKILL.md | 91 +++++++++++++++ googlephotos-automation/SKILL.md | 91 +++++++++++++++ googlesheets-automation/SKILL.md | 5 + googleslides-automation/SKILL.md | 91 +++++++++++++++ googlesuper-automation/SKILL.md | 91 +++++++++++++++ googletasks-automation/SKILL.md | 91 +++++++++++++++ gorgias-automation/SKILL.md | 91 +++++++++++++++ gosquared-automation/SKILL.md | 91 +++++++++++++++ grafbase-automation/SKILL.md | 91 +++++++++++++++ graphhopper-automation/SKILL.md | 91 +++++++++++++++ griptape-automation/SKILL.md | 91 +++++++++++++++ grist-automation/SKILL.md | 91 +++++++++++++++ groqcloud-automation/SKILL.md | 91 +++++++++++++++ gumroad-automation/SKILL.md | 91 +++++++++++++++ habitica-automation/SKILL.md | 91 +++++++++++++++ hackernews-automation/SKILL.md | 91 +++++++++++++++ happy-scribe-automation/SKILL.md | 91 +++++++++++++++ harvest-automation/SKILL.md | 91 +++++++++++++++ hashnode-automation/SKILL.md | 91 +++++++++++++++ helcim-automation/SKILL.md | 91 +++++++++++++++ helloleads-automation/SKILL.md | 91 +++++++++++++++ helpdesk-automation/SKILL.md | 5 + helpwise-automation/SKILL.md | 91 +++++++++++++++ here-automation/SKILL.md | 91 +++++++++++++++ heygen-automation/SKILL.md | 91 +++++++++++++++ heyreach-automation/SKILL.md | 91 +++++++++++++++ heyzine-automation/SKILL.md | 91 +++++++++++++++ highergov-automation/SKILL.md | 91 +++++++++++++++ highlevel-automation/SKILL.md | 91 +++++++++++++++ honeybadger-automation/SKILL.md | 91 +++++++++++++++ honeyhive-automation/SKILL.md | 91 +++++++++++++++ hookdeck-automation/SKILL.md | 91 +++++++++++++++ hotspotsystem-automation/SKILL.md | 91 +++++++++++++++ html-to-image-automation/SKILL.md | 91 +++++++++++++++ hubspot-automation/SKILL.md | 6 +- humanitix-automation/SKILL.md | 91 +++++++++++++++ humanloop-automation/SKILL.md | 91 +++++++++++++++ hunter-automation/SKILL.md | 91 +++++++++++++++ hypeauditor-automation/SKILL.md | 91 +++++++++++++++ hyperbrowser-automation/SKILL.md | 91 +++++++++++++++ hyperise-automation/SKILL.md | 91 +++++++++++++++ hystruct-automation/SKILL.md | 91 +++++++++++++++ icims-talent-cloud-automation/SKILL.md | 91 +++++++++++++++ icypeas-automation/SKILL.md | 91 +++++++++++++++ idea-scale-automation/SKILL.md | 91 +++++++++++++++ identitycheck-automation/SKILL.md | 91 +++++++++++++++ ignisign-automation/SKILL.md | 91 +++++++++++++++ imagekit-io-automation/SKILL.md | 91 +++++++++++++++ imgbb-automation/SKILL.md | 91 +++++++++++++++ imgix-automation/SKILL.md | 91 +++++++++++++++ influxdb-cloud-automation/SKILL.md | 91 +++++++++++++++ insighto-ai-automation/SKILL.md | 91 +++++++++++++++ instacart-automation/SKILL.md | 91 +++++++++++++++ instagram-automation/SKILL.md | 5 + instantly-automation/SKILL.md | 91 +++++++++++++++ intelliprint-automation/SKILL.md | 91 +++++++++++++++ intercom-automation/SKILL.md | 5 + interzoid-automation/SKILL.md | 91 +++++++++++++++ ip2location-automation/SKILL.md | 91 +++++++++++++++ ip2location-io-automation/SKILL.md | 91 +++++++++++++++ ip2proxy-automation/SKILL.md | 91 +++++++++++++++ ip2whois-automation/SKILL.md | 91 +++++++++++++++ ipdata-co-automation/SKILL.md | 91 +++++++++++++++ ipinfo-io-automation/SKILL.md | 91 +++++++++++++++ iqair-airvisual-automation/SKILL.md | 91 +++++++++++++++ jigsawstack-automation/SKILL.md | 91 +++++++++++++++ jira-automation/SKILL.md | 5 + jobnimbus-automation/SKILL.md | 91 +++++++++++++++ jotform-automation/SKILL.md | 91 +++++++++++++++ jumpcloud-automation/SKILL.md | 91 +++++++++++++++ junglescout-automation/SKILL.md | 91 +++++++++++++++ kadoa-automation/SKILL.md | 91 +++++++++++++++ kaggle-automation/SKILL.md | 91 +++++++++++++++ kaleido-automation/SKILL.md | 91 +++++++++++++++ keap-automation/SKILL.md | 91 +++++++++++++++ keen-io-automation/SKILL.md | 91 +++++++++++++++ kickbox-automation/SKILL.md | 91 +++++++++++++++ kit-automation/SKILL.md | 91 +++++++++++++++ klaviyo-automation/SKILL.md | 5 + klipfolio-automation/SKILL.md | 91 +++++++++++++++ ko-fi-automation/SKILL.md | 91 +++++++++++++++ kommo-automation/SKILL.md | 91 +++++++++++++++ kontent-ai-automation/SKILL.md | 91 +++++++++++++++ kraken-io-automation/SKILL.md | 91 +++++++++++++++ l2s-automation/SKILL.md | 91 +++++++++++++++ labs64-netlicensing-automation/SKILL.md | 91 +++++++++++++++ landbot-automation/SKILL.md | 91 +++++++++++++++ langbase-automation/SKILL.md | 91 +++++++++++++++ lastpass-automation/SKILL.md | 91 +++++++++++++++ launch-darkly-automation/SKILL.md | 91 +++++++++++++++ launch_darkly-automation/SKILL.md | 110 ++++++++++++++++++ leadfeeder-automation/SKILL.md | 91 +++++++++++++++ leadoku-automation/SKILL.md | 91 +++++++++++++++ leiga-automation/SKILL.md | 91 +++++++++++++++ lemlist-automation/SKILL.md | 91 +++++++++++++++ lemon-squeezy-automation/SKILL.md | 91 +++++++++++++++ lemon_squeezy-automation/SKILL.md | 110 ++++++++++++++++++ lessonspace-automation/SKILL.md | 91 +++++++++++++++ lever-automation/SKILL.md | 91 +++++++++++++++ lever-sandbox-automation/SKILL.md | 91 +++++++++++++++ leverly-automation/SKILL.md | 91 +++++++++++++++ lexoffice-automation/SKILL.md | 91 +++++++++++++++ linear-automation/SKILL.md | 5 + linguapop-automation/SKILL.md | 91 +++++++++++++++ linkedin-automation/SKILL.md | 5 + linkhut-automation/SKILL.md | 91 +++++++++++++++ linkup-automation/SKILL.md | 91 +++++++++++++++ listclean-automation/SKILL.md | 91 +++++++++++++++ listennotes-automation/SKILL.md | 91 +++++++++++++++ livesession-automation/SKILL.md | 91 +++++++++++++++ lmnt-automation/SKILL.md | 91 +++++++++++++++ lodgify-automation/SKILL.md | 91 +++++++++++++++ logo-dev-automation/SKILL.md | 91 +++++++++++++++ loomio-automation/SKILL.md | 91 +++++++++++++++ loyverse-automation/SKILL.md | 91 +++++++++++++++ magnetic-automation/SKILL.md | 91 +++++++++++++++ mailbluster-automation/SKILL.md | 91 +++++++++++++++ mailboxlayer-automation/SKILL.md | 91 +++++++++++++++ mailcheck-automation/SKILL.md | 91 +++++++++++++++ mailchimp-automation/SKILL.md | 5 + mailcoach-automation/SKILL.md | 91 +++++++++++++++ mailerlite-automation/SKILL.md | 91 +++++++++++++++ mailersend-automation/SKILL.md | 91 +++++++++++++++ mails-so-automation/SKILL.md | 91 +++++++++++++++ mailsoftly-automation/SKILL.md | 91 +++++++++++++++ maintainx-automation/SKILL.md | 91 +++++++++++++++ make-automation/SKILL.md | 5 + many-chat-automation/SKILL.md | 91 +++++++++++++++ many_chat-automation/SKILL.md | 110 ++++++++++++++++++ mapbox-automation/SKILL.md | 91 +++++++++++++++ mapulus-automation/SKILL.md | 91 +++++++++++++++ mboum-automation/SKILL.md | 91 +++++++++++++++ melo-automation/SKILL.md | 91 +++++++++++++++ mem-automation/SKILL.md | 91 +++++++++++++++ mem0-automation/SKILL.md | 91 +++++++++++++++ memberspot-automation/SKILL.md | 91 +++++++++++++++ memberstack-automation/SKILL.md | 91 +++++++++++++++ membervault-automation/SKILL.md | 91 +++++++++++++++ metaads-automation/SKILL.md | 91 +++++++++++++++ metaphor-automation/SKILL.md | 91 +++++++++++++++ mezmo-automation/SKILL.md | 91 +++++++++++++++ microsoft-clarity-automation/SKILL.md | 91 +++++++++++++++ microsoft-teams-automation/SKILL.md | 5 + microsoft-tenant-automation/SKILL.md | 91 +++++++++++++++ microsoft_clarity-automation/SKILL.md | 110 ++++++++++++++++++ minerstat-automation/SKILL.md | 91 +++++++++++++++ miro-automation/SKILL.md | 5 + missive-automation/SKILL.md | 91 +++++++++++++++ mistral-ai-automation/SKILL.md | 91 +++++++++++++++ mistral_ai-automation/SKILL.md | 110 ++++++++++++++++++ mixpanel-automation/SKILL.md | 5 + mocean-automation/SKILL.md | 91 +++++++++++++++ moco-automation/SKILL.md | 91 +++++++++++++++ modelry-automation/SKILL.md | 91 +++++++++++++++ monday-automation/SKILL.md | 5 + moneybird-automation/SKILL.md | 91 +++++++++++++++ moonclerk-automation/SKILL.md | 91 +++++++++++++++ moosend-automation/SKILL.md | 91 +++++++++++++++ mopinion-automation/SKILL.md | 91 +++++++++++++++ more-trees-automation/SKILL.md | 91 +++++++++++++++ moxie-automation/SKILL.md | 91 +++++++++++++++ moz-automation/SKILL.md | 91 +++++++++++++++ msg91-automation/SKILL.md | 91 +++++++++++++++ mural-automation/SKILL.md | 91 +++++++++++++++ mx-technologies-automation/SKILL.md | 91 +++++++++++++++ mx-toolbox-automation/SKILL.md | 91 +++++++++++++++ nango-automation/SKILL.md | 91 +++++++++++++++ nano-nets-automation/SKILL.md | 91 +++++++++++++++ nasa-automation/SKILL.md | 91 +++++++++++++++ nasdaq-automation/SKILL.md | 91 +++++++++++++++ ncscale-automation/SKILL.md | 91 +++++++++++++++ needle-automation/SKILL.md | 91 +++++++++++++++ neon-automation/SKILL.md | 91 +++++++++++++++ netsuite-automation/SKILL.md | 91 +++++++++++++++ neuronwriter-automation/SKILL.md | 91 +++++++++++++++ neutrino-automation/SKILL.md | 91 +++++++++++++++ neverbounce-automation/SKILL.md | 91 +++++++++++++++ new-relic-automation/SKILL.md | 91 +++++++++++++++ new_relic-automation/SKILL.md | 110 ++++++++++++++++++ news-api-automation/SKILL.md | 91 +++++++++++++++ nextdns-automation/SKILL.md | 91 +++++++++++++++ ngrok-automation/SKILL.md | 91 +++++++++++++++ ninox-automation/SKILL.md | 91 +++++++++++++++ nocrm-io-automation/SKILL.md | 91 +++++++++++++++ notion-automation/SKILL.md | 5 + npm-automation/SKILL.md | 91 +++++++++++++++ ocr-web-service-automation/SKILL.md | 91 +++++++++++++++ ocrspace-automation/SKILL.md | 91 +++++++++++++++ omnisend-automation/SKILL.md | 91 +++++++++++++++ oncehub-automation/SKILL.md | 91 +++++++++++++++ one-drive-automation/SKILL.md | 5 + onedesk-automation/SKILL.md | 91 +++++++++++++++ onepage-automation/SKILL.md | 91 +++++++++++++++ onesignal-rest-api-automation/SKILL.md | 91 +++++++++++++++ onesignal-user-auth-automation/SKILL.md | 91 +++++++++++++++ onesignal_rest_api-automation/SKILL.md | 110 ++++++++++++++++++ open-sea-automation/SKILL.md | 91 +++++++++++++++ openai-automation/SKILL.md | 91 +++++++++++++++ opencage-automation/SKILL.md | 91 +++++++++++++++ opengraph-io-automation/SKILL.md | 91 +++++++++++++++ openperplex-automation/SKILL.md | 91 +++++++++++++++ openrouter-automation/SKILL.md | 91 +++++++++++++++ openweather-api-automation/SKILL.md | 91 +++++++++++++++ optimoroute-automation/SKILL.md | 91 +++++++++++++++ outlook-automation/SKILL.md | 5 + outlook-calendar-automation/SKILL.md | 5 + owl-protocol-automation/SKILL.md | 91 +++++++++++++++ page-x-automation/SKILL.md | 91 +++++++++++++++ pagerduty-automation/SKILL.md | 5 + pandadoc-automation/SKILL.md | 91 +++++++++++++++ paradym-automation/SKILL.md | 91 +++++++++++++++ parallel-automation/SKILL.md | 91 +++++++++++++++ parma-automation/SKILL.md | 91 +++++++++++++++ parsehub-automation/SKILL.md | 91 +++++++++++++++ parsera-automation/SKILL.md | 91 +++++++++++++++ parseur-automation/SKILL.md | 91 +++++++++++++++ passcreator-automation/SKILL.md | 91 +++++++++++++++ passslot-automation/SKILL.md | 91 +++++++++++++++ payhip-automation/SKILL.md | 91 +++++++++++++++ pdf-api-io-automation/SKILL.md | 91 +++++++++++++++ pdf-co-automation/SKILL.md | 91 +++++++++++++++ pdf4me-automation/SKILL.md | 91 +++++++++++++++ pdfless-automation/SKILL.md | 91 +++++++++++++++ pdfmonkey-automation/SKILL.md | 91 +++++++++++++++ peopledatalabs-automation/SKILL.md | 91 +++++++++++++++ perigon-automation/SKILL.md | 91 +++++++++++++++ perplexityai-automation/SKILL.md | 91 +++++++++++++++ persistiq-automation/SKILL.md | 91 +++++++++++++++ pexels-automation/SKILL.md | 91 +++++++++++++++ phantombuster-automation/SKILL.md | 91 +++++++++++++++ piggy-automation/SKILL.md | 91 +++++++++++++++ piloterr-automation/SKILL.md | 91 +++++++++++++++ pilvio-automation/SKILL.md | 91 +++++++++++++++ pingdom-automation/SKILL.md | 91 +++++++++++++++ pipedrive-automation/SKILL.md | 5 + pipeline-crm-automation/SKILL.md | 91 +++++++++++++++ placekey-automation/SKILL.md | 91 +++++++++++++++ placid-automation/SKILL.md | 91 +++++++++++++++ plain-automation/SKILL.md | 91 +++++++++++++++ plasmic-automation/SKILL.md | 91 +++++++++++++++ platerecognizer-automation/SKILL.md | 91 +++++++++++++++ plisio-automation/SKILL.md | 91 +++++++++++++++ polygon-automation/SKILL.md | 91 +++++++++++++++ polygon-io-automation/SKILL.md | 91 +++++++++++++++ poptin-automation/SKILL.md | 91 +++++++++++++++ postgrid-automation/SKILL.md | 91 +++++++++++++++ postgrid-verify-automation/SKILL.md | 91 +++++++++++++++ posthog-automation/SKILL.md | 5 + postmark-automation/SKILL.md | 5 + precoro-automation/SKILL.md | 91 +++++++++++++++ prerender-automation/SKILL.md | 91 +++++++++++++++ printautopilot-automation/SKILL.md | 91 +++++++++++++++ prisma-automation/SKILL.md | 91 +++++++++++++++ prismic-automation/SKILL.md | 91 +++++++++++++++ process-street-automation/SKILL.md | 91 +++++++++++++++ procfu-automation/SKILL.md | 91 +++++++++++++++ productboard-automation/SKILL.md | 91 +++++++++++++++ productlane-automation/SKILL.md | 91 +++++++++++++++ project-bubble-automation/SKILL.md | 91 +++++++++++++++ proofly-automation/SKILL.md | 91 +++++++++++++++ proxiedmail-automation/SKILL.md | 91 +++++++++++++++ pushbullet-automation/SKILL.md | 91 +++++++++++++++ pushover-automation/SKILL.md | 91 +++++++++++++++ quaderno-automation/SKILL.md | 91 +++++++++++++++ qualaroo-automation/SKILL.md | 91 +++++++++++++++ quickbooks-automation/SKILL.md | 91 +++++++++++++++ radar-automation/SKILL.md | 91 +++++++++++++++ rafflys-automation/SKILL.md | 91 +++++++++++++++ ragic-automation/SKILL.md | 91 +++++++++++++++ raisely-automation/SKILL.md | 91 +++++++++++++++ ramp-automation/SKILL.md | 91 +++++++++++++++ ravenseotools-automation/SKILL.md | 91 +++++++++++++++ re-amaze-automation/SKILL.md | 91 +++++++++++++++ realphonevalidation-automation/SKILL.md | 91 +++++++++++++++ recallai-automation/SKILL.md | 91 +++++++++++++++ recruitee-automation/SKILL.md | 91 +++++++++++++++ reddit-automation/SKILL.md | 5 + refiner-automation/SKILL.md | 91 +++++++++++++++ remarkety-automation/SKILL.md | 91 +++++++++++++++ remote-retrieval-automation/SKILL.md | 91 +++++++++++++++ remove-bg-automation/SKILL.md | 91 +++++++++++++++ render-automation/SKILL.md | 5 + renderform-automation/SKILL.md | 91 +++++++++++++++ repairshopr-automation/SKILL.md | 91 +++++++++++++++ replicate-automation/SKILL.md | 91 +++++++++++++++ reply-automation/SKILL.md | 91 +++++++++++++++ reply-io-automation/SKILL.md | 91 +++++++++++++++ resend-automation/SKILL.md | 91 +++++++++++++++ respond-io-automation/SKILL.md | 91 +++++++++++++++ retailed-automation/SKILL.md | 91 +++++++++++++++ retellai-automation/SKILL.md | 91 +++++++++++++++ retently-automation/SKILL.md | 91 +++++++++++++++ rev-ai-automation/SKILL.md | 91 +++++++++++++++ revolt-automation/SKILL.md | 91 +++++++++++++++ ring-central-automation/SKILL.md | 91 +++++++++++++++ ring_central-automation/SKILL.md | 110 ++++++++++++++++++ rippling-automation/SKILL.md | 91 +++++++++++++++ ritekit-automation/SKILL.md | 91 +++++++++++++++ rkvst-automation/SKILL.md | 91 +++++++++++++++ rocketlane-automation/SKILL.md | 91 +++++++++++++++ rootly-automation/SKILL.md | 91 +++++++++++++++ rosette-text-analytics-automation/SKILL.md | 91 +++++++++++++++ route4me-automation/SKILL.md | 91 +++++++++++++++ safetyculture-automation/SKILL.md | 91 +++++++++++++++ sage-automation/SKILL.md | 91 +++++++++++++++ salesforce-automation/SKILL.md | 5 + .../SKILL.md | 91 +++++++++++++++ salesforce-service-cloud-automation/SKILL.md | 91 +++++++++++++++ salesmate-automation/SKILL.md | 91 +++++++++++++++ sap-successfactors-automation/SKILL.md | 91 +++++++++++++++ satismeter-automation/SKILL.md | 91 +++++++++++++++ scrape-do-automation/SKILL.md | 91 +++++++++++++++ scrapegraph-ai-automation/SKILL.md | 91 +++++++++++++++ scrapfly-automation/SKILL.md | 91 +++++++++++++++ scrapingant-automation/SKILL.md | 91 +++++++++++++++ scrapingbee-automation/SKILL.md | 91 +++++++++++++++ screenshot-fyi-automation/SKILL.md | 91 +++++++++++++++ screenshotone-automation/SKILL.md | 91 +++++++++++++++ seat-geek-automation/SKILL.md | 91 +++++++++++++++ securitytrails-automation/SKILL.md | 91 +++++++++++++++ segment-automation/SKILL.md | 5 + segmetrics-automation/SKILL.md | 91 +++++++++++++++ seismic-automation/SKILL.md | 91 +++++++++++++++ semanticscholar-automation/SKILL.md | 91 +++++++++++++++ semrush-automation/SKILL.md | 91 +++++++++++++++ sendbird-ai-chabot-automation/SKILL.md | 91 +++++++++++++++ sendbird-automation/SKILL.md | 91 +++++++++++++++ sendfox-automation/SKILL.md | 91 +++++++++++++++ sendgrid-automation/SKILL.md | 5 + sendlane-automation/SKILL.md | 91 +++++++++++++++ sendloop-automation/SKILL.md | 91 +++++++++++++++ sendspark-automation/SKILL.md | 91 +++++++++++++++ sensibo-automation/SKILL.md | 91 +++++++++++++++ sentry-automation/SKILL.md | 5 + seqera-automation/SKILL.md | 91 +++++++++++++++ serpapi-automation/SKILL.md | 91 +++++++++++++++ serpdog-automation/SKILL.md | 91 +++++++++++++++ serply-automation/SKILL.md | 91 +++++++++++++++ servicem8-automation/SKILL.md | 91 +++++++++++++++ sevdesk-automation/SKILL.md | 91 +++++++++++++++ share-point-automation/SKILL.md | 91 +++++++++++++++ share_point-automation/SKILL.md | 110 ++++++++++++++++++ shipengine-automation/SKILL.md | 91 +++++++++++++++ shopify-automation/SKILL.md | 5 + short-io-automation/SKILL.md | 91 +++++++++++++++ short-menu-automation/SKILL.md | 91 +++++++++++++++ shortcut-automation/SKILL.md | 91 +++++++++++++++ shorten-rest-automation/SKILL.md | 91 +++++++++++++++ shortpixel-automation/SKILL.md | 91 +++++++++++++++ shotstack-automation/SKILL.md | 91 +++++++++++++++ sidetracker-automation/SKILL.md | 91 +++++++++++++++ signaturely-automation/SKILL.md | 91 +++++++++++++++ signpath-automation/SKILL.md | 91 +++++++++++++++ signwell-automation/SKILL.md | 91 +++++++++++++++ .../SKILL.md | 91 +++++++++++++++ .../SKILL.md | 110 ++++++++++++++++++ simla-com-automation/SKILL.md | 91 +++++++++++++++ simple-analytics-automation/SKILL.md | 91 +++++++++++++++ simplesat-automation/SKILL.md | 91 +++++++++++++++ sitespeakai-automation/SKILL.md | 91 +++++++++++++++ skyfire-automation/SKILL.md | 91 +++++++++++++++ slack-automation/SKILL.md | 5 + slackbot-automation/SKILL.md | 91 +++++++++++++++ smartproxy-automation/SKILL.md | 91 +++++++++++++++ smartrecruiters-automation/SKILL.md | 91 +++++++++++++++ sms-alert-automation/SKILL.md | 91 +++++++++++++++ smtp2go-automation/SKILL.md | 91 +++++++++++++++ smugmug-automation/SKILL.md | 91 +++++++++++++++ snowflake-automation/SKILL.md | 91 +++++++++++++++ sourcegraph-automation/SKILL.md | 91 +++++++++++++++ splitwise-automation/SKILL.md | 91 +++++++++++++++ spoki-automation/SKILL.md | 91 +++++++++++++++ spondyr-automation/SKILL.md | 91 +++++++++++++++ spotify-automation/SKILL.md | 91 +++++++++++++++ spotlightr-automation/SKILL.md | 91 +++++++++++++++ square-automation/SKILL.md | 5 + sslmate-cert-spotter-api-automation/SKILL.md | 91 +++++++++++++++ stack-exchange-automation/SKILL.md | 91 +++++++++++++++ stannp-automation/SKILL.md | 91 +++++++++++++++ starton-automation/SKILL.md | 91 +++++++++++++++ statuscake-automation/SKILL.md | 91 +++++++++++++++ storeganise-automation/SKILL.md | 91 +++++++++++++++ storerocket-automation/SKILL.md | 91 +++++++++++++++ stormglass-io-automation/SKILL.md | 91 +++++++++++++++ strava-automation/SKILL.md | 91 +++++++++++++++ streamtime-automation/SKILL.md | 91 +++++++++++++++ stripe-automation/SKILL.md | 5 + supabase-automation/SKILL.md | 5 + supadata-automation/SKILL.md | 91 +++++++++++++++ superchat-automation/SKILL.md | 91 +++++++++++++++ supportbee-automation/SKILL.md | 91 +++++++++++++++ supportivekoala-automation/SKILL.md | 91 +++++++++++++++ survey-monkey-automation/SKILL.md | 91 +++++++++++++++ survey_monkey-automation/SKILL.md | 110 ++++++++++++++++++ svix-automation/SKILL.md | 91 +++++++++++++++ sympla-automation/SKILL.md | 91 +++++++++++++++ synthflow-ai-automation/SKILL.md | 91 +++++++++++++++ taggun-automation/SKILL.md | 91 +++++++++++++++ talenthr-automation/SKILL.md | 91 +++++++++++++++ tally-automation/SKILL.md | 91 +++++++++++++++ tapfiliate-automation/SKILL.md | 91 +++++++++++++++ tapform-automation/SKILL.md | 91 +++++++++++++++ tavily-automation/SKILL.md | 91 +++++++++++++++ taxjar-automation/SKILL.md | 91 +++++++++++++++ teamcamp-automation/SKILL.md | 91 +++++++++++++++ telegram-automation/SKILL.md | 5 + telnyx-automation/SKILL.md | 91 +++++++++++++++ teltel-automation/SKILL.md | 91 +++++++++++++++ templated-automation/SKILL.md | 91 +++++++++++++++ test-app-automation/SKILL.md | 91 +++++++++++++++ text-to-pdf-automation/SKILL.md | 91 +++++++++++++++ textcortex-automation/SKILL.md | 91 +++++++++++++++ textit-automation/SKILL.md | 91 +++++++++++++++ textrazor-automation/SKILL.md | 91 +++++++++++++++ thanks-io-automation/SKILL.md | 91 +++++++++++++++ the-odds-api-automation/SKILL.md | 91 +++++++++++++++ ticketmaster-automation/SKILL.md | 91 +++++++++++++++ ticktick-automation/SKILL.md | 91 +++++++++++++++ tiktok-automation/SKILL.md | 5 + timecamp-automation/SKILL.md | 91 +++++++++++++++ timekit-automation/SKILL.md | 91 +++++++++++++++ timelinesai-automation/SKILL.md | 91 +++++++++++++++ timelink-automation/SKILL.md | 91 +++++++++++++++ timely-automation/SKILL.md | 91 +++++++++++++++ tinyurl-automation/SKILL.md | 91 +++++++++++++++ tisane-automation/SKILL.md | 91 +++++++++++++++ todoist-automation/SKILL.md | 5 + toggl-automation/SKILL.md | 91 +++++++++++++++ token-metrics-automation/SKILL.md | 91 +++++++++++++++ tomba-automation/SKILL.md | 91 +++++++++++++++ tomtom-automation/SKILL.md | 91 +++++++++++++++ toneden-automation/SKILL.md | 91 +++++++++++++++ tpscheck-automation/SKILL.md | 91 +++++++++++++++ trello-automation/SKILL.md | 6 +- triggercmd-automation/SKILL.md | 91 +++++++++++++++ tripadvisor-content-api-automation/SKILL.md | 91 +++++++++++++++ turbot-pipes-automation/SKILL.md | 91 +++++++++++++++ turso-automation/SKILL.md | 91 +++++++++++++++ twelve-data-automation/SKILL.md | 91 +++++++++++++++ twitch-automation/SKILL.md | 91 +++++++++++++++ twitter-automation/SKILL.md | 5 + twocaptcha-automation/SKILL.md | 91 +++++++++++++++ typefully-automation/SKILL.md | 91 +++++++++++++++ typless-automation/SKILL.md | 91 +++++++++++++++ u301-automation/SKILL.md | 91 +++++++++++++++ unione-automation/SKILL.md | 91 +++++++++++++++ updown-io-automation/SKILL.md | 91 +++++++++++++++ uploadcare-automation/SKILL.md | 91 +++++++++++++++ uptimerobot-automation/SKILL.md | 91 +++++++++++++++ userlist-automation/SKILL.md | 91 +++++++++++++++ v0-automation/SKILL.md | 91 +++++++++++++++ venly-automation/SKILL.md | 91 +++++++++++++++ veo-automation/SKILL.md | 91 +++++++++++++++ vercel-automation/SKILL.md | 5 + verifiedemail-automation/SKILL.md | 91 +++++++++++++++ veriphone-automation/SKILL.md | 91 +++++++++++++++ vero-automation/SKILL.md | 91 +++++++++++++++ vestaboard-automation/SKILL.md | 91 +++++++++++++++ virustotal-automation/SKILL.md | 91 +++++++++++++++ visme-automation/SKILL.md | 91 +++++++++++++++ waboxapp-automation/SKILL.md | 91 +++++++++++++++ wachete-automation/SKILL.md | 91 +++++++++++++++ waiverfile-automation/SKILL.md | 91 +++++++++++++++ wakatime-automation/SKILL.md | 91 +++++++++++++++ wati-automation/SKILL.md | 91 +++++++++++++++ wave-accounting-automation/SKILL.md | 91 +++++++++++++++ wave_accounting-automation/SKILL.md | 110 ++++++++++++++++++ weathermap-automation/SKILL.md | 91 +++++++++++++++ webex-automation/SKILL.md | 91 +++++++++++++++ webflow-automation/SKILL.md | 5 + webscraping-ai-automation/SKILL.md | 91 +++++++++++++++ webvizio-automation/SKILL.md | 91 +++++++++++++++ whatsapp-automation/SKILL.md | 5 + whautomate-automation/SKILL.md | 91 +++++++++++++++ winston-ai-automation/SKILL.md | 91 +++++++++++++++ wit-ai-automation/SKILL.md | 91 +++++++++++++++ wiz-automation/SKILL.md | 91 +++++++++++++++ wolfram-alpha-api-automation/SKILL.md | 91 +++++++++++++++ woodpecker-co-automation/SKILL.md | 91 +++++++++++++++ workable-automation/SKILL.md | 91 +++++++++++++++ workday-automation/SKILL.md | 91 +++++++++++++++ workiom-automation/SKILL.md | 91 +++++++++++++++ worksnaps-automation/SKILL.md | 91 +++++++++++++++ wrike-automation/SKILL.md | 5 + writer-automation/SKILL.md | 91 +++++++++++++++ xero-automation/SKILL.md | 91 +++++++++++++++ y-gy-automation/SKILL.md | 91 +++++++++++++++ yandex-automation/SKILL.md | 91 +++++++++++++++ yelp-automation/SKILL.md | 91 +++++++++++++++ ynab-automation/SKILL.md | 91 +++++++++++++++ yousearch-automation/SKILL.md | 91 +++++++++++++++ youtube-automation/SKILL.md | 5 + zendesk-automation/SKILL.md | 5 + zenrows-automation/SKILL.md | 91 +++++++++++++++ zenserp-automation/SKILL.md | 91 +++++++++++++++ zeplin-automation/SKILL.md | 91 +++++++++++++++ zerobounce-automation/SKILL.md | 91 +++++++++++++++ zoho-automation/SKILL.md | 91 +++++++++++++++ zoho-bigin-automation/SKILL.md | 91 +++++++++++++++ zoho-books-automation/SKILL.md | 91 +++++++++++++++ zoho-crm-automation/SKILL.md | 5 + zoho-desk-automation/SKILL.md | 91 +++++++++++++++ zoho-inventory-automation/SKILL.md | 91 +++++++++++++++ zoho-invoice-automation/SKILL.md | 91 +++++++++++++++ zoho-mail-automation/SKILL.md | 91 +++++++++++++++ zoho_bigin-automation/SKILL.md | 110 ++++++++++++++++++ zoho_books-automation/SKILL.md | 110 ++++++++++++++++++ zoho_desk-automation/SKILL.md | 110 ++++++++++++++++++ zoho_inventory-automation/SKILL.md | 110 ++++++++++++++++++ zoho_invoice-automation/SKILL.md | 110 ++++++++++++++++++ zoho_mail-automation/SKILL.md | 110 ++++++++++++++++++ zoom-automation/SKILL.md | 5 + zoominfo-automation/SKILL.md | 91 +++++++++++++++ zylvie-automation/SKILL.md | 91 +++++++++++++++ zyte-api-automation/SKILL.md | 91 +++++++++++++++ 910 files changed, 76596 insertions(+), 3 deletions(-) create mode 100644 -21risk-automation/SKILL.md create mode 100644 -2chat-automation/SKILL.md create mode 100644 ably-automation/SKILL.md create mode 100644 abstract-automation/SKILL.md create mode 100644 abuselpdb-automation/SKILL.md create mode 100644 abyssale-automation/SKILL.md create mode 100644 accelo-automation/SKILL.md create mode 100644 accredible-certificates-automation/SKILL.md create mode 100644 acculynx-automation/SKILL.md create mode 100644 active-campaign-automation/SKILL.md create mode 100644 addresszen-automation/SKILL.md create mode 100644 adobe-automation/SKILL.md create mode 100644 adrapid-automation/SKILL.md create mode 100644 adyntel-automation/SKILL.md create mode 100644 aero-workflow-automation/SKILL.md create mode 100644 aeroleads-automation/SKILL.md create mode 100644 affinda-automation/SKILL.md create mode 100644 affinity-automation/SKILL.md create mode 100644 agencyzoom-automation/SKILL.md create mode 100644 agent-mail-automation/SKILL.md create mode 100644 agentql-automation/SKILL.md create mode 100644 agenty-automation/SKILL.md create mode 100644 agiled-automation/SKILL.md create mode 100644 agility-cms-automation/SKILL.md create mode 100644 ahrefs-automation/SKILL.md create mode 100644 ai-ml-api-automation/SKILL.md create mode 100644 aivoov-automation/SKILL.md create mode 100644 alchemy-automation/SKILL.md create mode 100644 algodocs-automation/SKILL.md create mode 100644 algolia-automation/SKILL.md create mode 100644 all-images-ai-automation/SKILL.md create mode 100644 alpha-vantage-automation/SKILL.md create mode 100644 altoviz-automation/SKILL.md create mode 100644 alttext-ai-automation/SKILL.md create mode 100644 amara-automation/SKILL.md create mode 100644 amazon-automation/SKILL.md create mode 100644 ambee-automation/SKILL.md create mode 100644 ambient-weather-automation/SKILL.md create mode 100644 amcards-automation/SKILL.md create mode 100644 anchor-browser-automation/SKILL.md create mode 100644 anonyflow-automation/SKILL.md create mode 100644 anthropic-administrator-automation/SKILL.md create mode 100644 anthropic_administrator-automation/SKILL.md create mode 100644 apaleo-automation/SKILL.md create mode 100644 apex27-automation/SKILL.md create mode 100644 api-bible-automation/SKILL.md create mode 100644 api-labz-automation/SKILL.md create mode 100644 api-ninjas-automation/SKILL.md create mode 100644 api-sports-automation/SKILL.md create mode 100644 api2pdf-automation/SKILL.md create mode 100644 apiflash-automation/SKILL.md create mode 100644 apify-automation/SKILL.md create mode 100644 apilio-automation/SKILL.md create mode 100644 apipie-ai-automation/SKILL.md create mode 100644 apitemplate-io-automation/SKILL.md create mode 100644 apiverve-automation/SKILL.md create mode 100644 apollo-automation/SKILL.md create mode 100644 appcircle-automation/SKILL.md create mode 100644 appdrag-automation/SKILL.md create mode 100644 appointo-automation/SKILL.md create mode 100644 appsflyer-automation/SKILL.md create mode 100644 appveyor-automation/SKILL.md create mode 100644 aryn-automation/SKILL.md create mode 100644 ascora-automation/SKILL.md create mode 100644 ashby-automation/SKILL.md create mode 100644 asin-data-api-automation/SKILL.md create mode 100644 astica-ai-automation/SKILL.md create mode 100644 async-interview-automation/SKILL.md create mode 100644 atlassian-automation/SKILL.md create mode 100644 attio-automation/SKILL.md create mode 100644 auth0-automation/SKILL.md create mode 100644 autobound-automation/SKILL.md create mode 100644 autom-automation/SKILL.md create mode 100644 axonaut-automation/SKILL.md create mode 100644 ayrshare-automation/SKILL.md create mode 100644 backendless-automation/SKILL.md create mode 100644 bannerbear-automation/SKILL.md create mode 100644 bart-automation/SKILL.md create mode 100644 baselinker-automation/SKILL.md create mode 100644 baserow-automation/SKILL.md create mode 100644 basin-automation/SKILL.md create mode 100644 battlenet-automation/SKILL.md create mode 100644 beaconchain-automation/SKILL.md create mode 100644 beaconstac-automation/SKILL.md create mode 100644 beamer-automation/SKILL.md create mode 100644 beeminder-automation/SKILL.md create mode 100644 bench-automation/SKILL.md create mode 100644 benchmark-email-automation/SKILL.md create mode 100644 benzinga-automation/SKILL.md create mode 100644 bestbuy-automation/SKILL.md create mode 100644 better-proposals-automation/SKILL.md create mode 100644 better-stack-automation/SKILL.md create mode 100644 bidsketch-automation/SKILL.md create mode 100644 big-data-cloud-automation/SKILL.md create mode 100644 bigmailer-automation/SKILL.md create mode 100644 bigml-automation/SKILL.md create mode 100644 bigpicture-io-automation/SKILL.md create mode 100644 bitquery-automation/SKILL.md create mode 100644 bitwarden-automation/SKILL.md create mode 100644 blackbaud-automation/SKILL.md create mode 100644 blackboard-automation/SKILL.md create mode 100644 blocknative-automation/SKILL.md create mode 100644 boldsign-automation/SKILL.md create mode 100644 bolna-automation/SKILL.md create mode 100644 boloforms-automation/SKILL.md create mode 100644 bolt-iot-automation/SKILL.md create mode 100644 bonsai-automation/SKILL.md create mode 100644 bookingmood-automation/SKILL.md create mode 100644 booqable-automation/SKILL.md create mode 100644 borneo-automation/SKILL.md create mode 100644 botbaba-automation/SKILL.md create mode 100644 botpress-automation/SKILL.md create mode 100644 botsonic-automation/SKILL.md create mode 100644 botstar-automation/SKILL.md create mode 100644 bouncer-automation/SKILL.md create mode 100644 boxhero-automation/SKILL.md create mode 100644 braintree-automation/SKILL.md create mode 100644 brandfetch-automation/SKILL.md create mode 100644 breeze-automation/SKILL.md create mode 100644 breezy-hr-automation/SKILL.md create mode 100644 brex-automation/SKILL.md create mode 100644 brex-staging-automation/SKILL.md create mode 100644 brightdata-automation/SKILL.md create mode 100644 brightpearl-automation/SKILL.md create mode 100644 brilliant-directories-automation/SKILL.md create mode 100644 browseai-automation/SKILL.md create mode 100644 browser-tool-automation/SKILL.md create mode 100644 browserbase-tool-automation/SKILL.md create mode 100644 browserhub-automation/SKILL.md create mode 100644 browserless-automation/SKILL.md create mode 100644 btcpay-server-automation/SKILL.md create mode 100644 bubble-automation/SKILL.md create mode 100644 bugbug-automation/SKILL.md create mode 100644 bugherd-automation/SKILL.md create mode 100644 bugsnag-automation/SKILL.md create mode 100644 buildkite-automation/SKILL.md create mode 100644 builtwith-automation/SKILL.md create mode 100644 bunnycdn-automation/SKILL.md create mode 100644 byteforms-automation/SKILL.md create mode 100644 cabinpanda-automation/SKILL.md create mode 100644 cal-automation/SKILL.md create mode 100644 calendarhero-automation/SKILL.md create mode 100644 callerapi-automation/SKILL.md create mode 100644 callingly-automation/SKILL.md create mode 100644 callpage-automation/SKILL.md create mode 100644 campaign-cleaner-automation/SKILL.md create mode 100644 campayn-automation/SKILL.md create mode 100644 canny-automation/SKILL.md create mode 100644 canvas-automation/SKILL.md create mode 100644 capsule-crm-automation/SKILL.md create mode 100644 capsule_crm-automation/SKILL.md create mode 100644 carbone-automation/SKILL.md create mode 100644 cardly-automation/SKILL.md create mode 100644 castingwords-automation/SKILL.md create mode 100644 cats-automation/SKILL.md create mode 100644 cdr-platform-automation/SKILL.md create mode 100644 census-bureau-automation/SKILL.md create mode 100644 centralstationcrm-automation/SKILL.md create mode 100644 certifier-automation/SKILL.md create mode 100644 chaser-automation/SKILL.md create mode 100644 chatbotkit-automation/SKILL.md create mode 100644 chatfai-automation/SKILL.md create mode 100644 chatwork-automation/SKILL.md create mode 100644 chmeetings-automation/SKILL.md create mode 100644 cincopa-automation/SKILL.md create mode 100644 claid-ai-automation/SKILL.md create mode 100644 classmarker-automation/SKILL.md create mode 100644 clearout-automation/SKILL.md create mode 100644 clickmeeting-automation/SKILL.md create mode 100644 clockify-automation/SKILL.md create mode 100644 cloudcart-automation/SKILL.md create mode 100644 cloudconvert-automation/SKILL.md create mode 100644 cloudflare-api-key-automation/SKILL.md create mode 100644 cloudflare-automation/SKILL.md create mode 100644 cloudflare-browser-rendering-automation/SKILL.md create mode 100644 cloudinary-automation/SKILL.md create mode 100644 cloudlayer-automation/SKILL.md create mode 100644 cloudpress-automation/SKILL.md create mode 100644 coassemble-automation/SKILL.md create mode 100644 codacy-automation/SKILL.md create mode 100644 codeinterpreter-automation/SKILL.md create mode 100644 codereadr-automation/SKILL.md create mode 100644 coinbase-automation/SKILL.md create mode 100644 coinmarketcal-automation/SKILL.md create mode 100644 coinmarketcap-automation/SKILL.md create mode 100644 coinranking-automation/SKILL.md create mode 100644 college-football-data-automation/SKILL.md create mode 100644 composio-automation/SKILL.md create mode 100644 composio-search-automation/SKILL.md create mode 100644 connecteam-automation/SKILL.md create mode 100644 contentful-automation/SKILL.md create mode 100644 contentful-graphql-automation/SKILL.md create mode 100644 control-d-automation/SKILL.md create mode 100644 conversion-tools-automation/SKILL.md create mode 100644 convertapi-automation/SKILL.md create mode 100644 conveyor-automation/SKILL.md create mode 100644 convolo-ai-automation/SKILL.md create mode 100644 corrently-automation/SKILL.md create mode 100644 countdown-api-automation/SKILL.md create mode 100644 coupa-automation/SKILL.md create mode 100644 craftmypdf-automation/SKILL.md create mode 100644 crowdin-automation/SKILL.md create mode 100644 crustdata-automation/SKILL.md create mode 100644 cults-automation/SKILL.md create mode 100644 curated-automation/SKILL.md create mode 100644 currents-api-automation/SKILL.md create mode 100644 customerio-automation/SKILL.md create mode 100644 customgpt-automation/SKILL.md create mode 100644 customjs-automation/SKILL.md create mode 100644 cutt-ly-automation/SKILL.md create mode 100644 d2lbrightspace-automation/SKILL.md create mode 100644 dadata-ru-automation/SKILL.md create mode 100644 daffy-automation/SKILL.md create mode 100644 dailybot-automation/SKILL.md create mode 100644 datagma-automation/SKILL.md create mode 100644 datarobot-automation/SKILL.md create mode 100644 deadline-funnel-automation/SKILL.md create mode 100644 deel-automation/SKILL.md create mode 100644 deepgram-automation/SKILL.md create mode 100644 demio-automation/SKILL.md create mode 100644 desktime-automation/SKILL.md create mode 100644 detrack-automation/SKILL.md create mode 100644 dialmycalls-automation/SKILL.md create mode 100644 dialpad-automation/SKILL.md create mode 100644 dictionary-api-automation/SKILL.md create mode 100644 diffbot-automation/SKILL.md create mode 100644 digicert-automation/SKILL.md create mode 100644 digital-ocean-automation/SKILL.md create mode 100644 discordbot-automation/SKILL.md create mode 100644 dnsfilter-automation/SKILL.md create mode 100644 dock-certs-automation/SKILL.md create mode 100644 docker-hub-automation/SKILL.md create mode 100644 docker_hub-automation/SKILL.md create mode 100644 docmosis-automation/SKILL.md create mode 100644 docnify-automation/SKILL.md create mode 100644 docsbot-ai-automation/SKILL.md create mode 100644 docsumo-automation/SKILL.md create mode 100644 docugenerate-automation/SKILL.md create mode 100644 documenso-automation/SKILL.md create mode 100644 documint-automation/SKILL.md create mode 100644 docupilot-automation/SKILL.md create mode 100644 docupost-automation/SKILL.md create mode 100644 docuseal-automation/SKILL.md create mode 100644 doppler-marketing-automation-automation/SKILL.md create mode 100644 doppler-secretops-automation/SKILL.md create mode 100644 dotsimple-automation/SKILL.md create mode 100644 dovetail-automation/SKILL.md create mode 100644 dpd2-automation/SKILL.md create mode 100644 draftable-automation/SKILL.md create mode 100644 dreamstudio-automation/SKILL.md create mode 100644 drip-jobs-automation/SKILL.md create mode 100644 dripcel-automation/SKILL.md create mode 100644 dromo-automation/SKILL.md create mode 100644 dropbox-sign-automation/SKILL.md create mode 100644 dropcontact-automation/SKILL.md create mode 100644 dungeon-fighter-online-automation/SKILL.md create mode 100644 dynamics365-automation/SKILL.md create mode 100644 echtpost-automation/SKILL.md create mode 100644 elevenlabs-automation/SKILL.md create mode 100644 elorus-automation/SKILL.md create mode 100644 emailable-automation/SKILL.md create mode 100644 emaillistverify-automation/SKILL.md create mode 100644 emailoctopus-automation/SKILL.md create mode 100644 emelia-automation/SKILL.md create mode 100644 encodian-automation/SKILL.md create mode 100644 endorsal-automation/SKILL.md create mode 100644 enginemailer-automation/SKILL.md create mode 100644 enigma-automation/SKILL.md create mode 100644 entelligence-automation/SKILL.md create mode 100644 eodhd-apis-automation/SKILL.md create mode 100644 epic-games-automation/SKILL.md create mode 100644 esignatures-io-automation/SKILL.md create mode 100644 espocrm-automation/SKILL.md create mode 100644 esputnik-automation/SKILL.md create mode 100644 etermin-automation/SKILL.md create mode 100644 evenium-automation/SKILL.md create mode 100644 eventbrite-automation/SKILL.md create mode 100644 eventee-automation/SKILL.md create mode 100644 eventzilla-automation/SKILL.md create mode 100644 everhour-automation/SKILL.md create mode 100644 eversign-automation/SKILL.md create mode 100644 exa-automation/SKILL.md create mode 100644 excel-automation/SKILL.md create mode 100644 exist-automation/SKILL.md create mode 100644 expofp-automation/SKILL.md create mode 100644 extracta-ai-automation/SKILL.md create mode 100644 facebook-automation/SKILL.md create mode 100644 faceup-automation/SKILL.md create mode 100644 factorial-automation/SKILL.md create mode 100644 feathery-automation/SKILL.md create mode 100644 felt-automation/SKILL.md create mode 100644 fibery-automation/SKILL.md create mode 100644 fidel-api-automation/SKILL.md create mode 100644 files-com-automation/SKILL.md create mode 100644 fillout-forms-automation/SKILL.md create mode 100644 fillout_forms-automation/SKILL.md create mode 100644 finage-automation/SKILL.md create mode 100644 findymail-automation/SKILL.md create mode 100644 finerworks-automation/SKILL.md create mode 100644 fingertip-automation/SKILL.md create mode 100644 finmei-automation/SKILL.md create mode 100644 fireberry-automation/SKILL.md create mode 100644 firecrawl-automation/SKILL.md create mode 100644 fireflies-automation/SKILL.md create mode 100644 firmao-automation/SKILL.md create mode 100644 fitbit-automation/SKILL.md create mode 100644 fixer-automation/SKILL.md create mode 100644 fixer-io-automation/SKILL.md create mode 100644 flexisign-automation/SKILL.md create mode 100644 flowiseai-automation/SKILL.md create mode 100644 flutterwave-automation/SKILL.md create mode 100644 fluxguard-automation/SKILL.md create mode 100644 folk-automation/SKILL.md create mode 100644 fomo-automation/SKILL.md create mode 100644 forcemanager-automation/SKILL.md create mode 100644 formbricks-automation/SKILL.md create mode 100644 formcarry-automation/SKILL.md create mode 100644 formdesk-automation/SKILL.md create mode 100644 formsite-automation/SKILL.md create mode 100644 foursquare-automation/SKILL.md create mode 100644 fraudlabs-pro-automation/SKILL.md create mode 100644 freshbooks-automation/SKILL.md create mode 100644 front-automation/SKILL.md create mode 100644 fullenrich-automation/SKILL.md create mode 100644 gagelist-automation/SKILL.md create mode 100644 gamma-automation/SKILL.md create mode 100644 gan-ai-automation/SKILL.md create mode 100644 gatherup-automation/SKILL.md create mode 100644 gemini-automation/SKILL.md create mode 100644 gender-api-automation/SKILL.md create mode 100644 genderapi-io-automation/SKILL.md create mode 100644 genderize-automation/SKILL.md create mode 100644 geoapify-automation/SKILL.md create mode 100644 geocodio-automation/SKILL.md create mode 100644 geokeo-automation/SKILL.md create mode 100644 getform-automation/SKILL.md create mode 100644 gift-up-automation/SKILL.md create mode 100644 gigasheet-automation/SKILL.md create mode 100644 giphy-automation/SKILL.md create mode 100644 gist-automation/SKILL.md create mode 100644 givebutter-automation/SKILL.md create mode 100644 gladia-automation/SKILL.md create mode 100644 gleap-automation/SKILL.md create mode 100644 globalping-automation/SKILL.md create mode 100644 go-to-webinar-automation/SKILL.md create mode 100644 godial-automation/SKILL.md create mode 100644 gong-automation/SKILL.md create mode 100644 goodbits-automation/SKILL.md create mode 100644 goody-automation/SKILL.md create mode 100644 google-address-validation-automation/SKILL.md create mode 100644 google-admin-automation/SKILL.md create mode 100644 google-classroom-automation/SKILL.md create mode 100644 google-cloud-vision-automation/SKILL.md create mode 100644 google-maps-automation/SKILL.md create mode 100644 google-search-console-automation/SKILL.md create mode 100644 google_admin-automation/SKILL.md create mode 100644 google_classroom-automation/SKILL.md create mode 100644 google_maps-automation/SKILL.md create mode 100644 google_search_console-automation/SKILL.md create mode 100644 googleads-automation/SKILL.md create mode 100644 googlebigquery-automation/SKILL.md create mode 100644 googlecalendar-automation/SKILL.md create mode 100644 googledocs-automation/SKILL.md create mode 100644 googledrive-automation/SKILL.md create mode 100644 googlemeet-automation/SKILL.md create mode 100644 googlephotos-automation/SKILL.md create mode 100644 googleslides-automation/SKILL.md create mode 100644 googlesuper-automation/SKILL.md create mode 100644 googletasks-automation/SKILL.md create mode 100644 gorgias-automation/SKILL.md create mode 100644 gosquared-automation/SKILL.md create mode 100644 grafbase-automation/SKILL.md create mode 100644 graphhopper-automation/SKILL.md create mode 100644 griptape-automation/SKILL.md create mode 100644 grist-automation/SKILL.md create mode 100644 groqcloud-automation/SKILL.md create mode 100644 gumroad-automation/SKILL.md create mode 100644 habitica-automation/SKILL.md create mode 100644 hackernews-automation/SKILL.md create mode 100644 happy-scribe-automation/SKILL.md create mode 100644 harvest-automation/SKILL.md create mode 100644 hashnode-automation/SKILL.md create mode 100644 helcim-automation/SKILL.md create mode 100644 helloleads-automation/SKILL.md create mode 100644 helpwise-automation/SKILL.md create mode 100644 here-automation/SKILL.md create mode 100644 heygen-automation/SKILL.md create mode 100644 heyreach-automation/SKILL.md create mode 100644 heyzine-automation/SKILL.md create mode 100644 highergov-automation/SKILL.md create mode 100644 highlevel-automation/SKILL.md create mode 100644 honeybadger-automation/SKILL.md create mode 100644 honeyhive-automation/SKILL.md create mode 100644 hookdeck-automation/SKILL.md create mode 100644 hotspotsystem-automation/SKILL.md create mode 100644 html-to-image-automation/SKILL.md create mode 100644 humanitix-automation/SKILL.md create mode 100644 humanloop-automation/SKILL.md create mode 100644 hunter-automation/SKILL.md create mode 100644 hypeauditor-automation/SKILL.md create mode 100644 hyperbrowser-automation/SKILL.md create mode 100644 hyperise-automation/SKILL.md create mode 100644 hystruct-automation/SKILL.md create mode 100644 icims-talent-cloud-automation/SKILL.md create mode 100644 icypeas-automation/SKILL.md create mode 100644 idea-scale-automation/SKILL.md create mode 100644 identitycheck-automation/SKILL.md create mode 100644 ignisign-automation/SKILL.md create mode 100644 imagekit-io-automation/SKILL.md create mode 100644 imgbb-automation/SKILL.md create mode 100644 imgix-automation/SKILL.md create mode 100644 influxdb-cloud-automation/SKILL.md create mode 100644 insighto-ai-automation/SKILL.md create mode 100644 instacart-automation/SKILL.md create mode 100644 instantly-automation/SKILL.md create mode 100644 intelliprint-automation/SKILL.md create mode 100644 interzoid-automation/SKILL.md create mode 100644 ip2location-automation/SKILL.md create mode 100644 ip2location-io-automation/SKILL.md create mode 100644 ip2proxy-automation/SKILL.md create mode 100644 ip2whois-automation/SKILL.md create mode 100644 ipdata-co-automation/SKILL.md create mode 100644 ipinfo-io-automation/SKILL.md create mode 100644 iqair-airvisual-automation/SKILL.md create mode 100644 jigsawstack-automation/SKILL.md create mode 100644 jobnimbus-automation/SKILL.md create mode 100644 jotform-automation/SKILL.md create mode 100644 jumpcloud-automation/SKILL.md create mode 100644 junglescout-automation/SKILL.md create mode 100644 kadoa-automation/SKILL.md create mode 100644 kaggle-automation/SKILL.md create mode 100644 kaleido-automation/SKILL.md create mode 100644 keap-automation/SKILL.md create mode 100644 keen-io-automation/SKILL.md create mode 100644 kickbox-automation/SKILL.md create mode 100644 kit-automation/SKILL.md create mode 100644 klipfolio-automation/SKILL.md create mode 100644 ko-fi-automation/SKILL.md create mode 100644 kommo-automation/SKILL.md create mode 100644 kontent-ai-automation/SKILL.md create mode 100644 kraken-io-automation/SKILL.md create mode 100644 l2s-automation/SKILL.md create mode 100644 labs64-netlicensing-automation/SKILL.md create mode 100644 landbot-automation/SKILL.md create mode 100644 langbase-automation/SKILL.md create mode 100644 lastpass-automation/SKILL.md create mode 100644 launch-darkly-automation/SKILL.md create mode 100644 launch_darkly-automation/SKILL.md create mode 100644 leadfeeder-automation/SKILL.md create mode 100644 leadoku-automation/SKILL.md create mode 100644 leiga-automation/SKILL.md create mode 100644 lemlist-automation/SKILL.md create mode 100644 lemon-squeezy-automation/SKILL.md create mode 100644 lemon_squeezy-automation/SKILL.md create mode 100644 lessonspace-automation/SKILL.md create mode 100644 lever-automation/SKILL.md create mode 100644 lever-sandbox-automation/SKILL.md create mode 100644 leverly-automation/SKILL.md create mode 100644 lexoffice-automation/SKILL.md create mode 100644 linguapop-automation/SKILL.md create mode 100644 linkhut-automation/SKILL.md create mode 100644 linkup-automation/SKILL.md create mode 100644 listclean-automation/SKILL.md create mode 100644 listennotes-automation/SKILL.md create mode 100644 livesession-automation/SKILL.md create mode 100644 lmnt-automation/SKILL.md create mode 100644 lodgify-automation/SKILL.md create mode 100644 logo-dev-automation/SKILL.md create mode 100644 loomio-automation/SKILL.md create mode 100644 loyverse-automation/SKILL.md create mode 100644 magnetic-automation/SKILL.md create mode 100644 mailbluster-automation/SKILL.md create mode 100644 mailboxlayer-automation/SKILL.md create mode 100644 mailcheck-automation/SKILL.md create mode 100644 mailcoach-automation/SKILL.md create mode 100644 mailerlite-automation/SKILL.md create mode 100644 mailersend-automation/SKILL.md create mode 100644 mails-so-automation/SKILL.md create mode 100644 mailsoftly-automation/SKILL.md create mode 100644 maintainx-automation/SKILL.md create mode 100644 many-chat-automation/SKILL.md create mode 100644 many_chat-automation/SKILL.md create mode 100644 mapbox-automation/SKILL.md create mode 100644 mapulus-automation/SKILL.md create mode 100644 mboum-automation/SKILL.md create mode 100644 melo-automation/SKILL.md create mode 100644 mem-automation/SKILL.md create mode 100644 mem0-automation/SKILL.md create mode 100644 memberspot-automation/SKILL.md create mode 100644 memberstack-automation/SKILL.md create mode 100644 membervault-automation/SKILL.md create mode 100644 metaads-automation/SKILL.md create mode 100644 metaphor-automation/SKILL.md create mode 100644 mezmo-automation/SKILL.md create mode 100644 microsoft-clarity-automation/SKILL.md create mode 100644 microsoft-tenant-automation/SKILL.md create mode 100644 microsoft_clarity-automation/SKILL.md create mode 100644 minerstat-automation/SKILL.md create mode 100644 missive-automation/SKILL.md create mode 100644 mistral-ai-automation/SKILL.md create mode 100644 mistral_ai-automation/SKILL.md create mode 100644 mocean-automation/SKILL.md create mode 100644 moco-automation/SKILL.md create mode 100644 modelry-automation/SKILL.md create mode 100644 moneybird-automation/SKILL.md create mode 100644 moonclerk-automation/SKILL.md create mode 100644 moosend-automation/SKILL.md create mode 100644 mopinion-automation/SKILL.md create mode 100644 more-trees-automation/SKILL.md create mode 100644 moxie-automation/SKILL.md create mode 100644 moz-automation/SKILL.md create mode 100644 msg91-automation/SKILL.md create mode 100644 mural-automation/SKILL.md create mode 100644 mx-technologies-automation/SKILL.md create mode 100644 mx-toolbox-automation/SKILL.md create mode 100644 nango-automation/SKILL.md create mode 100644 nano-nets-automation/SKILL.md create mode 100644 nasa-automation/SKILL.md create mode 100644 nasdaq-automation/SKILL.md create mode 100644 ncscale-automation/SKILL.md create mode 100644 needle-automation/SKILL.md create mode 100644 neon-automation/SKILL.md create mode 100644 netsuite-automation/SKILL.md create mode 100644 neuronwriter-automation/SKILL.md create mode 100644 neutrino-automation/SKILL.md create mode 100644 neverbounce-automation/SKILL.md create mode 100644 new-relic-automation/SKILL.md create mode 100644 new_relic-automation/SKILL.md create mode 100644 news-api-automation/SKILL.md create mode 100644 nextdns-automation/SKILL.md create mode 100644 ngrok-automation/SKILL.md create mode 100644 ninox-automation/SKILL.md create mode 100644 nocrm-io-automation/SKILL.md create mode 100644 npm-automation/SKILL.md create mode 100644 ocr-web-service-automation/SKILL.md create mode 100644 ocrspace-automation/SKILL.md create mode 100644 omnisend-automation/SKILL.md create mode 100644 oncehub-automation/SKILL.md create mode 100644 onedesk-automation/SKILL.md create mode 100644 onepage-automation/SKILL.md create mode 100644 onesignal-rest-api-automation/SKILL.md create mode 100644 onesignal-user-auth-automation/SKILL.md create mode 100644 onesignal_rest_api-automation/SKILL.md create mode 100644 open-sea-automation/SKILL.md create mode 100644 openai-automation/SKILL.md create mode 100644 opencage-automation/SKILL.md create mode 100644 opengraph-io-automation/SKILL.md create mode 100644 openperplex-automation/SKILL.md create mode 100644 openrouter-automation/SKILL.md create mode 100644 openweather-api-automation/SKILL.md create mode 100644 optimoroute-automation/SKILL.md create mode 100644 owl-protocol-automation/SKILL.md create mode 100644 page-x-automation/SKILL.md create mode 100644 pandadoc-automation/SKILL.md create mode 100644 paradym-automation/SKILL.md create mode 100644 parallel-automation/SKILL.md create mode 100644 parma-automation/SKILL.md create mode 100644 parsehub-automation/SKILL.md create mode 100644 parsera-automation/SKILL.md create mode 100644 parseur-automation/SKILL.md create mode 100644 passcreator-automation/SKILL.md create mode 100644 passslot-automation/SKILL.md create mode 100644 payhip-automation/SKILL.md create mode 100644 pdf-api-io-automation/SKILL.md create mode 100644 pdf-co-automation/SKILL.md create mode 100644 pdf4me-automation/SKILL.md create mode 100644 pdfless-automation/SKILL.md create mode 100644 pdfmonkey-automation/SKILL.md create mode 100644 peopledatalabs-automation/SKILL.md create mode 100644 perigon-automation/SKILL.md create mode 100644 perplexityai-automation/SKILL.md create mode 100644 persistiq-automation/SKILL.md create mode 100644 pexels-automation/SKILL.md create mode 100644 phantombuster-automation/SKILL.md create mode 100644 piggy-automation/SKILL.md create mode 100644 piloterr-automation/SKILL.md create mode 100644 pilvio-automation/SKILL.md create mode 100644 pingdom-automation/SKILL.md create mode 100644 pipeline-crm-automation/SKILL.md create mode 100644 placekey-automation/SKILL.md create mode 100644 placid-automation/SKILL.md create mode 100644 plain-automation/SKILL.md create mode 100644 plasmic-automation/SKILL.md create mode 100644 platerecognizer-automation/SKILL.md create mode 100644 plisio-automation/SKILL.md create mode 100644 polygon-automation/SKILL.md create mode 100644 polygon-io-automation/SKILL.md create mode 100644 poptin-automation/SKILL.md create mode 100644 postgrid-automation/SKILL.md create mode 100644 postgrid-verify-automation/SKILL.md create mode 100644 precoro-automation/SKILL.md create mode 100644 prerender-automation/SKILL.md create mode 100644 printautopilot-automation/SKILL.md create mode 100644 prisma-automation/SKILL.md create mode 100644 prismic-automation/SKILL.md create mode 100644 process-street-automation/SKILL.md create mode 100644 procfu-automation/SKILL.md create mode 100644 productboard-automation/SKILL.md create mode 100644 productlane-automation/SKILL.md create mode 100644 project-bubble-automation/SKILL.md create mode 100644 proofly-automation/SKILL.md create mode 100644 proxiedmail-automation/SKILL.md create mode 100644 pushbullet-automation/SKILL.md create mode 100644 pushover-automation/SKILL.md create mode 100644 quaderno-automation/SKILL.md create mode 100644 qualaroo-automation/SKILL.md create mode 100644 quickbooks-automation/SKILL.md create mode 100644 radar-automation/SKILL.md create mode 100644 rafflys-automation/SKILL.md create mode 100644 ragic-automation/SKILL.md create mode 100644 raisely-automation/SKILL.md create mode 100644 ramp-automation/SKILL.md create mode 100644 ravenseotools-automation/SKILL.md create mode 100644 re-amaze-automation/SKILL.md create mode 100644 realphonevalidation-automation/SKILL.md create mode 100644 recallai-automation/SKILL.md create mode 100644 recruitee-automation/SKILL.md create mode 100644 refiner-automation/SKILL.md create mode 100644 remarkety-automation/SKILL.md create mode 100644 remote-retrieval-automation/SKILL.md create mode 100644 remove-bg-automation/SKILL.md create mode 100644 renderform-automation/SKILL.md create mode 100644 repairshopr-automation/SKILL.md create mode 100644 replicate-automation/SKILL.md create mode 100644 reply-automation/SKILL.md create mode 100644 reply-io-automation/SKILL.md create mode 100644 resend-automation/SKILL.md create mode 100644 respond-io-automation/SKILL.md create mode 100644 retailed-automation/SKILL.md create mode 100644 retellai-automation/SKILL.md create mode 100644 retently-automation/SKILL.md create mode 100644 rev-ai-automation/SKILL.md create mode 100644 revolt-automation/SKILL.md create mode 100644 ring-central-automation/SKILL.md create mode 100644 ring_central-automation/SKILL.md create mode 100644 rippling-automation/SKILL.md create mode 100644 ritekit-automation/SKILL.md create mode 100644 rkvst-automation/SKILL.md create mode 100644 rocketlane-automation/SKILL.md create mode 100644 rootly-automation/SKILL.md create mode 100644 rosette-text-analytics-automation/SKILL.md create mode 100644 route4me-automation/SKILL.md create mode 100644 safetyculture-automation/SKILL.md create mode 100644 sage-automation/SKILL.md create mode 100644 salesforce-marketing-cloud-automation/SKILL.md create mode 100644 salesforce-service-cloud-automation/SKILL.md create mode 100644 salesmate-automation/SKILL.md create mode 100644 sap-successfactors-automation/SKILL.md create mode 100644 satismeter-automation/SKILL.md create mode 100644 scrape-do-automation/SKILL.md create mode 100644 scrapegraph-ai-automation/SKILL.md create mode 100644 scrapfly-automation/SKILL.md create mode 100644 scrapingant-automation/SKILL.md create mode 100644 scrapingbee-automation/SKILL.md create mode 100644 screenshot-fyi-automation/SKILL.md create mode 100644 screenshotone-automation/SKILL.md create mode 100644 seat-geek-automation/SKILL.md create mode 100644 securitytrails-automation/SKILL.md create mode 100644 segmetrics-automation/SKILL.md create mode 100644 seismic-automation/SKILL.md create mode 100644 semanticscholar-automation/SKILL.md create mode 100644 semrush-automation/SKILL.md create mode 100644 sendbird-ai-chabot-automation/SKILL.md create mode 100644 sendbird-automation/SKILL.md create mode 100644 sendfox-automation/SKILL.md create mode 100644 sendlane-automation/SKILL.md create mode 100644 sendloop-automation/SKILL.md create mode 100644 sendspark-automation/SKILL.md create mode 100644 sensibo-automation/SKILL.md create mode 100644 seqera-automation/SKILL.md create mode 100644 serpapi-automation/SKILL.md create mode 100644 serpdog-automation/SKILL.md create mode 100644 serply-automation/SKILL.md create mode 100644 servicem8-automation/SKILL.md create mode 100644 sevdesk-automation/SKILL.md create mode 100644 share-point-automation/SKILL.md create mode 100644 share_point-automation/SKILL.md create mode 100644 shipengine-automation/SKILL.md create mode 100644 short-io-automation/SKILL.md create mode 100644 short-menu-automation/SKILL.md create mode 100644 shortcut-automation/SKILL.md create mode 100644 shorten-rest-automation/SKILL.md create mode 100644 shortpixel-automation/SKILL.md create mode 100644 shotstack-automation/SKILL.md create mode 100644 sidetracker-automation/SKILL.md create mode 100644 signaturely-automation/SKILL.md create mode 100644 signpath-automation/SKILL.md create mode 100644 signwell-automation/SKILL.md create mode 100644 similarweb-digitalrank-api-automation/SKILL.md create mode 100644 similarweb_digitalrank_api-automation/SKILL.md create mode 100644 simla-com-automation/SKILL.md create mode 100644 simple-analytics-automation/SKILL.md create mode 100644 simplesat-automation/SKILL.md create mode 100644 sitespeakai-automation/SKILL.md create mode 100644 skyfire-automation/SKILL.md create mode 100644 slackbot-automation/SKILL.md create mode 100644 smartproxy-automation/SKILL.md create mode 100644 smartrecruiters-automation/SKILL.md create mode 100644 sms-alert-automation/SKILL.md create mode 100644 smtp2go-automation/SKILL.md create mode 100644 smugmug-automation/SKILL.md create mode 100644 snowflake-automation/SKILL.md create mode 100644 sourcegraph-automation/SKILL.md create mode 100644 splitwise-automation/SKILL.md create mode 100644 spoki-automation/SKILL.md create mode 100644 spondyr-automation/SKILL.md create mode 100644 spotify-automation/SKILL.md create mode 100644 spotlightr-automation/SKILL.md create mode 100644 sslmate-cert-spotter-api-automation/SKILL.md create mode 100644 stack-exchange-automation/SKILL.md create mode 100644 stannp-automation/SKILL.md create mode 100644 starton-automation/SKILL.md create mode 100644 statuscake-automation/SKILL.md create mode 100644 storeganise-automation/SKILL.md create mode 100644 storerocket-automation/SKILL.md create mode 100644 stormglass-io-automation/SKILL.md create mode 100644 strava-automation/SKILL.md create mode 100644 streamtime-automation/SKILL.md create mode 100644 supadata-automation/SKILL.md create mode 100644 superchat-automation/SKILL.md create mode 100644 supportbee-automation/SKILL.md create mode 100644 supportivekoala-automation/SKILL.md create mode 100644 survey-monkey-automation/SKILL.md create mode 100644 survey_monkey-automation/SKILL.md create mode 100644 svix-automation/SKILL.md create mode 100644 sympla-automation/SKILL.md create mode 100644 synthflow-ai-automation/SKILL.md create mode 100644 taggun-automation/SKILL.md create mode 100644 talenthr-automation/SKILL.md create mode 100644 tally-automation/SKILL.md create mode 100644 tapfiliate-automation/SKILL.md create mode 100644 tapform-automation/SKILL.md create mode 100644 tavily-automation/SKILL.md create mode 100644 taxjar-automation/SKILL.md create mode 100644 teamcamp-automation/SKILL.md create mode 100644 telnyx-automation/SKILL.md create mode 100644 teltel-automation/SKILL.md create mode 100644 templated-automation/SKILL.md create mode 100644 test-app-automation/SKILL.md create mode 100644 text-to-pdf-automation/SKILL.md create mode 100644 textcortex-automation/SKILL.md create mode 100644 textit-automation/SKILL.md create mode 100644 textrazor-automation/SKILL.md create mode 100644 thanks-io-automation/SKILL.md create mode 100644 the-odds-api-automation/SKILL.md create mode 100644 ticketmaster-automation/SKILL.md create mode 100644 ticktick-automation/SKILL.md create mode 100644 timecamp-automation/SKILL.md create mode 100644 timekit-automation/SKILL.md create mode 100644 timelinesai-automation/SKILL.md create mode 100644 timelink-automation/SKILL.md create mode 100644 timely-automation/SKILL.md create mode 100644 tinyurl-automation/SKILL.md create mode 100644 tisane-automation/SKILL.md create mode 100644 toggl-automation/SKILL.md create mode 100644 token-metrics-automation/SKILL.md create mode 100644 tomba-automation/SKILL.md create mode 100644 tomtom-automation/SKILL.md create mode 100644 toneden-automation/SKILL.md create mode 100644 tpscheck-automation/SKILL.md create mode 100644 triggercmd-automation/SKILL.md create mode 100644 tripadvisor-content-api-automation/SKILL.md create mode 100644 turbot-pipes-automation/SKILL.md create mode 100644 turso-automation/SKILL.md create mode 100644 twelve-data-automation/SKILL.md create mode 100644 twitch-automation/SKILL.md create mode 100644 twocaptcha-automation/SKILL.md create mode 100644 typefully-automation/SKILL.md create mode 100644 typless-automation/SKILL.md create mode 100644 u301-automation/SKILL.md create mode 100644 unione-automation/SKILL.md create mode 100644 updown-io-automation/SKILL.md create mode 100644 uploadcare-automation/SKILL.md create mode 100644 uptimerobot-automation/SKILL.md create mode 100644 userlist-automation/SKILL.md create mode 100644 v0-automation/SKILL.md create mode 100644 venly-automation/SKILL.md create mode 100644 veo-automation/SKILL.md create mode 100644 verifiedemail-automation/SKILL.md create mode 100644 veriphone-automation/SKILL.md create mode 100644 vero-automation/SKILL.md create mode 100644 vestaboard-automation/SKILL.md create mode 100644 virustotal-automation/SKILL.md create mode 100644 visme-automation/SKILL.md create mode 100644 waboxapp-automation/SKILL.md create mode 100644 wachete-automation/SKILL.md create mode 100644 waiverfile-automation/SKILL.md create mode 100644 wakatime-automation/SKILL.md create mode 100644 wati-automation/SKILL.md create mode 100644 wave-accounting-automation/SKILL.md create mode 100644 wave_accounting-automation/SKILL.md create mode 100644 weathermap-automation/SKILL.md create mode 100644 webex-automation/SKILL.md create mode 100644 webscraping-ai-automation/SKILL.md create mode 100644 webvizio-automation/SKILL.md create mode 100644 whautomate-automation/SKILL.md create mode 100644 winston-ai-automation/SKILL.md create mode 100644 wit-ai-automation/SKILL.md create mode 100644 wiz-automation/SKILL.md create mode 100644 wolfram-alpha-api-automation/SKILL.md create mode 100644 woodpecker-co-automation/SKILL.md create mode 100644 workable-automation/SKILL.md create mode 100644 workday-automation/SKILL.md create mode 100644 workiom-automation/SKILL.md create mode 100644 worksnaps-automation/SKILL.md create mode 100644 writer-automation/SKILL.md create mode 100644 xero-automation/SKILL.md create mode 100644 y-gy-automation/SKILL.md create mode 100644 yandex-automation/SKILL.md create mode 100644 yelp-automation/SKILL.md create mode 100644 ynab-automation/SKILL.md create mode 100644 yousearch-automation/SKILL.md create mode 100644 zenrows-automation/SKILL.md create mode 100644 zenserp-automation/SKILL.md create mode 100644 zeplin-automation/SKILL.md create mode 100644 zerobounce-automation/SKILL.md create mode 100644 zoho-automation/SKILL.md create mode 100644 zoho-bigin-automation/SKILL.md create mode 100644 zoho-books-automation/SKILL.md create mode 100644 zoho-desk-automation/SKILL.md create mode 100644 zoho-inventory-automation/SKILL.md create mode 100644 zoho-invoice-automation/SKILL.md create mode 100644 zoho-mail-automation/SKILL.md create mode 100644 zoho_bigin-automation/SKILL.md create mode 100644 zoho_books-automation/SKILL.md create mode 100644 zoho_desk-automation/SKILL.md create mode 100644 zoho_inventory-automation/SKILL.md create mode 100644 zoho_invoice-automation/SKILL.md create mode 100644 zoho_mail-automation/SKILL.md create mode 100644 zoominfo-automation/SKILL.md create mode 100644 zylvie-automation/SKILL.md create mode 100644 zyte-api-automation/SKILL.md diff --git a/-21risk-automation/SKILL.md b/-21risk-automation/SKILL.md new file mode 100644 index 0000000..7a7a784 --- /dev/null +++ b/-21risk-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: -21risk-automation +description: "Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# 21risk Automation via Rube MCP + +Automate 21risk operations through Composio's 21risk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/_21risk](https://composio.dev/toolkits/_21risk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active 21risk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `_21risk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `_21risk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "21risk operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific 21risk task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["_21risk"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with 21risk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `_21risk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/-2chat-automation/SKILL.md b/-2chat-automation/SKILL.md new file mode 100644 index 0000000..a390d0a --- /dev/null +++ b/-2chat-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: -2chat-automation +description: "Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# 2chat Automation via Rube MCP + +Automate 2chat operations through Composio's 2chat toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/_2chat](https://composio.dev/toolkits/_2chat) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active 2chat connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `_2chat` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `_2chat` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "2chat operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific 2chat task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["_2chat"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with 2chat-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `_2chat` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ably-automation/SKILL.md b/ably-automation/SKILL.md new file mode 100644 index 0000000..4bb303e --- /dev/null +++ b/ably-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ably-automation +description: "Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ably Automation via Rube MCP + +Automate Ably operations through Composio's Ably toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ably](https://composio.dev/toolkits/ably) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ably connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ably` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ably` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ably operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ably task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ably"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ably-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ably` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/abstract-automation/SKILL.md b/abstract-automation/SKILL.md new file mode 100644 index 0000000..a816a76 --- /dev/null +++ b/abstract-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: abstract-automation +description: "Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Abstract Automation via Rube MCP + +Automate Abstract operations through Composio's Abstract toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/abstract](https://composio.dev/toolkits/abstract) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Abstract connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `abstract` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `abstract` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Abstract operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Abstract task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["abstract"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Abstract-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `abstract` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/abuselpdb-automation/SKILL.md b/abuselpdb-automation/SKILL.md new file mode 100644 index 0000000..00bd03f --- /dev/null +++ b/abuselpdb-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: abuselpdb-automation +description: "Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Abuselpdb Automation via Rube MCP + +Automate Abuselpdb operations through Composio's Abuselpdb toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/abuselpdb](https://composio.dev/toolkits/abuselpdb) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Abuselpdb connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `abuselpdb` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `abuselpdb` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Abuselpdb operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Abuselpdb task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["abuselpdb"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Abuselpdb-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `abuselpdb` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/abyssale-automation/SKILL.md b/abyssale-automation/SKILL.md new file mode 100644 index 0000000..0f18791 --- /dev/null +++ b/abyssale-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: abyssale-automation +description: "Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Abyssale Automation via Rube MCP + +Automate Abyssale operations through Composio's Abyssale toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/abyssale](https://composio.dev/toolkits/abyssale) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Abyssale connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `abyssale` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `abyssale` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Abyssale operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Abyssale task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["abyssale"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Abyssale-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `abyssale` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/accelo-automation/SKILL.md b/accelo-automation/SKILL.md new file mode 100644 index 0000000..5252a20 --- /dev/null +++ b/accelo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: accelo-automation +description: "Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Accelo Automation via Rube MCP + +Automate Accelo operations through Composio's Accelo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/accelo](https://composio.dev/toolkits/accelo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Accelo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `accelo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `accelo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Accelo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Accelo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["accelo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Accelo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `accelo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/accredible-certificates-automation/SKILL.md b/accredible-certificates-automation/SKILL.md new file mode 100644 index 0000000..ff5e3ad --- /dev/null +++ b/accredible-certificates-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: accredible-certificates-automation +description: "Automate Accredible Certificates tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Accredible Certificates Automation via Rube MCP + +Automate Accredible Certificates operations through Composio's Accredible Certificates toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/accredible_certificates](https://composio.dev/toolkits/accredible_certificates) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Accredible Certificates connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `accredible_certificates` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `accredible_certificates` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Accredible Certificates operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Accredible Certificates task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["accredible_certificates"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Accredible Certificates-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `accredible_certificates` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/acculynx-automation/SKILL.md b/acculynx-automation/SKILL.md new file mode 100644 index 0000000..aaf8071 --- /dev/null +++ b/acculynx-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: acculynx-automation +description: "Automate Acculynx tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Acculynx Automation via Rube MCP + +Automate Acculynx operations through Composio's Acculynx toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/acculynx](https://composio.dev/toolkits/acculynx) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Acculynx connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `acculynx` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `acculynx` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Acculynx operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Acculynx task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["acculynx"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Acculynx-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `acculynx` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/active-campaign-automation/SKILL.md b/active-campaign-automation/SKILL.md new file mode 100644 index 0000000..427dece --- /dev/null +++ b/active-campaign-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: active-campaign-automation +description: "Automate ActiveCampaign tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# ActiveCampaign Automation via Rube MCP + +Automate ActiveCampaign operations through Composio's ActiveCampaign toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/active_campaign](https://composio.dev/toolkits/active_campaign) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active ActiveCampaign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `active_campaign` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `active_campaign` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "ActiveCampaign operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific ActiveCampaign task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["active_campaign"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with ActiveCampaign-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `active_campaign` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/activecampaign-automation/SKILL.md b/activecampaign-automation/SKILL.md index f618bc0..60d8120 100644 --- a/activecampaign-automation/SKILL.md +++ b/activecampaign-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate ActiveCampaign CRM and marketing automation operations through Composio's ActiveCampaign toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/active_campaign](https://composio.dev/toolkits/active_campaign) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -207,3 +209,6 @@ Automate ActiveCampaign CRM and marketing automation operations through Composio | Subscribe/unsubscribe | ACTIVE_CAMPAIGN_MANAGE_LIST_SUBSCRIPTION | action, list_id, email | | Add to automation | ACTIVE_CAMPAIGN_ADD_CONTACT_TO_AUTOMATION | contact_email, automation_id | | Create task | ACTIVE_CAMPAIGN_CREATE_CONTACT_TASK | relid, duedate, dealTasktype, title | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/addresszen-automation/SKILL.md b/addresszen-automation/SKILL.md new file mode 100644 index 0000000..7772925 --- /dev/null +++ b/addresszen-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: addresszen-automation +description: "Automate Addresszen tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Addresszen Automation via Rube MCP + +Automate Addresszen operations through Composio's Addresszen toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/addresszen](https://composio.dev/toolkits/addresszen) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Addresszen connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `addresszen` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `addresszen` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Addresszen operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Addresszen task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["addresszen"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Addresszen-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `addresszen` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/adobe-automation/SKILL.md b/adobe-automation/SKILL.md new file mode 100644 index 0000000..e4dad77 --- /dev/null +++ b/adobe-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: adobe-automation +description: "Automate Adobe tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Adobe Automation via Rube MCP + +Automate Adobe operations through Composio's Adobe toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/adobe](https://composio.dev/toolkits/adobe) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Adobe connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `adobe` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `adobe` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Adobe operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Adobe task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["adobe"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Adobe-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `adobe` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/adrapid-automation/SKILL.md b/adrapid-automation/SKILL.md new file mode 100644 index 0000000..a509990 --- /dev/null +++ b/adrapid-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: adrapid-automation +description: "Automate Adrapid tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Adrapid Automation via Rube MCP + +Automate Adrapid operations through Composio's Adrapid toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/adrapid](https://composio.dev/toolkits/adrapid) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Adrapid connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `adrapid` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `adrapid` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Adrapid operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Adrapid task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["adrapid"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Adrapid-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `adrapid` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/adyntel-automation/SKILL.md b/adyntel-automation/SKILL.md new file mode 100644 index 0000000..19a3585 --- /dev/null +++ b/adyntel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: adyntel-automation +description: "Automate Adyntel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Adyntel Automation via Rube MCP + +Automate Adyntel operations through Composio's Adyntel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/adyntel](https://composio.dev/toolkits/adyntel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Adyntel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Adyntel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Adyntel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["adyntel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Adyntel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/aero-workflow-automation/SKILL.md b/aero-workflow-automation/SKILL.md new file mode 100644 index 0000000..45292fd --- /dev/null +++ b/aero-workflow-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: aero-workflow-automation +description: "Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Aero Workflow Automation via Rube MCP + +Automate Aero Workflow operations through Composio's Aero Workflow toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/aero_workflow](https://composio.dev/toolkits/aero_workflow) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Aero Workflow connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `aero_workflow` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `aero_workflow` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Aero Workflow operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Aero Workflow task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["aero_workflow"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Aero Workflow-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `aero_workflow` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/aeroleads-automation/SKILL.md b/aeroleads-automation/SKILL.md new file mode 100644 index 0000000..be1792a --- /dev/null +++ b/aeroleads-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: aeroleads-automation +description: "Automate Aeroleads tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Aeroleads Automation via Rube MCP + +Automate Aeroleads operations through Composio's Aeroleads toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/aeroleads](https://composio.dev/toolkits/aeroleads) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Aeroleads connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `aeroleads` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `aeroleads` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Aeroleads operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Aeroleads task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["aeroleads"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Aeroleads-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `aeroleads` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/affinda-automation/SKILL.md b/affinda-automation/SKILL.md new file mode 100644 index 0000000..cbc7349 --- /dev/null +++ b/affinda-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: affinda-automation +description: "Automate Affinda tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Affinda Automation via Rube MCP + +Automate Affinda operations through Composio's Affinda toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/affinda](https://composio.dev/toolkits/affinda) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Affinda connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `affinda` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `affinda` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Affinda operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Affinda task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["affinda"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Affinda-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `affinda` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/affinity-automation/SKILL.md b/affinity-automation/SKILL.md new file mode 100644 index 0000000..f043530 --- /dev/null +++ b/affinity-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: affinity-automation +description: "Automate Affinity tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Affinity Automation via Rube MCP + +Automate Affinity operations through Composio's Affinity toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/affinity](https://composio.dev/toolkits/affinity) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Affinity connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `affinity` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `affinity` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Affinity operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Affinity task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["affinity"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Affinity-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `affinity` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/agencyzoom-automation/SKILL.md b/agencyzoom-automation/SKILL.md new file mode 100644 index 0000000..0e25772 --- /dev/null +++ b/agencyzoom-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: agencyzoom-automation +description: "Automate Agencyzoom tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Agencyzoom Automation via Rube MCP + +Automate Agencyzoom operations through Composio's Agencyzoom toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/agencyzoom](https://composio.dev/toolkits/agencyzoom) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Agencyzoom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `agencyzoom` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `agencyzoom` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Agencyzoom operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Agencyzoom task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["agencyzoom"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Agencyzoom-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `agencyzoom` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/agent-mail-automation/SKILL.md b/agent-mail-automation/SKILL.md new file mode 100644 index 0000000..6236ffb --- /dev/null +++ b/agent-mail-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: agent-mail-automation +description: "Automate Agent Mail tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Agent Mail Automation via Rube MCP + +Automate Agent Mail operations through Composio's Agent Mail toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/agent_mail](https://composio.dev/toolkits/agent_mail) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Agent Mail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `agent_mail` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `agent_mail` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Agent Mail operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Agent Mail task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["agent_mail"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Agent Mail-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `agent_mail` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/agentql-automation/SKILL.md b/agentql-automation/SKILL.md new file mode 100644 index 0000000..94dfa47 --- /dev/null +++ b/agentql-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: agentql-automation +description: "Automate Agentql tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Agentql Automation via Rube MCP + +Automate Agentql operations through Composio's Agentql toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/agentql](https://composio.dev/toolkits/agentql) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Agentql connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `agentql` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `agentql` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Agentql operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Agentql task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["agentql"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Agentql-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `agentql` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/agenty-automation/SKILL.md b/agenty-automation/SKILL.md new file mode 100644 index 0000000..8779fa9 --- /dev/null +++ b/agenty-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: agenty-automation +description: "Automate Agenty tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Agenty Automation via Rube MCP + +Automate Agenty operations through Composio's Agenty toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/agenty](https://composio.dev/toolkits/agenty) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Agenty connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `agenty` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `agenty` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Agenty operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Agenty task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["agenty"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Agenty-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `agenty` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/agiled-automation/SKILL.md b/agiled-automation/SKILL.md new file mode 100644 index 0000000..b10aa91 --- /dev/null +++ b/agiled-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: agiled-automation +description: "Automate Agiled tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Agiled Automation via Rube MCP + +Automate Agiled operations through Composio's Agiled toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/agiled](https://composio.dev/toolkits/agiled) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Agiled connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `agiled` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `agiled` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Agiled operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Agiled task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["agiled"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Agiled-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `agiled` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/agility-cms-automation/SKILL.md b/agility-cms-automation/SKILL.md new file mode 100644 index 0000000..77b5ba3 --- /dev/null +++ b/agility-cms-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: agility-cms-automation +description: "Automate Agility CMS tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Agility CMS Automation via Rube MCP + +Automate Agility CMS operations through Composio's Agility CMS toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/agility_cms](https://composio.dev/toolkits/agility_cms) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Agility CMS connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `agility_cms` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `agility_cms` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Agility CMS operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Agility CMS task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["agility_cms"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Agility CMS-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `agility_cms` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ahrefs-automation/SKILL.md b/ahrefs-automation/SKILL.md new file mode 100644 index 0000000..be716fd --- /dev/null +++ b/ahrefs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ahrefs-automation +description: "Automate Ahrefs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ahrefs Automation via Rube MCP + +Automate Ahrefs operations through Composio's Ahrefs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ahrefs](https://composio.dev/toolkits/ahrefs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ahrefs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ahrefs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ahrefs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ahrefs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ahrefs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ahrefs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ahrefs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ahrefs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ai-ml-api-automation/SKILL.md b/ai-ml-api-automation/SKILL.md new file mode 100644 index 0000000..2ccf6e5 --- /dev/null +++ b/ai-ml-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ai-ml-api-automation +description: "Automate AI ML API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# AI ML API Automation via Rube MCP + +Automate AI ML API operations through Composio's AI ML API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ai_ml_api](https://composio.dev/toolkits/ai_ml_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active AI ML API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ai_ml_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ai_ml_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "AI ML API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific AI ML API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ai_ml_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with AI ML API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ai_ml_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/airtable-automation/SKILL.md b/airtable-automation/SKILL.md index 1a39963..962f534 100644 --- a/airtable-automation/SKILL.md +++ b/airtable-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Airtable operations through Composio's Airtable toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/airtable](https://composio.dev/toolkits/airtable) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -168,3 +170,6 @@ Automate Airtable operations through Composio's Airtable toolkit via Rube MCP. | Update field | AIRTABLE_UPDATE_FIELD | baseId, tableIdOrName, fieldId | | Update table | AIRTABLE_UPDATE_TABLE | baseId, tableIdOrName, name | | List comments | AIRTABLE_LIST_COMMENTS | baseId, tableIdOrName, recordId | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/aivoov-automation/SKILL.md b/aivoov-automation/SKILL.md new file mode 100644 index 0000000..595479a --- /dev/null +++ b/aivoov-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: aivoov-automation +description: "Automate Aivoov tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Aivoov Automation via Rube MCP + +Automate Aivoov operations through Composio's Aivoov toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/aivoov](https://composio.dev/toolkits/aivoov) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Aivoov connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `aivoov` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `aivoov` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Aivoov operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Aivoov task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["aivoov"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Aivoov-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `aivoov` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/alchemy-automation/SKILL.md b/alchemy-automation/SKILL.md new file mode 100644 index 0000000..dfc0fee --- /dev/null +++ b/alchemy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: alchemy-automation +description: "Automate Alchemy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Alchemy Automation via Rube MCP + +Automate Alchemy operations through Composio's Alchemy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/alchemy](https://composio.dev/toolkits/alchemy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Alchemy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `alchemy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `alchemy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Alchemy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Alchemy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["alchemy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Alchemy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `alchemy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/algodocs-automation/SKILL.md b/algodocs-automation/SKILL.md new file mode 100644 index 0000000..24f6144 --- /dev/null +++ b/algodocs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: algodocs-automation +description: "Automate Algodocs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Algodocs Automation via Rube MCP + +Automate Algodocs operations through Composio's Algodocs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/algodocs](https://composio.dev/toolkits/algodocs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Algodocs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `algodocs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `algodocs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Algodocs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Algodocs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["algodocs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Algodocs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `algodocs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/algolia-automation/SKILL.md b/algolia-automation/SKILL.md new file mode 100644 index 0000000..da6db45 --- /dev/null +++ b/algolia-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: algolia-automation +description: "Automate Algolia tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Algolia Automation via Rube MCP + +Automate Algolia operations through Composio's Algolia toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/algolia](https://composio.dev/toolkits/algolia) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Algolia connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `algolia` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `algolia` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Algolia operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Algolia task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["algolia"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Algolia-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `algolia` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/all-images-ai-automation/SKILL.md b/all-images-ai-automation/SKILL.md new file mode 100644 index 0000000..a0a1a40 --- /dev/null +++ b/all-images-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: all-images-ai-automation +description: "Automate All Images AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# All Images AI Automation via Rube MCP + +Automate All Images AI operations through Composio's All Images AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/all_images_ai](https://composio.dev/toolkits/all_images_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active All Images AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `all_images_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `all_images_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "All Images AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific All Images AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["all_images_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with All Images AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `all_images_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/alpha-vantage-automation/SKILL.md b/alpha-vantage-automation/SKILL.md new file mode 100644 index 0000000..77f34bd --- /dev/null +++ b/alpha-vantage-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: alpha-vantage-automation +description: "Automate Alpha Vantage tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Alpha Vantage Automation via Rube MCP + +Automate Alpha Vantage operations through Composio's Alpha Vantage toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/alpha_vantage](https://composio.dev/toolkits/alpha_vantage) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Alpha Vantage connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `alpha_vantage` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `alpha_vantage` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Alpha Vantage operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Alpha Vantage task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["alpha_vantage"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Alpha Vantage-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `alpha_vantage` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/altoviz-automation/SKILL.md b/altoviz-automation/SKILL.md new file mode 100644 index 0000000..e79a144 --- /dev/null +++ b/altoviz-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: altoviz-automation +description: "Automate Altoviz tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Altoviz Automation via Rube MCP + +Automate Altoviz operations through Composio's Altoviz toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/altoviz](https://composio.dev/toolkits/altoviz) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Altoviz connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `altoviz` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `altoviz` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Altoviz operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Altoviz task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["altoviz"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Altoviz-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `altoviz` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/alttext-ai-automation/SKILL.md b/alttext-ai-automation/SKILL.md new file mode 100644 index 0000000..8d17105 --- /dev/null +++ b/alttext-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: alttext-ai-automation +description: "Automate Alttext AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Alttext AI Automation via Rube MCP + +Automate Alttext AI operations through Composio's Alttext AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/alttext_ai](https://composio.dev/toolkits/alttext_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Alttext AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `alttext_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `alttext_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Alttext AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Alttext AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["alttext_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Alttext AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `alttext_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/amara-automation/SKILL.md b/amara-automation/SKILL.md new file mode 100644 index 0000000..8f47bfe --- /dev/null +++ b/amara-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: amara-automation +description: "Automate Amara tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Amara Automation via Rube MCP + +Automate Amara operations through Composio's Amara toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/amara](https://composio.dev/toolkits/amara) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Amara connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amara` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `amara` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Amara operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Amara task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["amara"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Amara-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `amara` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/amazon-automation/SKILL.md b/amazon-automation/SKILL.md new file mode 100644 index 0000000..06de21f --- /dev/null +++ b/amazon-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: amazon-automation +description: "Automate Amazon tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Amazon Automation via Rube MCP + +Automate Amazon operations through Composio's Amazon toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/amazon](https://composio.dev/toolkits/amazon) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Amazon connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amazon` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `amazon` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Amazon operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Amazon task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["amazon"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Amazon-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `amazon` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ambee-automation/SKILL.md b/ambee-automation/SKILL.md new file mode 100644 index 0000000..f913081 --- /dev/null +++ b/ambee-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ambee-automation +description: "Automate Ambee tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ambee Automation via Rube MCP + +Automate Ambee operations through Composio's Ambee toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ambee](https://composio.dev/toolkits/ambee) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ambee connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ambee` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ambee` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ambee operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ambee task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ambee"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ambee-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ambee` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ambient-weather-automation/SKILL.md b/ambient-weather-automation/SKILL.md new file mode 100644 index 0000000..e2bc525 --- /dev/null +++ b/ambient-weather-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ambient-weather-automation +description: "Automate Ambient Weather tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ambient Weather Automation via Rube MCP + +Automate Ambient Weather operations through Composio's Ambient Weather toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ambient_weather](https://composio.dev/toolkits/ambient_weather) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ambient Weather connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ambient_weather` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ambient_weather` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ambient Weather operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ambient Weather task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ambient_weather"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ambient Weather-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ambient_weather` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/amcards-automation/SKILL.md b/amcards-automation/SKILL.md new file mode 100644 index 0000000..0938670 --- /dev/null +++ b/amcards-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: amcards-automation +description: "Automate Amcards tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Amcards Automation via Rube MCP + +Automate Amcards operations through Composio's Amcards toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/amcards](https://composio.dev/toolkits/amcards) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Amcards connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amcards` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `amcards` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Amcards operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Amcards task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["amcards"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Amcards-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `amcards` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/amplitude-automation/SKILL.md b/amplitude-automation/SKILL.md index c9b23c0..633e1c1 100644 --- a/amplitude-automation/SKILL.md +++ b/amplitude-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/amplitude](https://composio.dev/toolkits/amplitude) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -214,3 +216,6 @@ For cohort membership updates: | Update cohort members | AMPLITUDE_UPDATE_COHORT_MEMBERSHIP | cohort_id, memberships | | Check cohort status | AMPLITUDE_CHECK_COHORT_STATUS | request_id | | List event categories | AMPLITUDE_GET_EVENT_CATEGORIES | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/anchor-browser-automation/SKILL.md b/anchor-browser-automation/SKILL.md new file mode 100644 index 0000000..46b9620 --- /dev/null +++ b/anchor-browser-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: anchor-browser-automation +description: "Automate Anchor Browser tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Anchor Browser Automation via Rube MCP + +Automate Anchor Browser operations through Composio's Anchor Browser toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/anchor_browser](https://composio.dev/toolkits/anchor_browser) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Anchor Browser connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `anchor_browser` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `anchor_browser` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Anchor Browser operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Anchor Browser task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["anchor_browser"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Anchor Browser-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `anchor_browser` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/anonyflow-automation/SKILL.md b/anonyflow-automation/SKILL.md new file mode 100644 index 0000000..9a36d49 --- /dev/null +++ b/anonyflow-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: anonyflow-automation +description: "Automate Anonyflow tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Anonyflow Automation via Rube MCP + +Automate Anonyflow operations through Composio's Anonyflow toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/anonyflow](https://composio.dev/toolkits/anonyflow) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Anonyflow connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `anonyflow` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `anonyflow` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Anonyflow operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Anonyflow task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["anonyflow"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Anonyflow-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `anonyflow` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/anthropic-administrator-automation/SKILL.md b/anthropic-administrator-automation/SKILL.md new file mode 100644 index 0000000..0d48243 --- /dev/null +++ b/anthropic-administrator-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: anthropic-administrator-automation +description: "Automate Anthropic Admin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Anthropic Admin Automation via Rube MCP + +Automate Anthropic Admin operations through Composio's Anthropic Admin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/anthropic_administrator](https://composio.dev/toolkits/anthropic_administrator) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Anthropic Admin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `anthropic_administrator` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `anthropic_administrator` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Anthropic Admin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Anthropic Admin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["anthropic_administrator"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Anthropic Admin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `anthropic_administrator` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/anthropic_administrator-automation/SKILL.md b/anthropic_administrator-automation/SKILL.md new file mode 100644 index 0000000..588c244 --- /dev/null +++ b/anthropic_administrator-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: anthropic_administrator-automation +description: "Automate Anthropic Admin tasks via Rube MCP (Composio): API keys, usage, workspaces, and organization management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Anthropic Admin Automation via Rube MCP + +Automate Anthropic Admin operations through Composio's Anthropic Admin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/anthropic_administrator](https://composio.dev/toolkits/anthropic_administrator) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Anthropic Admin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `anthropic_administrator` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `anthropic_administrator` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "API keys, usage, workspaces, and organization management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Anthropic Admin +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Anthropic Admin Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Anthropic Admin tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Anthropic Admin Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Anthropic Admin operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Anthropic Admin connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Anthropic Admin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `anthropic_administrator` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/anthropic_administrator](https://composio.dev/toolkits/anthropic_administrator) diff --git a/apaleo-automation/SKILL.md b/apaleo-automation/SKILL.md new file mode 100644 index 0000000..55f44bd --- /dev/null +++ b/apaleo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apaleo-automation +description: "Automate Apaleo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apaleo Automation via Rube MCP + +Automate Apaleo operations through Composio's Apaleo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apaleo](https://composio.dev/toolkits/apaleo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apaleo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apaleo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apaleo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apaleo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apaleo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apaleo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apaleo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apaleo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apex27-automation/SKILL.md b/apex27-automation/SKILL.md new file mode 100644 index 0000000..e94b7cd --- /dev/null +++ b/apex27-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apex27-automation +description: "Automate Apex27 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apex27 Automation via Rube MCP + +Automate Apex27 operations through Composio's Apex27 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apex27](https://composio.dev/toolkits/apex27) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apex27 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apex27` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apex27` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apex27 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apex27 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apex27"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apex27-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apex27` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/api-bible-automation/SKILL.md b/api-bible-automation/SKILL.md new file mode 100644 index 0000000..defca6e --- /dev/null +++ b/api-bible-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: api-bible-automation +description: "Automate API Bible tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# API Bible Automation via Rube MCP + +Automate API Bible operations through Composio's API Bible toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/api_bible](https://composio.dev/toolkits/api_bible) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active API Bible connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `api_bible` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `api_bible` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "API Bible operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific API Bible task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["api_bible"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with API Bible-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `api_bible` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/api-labz-automation/SKILL.md b/api-labz-automation/SKILL.md new file mode 100644 index 0000000..55c206d --- /dev/null +++ b/api-labz-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: api-labz-automation +description: "Automate API Labz tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# API Labz Automation via Rube MCP + +Automate API Labz operations through Composio's API Labz toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/api_labz](https://composio.dev/toolkits/api_labz) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active API Labz connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `api_labz` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `api_labz` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "API Labz operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific API Labz task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["api_labz"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with API Labz-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `api_labz` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/api-ninjas-automation/SKILL.md b/api-ninjas-automation/SKILL.md new file mode 100644 index 0000000..b6f20ec --- /dev/null +++ b/api-ninjas-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: api-ninjas-automation +description: "Automate API Ninjas tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# API Ninjas Automation via Rube MCP + +Automate API Ninjas operations through Composio's API Ninjas toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/api_ninjas](https://composio.dev/toolkits/api_ninjas) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active API Ninjas connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `api_ninjas` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `api_ninjas` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "API Ninjas operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific API Ninjas task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["api_ninjas"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with API Ninjas-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `api_ninjas` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/api-sports-automation/SKILL.md b/api-sports-automation/SKILL.md new file mode 100644 index 0000000..0653d97 --- /dev/null +++ b/api-sports-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: api-sports-automation +description: "Automate API Sports tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# API Sports Automation via Rube MCP + +Automate API Sports operations through Composio's API Sports toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/api_sports](https://composio.dev/toolkits/api_sports) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active API Sports connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `api_sports` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `api_sports` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "API Sports operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific API Sports task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["api_sports"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with API Sports-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `api_sports` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/api2pdf-automation/SKILL.md b/api2pdf-automation/SKILL.md new file mode 100644 index 0000000..7b44573 --- /dev/null +++ b/api2pdf-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: api2pdf-automation +description: "Automate Api2pdf tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Api2pdf Automation via Rube MCP + +Automate Api2pdf operations through Composio's Api2pdf toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/api2pdf](https://composio.dev/toolkits/api2pdf) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Api2pdf connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `api2pdf` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `api2pdf` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Api2pdf operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Api2pdf task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["api2pdf"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Api2pdf-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `api2pdf` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apiflash-automation/SKILL.md b/apiflash-automation/SKILL.md new file mode 100644 index 0000000..917efe8 --- /dev/null +++ b/apiflash-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apiflash-automation +description: "Automate Apiflash tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apiflash Automation via Rube MCP + +Automate Apiflash operations through Composio's Apiflash toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apiflash](https://composio.dev/toolkits/apiflash) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apiflash connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apiflash` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apiflash` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apiflash operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apiflash task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apiflash"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apiflash-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apiflash` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apify-automation/SKILL.md b/apify-automation/SKILL.md new file mode 100644 index 0000000..7284038 --- /dev/null +++ b/apify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apify-automation +description: "Automate Apify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apify Automation via Rube MCP + +Automate Apify operations through Composio's Apify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apify](https://composio.dev/toolkits/apify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apilio-automation/SKILL.md b/apilio-automation/SKILL.md new file mode 100644 index 0000000..b8b1260 --- /dev/null +++ b/apilio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apilio-automation +description: "Automate Apilio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apilio Automation via Rube MCP + +Automate Apilio operations through Composio's Apilio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apilio](https://composio.dev/toolkits/apilio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apilio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apilio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apilio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apilio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apilio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apilio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apilio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apilio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apipie-ai-automation/SKILL.md b/apipie-ai-automation/SKILL.md new file mode 100644 index 0000000..4162601 --- /dev/null +++ b/apipie-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apipie-ai-automation +description: "Automate Apipie AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apipie AI Automation via Rube MCP + +Automate Apipie AI operations through Composio's Apipie AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apipie_ai](https://composio.dev/toolkits/apipie_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apipie AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apipie_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apipie_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apipie AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apipie AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apipie_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apipie AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apipie_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apitemplate-io-automation/SKILL.md b/apitemplate-io-automation/SKILL.md new file mode 100644 index 0000000..0af94b5 --- /dev/null +++ b/apitemplate-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apitemplate-io-automation +description: "Automate Apitemplate IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apitemplate IO Automation via Rube MCP + +Automate Apitemplate IO operations through Composio's Apitemplate IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apitemplate_io](https://composio.dev/toolkits/apitemplate_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apitemplate IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apitemplate_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apitemplate_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apitemplate IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apitemplate IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apitemplate_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apitemplate IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apitemplate_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apiverve-automation/SKILL.md b/apiverve-automation/SKILL.md new file mode 100644 index 0000000..076baca --- /dev/null +++ b/apiverve-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apiverve-automation +description: "Automate Apiverve tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apiverve Automation via Rube MCP + +Automate Apiverve operations through Composio's Apiverve toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apiverve](https://composio.dev/toolkits/apiverve) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apiverve connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apiverve` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apiverve` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apiverve operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apiverve task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apiverve"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apiverve-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apiverve` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/apollo-automation/SKILL.md b/apollo-automation/SKILL.md new file mode 100644 index 0000000..da1b64e --- /dev/null +++ b/apollo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: apollo-automation +description: "Automate Apollo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Apollo Automation via Rube MCP + +Automate Apollo operations through Composio's Apollo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/apollo](https://composio.dev/toolkits/apollo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Apollo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apollo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `apollo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Apollo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Apollo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["apollo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Apollo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apollo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/appcircle-automation/SKILL.md b/appcircle-automation/SKILL.md new file mode 100644 index 0000000..6785261 --- /dev/null +++ b/appcircle-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: appcircle-automation +description: "Automate Appcircle tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Appcircle Automation via Rube MCP + +Automate Appcircle operations through Composio's Appcircle toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/appcircle](https://composio.dev/toolkits/appcircle) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Appcircle connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appcircle` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appcircle` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Appcircle operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Appcircle task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["appcircle"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Appcircle-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appcircle` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/appdrag-automation/SKILL.md b/appdrag-automation/SKILL.md new file mode 100644 index 0000000..6e5bb32 --- /dev/null +++ b/appdrag-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: appdrag-automation +description: "Automate Appdrag tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Appdrag Automation via Rube MCP + +Automate Appdrag operations through Composio's Appdrag toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/appdrag](https://composio.dev/toolkits/appdrag) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Appdrag connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appdrag` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appdrag` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Appdrag operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Appdrag task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["appdrag"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Appdrag-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appdrag` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/appointo-automation/SKILL.md b/appointo-automation/SKILL.md new file mode 100644 index 0000000..7c1171b --- /dev/null +++ b/appointo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: appointo-automation +description: "Automate Appointo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Appointo Automation via Rube MCP + +Automate Appointo operations through Composio's Appointo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/appointo](https://composio.dev/toolkits/appointo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Appointo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appointo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appointo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Appointo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Appointo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["appointo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Appointo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appointo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/appsflyer-automation/SKILL.md b/appsflyer-automation/SKILL.md new file mode 100644 index 0000000..b5b066e --- /dev/null +++ b/appsflyer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: appsflyer-automation +description: "Automate Appsflyer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Appsflyer Automation via Rube MCP + +Automate Appsflyer operations through Composio's Appsflyer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/appsflyer](https://composio.dev/toolkits/appsflyer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Appsflyer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appsflyer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appsflyer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Appsflyer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Appsflyer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["appsflyer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Appsflyer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appsflyer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/appveyor-automation/SKILL.md b/appveyor-automation/SKILL.md new file mode 100644 index 0000000..ca3a737 --- /dev/null +++ b/appveyor-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: appveyor-automation +description: "Automate Appveyor tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Appveyor Automation via Rube MCP + +Automate Appveyor operations through Composio's Appveyor toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/appveyor](https://composio.dev/toolkits/appveyor) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Appveyor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `appveyor` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `appveyor` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Appveyor operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Appveyor task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["appveyor"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Appveyor-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `appveyor` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/aryn-automation/SKILL.md b/aryn-automation/SKILL.md new file mode 100644 index 0000000..79af351 --- /dev/null +++ b/aryn-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: aryn-automation +description: "Automate Aryn tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Aryn Automation via Rube MCP + +Automate Aryn operations through Composio's Aryn toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/aryn](https://composio.dev/toolkits/aryn) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Aryn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `aryn` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `aryn` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Aryn operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Aryn task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["aryn"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Aryn-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `aryn` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/asana-automation/SKILL.md b/asana-automation/SKILL.md index 63e7b83..600efe5 100644 --- a/asana-automation/SKILL.md +++ b/asana-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Asana operations through Composio's Asana toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/asana](https://composio.dev/toolkits/asana) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -169,3 +171,6 @@ Automate Asana operations through Composio's Asana toolkit via Rube MCP. | Workspace users | ASANA_GET_USERS_FOR_WORKSPACE | workspace_gid | | Current user | ASANA_GET_CURRENT_USER | (none) | | Parallel requests | ASANA_SUBMIT_PARALLEL_REQUESTS | actions | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ascora-automation/SKILL.md b/ascora-automation/SKILL.md new file mode 100644 index 0000000..cf10f3e --- /dev/null +++ b/ascora-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ascora-automation +description: "Automate Ascora tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ascora Automation via Rube MCP + +Automate Ascora operations through Composio's Ascora toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ascora](https://composio.dev/toolkits/ascora) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ascora connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ascora` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ascora` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ascora operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ascora task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ascora"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ascora-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ascora` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ashby-automation/SKILL.md b/ashby-automation/SKILL.md new file mode 100644 index 0000000..4b5ae08 --- /dev/null +++ b/ashby-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ashby-automation +description: "Automate Ashby tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ashby Automation via Rube MCP + +Automate Ashby operations through Composio's Ashby toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ashby](https://composio.dev/toolkits/ashby) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ashby connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ashby` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ashby` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ashby operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ashby task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ashby"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ashby-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ashby` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/asin-data-api-automation/SKILL.md b/asin-data-api-automation/SKILL.md new file mode 100644 index 0000000..7c029e7 --- /dev/null +++ b/asin-data-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: asin-data-api-automation +description: "Automate Asin Data API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Asin Data API Automation via Rube MCP + +Automate Asin Data API operations through Composio's Asin Data API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/asin_data_api](https://composio.dev/toolkits/asin_data_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Asin Data API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `asin_data_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `asin_data_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Asin Data API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Asin Data API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["asin_data_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Asin Data API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `asin_data_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/astica-ai-automation/SKILL.md b/astica-ai-automation/SKILL.md new file mode 100644 index 0000000..d134c11 --- /dev/null +++ b/astica-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: astica-ai-automation +description: "Automate Astica AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Astica AI Automation via Rube MCP + +Automate Astica AI operations through Composio's Astica AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/astica_ai](https://composio.dev/toolkits/astica_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Astica AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `astica_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `astica_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Astica AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Astica AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["astica_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Astica AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `astica_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/async-interview-automation/SKILL.md b/async-interview-automation/SKILL.md new file mode 100644 index 0000000..82f3a54 --- /dev/null +++ b/async-interview-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: async-interview-automation +description: "Automate Async Interview tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Async Interview Automation via Rube MCP + +Automate Async Interview operations through Composio's Async Interview toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/async_interview](https://composio.dev/toolkits/async_interview) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Async Interview connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `async_interview` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `async_interview` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Async Interview operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Async Interview task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["async_interview"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Async Interview-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `async_interview` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/atlassian-automation/SKILL.md b/atlassian-automation/SKILL.md new file mode 100644 index 0000000..5cc32a2 --- /dev/null +++ b/atlassian-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: atlassian-automation +description: "Automate Atlassian tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Atlassian Automation via Rube MCP + +Automate Atlassian operations through Composio's Atlassian toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/atlassian](https://composio.dev/toolkits/atlassian) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Atlassian connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `atlassian` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `atlassian` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Atlassian operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Atlassian task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["atlassian"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Atlassian-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `atlassian` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/attio-automation/SKILL.md b/attio-automation/SKILL.md new file mode 100644 index 0000000..c741239 --- /dev/null +++ b/attio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: attio-automation +description: "Automate Attio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Attio Automation via Rube MCP + +Automate Attio operations through Composio's Attio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/attio](https://composio.dev/toolkits/attio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Attio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `attio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `attio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Attio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Attio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["attio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Attio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `attio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/auth0-automation/SKILL.md b/auth0-automation/SKILL.md new file mode 100644 index 0000000..91b36d2 --- /dev/null +++ b/auth0-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: auth0-automation +description: "Automate Auth0 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Auth0 Automation via Rube MCP + +Automate Auth0 operations through Composio's Auth0 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/auth0](https://composio.dev/toolkits/auth0) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Auth0 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `auth0` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `auth0` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Auth0 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Auth0 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["auth0"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Auth0-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `auth0` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/autobound-automation/SKILL.md b/autobound-automation/SKILL.md new file mode 100644 index 0000000..3cc54f4 --- /dev/null +++ b/autobound-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: autobound-automation +description: "Automate Autobound tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Autobound Automation via Rube MCP + +Automate Autobound operations through Composio's Autobound toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/autobound](https://composio.dev/toolkits/autobound) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Autobound connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `autobound` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `autobound` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Autobound operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Autobound task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["autobound"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Autobound-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `autobound` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/autom-automation/SKILL.md b/autom-automation/SKILL.md new file mode 100644 index 0000000..e3bf67a --- /dev/null +++ b/autom-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: autom-automation +description: "Automate Autom tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Autom Automation via Rube MCP + +Automate Autom operations through Composio's Autom toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/autom](https://composio.dev/toolkits/autom) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Autom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `autom` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `autom` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Autom operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Autom task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["autom"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Autom-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `autom` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/axonaut-automation/SKILL.md b/axonaut-automation/SKILL.md new file mode 100644 index 0000000..39f7f28 --- /dev/null +++ b/axonaut-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: axonaut-automation +description: "Automate Axonaut tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Axonaut Automation via Rube MCP + +Automate Axonaut operations through Composio's Axonaut toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/axonaut](https://composio.dev/toolkits/axonaut) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Axonaut connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `axonaut` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `axonaut` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Axonaut operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Axonaut task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["axonaut"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Axonaut-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `axonaut` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ayrshare-automation/SKILL.md b/ayrshare-automation/SKILL.md new file mode 100644 index 0000000..f705151 --- /dev/null +++ b/ayrshare-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ayrshare-automation +description: "Automate Ayrshare tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ayrshare Automation via Rube MCP + +Automate Ayrshare operations through Composio's Ayrshare toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ayrshare](https://composio.dev/toolkits/ayrshare) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ayrshare connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ayrshare` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ayrshare` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ayrshare operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ayrshare task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ayrshare"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ayrshare-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ayrshare` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/backendless-automation/SKILL.md b/backendless-automation/SKILL.md new file mode 100644 index 0000000..db69aa2 --- /dev/null +++ b/backendless-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: backendless-automation +description: "Automate Backendless tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Backendless Automation via Rube MCP + +Automate Backendless operations through Composio's Backendless toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/backendless](https://composio.dev/toolkits/backendless) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Backendless connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `backendless` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `backendless` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Backendless operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Backendless task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["backendless"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Backendless-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `backendless` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bamboohr-automation/SKILL.md b/bamboohr-automation/SKILL.md index 7c075a8..6a25e50 100644 --- a/bamboohr-automation/SKILL.md +++ b/bamboohr-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate BambooHR human resources operations through Composio's BambooHR toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/bamboohr](https://composio.dev/toolkits/bamboohr) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -218,3 +220,6 @@ For keeping external systems in sync with BambooHR: | Update employee | BAMBOOHR_UPDATE_EMPLOYEE | id, (field updates) | | List dependents | BAMBOOHR_DEPENDENTS_GET_ALL | employeeId | | Benefit coverages | BAMBOOHR_BENEFIT_GET_COVERAGES | (check schema) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bannerbear-automation/SKILL.md b/bannerbear-automation/SKILL.md new file mode 100644 index 0000000..c9c5e87 --- /dev/null +++ b/bannerbear-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bannerbear-automation +description: "Automate Bannerbear tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bannerbear Automation via Rube MCP + +Automate Bannerbear operations through Composio's Bannerbear toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bannerbear](https://composio.dev/toolkits/bannerbear) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bannerbear connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bannerbear` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bannerbear` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bannerbear operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bannerbear task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bannerbear"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bannerbear-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bannerbear` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bart-automation/SKILL.md b/bart-automation/SKILL.md new file mode 100644 index 0000000..d043e09 --- /dev/null +++ b/bart-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bart-automation +description: "Automate Bart tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bart Automation via Rube MCP + +Automate Bart operations through Composio's Bart toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bart](https://composio.dev/toolkits/bart) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bart connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bart` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bart` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bart operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bart task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bart"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bart-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bart` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/basecamp-automation/SKILL.md b/basecamp-automation/SKILL.md index 4b8312d..b5be28b 100644 --- a/basecamp-automation/SKILL.md +++ b/basecamp-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Basecamp operations including project management, to-do list creation, task management, message board posting, people management, and to-do group organization through Composio's Basecamp toolkit. +**Toolkit docs**: [composio.dev/toolkits/basecamp](https://composio.dev/toolkits/basecamp) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -232,3 +234,6 @@ Basecamp uses page-based pagination on list endpoints: | List all people | `BASECAMP_GET_PEOPLE` | (none) | | List project people | `BASECAMP_LIST_PROJECT_PEOPLE` | `project_id` | | Manage access | `BASECAMP_PUT_PROJECTS_PEOPLE_USERS` | `project_id`, `grant`, `revoke`, `create` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/baselinker-automation/SKILL.md b/baselinker-automation/SKILL.md new file mode 100644 index 0000000..408723c --- /dev/null +++ b/baselinker-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: baselinker-automation +description: "Automate Baselinker tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Baselinker Automation via Rube MCP + +Automate Baselinker operations through Composio's Baselinker toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/baselinker](https://composio.dev/toolkits/baselinker) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Baselinker connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `baselinker` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `baselinker` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Baselinker operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Baselinker task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["baselinker"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Baselinker-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `baselinker` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/baserow-automation/SKILL.md b/baserow-automation/SKILL.md new file mode 100644 index 0000000..e2c7ecd --- /dev/null +++ b/baserow-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: baserow-automation +description: "Automate Baserow tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Baserow Automation via Rube MCP + +Automate Baserow operations through Composio's Baserow toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/baserow](https://composio.dev/toolkits/baserow) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Baserow connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `baserow` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `baserow` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Baserow operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Baserow task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["baserow"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Baserow-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `baserow` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/basin-automation/SKILL.md b/basin-automation/SKILL.md new file mode 100644 index 0000000..ad5799c --- /dev/null +++ b/basin-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: basin-automation +description: "Automate Basin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Basin Automation via Rube MCP + +Automate Basin operations through Composio's Basin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/basin](https://composio.dev/toolkits/basin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Basin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `basin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `basin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Basin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Basin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["basin"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Basin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `basin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/battlenet-automation/SKILL.md b/battlenet-automation/SKILL.md new file mode 100644 index 0000000..07bb858 --- /dev/null +++ b/battlenet-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: battlenet-automation +description: "Automate Battlenet tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Battlenet Automation via Rube MCP + +Automate Battlenet operations through Composio's Battlenet toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/battlenet](https://composio.dev/toolkits/battlenet) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Battlenet connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `battlenet` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `battlenet` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Battlenet operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Battlenet task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["battlenet"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Battlenet-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `battlenet` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/beaconchain-automation/SKILL.md b/beaconchain-automation/SKILL.md new file mode 100644 index 0000000..5aefd0f --- /dev/null +++ b/beaconchain-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: beaconchain-automation +description: "Automate Beaconchain tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Beaconchain Automation via Rube MCP + +Automate Beaconchain operations through Composio's Beaconchain toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/beaconchain](https://composio.dev/toolkits/beaconchain) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Beaconchain connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `beaconchain` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `beaconchain` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Beaconchain operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Beaconchain task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["beaconchain"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Beaconchain-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `beaconchain` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/beaconstac-automation/SKILL.md b/beaconstac-automation/SKILL.md new file mode 100644 index 0000000..cffa710 --- /dev/null +++ b/beaconstac-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: beaconstac-automation +description: "Automate Beaconstac tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Beaconstac Automation via Rube MCP + +Automate Beaconstac operations through Composio's Beaconstac toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/beaconstac](https://composio.dev/toolkits/beaconstac) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Beaconstac connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `beaconstac` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `beaconstac` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Beaconstac operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Beaconstac task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["beaconstac"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Beaconstac-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `beaconstac` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/beamer-automation/SKILL.md b/beamer-automation/SKILL.md new file mode 100644 index 0000000..be4a439 --- /dev/null +++ b/beamer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: beamer-automation +description: "Automate Beamer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Beamer Automation via Rube MCP + +Automate Beamer operations through Composio's Beamer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/beamer](https://composio.dev/toolkits/beamer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Beamer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `beamer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `beamer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Beamer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Beamer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["beamer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Beamer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `beamer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/beeminder-automation/SKILL.md b/beeminder-automation/SKILL.md new file mode 100644 index 0000000..f78db41 --- /dev/null +++ b/beeminder-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: beeminder-automation +description: "Automate Beeminder tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Beeminder Automation via Rube MCP + +Automate Beeminder operations through Composio's Beeminder toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/beeminder](https://composio.dev/toolkits/beeminder) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Beeminder connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `beeminder` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `beeminder` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Beeminder operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Beeminder task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["beeminder"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Beeminder-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `beeminder` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bench-automation/SKILL.md b/bench-automation/SKILL.md new file mode 100644 index 0000000..205c6f8 --- /dev/null +++ b/bench-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bench-automation +description: "Automate Bench tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bench Automation via Rube MCP + +Automate Bench operations through Composio's Bench toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bench](https://composio.dev/toolkits/bench) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bench connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bench` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bench` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bench operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bench task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bench"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bench-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bench` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/benchmark-email-automation/SKILL.md b/benchmark-email-automation/SKILL.md new file mode 100644 index 0000000..c371308 --- /dev/null +++ b/benchmark-email-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: benchmark-email-automation +description: "Automate Benchmark Email tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Benchmark Email Automation via Rube MCP + +Automate Benchmark Email operations through Composio's Benchmark Email toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/benchmark_email](https://composio.dev/toolkits/benchmark_email) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Benchmark Email connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `benchmark_email` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `benchmark_email` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Benchmark Email operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Benchmark Email task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["benchmark_email"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Benchmark Email-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `benchmark_email` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/benzinga-automation/SKILL.md b/benzinga-automation/SKILL.md new file mode 100644 index 0000000..01d8196 --- /dev/null +++ b/benzinga-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: benzinga-automation +description: "Automate Benzinga tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Benzinga Automation via Rube MCP + +Automate Benzinga operations through Composio's Benzinga toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/benzinga](https://composio.dev/toolkits/benzinga) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Benzinga connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `benzinga` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `benzinga` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Benzinga operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Benzinga task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["benzinga"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Benzinga-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `benzinga` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bestbuy-automation/SKILL.md b/bestbuy-automation/SKILL.md new file mode 100644 index 0000000..0e7b8e5 --- /dev/null +++ b/bestbuy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bestbuy-automation +description: "Automate Bestbuy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bestbuy Automation via Rube MCP + +Automate Bestbuy operations through Composio's Bestbuy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bestbuy](https://composio.dev/toolkits/bestbuy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bestbuy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bestbuy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bestbuy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bestbuy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bestbuy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bestbuy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bestbuy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bestbuy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/better-proposals-automation/SKILL.md b/better-proposals-automation/SKILL.md new file mode 100644 index 0000000..24451c3 --- /dev/null +++ b/better-proposals-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: better-proposals-automation +description: "Automate Better Proposals tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Better Proposals Automation via Rube MCP + +Automate Better Proposals operations through Composio's Better Proposals toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/better_proposals](https://composio.dev/toolkits/better_proposals) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Better Proposals connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `better_proposals` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `better_proposals` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Better Proposals operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Better Proposals task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["better_proposals"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Better Proposals-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `better_proposals` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/better-stack-automation/SKILL.md b/better-stack-automation/SKILL.md new file mode 100644 index 0000000..e069746 --- /dev/null +++ b/better-stack-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: better-stack-automation +description: "Automate Better Stack tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Better Stack Automation via Rube MCP + +Automate Better Stack operations through Composio's Better Stack toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/better_stack](https://composio.dev/toolkits/better_stack) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Better Stack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `better_stack` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `better_stack` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Better Stack operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Better Stack task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["better_stack"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Better Stack-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `better_stack` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bidsketch-automation/SKILL.md b/bidsketch-automation/SKILL.md new file mode 100644 index 0000000..fd56d38 --- /dev/null +++ b/bidsketch-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bidsketch-automation +description: "Automate Bidsketch tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bidsketch Automation via Rube MCP + +Automate Bidsketch operations through Composio's Bidsketch toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bidsketch](https://composio.dev/toolkits/bidsketch) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bidsketch connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bidsketch` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bidsketch` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bidsketch operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bidsketch task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bidsketch"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bidsketch-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bidsketch` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/big-data-cloud-automation/SKILL.md b/big-data-cloud-automation/SKILL.md new file mode 100644 index 0000000..49d93e9 --- /dev/null +++ b/big-data-cloud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: big-data-cloud-automation +description: "Automate Big Data Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Big Data Cloud Automation via Rube MCP + +Automate Big Data Cloud operations through Composio's Big Data Cloud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/big_data_cloud](https://composio.dev/toolkits/big_data_cloud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Big Data Cloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `big_data_cloud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `big_data_cloud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Big Data Cloud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Big Data Cloud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["big_data_cloud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Big Data Cloud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `big_data_cloud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bigmailer-automation/SKILL.md b/bigmailer-automation/SKILL.md new file mode 100644 index 0000000..27da7c3 --- /dev/null +++ b/bigmailer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bigmailer-automation +description: "Automate Bigmailer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bigmailer Automation via Rube MCP + +Automate Bigmailer operations through Composio's Bigmailer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bigmailer](https://composio.dev/toolkits/bigmailer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bigmailer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bigmailer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bigmailer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bigmailer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bigmailer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bigmailer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bigmailer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bigmailer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bigml-automation/SKILL.md b/bigml-automation/SKILL.md new file mode 100644 index 0000000..d787216 --- /dev/null +++ b/bigml-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bigml-automation +description: "Automate Bigml tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bigml Automation via Rube MCP + +Automate Bigml operations through Composio's Bigml toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bigml](https://composio.dev/toolkits/bigml) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bigml connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bigml` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bigml` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bigml operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bigml task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bigml"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bigml-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bigml` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bigpicture-io-automation/SKILL.md b/bigpicture-io-automation/SKILL.md new file mode 100644 index 0000000..3b77917 --- /dev/null +++ b/bigpicture-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bigpicture-io-automation +description: "Automate Bigpicture IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bigpicture IO Automation via Rube MCP + +Automate Bigpicture IO operations through Composio's Bigpicture IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bigpicture_io](https://composio.dev/toolkits/bigpicture_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bigpicture IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bigpicture_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bigpicture_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bigpicture IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bigpicture IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bigpicture_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bigpicture IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bigpicture_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bitbucket-automation/SKILL.md b/bitbucket-automation/SKILL.md index 154f782..c304587 100644 --- a/bitbucket-automation/SKILL.md +++ b/bitbucket-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit. +**Toolkit docs**: [composio.dev/toolkits/bitbucket](https://composio.dev/toolkits/bitbucket) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -222,3 +224,6 @@ Bitbucket Query Language is available on list endpoints: | Comment on issue | `BITBUCKET_CREATE_ISSUE_COMMENT` | `workspace`, `repo_slug`, `issue_id`, `content` | | Delete issue | `BITBUCKET_DELETE_ISSUE` | `workspace`, `repo_slug`, `issue_id` | | List members | `BITBUCKET_LIST_WORKSPACE_MEMBERS` | `workspace` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bitquery-automation/SKILL.md b/bitquery-automation/SKILL.md new file mode 100644 index 0000000..80ad55d --- /dev/null +++ b/bitquery-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bitquery-automation +description: "Automate Bitquery tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bitquery Automation via Rube MCP + +Automate Bitquery operations through Composio's Bitquery toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bitquery](https://composio.dev/toolkits/bitquery) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bitquery connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bitquery` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitquery` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bitquery operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bitquery task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bitquery"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bitquery-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bitquery` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bitwarden-automation/SKILL.md b/bitwarden-automation/SKILL.md new file mode 100644 index 0000000..98437b6 --- /dev/null +++ b/bitwarden-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bitwarden-automation +description: "Automate Bitwarden tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bitwarden Automation via Rube MCP + +Automate Bitwarden operations through Composio's Bitwarden toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bitwarden](https://composio.dev/toolkits/bitwarden) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bitwarden connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bitwarden` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitwarden` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bitwarden operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bitwarden task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bitwarden"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bitwarden-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bitwarden` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/blackbaud-automation/SKILL.md b/blackbaud-automation/SKILL.md new file mode 100644 index 0000000..486765f --- /dev/null +++ b/blackbaud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: blackbaud-automation +description: "Automate Blackbaud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Blackbaud Automation via Rube MCP + +Automate Blackbaud operations through Composio's Blackbaud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/blackbaud](https://composio.dev/toolkits/blackbaud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Blackbaud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `blackbaud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `blackbaud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Blackbaud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Blackbaud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["blackbaud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Blackbaud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `blackbaud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/blackboard-automation/SKILL.md b/blackboard-automation/SKILL.md new file mode 100644 index 0000000..a48a37b --- /dev/null +++ b/blackboard-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: blackboard-automation +description: "Automate Blackboard tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Blackboard Automation via Rube MCP + +Automate Blackboard operations through Composio's Blackboard toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/blackboard](https://composio.dev/toolkits/blackboard) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Blackboard connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `blackboard` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `blackboard` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Blackboard operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Blackboard task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["blackboard"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Blackboard-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `blackboard` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/blocknative-automation/SKILL.md b/blocknative-automation/SKILL.md new file mode 100644 index 0000000..453fb2a --- /dev/null +++ b/blocknative-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: blocknative-automation +description: "Automate Blocknative tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Blocknative Automation via Rube MCP + +Automate Blocknative operations through Composio's Blocknative toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/blocknative](https://composio.dev/toolkits/blocknative) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Blocknative connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `blocknative` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `blocknative` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Blocknative operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Blocknative task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["blocknative"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Blocknative-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `blocknative` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/boldsign-automation/SKILL.md b/boldsign-automation/SKILL.md new file mode 100644 index 0000000..e0ff54c --- /dev/null +++ b/boldsign-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: boldsign-automation +description: "Automate Boldsign tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Boldsign Automation via Rube MCP + +Automate Boldsign operations through Composio's Boldsign toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/boldsign](https://composio.dev/toolkits/boldsign) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Boldsign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `boldsign` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `boldsign` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Boldsign operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Boldsign task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["boldsign"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Boldsign-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `boldsign` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bolna-automation/SKILL.md b/bolna-automation/SKILL.md new file mode 100644 index 0000000..d685ace --- /dev/null +++ b/bolna-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bolna-automation +description: "Automate Bolna tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bolna Automation via Rube MCP + +Automate Bolna operations through Composio's Bolna toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bolna](https://composio.dev/toolkits/bolna) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bolna connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bolna` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bolna` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bolna operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bolna task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bolna"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bolna-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bolna` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/boloforms-automation/SKILL.md b/boloforms-automation/SKILL.md new file mode 100644 index 0000000..7351730 --- /dev/null +++ b/boloforms-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: boloforms-automation +description: "Automate Boloforms tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Boloforms Automation via Rube MCP + +Automate Boloforms operations through Composio's Boloforms toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/boloforms](https://composio.dev/toolkits/boloforms) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Boloforms connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `boloforms` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `boloforms` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Boloforms operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Boloforms task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["boloforms"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Boloforms-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `boloforms` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bolt-iot-automation/SKILL.md b/bolt-iot-automation/SKILL.md new file mode 100644 index 0000000..b782c2a --- /dev/null +++ b/bolt-iot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bolt-iot-automation +description: "Automate Bolt Iot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bolt Iot Automation via Rube MCP + +Automate Bolt Iot operations through Composio's Bolt Iot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bolt_iot](https://composio.dev/toolkits/bolt_iot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bolt Iot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bolt_iot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bolt_iot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bolt Iot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bolt Iot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bolt_iot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bolt Iot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bolt_iot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bonsai-automation/SKILL.md b/bonsai-automation/SKILL.md new file mode 100644 index 0000000..80ff2e3 --- /dev/null +++ b/bonsai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bonsai-automation +description: "Automate Bonsai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bonsai Automation via Rube MCP + +Automate Bonsai operations through Composio's Bonsai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bonsai](https://composio.dev/toolkits/bonsai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bonsai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bonsai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bonsai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bonsai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bonsai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bonsai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bonsai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bonsai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bookingmood-automation/SKILL.md b/bookingmood-automation/SKILL.md new file mode 100644 index 0000000..74aefb8 --- /dev/null +++ b/bookingmood-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bookingmood-automation +description: "Automate Bookingmood tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bookingmood Automation via Rube MCP + +Automate Bookingmood operations through Composio's Bookingmood toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bookingmood](https://composio.dev/toolkits/bookingmood) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bookingmood connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bookingmood` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bookingmood` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bookingmood operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bookingmood task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bookingmood"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bookingmood-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bookingmood` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/booqable-automation/SKILL.md b/booqable-automation/SKILL.md new file mode 100644 index 0000000..5d8a2e4 --- /dev/null +++ b/booqable-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: booqable-automation +description: "Automate Booqable tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Booqable Automation via Rube MCP + +Automate Booqable operations through Composio's Booqable toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/booqable](https://composio.dev/toolkits/booqable) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Booqable connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `booqable` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `booqable` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Booqable operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Booqable task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["booqable"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Booqable-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `booqable` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/borneo-automation/SKILL.md b/borneo-automation/SKILL.md new file mode 100644 index 0000000..17e1762 --- /dev/null +++ b/borneo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: borneo-automation +description: "Automate Borneo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Borneo Automation via Rube MCP + +Automate Borneo operations through Composio's Borneo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/borneo](https://composio.dev/toolkits/borneo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Borneo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `borneo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `borneo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Borneo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Borneo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["borneo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Borneo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `borneo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/botbaba-automation/SKILL.md b/botbaba-automation/SKILL.md new file mode 100644 index 0000000..4098122 --- /dev/null +++ b/botbaba-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: botbaba-automation +description: "Automate Botbaba tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Botbaba Automation via Rube MCP + +Automate Botbaba operations through Composio's Botbaba toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/botbaba](https://composio.dev/toolkits/botbaba) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Botbaba connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `botbaba` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `botbaba` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Botbaba operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Botbaba task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["botbaba"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Botbaba-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `botbaba` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/botpress-automation/SKILL.md b/botpress-automation/SKILL.md new file mode 100644 index 0000000..6019c45 --- /dev/null +++ b/botpress-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: botpress-automation +description: "Automate Botpress tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Botpress Automation via Rube MCP + +Automate Botpress operations through Composio's Botpress toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/botpress](https://composio.dev/toolkits/botpress) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Botpress connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `botpress` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `botpress` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Botpress operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Botpress task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["botpress"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Botpress-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `botpress` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/botsonic-automation/SKILL.md b/botsonic-automation/SKILL.md new file mode 100644 index 0000000..2caa57c --- /dev/null +++ b/botsonic-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: botsonic-automation +description: "Automate Botsonic tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Botsonic Automation via Rube MCP + +Automate Botsonic operations through Composio's Botsonic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/botsonic](https://composio.dev/toolkits/botsonic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Botsonic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `botsonic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `botsonic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Botsonic operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Botsonic task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["botsonic"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Botsonic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `botsonic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/botstar-automation/SKILL.md b/botstar-automation/SKILL.md new file mode 100644 index 0000000..e418e89 --- /dev/null +++ b/botstar-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: botstar-automation +description: "Automate Botstar tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Botstar Automation via Rube MCP + +Automate Botstar operations through Composio's Botstar toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/botstar](https://composio.dev/toolkits/botstar) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Botstar connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `botstar` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `botstar` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Botstar operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Botstar task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["botstar"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Botstar-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `botstar` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bouncer-automation/SKILL.md b/bouncer-automation/SKILL.md new file mode 100644 index 0000000..3692fda --- /dev/null +++ b/bouncer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bouncer-automation +description: "Automate Bouncer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bouncer Automation via Rube MCP + +Automate Bouncer operations through Composio's Bouncer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bouncer](https://composio.dev/toolkits/bouncer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bouncer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bouncer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bouncer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bouncer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bouncer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bouncer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bouncer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bouncer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/box-automation/SKILL.md b/box-automation/SKILL.md index df73531..0172f8c 100644 --- a/box-automation/SKILL.md +++ b/box-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Box operations including file upload/download, content search, folder management, collaboration, metadata queries, and sign requests through Composio's Box toolkit. +**Toolkit docs**: [composio.dev/toolkits/box](https://composio.dev/toolkits/box) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -231,3 +233,6 @@ Box tools use double underscore notation for nested objects: | Cancel sign request | `BOX_CANCEL_BOX_SIGN_REQUEST` | `sign_request_id` | | Recent items | `BOX_LIST_RECENTLY_ACCESSED_ITEMS` | (none) | | Create zip download | `BOX_CREATE_ZIP_DOWNLOAD` | item IDs | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/boxhero-automation/SKILL.md b/boxhero-automation/SKILL.md new file mode 100644 index 0000000..ff6a3c4 --- /dev/null +++ b/boxhero-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: boxhero-automation +description: "Automate Boxhero tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Boxhero Automation via Rube MCP + +Automate Boxhero operations through Composio's Boxhero toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/boxhero](https://composio.dev/toolkits/boxhero) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Boxhero connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `boxhero` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `boxhero` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Boxhero operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Boxhero task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["boxhero"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Boxhero-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `boxhero` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/braintree-automation/SKILL.md b/braintree-automation/SKILL.md new file mode 100644 index 0000000..5f6bb25 --- /dev/null +++ b/braintree-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: braintree-automation +description: "Automate Braintree tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Braintree Automation via Rube MCP + +Automate Braintree operations through Composio's Braintree toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/braintree](https://composio.dev/toolkits/braintree) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Braintree connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `braintree` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `braintree` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Braintree operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Braintree task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["braintree"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Braintree-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `braintree` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/brandfetch-automation/SKILL.md b/brandfetch-automation/SKILL.md new file mode 100644 index 0000000..565bff8 --- /dev/null +++ b/brandfetch-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: brandfetch-automation +description: "Automate Brandfetch tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Brandfetch Automation via Rube MCP + +Automate Brandfetch operations through Composio's Brandfetch toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/brandfetch](https://composio.dev/toolkits/brandfetch) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Brandfetch connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brandfetch` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brandfetch` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Brandfetch operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Brandfetch task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["brandfetch"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Brandfetch-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `brandfetch` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/breeze-automation/SKILL.md b/breeze-automation/SKILL.md new file mode 100644 index 0000000..a84c33c --- /dev/null +++ b/breeze-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: breeze-automation +description: "Automate Breeze tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Breeze Automation via Rube MCP + +Automate Breeze operations through Composio's Breeze toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/breeze](https://composio.dev/toolkits/breeze) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Breeze connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `breeze` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `breeze` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Breeze operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Breeze task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["breeze"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Breeze-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `breeze` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/breezy-hr-automation/SKILL.md b/breezy-hr-automation/SKILL.md new file mode 100644 index 0000000..2fba1a3 --- /dev/null +++ b/breezy-hr-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: breezy-hr-automation +description: "Automate Breezy HR tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Breezy HR Automation via Rube MCP + +Automate Breezy HR operations through Composio's Breezy HR toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/breezy_hr](https://composio.dev/toolkits/breezy_hr) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Breezy HR connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `breezy_hr` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `breezy_hr` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Breezy HR operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Breezy HR task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["breezy_hr"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Breezy HR-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `breezy_hr` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/brevo-automation/SKILL.md b/brevo-automation/SKILL.md index 55b6a8c..d3f917d 100644 --- a/brevo-automation/SKILL.md +++ b/brevo-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/brevo](https://composio.dev/toolkits/brevo) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -195,3 +197,6 @@ Automate Brevo (formerly Sendinblue) email marketing operations through Composio | Update template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateId, htmlContent | | Delete template | BREVO_DELETE_EMAIL_TEMPLATE | templateId | | List senders | BREVO_GET_ALL_SENDERS | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/brex-automation/SKILL.md b/brex-automation/SKILL.md new file mode 100644 index 0000000..f4ed372 --- /dev/null +++ b/brex-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: brex-automation +description: "Automate Brex tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Brex Automation via Rube MCP + +Automate Brex operations through Composio's Brex toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/brex](https://composio.dev/toolkits/brex) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Brex connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brex` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brex` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Brex operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Brex task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["brex"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Brex-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `brex` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/brex-staging-automation/SKILL.md b/brex-staging-automation/SKILL.md new file mode 100644 index 0000000..ee1af30 --- /dev/null +++ b/brex-staging-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: brex-staging-automation +description: "Automate Brex Staging tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Brex Staging Automation via Rube MCP + +Automate Brex Staging operations through Composio's Brex Staging toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/brex_staging](https://composio.dev/toolkits/brex_staging) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Brex Staging connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brex_staging` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brex_staging` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Brex Staging operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Brex Staging task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["brex_staging"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Brex Staging-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `brex_staging` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/brightdata-automation/SKILL.md b/brightdata-automation/SKILL.md new file mode 100644 index 0000000..5992356 --- /dev/null +++ b/brightdata-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: brightdata-automation +description: "Automate Brightdata tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Brightdata Automation via Rube MCP + +Automate Brightdata operations through Composio's Brightdata toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/brightdata](https://composio.dev/toolkits/brightdata) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Brightdata connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brightdata` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brightdata` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Brightdata operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Brightdata task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["brightdata"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Brightdata-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `brightdata` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/brightpearl-automation/SKILL.md b/brightpearl-automation/SKILL.md new file mode 100644 index 0000000..ba3d9d7 --- /dev/null +++ b/brightpearl-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: brightpearl-automation +description: "Automate Brightpearl tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Brightpearl Automation via Rube MCP + +Automate Brightpearl operations through Composio's Brightpearl toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/brightpearl](https://composio.dev/toolkits/brightpearl) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Brightpearl connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brightpearl` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brightpearl` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Brightpearl operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Brightpearl task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["brightpearl"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Brightpearl-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `brightpearl` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/brilliant-directories-automation/SKILL.md b/brilliant-directories-automation/SKILL.md new file mode 100644 index 0000000..2132fda --- /dev/null +++ b/brilliant-directories-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: brilliant-directories-automation +description: "Automate Brilliant Directories tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Brilliant Directories Automation via Rube MCP + +Automate Brilliant Directories operations through Composio's Brilliant Directories toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/brilliant_directories](https://composio.dev/toolkits/brilliant_directories) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Brilliant Directories connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brilliant_directories` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brilliant_directories` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Brilliant Directories operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Brilliant Directories task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["brilliant_directories"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Brilliant Directories-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `brilliant_directories` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/browseai-automation/SKILL.md b/browseai-automation/SKILL.md new file mode 100644 index 0000000..f33e02c --- /dev/null +++ b/browseai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: browseai-automation +description: "Automate Browseai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Browseai Automation via Rube MCP + +Automate Browseai operations through Composio's Browseai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/browseai](https://composio.dev/toolkits/browseai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Browseai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `browseai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `browseai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Browseai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Browseai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["browseai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Browseai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `browseai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/browser-tool-automation/SKILL.md b/browser-tool-automation/SKILL.md new file mode 100644 index 0000000..72a4d3d --- /dev/null +++ b/browser-tool-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: browser-tool-automation +description: "Automate Browser Tool tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Browser Tool Automation via Rube MCP + +Automate Browser Tool operations through Composio's Browser Tool toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/browser_tool](https://composio.dev/toolkits/browser_tool) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Browser Tool connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `browser_tool` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `browser_tool` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Browser Tool operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Browser Tool task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["browser_tool"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Browser Tool-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `browser_tool` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/browserbase-tool-automation/SKILL.md b/browserbase-tool-automation/SKILL.md new file mode 100644 index 0000000..226ab9c --- /dev/null +++ b/browserbase-tool-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: browserbase-tool-automation +description: "Automate Browserbase Tool tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Browserbase Tool Automation via Rube MCP + +Automate Browserbase Tool operations through Composio's Browserbase Tool toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/browserbase_tool](https://composio.dev/toolkits/browserbase_tool) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Browserbase Tool connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `browserbase_tool` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `browserbase_tool` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Browserbase Tool operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Browserbase Tool task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["browserbase_tool"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Browserbase Tool-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `browserbase_tool` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/browserhub-automation/SKILL.md b/browserhub-automation/SKILL.md new file mode 100644 index 0000000..da27fe0 --- /dev/null +++ b/browserhub-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: browserhub-automation +description: "Automate Browserhub tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Browserhub Automation via Rube MCP + +Automate Browserhub operations through Composio's Browserhub toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/browserhub](https://composio.dev/toolkits/browserhub) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Browserhub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `browserhub` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `browserhub` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Browserhub operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Browserhub task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["browserhub"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Browserhub-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `browserhub` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/browserless-automation/SKILL.md b/browserless-automation/SKILL.md new file mode 100644 index 0000000..569d77b --- /dev/null +++ b/browserless-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: browserless-automation +description: "Automate Browserless tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Browserless Automation via Rube MCP + +Automate Browserless operations through Composio's Browserless toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/browserless](https://composio.dev/toolkits/browserless) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Browserless connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `browserless` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `browserless` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Browserless operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Browserless task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["browserless"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Browserless-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `browserless` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/btcpay-server-automation/SKILL.md b/btcpay-server-automation/SKILL.md new file mode 100644 index 0000000..be19b50 --- /dev/null +++ b/btcpay-server-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: btcpay-server-automation +description: "Automate Btcpay Server tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Btcpay Server Automation via Rube MCP + +Automate Btcpay Server operations through Composio's Btcpay Server toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/btcpay_server](https://composio.dev/toolkits/btcpay_server) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Btcpay Server connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `btcpay_server` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `btcpay_server` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Btcpay Server operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Btcpay Server task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["btcpay_server"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Btcpay Server-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `btcpay_server` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bubble-automation/SKILL.md b/bubble-automation/SKILL.md new file mode 100644 index 0000000..7751202 --- /dev/null +++ b/bubble-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bubble-automation +description: "Automate Bubble tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bubble Automation via Rube MCP + +Automate Bubble operations through Composio's Bubble toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bubble](https://composio.dev/toolkits/bubble) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bubble connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bubble` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bubble` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bubble operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bubble task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bubble"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bubble-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bubble` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bugbug-automation/SKILL.md b/bugbug-automation/SKILL.md new file mode 100644 index 0000000..4406fe7 --- /dev/null +++ b/bugbug-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bugbug-automation +description: "Automate Bugbug tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bugbug Automation via Rube MCP + +Automate Bugbug operations through Composio's Bugbug toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bugbug](https://composio.dev/toolkits/bugbug) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bugbug connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bugbug` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bugbug` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bugbug operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bugbug task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bugbug"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bugbug-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bugbug` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bugherd-automation/SKILL.md b/bugherd-automation/SKILL.md new file mode 100644 index 0000000..3d9df38 --- /dev/null +++ b/bugherd-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bugherd-automation +description: "Automate Bugherd tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bugherd Automation via Rube MCP + +Automate Bugherd operations through Composio's Bugherd toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bugherd](https://composio.dev/toolkits/bugherd) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bugherd connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bugherd` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bugherd` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bugherd operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bugherd task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bugherd"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bugherd-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bugherd` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bugsnag-automation/SKILL.md b/bugsnag-automation/SKILL.md new file mode 100644 index 0000000..39ba8c9 --- /dev/null +++ b/bugsnag-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bugsnag-automation +description: "Automate Bugsnag tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bugsnag Automation via Rube MCP + +Automate Bugsnag operations through Composio's Bugsnag toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bugsnag](https://composio.dev/toolkits/bugsnag) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bugsnag connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bugsnag` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bugsnag` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bugsnag operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bugsnag task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bugsnag"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bugsnag-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bugsnag` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/buildkite-automation/SKILL.md b/buildkite-automation/SKILL.md new file mode 100644 index 0000000..4ef62fb --- /dev/null +++ b/buildkite-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: buildkite-automation +description: "Automate Buildkite tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Buildkite Automation via Rube MCP + +Automate Buildkite operations through Composio's Buildkite toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/buildkite](https://composio.dev/toolkits/buildkite) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Buildkite connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `buildkite` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `buildkite` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Buildkite operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Buildkite task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["buildkite"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Buildkite-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `buildkite` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/builtwith-automation/SKILL.md b/builtwith-automation/SKILL.md new file mode 100644 index 0000000..ccb6bc2 --- /dev/null +++ b/builtwith-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: builtwith-automation +description: "Automate Builtwith tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Builtwith Automation via Rube MCP + +Automate Builtwith operations through Composio's Builtwith toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/builtwith](https://composio.dev/toolkits/builtwith) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Builtwith connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `builtwith` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `builtwith` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Builtwith operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Builtwith task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["builtwith"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Builtwith-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `builtwith` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/bunnycdn-automation/SKILL.md b/bunnycdn-automation/SKILL.md new file mode 100644 index 0000000..da09b9a --- /dev/null +++ b/bunnycdn-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: bunnycdn-automation +description: "Automate Bunnycdn tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Bunnycdn Automation via Rube MCP + +Automate Bunnycdn operations through Composio's Bunnycdn toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/bunnycdn](https://composio.dev/toolkits/bunnycdn) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Bunnycdn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bunnycdn` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bunnycdn` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Bunnycdn operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Bunnycdn task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["bunnycdn"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Bunnycdn-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bunnycdn` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/byteforms-automation/SKILL.md b/byteforms-automation/SKILL.md new file mode 100644 index 0000000..a298958 --- /dev/null +++ b/byteforms-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: byteforms-automation +description: "Automate Byteforms tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Byteforms Automation via Rube MCP + +Automate Byteforms operations through Composio's Byteforms toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/byteforms](https://composio.dev/toolkits/byteforms) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Byteforms connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `byteforms` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `byteforms` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Byteforms operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Byteforms task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["byteforms"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Byteforms-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `byteforms` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cabinpanda-automation/SKILL.md b/cabinpanda-automation/SKILL.md new file mode 100644 index 0000000..7be81f9 --- /dev/null +++ b/cabinpanda-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cabinpanda-automation +description: "Automate Cabinpanda tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cabinpanda Automation via Rube MCP + +Automate Cabinpanda operations through Composio's Cabinpanda toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cabinpanda](https://composio.dev/toolkits/cabinpanda) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cabinpanda connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cabinpanda` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cabinpanda` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cabinpanda operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cabinpanda task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cabinpanda"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cabinpanda-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cabinpanda` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cal-automation/SKILL.md b/cal-automation/SKILL.md new file mode 100644 index 0000000..2760f0b --- /dev/null +++ b/cal-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cal-automation +description: "Automate Cal tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cal Automation via Rube MCP + +Automate Cal operations through Composio's Cal toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cal](https://composio.dev/toolkits/cal) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cal connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cal` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cal` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cal operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cal task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cal"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cal-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cal` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cal-com-automation/SKILL.md b/cal-com-automation/SKILL.md index 22d5765..c0d7ff5 100644 --- a/cal-com-automation/SKILL.md +++ b/cal-com-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Cal.com scheduling operations through Composio's Cal toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/cal](https://composio.dev/toolkits/cal) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -201,3 +203,6 @@ Automate Cal.com scheduling operations through Composio's Cal toolkit via Rube M | Create team | CAL_CREATE_TEAM_IN_ORGANIZATION | name, slug | | Team event types | CAL_RETRIEVE_TEAM_EVENT_TYPES | teamId | | Get org ID | CAL_GET_ORGANIZATION_ID | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/calendarhero-automation/SKILL.md b/calendarhero-automation/SKILL.md new file mode 100644 index 0000000..168f735 --- /dev/null +++ b/calendarhero-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: calendarhero-automation +description: "Automate Calendarhero tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Calendarhero Automation via Rube MCP + +Automate Calendarhero operations through Composio's Calendarhero toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/calendarhero](https://composio.dev/toolkits/calendarhero) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Calendarhero connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `calendarhero` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `calendarhero` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Calendarhero operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Calendarhero task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["calendarhero"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Calendarhero-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `calendarhero` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/calendly-automation/SKILL.md b/calendly-automation/SKILL.md index 5ef8bd4..c8eb702 100644 --- a/calendly-automation/SKILL.md +++ b/calendly-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit. +**Toolkit docs**: [composio.dev/toolkits/calendly](https://composio.dev/toolkits/calendly) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -209,3 +211,6 @@ Most Calendly list endpoints use token-based pagination: | List org invitations | `CALENDLY_LIST_ORGANIZATION_INVITATIONS` | `uuid`, `status` | | Revoke org invitation | `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` | org UUID, invitation UUID | | Remove from org | `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` | membership UUID | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/callerapi-automation/SKILL.md b/callerapi-automation/SKILL.md new file mode 100644 index 0000000..3196f84 --- /dev/null +++ b/callerapi-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: callerapi-automation +description: "Automate Callerapi tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Callerapi Automation via Rube MCP + +Automate Callerapi operations through Composio's Callerapi toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/callerapi](https://composio.dev/toolkits/callerapi) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Callerapi connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `callerapi` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `callerapi` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Callerapi operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Callerapi task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["callerapi"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Callerapi-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `callerapi` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/callingly-automation/SKILL.md b/callingly-automation/SKILL.md new file mode 100644 index 0000000..e11559b --- /dev/null +++ b/callingly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: callingly-automation +description: "Automate Callingly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Callingly Automation via Rube MCP + +Automate Callingly operations through Composio's Callingly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/callingly](https://composio.dev/toolkits/callingly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Callingly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `callingly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `callingly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Callingly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Callingly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["callingly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Callingly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `callingly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/callpage-automation/SKILL.md b/callpage-automation/SKILL.md new file mode 100644 index 0000000..ae84d2e --- /dev/null +++ b/callpage-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: callpage-automation +description: "Automate Callpage tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Callpage Automation via Rube MCP + +Automate Callpage operations through Composio's Callpage toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/callpage](https://composio.dev/toolkits/callpage) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Callpage connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `callpage` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `callpage` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Callpage operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Callpage task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["callpage"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Callpage-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `callpage` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/campaign-cleaner-automation/SKILL.md b/campaign-cleaner-automation/SKILL.md new file mode 100644 index 0000000..4c05eed --- /dev/null +++ b/campaign-cleaner-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: campaign-cleaner-automation +description: "Automate Campaign Cleaner tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Campaign Cleaner Automation via Rube MCP + +Automate Campaign Cleaner operations through Composio's Campaign Cleaner toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/campaign_cleaner](https://composio.dev/toolkits/campaign_cleaner) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Campaign Cleaner connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `campaign_cleaner` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `campaign_cleaner` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Campaign Cleaner operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Campaign Cleaner task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["campaign_cleaner"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Campaign Cleaner-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `campaign_cleaner` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/campayn-automation/SKILL.md b/campayn-automation/SKILL.md new file mode 100644 index 0000000..9c35603 --- /dev/null +++ b/campayn-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: campayn-automation +description: "Automate Campayn tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Campayn Automation via Rube MCP + +Automate Campayn operations through Composio's Campayn toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/campayn](https://composio.dev/toolkits/campayn) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Campayn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `campayn` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `campayn` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Campayn operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Campayn task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["campayn"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Campayn-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `campayn` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/canny-automation/SKILL.md b/canny-automation/SKILL.md new file mode 100644 index 0000000..07ec06b --- /dev/null +++ b/canny-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: canny-automation +description: "Automate Canny tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Canny Automation via Rube MCP + +Automate Canny operations through Composio's Canny toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/canny](https://composio.dev/toolkits/canny) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Canny connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `canny` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `canny` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Canny operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Canny task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["canny"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Canny-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `canny` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/canva-automation/SKILL.md b/canva-automation/SKILL.md index 05f8017..7bf3b97 100644 --- a/canva-automation/SKILL.md +++ b/canva-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Canva design operations through Composio's Canva toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/canva](https://composio.dev/toolkits/canva) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -215,3 +217,6 @@ Many Canva operations are asynchronous: | Move to folder | CANVA_MOVE_ITEM_TO_SPECIFIED_FOLDER | item_id, folder_id | | List templates | CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST | (none) | | Autofill template | CANVA_INITIATE_CANVA_DESIGN_AUTOFILL_JOB | brand_template_id, data | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/canvas-automation/SKILL.md b/canvas-automation/SKILL.md new file mode 100644 index 0000000..f3ed6d0 --- /dev/null +++ b/canvas-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: canvas-automation +description: "Automate Canvas tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Canvas Automation via Rube MCP + +Automate Canvas operations through Composio's Canvas toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/canvas](https://composio.dev/toolkits/canvas) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Canvas connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `canvas` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `canvas` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Canvas operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Canvas task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["canvas"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Canvas-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `canvas` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/capsule-crm-automation/SKILL.md b/capsule-crm-automation/SKILL.md new file mode 100644 index 0000000..90ff2b8 --- /dev/null +++ b/capsule-crm-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: capsule-crm-automation +description: "Automate Capsule CRM tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Capsule CRM Automation via Rube MCP + +Automate Capsule CRM operations through Composio's Capsule CRM toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/capsule_crm](https://composio.dev/toolkits/capsule_crm) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Capsule CRM connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `capsule_crm` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `capsule_crm` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Capsule CRM operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Capsule CRM task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["capsule_crm"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Capsule CRM-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `capsule_crm` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/capsule_crm-automation/SKILL.md b/capsule_crm-automation/SKILL.md new file mode 100644 index 0000000..d1a25d4 --- /dev/null +++ b/capsule_crm-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: capsule_crm-automation +description: "Automate Capsule CRM tasks via Rube MCP (Composio): contacts, opportunities, cases, tasks, and pipeline management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Capsule CRM Automation via Rube MCP + +Automate Capsule CRM operations through Composio's Capsule CRM toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/capsule_crm](https://composio.dev/toolkits/capsule_crm) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Capsule CRM connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `capsule_crm` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `capsule_crm` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "contacts, opportunities, cases, tasks, and pipeline management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Capsule CRM +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Capsule CRM Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Capsule CRM tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Capsule CRM Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Capsule CRM operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Capsule CRM connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Capsule CRM-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `capsule_crm` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/capsule_crm](https://composio.dev/toolkits/capsule_crm) diff --git a/carbone-automation/SKILL.md b/carbone-automation/SKILL.md new file mode 100644 index 0000000..01cd246 --- /dev/null +++ b/carbone-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: carbone-automation +description: "Automate Carbone tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Carbone Automation via Rube MCP + +Automate Carbone operations through Composio's Carbone toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/carbone](https://composio.dev/toolkits/carbone) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Carbone connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `carbone` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `carbone` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Carbone operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Carbone task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["carbone"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Carbone-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `carbone` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cardly-automation/SKILL.md b/cardly-automation/SKILL.md new file mode 100644 index 0000000..9df8db9 --- /dev/null +++ b/cardly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cardly-automation +description: "Automate Cardly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cardly Automation via Rube MCP + +Automate Cardly operations through Composio's Cardly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cardly](https://composio.dev/toolkits/cardly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cardly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cardly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cardly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cardly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cardly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cardly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cardly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cardly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/castingwords-automation/SKILL.md b/castingwords-automation/SKILL.md new file mode 100644 index 0000000..ac2983d --- /dev/null +++ b/castingwords-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: castingwords-automation +description: "Automate Castingwords tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Castingwords Automation via Rube MCP + +Automate Castingwords operations through Composio's Castingwords toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/castingwords](https://composio.dev/toolkits/castingwords) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Castingwords connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `castingwords` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `castingwords` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Castingwords operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Castingwords task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["castingwords"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Castingwords-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `castingwords` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cats-automation/SKILL.md b/cats-automation/SKILL.md new file mode 100644 index 0000000..c8315bd --- /dev/null +++ b/cats-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cats-automation +description: "Automate Cats tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cats Automation via Rube MCP + +Automate Cats operations through Composio's Cats toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cats](https://composio.dev/toolkits/cats) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cats connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cats` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cats` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cats operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cats task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cats"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cats-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cats` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cdr-platform-automation/SKILL.md b/cdr-platform-automation/SKILL.md new file mode 100644 index 0000000..c9fd1ab --- /dev/null +++ b/cdr-platform-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cdr-platform-automation +description: "Automate Cdr Platform tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cdr Platform Automation via Rube MCP + +Automate Cdr Platform operations through Composio's Cdr Platform toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cdr_platform](https://composio.dev/toolkits/cdr_platform) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cdr Platform connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cdr_platform` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cdr_platform` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cdr Platform operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cdr Platform task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cdr_platform"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cdr Platform-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cdr_platform` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/census-bureau-automation/SKILL.md b/census-bureau-automation/SKILL.md new file mode 100644 index 0000000..f21fd07 --- /dev/null +++ b/census-bureau-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: census-bureau-automation +description: "Automate Census Bureau tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Census Bureau Automation via Rube MCP + +Automate Census Bureau operations through Composio's Census Bureau toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/census_bureau](https://composio.dev/toolkits/census_bureau) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Census Bureau connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `census_bureau` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `census_bureau` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Census Bureau operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Census Bureau task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["census_bureau"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Census Bureau-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `census_bureau` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/centralstationcrm-automation/SKILL.md b/centralstationcrm-automation/SKILL.md new file mode 100644 index 0000000..8ecbc24 --- /dev/null +++ b/centralstationcrm-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: centralstationcrm-automation +description: "Automate Centralstationcrm tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Centralstationcrm Automation via Rube MCP + +Automate Centralstationcrm operations through Composio's Centralstationcrm toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/centralstationcrm](https://composio.dev/toolkits/centralstationcrm) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Centralstationcrm connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `centralstationcrm` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `centralstationcrm` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Centralstationcrm operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Centralstationcrm task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["centralstationcrm"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Centralstationcrm-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `centralstationcrm` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/certifier-automation/SKILL.md b/certifier-automation/SKILL.md new file mode 100644 index 0000000..13b7626 --- /dev/null +++ b/certifier-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: certifier-automation +description: "Automate Certifier tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Certifier Automation via Rube MCP + +Automate Certifier operations through Composio's Certifier toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/certifier](https://composio.dev/toolkits/certifier) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Certifier connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `certifier` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `certifier` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Certifier operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Certifier task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["certifier"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Certifier-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `certifier` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/chaser-automation/SKILL.md b/chaser-automation/SKILL.md new file mode 100644 index 0000000..88ed45d --- /dev/null +++ b/chaser-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: chaser-automation +description: "Automate Chaser tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Chaser Automation via Rube MCP + +Automate Chaser operations through Composio's Chaser toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/chaser](https://composio.dev/toolkits/chaser) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Chaser connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chaser` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `chaser` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Chaser operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Chaser task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["chaser"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Chaser-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `chaser` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/chatbotkit-automation/SKILL.md b/chatbotkit-automation/SKILL.md new file mode 100644 index 0000000..9965041 --- /dev/null +++ b/chatbotkit-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: chatbotkit-automation +description: "Automate Chatbotkit tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Chatbotkit Automation via Rube MCP + +Automate Chatbotkit operations through Composio's Chatbotkit toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/chatbotkit](https://composio.dev/toolkits/chatbotkit) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Chatbotkit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chatbotkit` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `chatbotkit` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Chatbotkit operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Chatbotkit task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["chatbotkit"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Chatbotkit-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `chatbotkit` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/chatfai-automation/SKILL.md b/chatfai-automation/SKILL.md new file mode 100644 index 0000000..93d8d0c --- /dev/null +++ b/chatfai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: chatfai-automation +description: "Automate Chatfai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Chatfai Automation via Rube MCP + +Automate Chatfai operations through Composio's Chatfai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/chatfai](https://composio.dev/toolkits/chatfai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Chatfai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chatfai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `chatfai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Chatfai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Chatfai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["chatfai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Chatfai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `chatfai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/chatwork-automation/SKILL.md b/chatwork-automation/SKILL.md new file mode 100644 index 0000000..0bfa2fb --- /dev/null +++ b/chatwork-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: chatwork-automation +description: "Automate Chatwork tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Chatwork Automation via Rube MCP + +Automate Chatwork operations through Composio's Chatwork toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/chatwork](https://composio.dev/toolkits/chatwork) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Chatwork connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chatwork` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `chatwork` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Chatwork operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Chatwork task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["chatwork"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Chatwork-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `chatwork` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/chmeetings-automation/SKILL.md b/chmeetings-automation/SKILL.md new file mode 100644 index 0000000..e633708 --- /dev/null +++ b/chmeetings-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: chmeetings-automation +description: "Automate Chmeetings tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Chmeetings Automation via Rube MCP + +Automate Chmeetings operations through Composio's Chmeetings toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/chmeetings](https://composio.dev/toolkits/chmeetings) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Chmeetings connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chmeetings` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `chmeetings` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Chmeetings operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Chmeetings task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["chmeetings"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Chmeetings-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `chmeetings` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cincopa-automation/SKILL.md b/cincopa-automation/SKILL.md new file mode 100644 index 0000000..f814e4c --- /dev/null +++ b/cincopa-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cincopa-automation +description: "Automate Cincopa tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cincopa Automation via Rube MCP + +Automate Cincopa operations through Composio's Cincopa toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cincopa](https://composio.dev/toolkits/cincopa) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cincopa connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cincopa` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cincopa` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cincopa operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cincopa task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cincopa"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cincopa-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cincopa` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/circleci-automation/SKILL.md b/circleci-automation/SKILL.md index bc2ee72..f1b4b06 100644 --- a/circleci-automation/SKILL.md +++ b/circleci-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate CircleCI CI/CD operations through Composio's CircleCI toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/circleci](https://composio.dev/toolkits/circleci) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -175,3 +177,6 @@ Format: {vcs_type}/{org_name}/{repo_name} | Get job details | CIRCLECI_GET_JOB_DETAILS | project_slug, job_number | | Get job artifacts | CIRCLECI_GET_JOB_ARTIFACTS | project_slug, job_number | | Get test metadata | CIRCLECI_GET_TEST_METADATA | project_slug, job_number | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/claid-ai-automation/SKILL.md b/claid-ai-automation/SKILL.md new file mode 100644 index 0000000..94964ed --- /dev/null +++ b/claid-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: claid-ai-automation +description: "Automate Claid AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Claid AI Automation via Rube MCP + +Automate Claid AI operations through Composio's Claid AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/claid_ai](https://composio.dev/toolkits/claid_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Claid AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `claid_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `claid_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Claid AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Claid AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["claid_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Claid AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `claid_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/classmarker-automation/SKILL.md b/classmarker-automation/SKILL.md new file mode 100644 index 0000000..c6eaea4 --- /dev/null +++ b/classmarker-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: classmarker-automation +description: "Automate Classmarker tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Classmarker Automation via Rube MCP + +Automate Classmarker operations through Composio's Classmarker toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/classmarker](https://composio.dev/toolkits/classmarker) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Classmarker connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `classmarker` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `classmarker` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Classmarker operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Classmarker task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["classmarker"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Classmarker-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `classmarker` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/clearout-automation/SKILL.md b/clearout-automation/SKILL.md new file mode 100644 index 0000000..500c334 --- /dev/null +++ b/clearout-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: clearout-automation +description: "Automate Clearout tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Clearout Automation via Rube MCP + +Automate Clearout operations through Composio's Clearout toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/clearout](https://composio.dev/toolkits/clearout) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Clearout connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `clearout` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clearout` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Clearout operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Clearout task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["clearout"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Clearout-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `clearout` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/clickmeeting-automation/SKILL.md b/clickmeeting-automation/SKILL.md new file mode 100644 index 0000000..67002b6 --- /dev/null +++ b/clickmeeting-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: clickmeeting-automation +description: "Automate Clickmeeting tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Clickmeeting Automation via Rube MCP + +Automate Clickmeeting operations through Composio's Clickmeeting toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/clickmeeting](https://composio.dev/toolkits/clickmeeting) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Clickmeeting connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `clickmeeting` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clickmeeting` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Clickmeeting operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Clickmeeting task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["clickmeeting"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Clickmeeting-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `clickmeeting` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/clickup-automation/SKILL.md b/clickup-automation/SKILL.md index 91c9448..f67d87d 100644 --- a/clickup-automation/SKILL.md +++ b/clickup-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate ClickUp project management workflows including task creation and updates, workspace hierarchy navigation, comments, and team member management through Composio's ClickUp toolkit. +**Toolkit docs**: [composio.dev/toolkits/clickup](https://composio.dev/toolkits/clickup) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -232,3 +234,6 @@ Always resolve names to IDs through the hierarchy: | List user groups | `CLICKUP_GET_TEAMS` | `team_id` | | Get user details | `CLICKUP_GET_USER` | `team_id`, `user_id` | | Custom roles | `CLICKUP_GET_CUSTOM_ROLES` | `team_id` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/clockify-automation/SKILL.md b/clockify-automation/SKILL.md new file mode 100644 index 0000000..283f4ed --- /dev/null +++ b/clockify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: clockify-automation +description: "Automate Clockify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Clockify Automation via Rube MCP + +Automate Clockify operations through Composio's Clockify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/clockify](https://composio.dev/toolkits/clockify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Clockify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `clockify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clockify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Clockify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Clockify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["clockify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Clockify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `clockify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/close-automation/SKILL.md b/close-automation/SKILL.md index 4453b10..d662f36 100644 --- a/close-automation/SKILL.md +++ b/close-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Close CRM operations through Composio's Close toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/close](https://composio.dev/toolkits/close) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -210,3 +212,6 @@ Close data model: | Create task | CLOSE_CREATE_TASK | lead_id, text, date, assigned_to | | Get note | CLOSE_GET_NOTE | note_id | | Delete call | CLOSE_DELETE_CALL | call_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudcart-automation/SKILL.md b/cloudcart-automation/SKILL.md new file mode 100644 index 0000000..0e1d519 --- /dev/null +++ b/cloudcart-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudcart-automation +description: "Automate Cloudcart tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudcart Automation via Rube MCP + +Automate Cloudcart operations through Composio's Cloudcart toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudcart](https://composio.dev/toolkits/cloudcart) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudcart connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudcart` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudcart` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudcart operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudcart task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudcart"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudcart-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudcart` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudconvert-automation/SKILL.md b/cloudconvert-automation/SKILL.md new file mode 100644 index 0000000..223ea95 --- /dev/null +++ b/cloudconvert-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudconvert-automation +description: "Automate Cloudconvert tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudconvert Automation via Rube MCP + +Automate Cloudconvert operations through Composio's Cloudconvert toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudconvert](https://composio.dev/toolkits/cloudconvert) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudconvert connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudconvert` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudconvert` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudconvert operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudconvert task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudconvert"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudconvert-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudconvert` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudflare-api-key-automation/SKILL.md b/cloudflare-api-key-automation/SKILL.md new file mode 100644 index 0000000..1459f4c --- /dev/null +++ b/cloudflare-api-key-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudflare-api-key-automation +description: "Automate Cloudflare API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudflare API Automation via Rube MCP + +Automate Cloudflare API operations through Composio's Cloudflare API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudflare_api_key](https://composio.dev/toolkits/cloudflare_api_key) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudflare API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare_api_key` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare_api_key` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudflare API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudflare API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudflare_api_key"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudflare API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare_api_key` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudflare-automation/SKILL.md b/cloudflare-automation/SKILL.md new file mode 100644 index 0000000..4ee3239 --- /dev/null +++ b/cloudflare-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudflare-automation +description: "Automate Cloudflare tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudflare Automation via Rube MCP + +Automate Cloudflare operations through Composio's Cloudflare toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudflare](https://composio.dev/toolkits/cloudflare) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudflare connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudflare operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudflare task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudflare"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudflare-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudflare-browser-rendering-automation/SKILL.md b/cloudflare-browser-rendering-automation/SKILL.md new file mode 100644 index 0000000..ee50966 --- /dev/null +++ b/cloudflare-browser-rendering-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudflare-browser-rendering-automation +description: "Automate Cloudflare Browser Rendering tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudflare Browser Rendering Automation via Rube MCP + +Automate Cloudflare Browser Rendering operations through Composio's Cloudflare Browser Rendering toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudflare_browser_rendering](https://composio.dev/toolkits/cloudflare_browser_rendering) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudflare Browser Rendering connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare_browser_rendering` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare_browser_rendering` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudflare Browser Rendering operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudflare Browser Rendering task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudflare_browser_rendering"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudflare Browser Rendering-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudflare_browser_rendering` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudinary-automation/SKILL.md b/cloudinary-automation/SKILL.md new file mode 100644 index 0000000..86fe920 --- /dev/null +++ b/cloudinary-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudinary-automation +description: "Automate Cloudinary tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudinary Automation via Rube MCP + +Automate Cloudinary operations through Composio's Cloudinary toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudinary](https://composio.dev/toolkits/cloudinary) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudinary connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudinary` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudinary` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudinary operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudinary task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudinary"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudinary-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudinary` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudlayer-automation/SKILL.md b/cloudlayer-automation/SKILL.md new file mode 100644 index 0000000..44079e2 --- /dev/null +++ b/cloudlayer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudlayer-automation +description: "Automate Cloudlayer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudlayer Automation via Rube MCP + +Automate Cloudlayer operations through Composio's Cloudlayer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudlayer](https://composio.dev/toolkits/cloudlayer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudlayer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudlayer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudlayer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudlayer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudlayer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudlayer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudlayer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudlayer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cloudpress-automation/SKILL.md b/cloudpress-automation/SKILL.md new file mode 100644 index 0000000..0e592df --- /dev/null +++ b/cloudpress-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cloudpress-automation +description: "Automate Cloudpress tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cloudpress Automation via Rube MCP + +Automate Cloudpress operations through Composio's Cloudpress toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cloudpress](https://composio.dev/toolkits/cloudpress) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cloudpress connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudpress` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudpress` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cloudpress operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cloudpress task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cloudpress"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cloudpress-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cloudpress` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/coassemble-automation/SKILL.md b/coassemble-automation/SKILL.md new file mode 100644 index 0000000..6a3136a --- /dev/null +++ b/coassemble-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: coassemble-automation +description: "Automate Coassemble tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Coassemble Automation via Rube MCP + +Automate Coassemble operations through Composio's Coassemble toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/coassemble](https://composio.dev/toolkits/coassemble) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Coassemble connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coassemble` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `coassemble` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Coassemble operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Coassemble task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["coassemble"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Coassemble-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `coassemble` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/coda-automation/SKILL.md b/coda-automation/SKILL.md index 55a0eba..9ce0326 100644 --- a/coda-automation/SKILL.md +++ b/coda-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Coda document and data operations through Composio's Coda toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/coda](https://composio.dev/toolkits/coda) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -239,3 +241,6 @@ Automate Coda document and data operations through Composio's Coda toolkit via R | Publish doc | CODA_PUBLISH_DOC | docId, slug | | Unpublish doc | CODA_UNPUBLISH_DOC | docId | | List packs | CODA_LIST_PACKS | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/codacy-automation/SKILL.md b/codacy-automation/SKILL.md new file mode 100644 index 0000000..0179d90 --- /dev/null +++ b/codacy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: codacy-automation +description: "Automate Codacy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Codacy Automation via Rube MCP + +Automate Codacy operations through Composio's Codacy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/codacy](https://composio.dev/toolkits/codacy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Codacy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `codacy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `codacy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Codacy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Codacy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["codacy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Codacy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `codacy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/codeinterpreter-automation/SKILL.md b/codeinterpreter-automation/SKILL.md new file mode 100644 index 0000000..1f56fb0 --- /dev/null +++ b/codeinterpreter-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: codeinterpreter-automation +description: "Automate Codeinterpreter tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Codeinterpreter Automation via Rube MCP + +Automate Codeinterpreter operations through Composio's Codeinterpreter toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/codeinterpreter](https://composio.dev/toolkits/codeinterpreter) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Codeinterpreter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `codeinterpreter` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `codeinterpreter` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Codeinterpreter operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Codeinterpreter task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["codeinterpreter"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Codeinterpreter-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `codeinterpreter` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/codereadr-automation/SKILL.md b/codereadr-automation/SKILL.md new file mode 100644 index 0000000..2256df6 --- /dev/null +++ b/codereadr-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: codereadr-automation +description: "Automate Codereadr tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Codereadr Automation via Rube MCP + +Automate Codereadr operations through Composio's Codereadr toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/codereadr](https://composio.dev/toolkits/codereadr) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Codereadr connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `codereadr` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `codereadr` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Codereadr operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Codereadr task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["codereadr"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Codereadr-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `codereadr` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/coinbase-automation/SKILL.md b/coinbase-automation/SKILL.md new file mode 100644 index 0000000..2953207 --- /dev/null +++ b/coinbase-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: coinbase-automation +description: "Automate Coinbase tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Coinbase Automation via Rube MCP + +Automate Coinbase operations through Composio's Coinbase toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/coinbase](https://composio.dev/toolkits/coinbase) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Coinbase connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coinbase` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `coinbase` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Coinbase operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Coinbase task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["coinbase"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Coinbase-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `coinbase` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/coinmarketcal-automation/SKILL.md b/coinmarketcal-automation/SKILL.md new file mode 100644 index 0000000..ca2883f --- /dev/null +++ b/coinmarketcal-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: coinmarketcal-automation +description: "Automate Coinmarketcal tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Coinmarketcal Automation via Rube MCP + +Automate Coinmarketcal operations through Composio's Coinmarketcal toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/coinmarketcal](https://composio.dev/toolkits/coinmarketcal) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Coinmarketcal connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcal` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcal` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Coinmarketcal operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Coinmarketcal task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["coinmarketcal"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Coinmarketcal-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcal` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/coinmarketcap-automation/SKILL.md b/coinmarketcap-automation/SKILL.md new file mode 100644 index 0000000..c6eca82 --- /dev/null +++ b/coinmarketcap-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: coinmarketcap-automation +description: "Automate Coinmarketcap tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Coinmarketcap Automation via Rube MCP + +Automate Coinmarketcap operations through Composio's Coinmarketcap toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/coinmarketcap](https://composio.dev/toolkits/coinmarketcap) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Coinmarketcap connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcap` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcap` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Coinmarketcap operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Coinmarketcap task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["coinmarketcap"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Coinmarketcap-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcap` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/coinranking-automation/SKILL.md b/coinranking-automation/SKILL.md new file mode 100644 index 0000000..e71a57e --- /dev/null +++ b/coinranking-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: coinranking-automation +description: "Automate Coinranking tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Coinranking Automation via Rube MCP + +Automate Coinranking operations through Composio's Coinranking toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/coinranking](https://composio.dev/toolkits/coinranking) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Coinranking connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coinranking` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `coinranking` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Coinranking operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Coinranking task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["coinranking"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Coinranking-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `coinranking` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/college-football-data-automation/SKILL.md b/college-football-data-automation/SKILL.md new file mode 100644 index 0000000..bbe995c --- /dev/null +++ b/college-football-data-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: college-football-data-automation +description: "Automate College Football Data tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# College Football Data Automation via Rube MCP + +Automate College Football Data operations through Composio's College Football Data toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/college_football_data](https://composio.dev/toolkits/college_football_data) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active College Football Data connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `college_football_data` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `college_football_data` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "College Football Data operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific College Football Data task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["college_football_data"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with College Football Data-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `college_football_data` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/composio-automation/SKILL.md b/composio-automation/SKILL.md new file mode 100644 index 0000000..f8a396e --- /dev/null +++ b/composio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: composio-automation +description: "Automate Composio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Composio Automation via Rube MCP + +Automate Composio operations through Composio's Composio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/composio](https://composio.dev/toolkits/composio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Composio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `composio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `composio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Composio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Composio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["composio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Composio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `composio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/composio-search-automation/SKILL.md b/composio-search-automation/SKILL.md new file mode 100644 index 0000000..9c8d71c --- /dev/null +++ b/composio-search-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: composio-search-automation +description: "Automate Composio Search tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Composio Search Automation via Rube MCP + +Automate Composio Search operations through Composio's Composio Search toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/composio_search](https://composio.dev/toolkits/composio_search) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Composio Search connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `composio_search` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `composio_search` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Composio Search operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Composio Search task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["composio_search"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Composio Search-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `composio_search` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/confluence-automation/SKILL.md b/confluence-automation/SKILL.md index 0f90ed1..0c6e78b 100644 --- a/confluence-automation/SKILL.md +++ b/confluence-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Confluence operations including page creation and updates, content search with CQL, space management, label tagging, and page hierarchy navigation through Composio's Confluence toolkit. +**Toolkit docs**: [composio.dev/toolkits/confluence](https://composio.dev/toolkits/confluence) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -206,3 +208,6 @@ Confluence uses two pagination styles: | Add label | `CONFLUENCE_ADD_CONTENT_LABEL` | content ID, label | | Page versions | `CONFLUENCE_GET_PAGE_VERSIONS` | `id` | | Space labels | `CONFLUENCE_GET_LABELS_FOR_SPACE` | space ID | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/connecteam-automation/SKILL.md b/connecteam-automation/SKILL.md new file mode 100644 index 0000000..0c052a2 --- /dev/null +++ b/connecteam-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: connecteam-automation +description: "Automate Connecteam tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Connecteam Automation via Rube MCP + +Automate Connecteam operations through Composio's Connecteam toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/connecteam](https://composio.dev/toolkits/connecteam) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Connecteam connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `connecteam` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `connecteam` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Connecteam operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Connecteam task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["connecteam"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Connecteam-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `connecteam` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/contentful-automation/SKILL.md b/contentful-automation/SKILL.md new file mode 100644 index 0000000..356a191 --- /dev/null +++ b/contentful-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: contentful-automation +description: "Automate Contentful tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Contentful Automation via Rube MCP + +Automate Contentful operations through Composio's Contentful toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/contentful](https://composio.dev/toolkits/contentful) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Contentful connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `contentful` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `contentful` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Contentful operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Contentful task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["contentful"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Contentful-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `contentful` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/contentful-graphql-automation/SKILL.md b/contentful-graphql-automation/SKILL.md new file mode 100644 index 0000000..ecbfd3c --- /dev/null +++ b/contentful-graphql-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: contentful-graphql-automation +description: "Automate Contentful Graphql tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Contentful Graphql Automation via Rube MCP + +Automate Contentful Graphql operations through Composio's Contentful Graphql toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/contentful_graphql](https://composio.dev/toolkits/contentful_graphql) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Contentful Graphql connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `contentful_graphql` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `contentful_graphql` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Contentful Graphql operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Contentful Graphql task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["contentful_graphql"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Contentful Graphql-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `contentful_graphql` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/control-d-automation/SKILL.md b/control-d-automation/SKILL.md new file mode 100644 index 0000000..e6be5e5 --- /dev/null +++ b/control-d-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: control-d-automation +description: "Automate Control D tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Control D Automation via Rube MCP + +Automate Control D operations through Composio's Control D toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/control_d](https://composio.dev/toolkits/control_d) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Control D connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `control_d` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `control_d` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Control D operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Control D task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["control_d"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Control D-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `control_d` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/conversion-tools-automation/SKILL.md b/conversion-tools-automation/SKILL.md new file mode 100644 index 0000000..1f443a6 --- /dev/null +++ b/conversion-tools-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: conversion-tools-automation +description: "Automate Conversion Tools tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Conversion Tools Automation via Rube MCP + +Automate Conversion Tools operations through Composio's Conversion Tools toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/conversion_tools](https://composio.dev/toolkits/conversion_tools) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Conversion Tools connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `conversion_tools` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `conversion_tools` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Conversion Tools operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Conversion Tools task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["conversion_tools"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Conversion Tools-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `conversion_tools` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/convertapi-automation/SKILL.md b/convertapi-automation/SKILL.md new file mode 100644 index 0000000..c07d1d1 --- /dev/null +++ b/convertapi-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: convertapi-automation +description: "Automate Convertapi tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Convertapi Automation via Rube MCP + +Automate Convertapi operations through Composio's Convertapi toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/convertapi](https://composio.dev/toolkits/convertapi) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Convertapi connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `convertapi` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `convertapi` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Convertapi operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Convertapi task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["convertapi"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Convertapi-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `convertapi` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/convertkit-automation/SKILL.md b/convertkit-automation/SKILL.md index 15b0841..9ec6f21 100644 --- a/convertkit-automation/SKILL.md +++ b/convertkit-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate ConvertKit (now known as Kit) email marketing operations through Composio's Kit toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/kit](https://composio.dev/toolkits/kit) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -193,3 +195,6 @@ Kit uses cursor-based pagination: | Get broadcast | KIT_GET_BROADCAST | id | | Get broadcast stats | KIT_GET_BROADCAST_STATS | id | | Delete broadcast | KIT_DELETE_BROADCAST | id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/conveyor-automation/SKILL.md b/conveyor-automation/SKILL.md new file mode 100644 index 0000000..0494461 --- /dev/null +++ b/conveyor-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: conveyor-automation +description: "Automate Conveyor tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Conveyor Automation via Rube MCP + +Automate Conveyor operations through Composio's Conveyor toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/conveyor](https://composio.dev/toolkits/conveyor) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Conveyor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `conveyor` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `conveyor` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Conveyor operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Conveyor task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["conveyor"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Conveyor-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `conveyor` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/convolo-ai-automation/SKILL.md b/convolo-ai-automation/SKILL.md new file mode 100644 index 0000000..2f91570 --- /dev/null +++ b/convolo-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: convolo-ai-automation +description: "Automate Convolo AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Convolo AI Automation via Rube MCP + +Automate Convolo AI operations through Composio's Convolo AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/convolo_ai](https://composio.dev/toolkits/convolo_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Convolo AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `convolo_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `convolo_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Convolo AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Convolo AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["convolo_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Convolo AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `convolo_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/corrently-automation/SKILL.md b/corrently-automation/SKILL.md new file mode 100644 index 0000000..dcb1449 --- /dev/null +++ b/corrently-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: corrently-automation +description: "Automate Corrently tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Corrently Automation via Rube MCP + +Automate Corrently operations through Composio's Corrently toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/corrently](https://composio.dev/toolkits/corrently) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Corrently connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `corrently` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `corrently` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Corrently operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Corrently task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["corrently"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Corrently-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `corrently` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/countdown-api-automation/SKILL.md b/countdown-api-automation/SKILL.md new file mode 100644 index 0000000..807c97c --- /dev/null +++ b/countdown-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: countdown-api-automation +description: "Automate Countdown API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Countdown API Automation via Rube MCP + +Automate Countdown API operations through Composio's Countdown API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/countdown_api](https://composio.dev/toolkits/countdown_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Countdown API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `countdown_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `countdown_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Countdown API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Countdown API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["countdown_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Countdown API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `countdown_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/coupa-automation/SKILL.md b/coupa-automation/SKILL.md new file mode 100644 index 0000000..d00abb4 --- /dev/null +++ b/coupa-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: coupa-automation +description: "Automate Coupa tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Coupa Automation via Rube MCP + +Automate Coupa operations through Composio's Coupa toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/coupa](https://composio.dev/toolkits/coupa) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Coupa connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `coupa` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `coupa` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Coupa operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Coupa task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["coupa"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Coupa-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `coupa` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/craftmypdf-automation/SKILL.md b/craftmypdf-automation/SKILL.md new file mode 100644 index 0000000..52dfa2b --- /dev/null +++ b/craftmypdf-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: craftmypdf-automation +description: "Automate Craftmypdf tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Craftmypdf Automation via Rube MCP + +Automate Craftmypdf operations through Composio's Craftmypdf toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/craftmypdf](https://composio.dev/toolkits/craftmypdf) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Craftmypdf connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `craftmypdf` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `craftmypdf` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Craftmypdf operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Craftmypdf task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["craftmypdf"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Craftmypdf-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `craftmypdf` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/crowdin-automation/SKILL.md b/crowdin-automation/SKILL.md new file mode 100644 index 0000000..0ec36de --- /dev/null +++ b/crowdin-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: crowdin-automation +description: "Automate Crowdin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Crowdin Automation via Rube MCP + +Automate Crowdin operations through Composio's Crowdin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/crowdin](https://composio.dev/toolkits/crowdin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Crowdin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `crowdin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `crowdin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Crowdin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Crowdin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["crowdin"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Crowdin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `crowdin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/crustdata-automation/SKILL.md b/crustdata-automation/SKILL.md new file mode 100644 index 0000000..61d1f7e --- /dev/null +++ b/crustdata-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: crustdata-automation +description: "Automate Crustdata tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Crustdata Automation via Rube MCP + +Automate Crustdata operations through Composio's Crustdata toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/crustdata](https://composio.dev/toolkits/crustdata) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Crustdata connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `crustdata` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `crustdata` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Crustdata operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Crustdata task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["crustdata"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Crustdata-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `crustdata` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cults-automation/SKILL.md b/cults-automation/SKILL.md new file mode 100644 index 0000000..b28e7f6 --- /dev/null +++ b/cults-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cults-automation +description: "Automate Cults tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cults Automation via Rube MCP + +Automate Cults operations through Composio's Cults toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cults](https://composio.dev/toolkits/cults) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cults connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cults` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cults` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cults operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cults task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cults"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cults-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cults` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/curated-automation/SKILL.md b/curated-automation/SKILL.md new file mode 100644 index 0000000..ea9d2c6 --- /dev/null +++ b/curated-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: curated-automation +description: "Automate Curated tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Curated Automation via Rube MCP + +Automate Curated operations through Composio's Curated toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/curated](https://composio.dev/toolkits/curated) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Curated connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `curated` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `curated` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Curated operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Curated task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["curated"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Curated-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `curated` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/currents-api-automation/SKILL.md b/currents-api-automation/SKILL.md new file mode 100644 index 0000000..83e3f97 --- /dev/null +++ b/currents-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: currents-api-automation +description: "Automate Currents API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Currents API Automation via Rube MCP + +Automate Currents API operations through Composio's Currents API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/currents_api](https://composio.dev/toolkits/currents_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Currents API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `currents_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `currents_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Currents API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Currents API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["currents_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Currents API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `currents_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/customerio-automation/SKILL.md b/customerio-automation/SKILL.md new file mode 100644 index 0000000..3516bfc --- /dev/null +++ b/customerio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: customerio-automation +description: "Automate Customerio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Customerio Automation via Rube MCP + +Automate Customerio operations through Composio's Customerio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/customerio](https://composio.dev/toolkits/customerio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Customerio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `customerio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `customerio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Customerio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Customerio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["customerio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Customerio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `customerio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/customgpt-automation/SKILL.md b/customgpt-automation/SKILL.md new file mode 100644 index 0000000..ec956c1 --- /dev/null +++ b/customgpt-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: customgpt-automation +description: "Automate Customgpt tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Customgpt Automation via Rube MCP + +Automate Customgpt operations through Composio's Customgpt toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/customgpt](https://composio.dev/toolkits/customgpt) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Customgpt connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `customgpt` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `customgpt` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Customgpt operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Customgpt task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["customgpt"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Customgpt-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `customgpt` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/customjs-automation/SKILL.md b/customjs-automation/SKILL.md new file mode 100644 index 0000000..9083e54 --- /dev/null +++ b/customjs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: customjs-automation +description: "Automate Customjs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Customjs Automation via Rube MCP + +Automate Customjs operations through Composio's Customjs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/customjs](https://composio.dev/toolkits/customjs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Customjs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `customjs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `customjs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Customjs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Customjs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["customjs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Customjs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `customjs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/cutt-ly-automation/SKILL.md b/cutt-ly-automation/SKILL.md new file mode 100644 index 0000000..a91a4f2 --- /dev/null +++ b/cutt-ly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: cutt-ly-automation +description: "Automate Cutt Ly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Cutt Ly Automation via Rube MCP + +Automate Cutt Ly operations through Composio's Cutt Ly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/cutt_ly](https://composio.dev/toolkits/cutt_ly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Cutt Ly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cutt_ly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cutt_ly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Cutt Ly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Cutt Ly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["cutt_ly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Cutt Ly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `cutt_ly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/d2lbrightspace-automation/SKILL.md b/d2lbrightspace-automation/SKILL.md new file mode 100644 index 0000000..4d9f571 --- /dev/null +++ b/d2lbrightspace-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: d2lbrightspace-automation +description: "Automate D2lbrightspace tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# D2lbrightspace Automation via Rube MCP + +Automate D2lbrightspace operations through Composio's D2lbrightspace toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/d2lbrightspace](https://composio.dev/toolkits/d2lbrightspace) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active D2lbrightspace connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `d2lbrightspace` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `d2lbrightspace` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "D2lbrightspace operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific D2lbrightspace task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["d2lbrightspace"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with D2lbrightspace-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `d2lbrightspace` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dadata-ru-automation/SKILL.md b/dadata-ru-automation/SKILL.md new file mode 100644 index 0000000..24dd5f0 --- /dev/null +++ b/dadata-ru-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dadata-ru-automation +description: "Automate Dadata Ru tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dadata Ru Automation via Rube MCP + +Automate Dadata Ru operations through Composio's Dadata Ru toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dadata_ru](https://composio.dev/toolkits/dadata_ru) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dadata Ru connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dadata_ru` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dadata_ru` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dadata Ru operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dadata Ru task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dadata_ru"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dadata Ru-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dadata_ru` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/daffy-automation/SKILL.md b/daffy-automation/SKILL.md new file mode 100644 index 0000000..599ba5c --- /dev/null +++ b/daffy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: daffy-automation +description: "Automate Daffy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Daffy Automation via Rube MCP + +Automate Daffy operations through Composio's Daffy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/daffy](https://composio.dev/toolkits/daffy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Daffy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `daffy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `daffy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Daffy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Daffy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["daffy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Daffy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `daffy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dailybot-automation/SKILL.md b/dailybot-automation/SKILL.md new file mode 100644 index 0000000..a7e9d00 --- /dev/null +++ b/dailybot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dailybot-automation +description: "Automate Dailybot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dailybot Automation via Rube MCP + +Automate Dailybot operations through Composio's Dailybot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dailybot](https://composio.dev/toolkits/dailybot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dailybot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dailybot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dailybot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dailybot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dailybot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dailybot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dailybot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dailybot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/datadog-automation/SKILL.md b/datadog-automation/SKILL.md index 3cb9f3f..92113be 100644 --- a/datadog-automation/SKILL.md +++ b/datadog-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Datadog monitoring and observability operations through Composio's Datadog toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/datadog](https://composio.dev/toolkits/datadog) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -233,3 +235,6 @@ logs("service:web status:error").index("main").rollup("count").last("5m") > 10 | Create downtime | DATADOG_CREATE_DOWNTIME | scope, start, end | | List hosts | DATADOG_LIST_HOSTS | filter, sort_field | | Get trace | DATADOG_GET_TRACE_BY_ID | trace_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/datagma-automation/SKILL.md b/datagma-automation/SKILL.md new file mode 100644 index 0000000..34b313e --- /dev/null +++ b/datagma-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: datagma-automation +description: "Automate Datagma tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Datagma Automation via Rube MCP + +Automate Datagma operations through Composio's Datagma toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/datagma](https://composio.dev/toolkits/datagma) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Datagma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datagma` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `datagma` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Datagma operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Datagma task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["datagma"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Datagma-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `datagma` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/datarobot-automation/SKILL.md b/datarobot-automation/SKILL.md new file mode 100644 index 0000000..32267ed --- /dev/null +++ b/datarobot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: datarobot-automation +description: "Automate Datarobot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Datarobot Automation via Rube MCP + +Automate Datarobot operations through Composio's Datarobot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/datarobot](https://composio.dev/toolkits/datarobot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Datarobot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datarobot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `datarobot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Datarobot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Datarobot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["datarobot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Datarobot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `datarobot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/deadline-funnel-automation/SKILL.md b/deadline-funnel-automation/SKILL.md new file mode 100644 index 0000000..4066d92 --- /dev/null +++ b/deadline-funnel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: deadline-funnel-automation +description: "Automate Deadline Funnel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Deadline Funnel Automation via Rube MCP + +Automate Deadline Funnel operations through Composio's Deadline Funnel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/deadline_funnel](https://composio.dev/toolkits/deadline_funnel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Deadline Funnel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `deadline_funnel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `deadline_funnel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Deadline Funnel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Deadline Funnel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["deadline_funnel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Deadline Funnel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `deadline_funnel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/deel-automation/SKILL.md b/deel-automation/SKILL.md new file mode 100644 index 0000000..1d2b044 --- /dev/null +++ b/deel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: deel-automation +description: "Automate Deel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Deel Automation via Rube MCP + +Automate Deel operations through Composio's Deel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/deel](https://composio.dev/toolkits/deel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Deel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `deel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `deel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Deel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Deel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["deel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Deel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `deel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/deepgram-automation/SKILL.md b/deepgram-automation/SKILL.md new file mode 100644 index 0000000..cbf3fd6 --- /dev/null +++ b/deepgram-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: deepgram-automation +description: "Automate Deepgram tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Deepgram Automation via Rube MCP + +Automate Deepgram operations through Composio's Deepgram toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/deepgram](https://composio.dev/toolkits/deepgram) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Deepgram connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `deepgram` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `deepgram` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Deepgram operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Deepgram task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["deepgram"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Deepgram-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `deepgram` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/demio-automation/SKILL.md b/demio-automation/SKILL.md new file mode 100644 index 0000000..21543c9 --- /dev/null +++ b/demio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: demio-automation +description: "Automate Demio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Demio Automation via Rube MCP + +Automate Demio operations through Composio's Demio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/demio](https://composio.dev/toolkits/demio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Demio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `demio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `demio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Demio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Demio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["demio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Demio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `demio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/desktime-automation/SKILL.md b/desktime-automation/SKILL.md new file mode 100644 index 0000000..c4d2833 --- /dev/null +++ b/desktime-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: desktime-automation +description: "Automate Desktime tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Desktime Automation via Rube MCP + +Automate Desktime operations through Composio's Desktime toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/desktime](https://composio.dev/toolkits/desktime) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Desktime connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `desktime` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `desktime` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Desktime operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Desktime task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["desktime"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Desktime-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `desktime` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/detrack-automation/SKILL.md b/detrack-automation/SKILL.md new file mode 100644 index 0000000..1de64fd --- /dev/null +++ b/detrack-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: detrack-automation +description: "Automate Detrack tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Detrack Automation via Rube MCP + +Automate Detrack operations through Composio's Detrack toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/detrack](https://composio.dev/toolkits/detrack) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Detrack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `detrack` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `detrack` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Detrack operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Detrack task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["detrack"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Detrack-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `detrack` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dialmycalls-automation/SKILL.md b/dialmycalls-automation/SKILL.md new file mode 100644 index 0000000..48845a4 --- /dev/null +++ b/dialmycalls-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dialmycalls-automation +description: "Automate Dialmycalls tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dialmycalls Automation via Rube MCP + +Automate Dialmycalls operations through Composio's Dialmycalls toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dialmycalls](https://composio.dev/toolkits/dialmycalls) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dialmycalls connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dialmycalls` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dialmycalls` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dialmycalls operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dialmycalls task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dialmycalls"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dialmycalls-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dialmycalls` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dialpad-automation/SKILL.md b/dialpad-automation/SKILL.md new file mode 100644 index 0000000..e9ad8f9 --- /dev/null +++ b/dialpad-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dialpad-automation +description: "Automate Dialpad tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dialpad Automation via Rube MCP + +Automate Dialpad operations through Composio's Dialpad toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dialpad](https://composio.dev/toolkits/dialpad) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dialpad connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dialpad` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dialpad` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dialpad operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dialpad task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dialpad"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dialpad-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dialpad` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dictionary-api-automation/SKILL.md b/dictionary-api-automation/SKILL.md new file mode 100644 index 0000000..d3bf09b --- /dev/null +++ b/dictionary-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dictionary-api-automation +description: "Automate Dictionary API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dictionary API Automation via Rube MCP + +Automate Dictionary API operations through Composio's Dictionary API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dictionary_api](https://composio.dev/toolkits/dictionary_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dictionary API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dictionary_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dictionary_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dictionary API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dictionary API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dictionary_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dictionary API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dictionary_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/diffbot-automation/SKILL.md b/diffbot-automation/SKILL.md new file mode 100644 index 0000000..82b943b --- /dev/null +++ b/diffbot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: diffbot-automation +description: "Automate Diffbot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Diffbot Automation via Rube MCP + +Automate Diffbot operations through Composio's Diffbot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/diffbot](https://composio.dev/toolkits/diffbot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Diffbot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `diffbot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `diffbot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Diffbot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Diffbot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["diffbot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Diffbot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `diffbot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/digicert-automation/SKILL.md b/digicert-automation/SKILL.md new file mode 100644 index 0000000..b84161d --- /dev/null +++ b/digicert-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: digicert-automation +description: "Automate Digicert tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Digicert Automation via Rube MCP + +Automate Digicert operations through Composio's Digicert toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/digicert](https://composio.dev/toolkits/digicert) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Digicert connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `digicert` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `digicert` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Digicert operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Digicert task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["digicert"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Digicert-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `digicert` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/digital-ocean-automation/SKILL.md b/digital-ocean-automation/SKILL.md new file mode 100644 index 0000000..3279a76 --- /dev/null +++ b/digital-ocean-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: digital-ocean-automation +description: "Automate DigitalOcean tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# DigitalOcean Automation via Rube MCP + +Automate DigitalOcean operations through Composio's DigitalOcean toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/digital_ocean](https://composio.dev/toolkits/digital_ocean) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active DigitalOcean connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `digital_ocean` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `digital_ocean` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "DigitalOcean operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific DigitalOcean task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["digital_ocean"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with DigitalOcean-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `digital_ocean` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/discord-automation/SKILL.md b/discord-automation/SKILL.md index ebe2947..c6a6bbc 100644 --- a/discord-automation/SKILL.md +++ b/discord-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Discord operations through Composio's Discord/Discordbot toolkits via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/discord](https://composio.dev/toolkits/discord) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -185,3 +187,6 @@ Permissions are combined using bitwise OR: | Clear reactions | DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS | channel_id, message_id | | Test auth | DISCORDBOT_TEST_AUTH | (none) | | Get channel | DISCORDBOT_GET_CHANNEL | channel_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/discordbot-automation/SKILL.md b/discordbot-automation/SKILL.md new file mode 100644 index 0000000..d8938a2 --- /dev/null +++ b/discordbot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: discordbot-automation +description: "Automate Discordbot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Discordbot Automation via Rube MCP + +Automate Discordbot operations through Composio's Discordbot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/discordbot](https://composio.dev/toolkits/discordbot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Discordbot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `discordbot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `discordbot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Discordbot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Discordbot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["discordbot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Discordbot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `discordbot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dnsfilter-automation/SKILL.md b/dnsfilter-automation/SKILL.md new file mode 100644 index 0000000..022945d --- /dev/null +++ b/dnsfilter-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dnsfilter-automation +description: "Automate Dnsfilter tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dnsfilter Automation via Rube MCP + +Automate Dnsfilter operations through Composio's Dnsfilter toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dnsfilter](https://composio.dev/toolkits/dnsfilter) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dnsfilter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dnsfilter` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dnsfilter` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dnsfilter operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dnsfilter task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dnsfilter"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dnsfilter-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dnsfilter` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dock-certs-automation/SKILL.md b/dock-certs-automation/SKILL.md new file mode 100644 index 0000000..d8df22b --- /dev/null +++ b/dock-certs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dock-certs-automation +description: "Automate Dock Certs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dock Certs Automation via Rube MCP + +Automate Dock Certs operations through Composio's Dock Certs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dock_certs](https://composio.dev/toolkits/dock_certs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dock Certs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dock_certs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dock_certs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dock Certs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dock Certs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dock_certs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dock Certs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dock_certs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docker-hub-automation/SKILL.md b/docker-hub-automation/SKILL.md new file mode 100644 index 0000000..dc6029f --- /dev/null +++ b/docker-hub-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docker-hub-automation +description: "Automate Docker Hub tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docker Hub Automation via Rube MCP + +Automate Docker Hub operations through Composio's Docker Hub toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docker_hub](https://composio.dev/toolkits/docker_hub) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docker Hub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docker Hub operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docker Hub task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docker_hub"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docker Hub-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docker_hub-automation/SKILL.md b/docker_hub-automation/SKILL.md new file mode 100644 index 0000000..f68f903 --- /dev/null +++ b/docker_hub-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: docker_hub-automation +description: "Automate Docker Hub tasks via Rube MCP (Composio): repositories, images, tags, and container registry management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docker Hub Automation via Rube MCP + +Automate Docker Hub operations through Composio's Docker Hub toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docker_hub](https://composio.dev/toolkits/docker_hub) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docker Hub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "repositories, images, tags, and container registry management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Docker Hub +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Docker Hub Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Docker Hub tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Docker Hub Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Docker Hub operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Docker Hub connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docker Hub-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docker_hub` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/docker_hub](https://composio.dev/toolkits/docker_hub) diff --git a/docmosis-automation/SKILL.md b/docmosis-automation/SKILL.md new file mode 100644 index 0000000..c36e956 --- /dev/null +++ b/docmosis-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docmosis-automation +description: "Automate Docmosis tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docmosis Automation via Rube MCP + +Automate Docmosis operations through Composio's Docmosis toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docmosis](https://composio.dev/toolkits/docmosis) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docmosis connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docmosis` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docmosis` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docmosis operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docmosis task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docmosis"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docmosis-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docmosis` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docnify-automation/SKILL.md b/docnify-automation/SKILL.md new file mode 100644 index 0000000..f2e37b3 --- /dev/null +++ b/docnify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docnify-automation +description: "Automate Docnify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docnify Automation via Rube MCP + +Automate Docnify operations through Composio's Docnify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docnify](https://composio.dev/toolkits/docnify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docnify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docnify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docnify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docnify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docnify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docnify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docnify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docnify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docsbot-ai-automation/SKILL.md b/docsbot-ai-automation/SKILL.md new file mode 100644 index 0000000..67ce8a7 --- /dev/null +++ b/docsbot-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docsbot-ai-automation +description: "Automate Docsbot AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docsbot AI Automation via Rube MCP + +Automate Docsbot AI operations through Composio's Docsbot AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docsbot_ai](https://composio.dev/toolkits/docsbot_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docsbot AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docsbot_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docsbot_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docsbot AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docsbot AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docsbot_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docsbot AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docsbot_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docsumo-automation/SKILL.md b/docsumo-automation/SKILL.md new file mode 100644 index 0000000..2ef4c5e --- /dev/null +++ b/docsumo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docsumo-automation +description: "Automate Docsumo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docsumo Automation via Rube MCP + +Automate Docsumo operations through Composio's Docsumo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docsumo](https://composio.dev/toolkits/docsumo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docsumo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docsumo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docsumo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docsumo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docsumo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docsumo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docsumo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docsumo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docugenerate-automation/SKILL.md b/docugenerate-automation/SKILL.md new file mode 100644 index 0000000..064cc23 --- /dev/null +++ b/docugenerate-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docugenerate-automation +description: "Automate Docugenerate tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docugenerate Automation via Rube MCP + +Automate Docugenerate operations through Composio's Docugenerate toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docugenerate](https://composio.dev/toolkits/docugenerate) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docugenerate connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docugenerate` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docugenerate` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docugenerate operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docugenerate task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docugenerate"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docugenerate-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docugenerate` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/documenso-automation/SKILL.md b/documenso-automation/SKILL.md new file mode 100644 index 0000000..72a6c63 --- /dev/null +++ b/documenso-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: documenso-automation +description: "Automate Documenso tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Documenso Automation via Rube MCP + +Automate Documenso operations through Composio's Documenso toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/documenso](https://composio.dev/toolkits/documenso) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Documenso connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `documenso` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `documenso` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Documenso operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Documenso task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["documenso"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Documenso-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `documenso` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/documint-automation/SKILL.md b/documint-automation/SKILL.md new file mode 100644 index 0000000..1002d65 --- /dev/null +++ b/documint-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: documint-automation +description: "Automate Documint tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Documint Automation via Rube MCP + +Automate Documint operations through Composio's Documint toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/documint](https://composio.dev/toolkits/documint) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Documint connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `documint` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `documint` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Documint operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Documint task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["documint"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Documint-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `documint` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docupilot-automation/SKILL.md b/docupilot-automation/SKILL.md new file mode 100644 index 0000000..9d11d78 --- /dev/null +++ b/docupilot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docupilot-automation +description: "Automate Docupilot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docupilot Automation via Rube MCP + +Automate Docupilot operations through Composio's Docupilot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docupilot](https://composio.dev/toolkits/docupilot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docupilot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docupilot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docupilot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docupilot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docupilot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docupilot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docupilot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docupilot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docupost-automation/SKILL.md b/docupost-automation/SKILL.md new file mode 100644 index 0000000..8abca26 --- /dev/null +++ b/docupost-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docupost-automation +description: "Automate Docupost tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docupost Automation via Rube MCP + +Automate Docupost operations through Composio's Docupost toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docupost](https://composio.dev/toolkits/docupost) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docupost connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docupost` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docupost` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docupost operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docupost task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docupost"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docupost-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docupost` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docuseal-automation/SKILL.md b/docuseal-automation/SKILL.md new file mode 100644 index 0000000..bb2a2da --- /dev/null +++ b/docuseal-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: docuseal-automation +description: "Automate Docuseal tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Docuseal Automation via Rube MCP + +Automate Docuseal operations through Composio's Docuseal toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/docuseal](https://composio.dev/toolkits/docuseal) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Docuseal connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docuseal` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docuseal` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Docuseal operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Docuseal task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["docuseal"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Docuseal-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `docuseal` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/docusign-automation/SKILL.md b/docusign-automation/SKILL.md index b3cb0c9..a6f6294 100644 --- a/docusign-automation/SKILL.md +++ b/docusign-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/docusign](https://composio.dev/toolkits/docusign) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -206,3 +208,6 @@ created (draft) -> sent -> delivered -> signed -> completed | Send envelope | DOCUSIGN_SEND_ENVELOPE | envelopeId | | Get envelope status | DOCUSIGN_GET_ENVELOPE | envelopeId | | Add template to envelope | DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE | envelopeId, documentId, templateId | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/doppler-marketing-automation-automation/SKILL.md b/doppler-marketing-automation-automation/SKILL.md new file mode 100644 index 0000000..a3f2ca2 --- /dev/null +++ b/doppler-marketing-automation-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: doppler-marketing-automation-automation +description: "Automate Doppler Marketing Automation tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Doppler Marketing Automation Automation via Rube MCP + +Automate Doppler Marketing Automation operations through Composio's Doppler Marketing Automation toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/doppler_marketing_automation](https://composio.dev/toolkits/doppler_marketing_automation) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Doppler Marketing Automation connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `doppler_marketing_automation` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `doppler_marketing_automation` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Doppler Marketing Automation operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Doppler Marketing Automation task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["doppler_marketing_automation"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Doppler Marketing Automation-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `doppler_marketing_automation` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/doppler-secretops-automation/SKILL.md b/doppler-secretops-automation/SKILL.md new file mode 100644 index 0000000..47063bc --- /dev/null +++ b/doppler-secretops-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: doppler-secretops-automation +description: "Automate Doppler Secretops tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Doppler Secretops Automation via Rube MCP + +Automate Doppler Secretops operations through Composio's Doppler Secretops toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/doppler_secretops](https://composio.dev/toolkits/doppler_secretops) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Doppler Secretops connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `doppler_secretops` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `doppler_secretops` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Doppler Secretops operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Doppler Secretops task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["doppler_secretops"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Doppler Secretops-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `doppler_secretops` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dotsimple-automation/SKILL.md b/dotsimple-automation/SKILL.md new file mode 100644 index 0000000..1172d0e --- /dev/null +++ b/dotsimple-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dotsimple-automation +description: "Automate Dotsimple tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dotsimple Automation via Rube MCP + +Automate Dotsimple operations through Composio's Dotsimple toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dotsimple](https://composio.dev/toolkits/dotsimple) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dotsimple connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dotsimple` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dotsimple` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dotsimple operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dotsimple task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dotsimple"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dotsimple-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dotsimple` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dovetail-automation/SKILL.md b/dovetail-automation/SKILL.md new file mode 100644 index 0000000..e3118f2 --- /dev/null +++ b/dovetail-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dovetail-automation +description: "Automate Dovetail tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dovetail Automation via Rube MCP + +Automate Dovetail operations through Composio's Dovetail toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dovetail](https://composio.dev/toolkits/dovetail) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dovetail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dovetail` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dovetail` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dovetail operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dovetail task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dovetail"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dovetail-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dovetail` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dpd2-automation/SKILL.md b/dpd2-automation/SKILL.md new file mode 100644 index 0000000..99de4e8 --- /dev/null +++ b/dpd2-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dpd2-automation +description: "Automate Dpd2 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dpd2 Automation via Rube MCP + +Automate Dpd2 operations through Composio's Dpd2 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dpd2](https://composio.dev/toolkits/dpd2) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dpd2 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dpd2` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dpd2` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dpd2 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dpd2 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dpd2"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dpd2-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dpd2` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/draftable-automation/SKILL.md b/draftable-automation/SKILL.md new file mode 100644 index 0000000..3790c8e --- /dev/null +++ b/draftable-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: draftable-automation +description: "Automate Draftable tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Draftable Automation via Rube MCP + +Automate Draftable operations through Composio's Draftable toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/draftable](https://composio.dev/toolkits/draftable) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Draftable connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `draftable` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `draftable` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Draftable operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Draftable task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["draftable"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Draftable-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `draftable` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dreamstudio-automation/SKILL.md b/dreamstudio-automation/SKILL.md new file mode 100644 index 0000000..1420e17 --- /dev/null +++ b/dreamstudio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dreamstudio-automation +description: "Automate Dreamstudio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dreamstudio Automation via Rube MCP + +Automate Dreamstudio operations through Composio's Dreamstudio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dreamstudio](https://composio.dev/toolkits/dreamstudio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dreamstudio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dreamstudio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dreamstudio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dreamstudio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dreamstudio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dreamstudio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dreamstudio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dreamstudio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/drip-jobs-automation/SKILL.md b/drip-jobs-automation/SKILL.md new file mode 100644 index 0000000..9b1af04 --- /dev/null +++ b/drip-jobs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: drip-jobs-automation +description: "Automate Drip Jobs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Drip Jobs Automation via Rube MCP + +Automate Drip Jobs operations through Composio's Drip Jobs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/drip_jobs](https://composio.dev/toolkits/drip_jobs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Drip Jobs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `drip_jobs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `drip_jobs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Drip Jobs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Drip Jobs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["drip_jobs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Drip Jobs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `drip_jobs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dripcel-automation/SKILL.md b/dripcel-automation/SKILL.md new file mode 100644 index 0000000..4942da7 --- /dev/null +++ b/dripcel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dripcel-automation +description: "Automate Dripcel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dripcel Automation via Rube MCP + +Automate Dripcel operations through Composio's Dripcel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dripcel](https://composio.dev/toolkits/dripcel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dripcel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dripcel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dripcel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dripcel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dripcel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dripcel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dripcel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dripcel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dromo-automation/SKILL.md b/dromo-automation/SKILL.md new file mode 100644 index 0000000..a1c5414 --- /dev/null +++ b/dromo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dromo-automation +description: "Automate Dromo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dromo Automation via Rube MCP + +Automate Dromo operations through Composio's Dromo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dromo](https://composio.dev/toolkits/dromo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dromo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dromo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dromo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dromo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dromo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dromo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dromo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dromo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dropbox-automation/SKILL.md b/dropbox-automation/SKILL.md index 35ccb52..31a9410 100644 --- a/dropbox-automation/SKILL.md +++ b/dropbox-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Dropbox operations including file upload/download, search, folder management, sharing links, batch operations, and metadata retrieval through Composio's Dropbox toolkit. +**Toolkit docs**: [composio.dev/toolkits/dropbox](https://composio.dev/toolkits/dropbox) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -228,3 +230,6 @@ Several Dropbox operations run asynchronously: | Delete batch | `DROPBOX_DELETE_BATCH` | `entries` | | Copy file/folder | `DROPBOX_COPY_FILE_OR_FOLDER` | `from_path`, `to_path` | | Check batch status | `DROPBOX_CHECK_MOVE_BATCH` | `async_job_id` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dropbox-sign-automation/SKILL.md b/dropbox-sign-automation/SKILL.md new file mode 100644 index 0000000..fcee2ca --- /dev/null +++ b/dropbox-sign-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dropbox-sign-automation +description: "Automate Dropbox Sign tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dropbox Sign Automation via Rube MCP + +Automate Dropbox Sign operations through Composio's Dropbox Sign toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dropbox_sign](https://composio.dev/toolkits/dropbox_sign) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dropbox Sign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dropbox_sign` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dropbox_sign` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dropbox Sign operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dropbox Sign task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dropbox_sign"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dropbox Sign-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dropbox_sign` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dropcontact-automation/SKILL.md b/dropcontact-automation/SKILL.md new file mode 100644 index 0000000..7606b45 --- /dev/null +++ b/dropcontact-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dropcontact-automation +description: "Automate Dropcontact tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dropcontact Automation via Rube MCP + +Automate Dropcontact operations through Composio's Dropcontact toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dropcontact](https://composio.dev/toolkits/dropcontact) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dropcontact connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dropcontact` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dropcontact` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dropcontact operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dropcontact task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dropcontact"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dropcontact-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dropcontact` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dungeon-fighter-online-automation/SKILL.md b/dungeon-fighter-online-automation/SKILL.md new file mode 100644 index 0000000..f107618 --- /dev/null +++ b/dungeon-fighter-online-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dungeon-fighter-online-automation +description: "Automate Dungeon Fighter Online tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dungeon Fighter Online Automation via Rube MCP + +Automate Dungeon Fighter Online operations through Composio's Dungeon Fighter Online toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dungeon_fighter_online](https://composio.dev/toolkits/dungeon_fighter_online) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dungeon Fighter Online connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dungeon_fighter_online` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dungeon_fighter_online` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dungeon Fighter Online operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dungeon Fighter Online task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dungeon_fighter_online"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dungeon Fighter Online-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dungeon_fighter_online` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/dynamics365-automation/SKILL.md b/dynamics365-automation/SKILL.md new file mode 100644 index 0000000..5aa5e13 --- /dev/null +++ b/dynamics365-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: dynamics365-automation +description: "Automate Dynamics365 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Dynamics365 Automation via Rube MCP + +Automate Dynamics365 operations through Composio's Dynamics365 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/dynamics365](https://composio.dev/toolkits/dynamics365) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Dynamics365 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dynamics365` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dynamics365` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Dynamics365 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Dynamics365 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["dynamics365"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Dynamics365-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dynamics365` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/echtpost-automation/SKILL.md b/echtpost-automation/SKILL.md new file mode 100644 index 0000000..750c1ea --- /dev/null +++ b/echtpost-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: echtpost-automation +description: "Automate Echtpost tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Echtpost Automation via Rube MCP + +Automate Echtpost operations through Composio's Echtpost toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/echtpost](https://composio.dev/toolkits/echtpost) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Echtpost connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `echtpost` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `echtpost` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Echtpost operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Echtpost task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["echtpost"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Echtpost-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `echtpost` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/elevenlabs-automation/SKILL.md b/elevenlabs-automation/SKILL.md new file mode 100644 index 0000000..6ca840d --- /dev/null +++ b/elevenlabs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: elevenlabs-automation +description: "Automate Elevenlabs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Elevenlabs Automation via Rube MCP + +Automate Elevenlabs operations through Composio's Elevenlabs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/elevenlabs](https://composio.dev/toolkits/elevenlabs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Elevenlabs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `elevenlabs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `elevenlabs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Elevenlabs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Elevenlabs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["elevenlabs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Elevenlabs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `elevenlabs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/elorus-automation/SKILL.md b/elorus-automation/SKILL.md new file mode 100644 index 0000000..d3b7299 --- /dev/null +++ b/elorus-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: elorus-automation +description: "Automate Elorus tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Elorus Automation via Rube MCP + +Automate Elorus operations through Composio's Elorus toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/elorus](https://composio.dev/toolkits/elorus) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Elorus connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `elorus` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `elorus` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Elorus operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Elorus task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["elorus"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Elorus-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `elorus` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/emailable-automation/SKILL.md b/emailable-automation/SKILL.md new file mode 100644 index 0000000..98e4682 --- /dev/null +++ b/emailable-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: emailable-automation +description: "Automate Emailable tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Emailable Automation via Rube MCP + +Automate Emailable operations through Composio's Emailable toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/emailable](https://composio.dev/toolkits/emailable) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Emailable connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `emailable` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `emailable` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Emailable operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Emailable task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["emailable"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Emailable-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `emailable` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/emaillistverify-automation/SKILL.md b/emaillistverify-automation/SKILL.md new file mode 100644 index 0000000..017e523 --- /dev/null +++ b/emaillistverify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: emaillistverify-automation +description: "Automate Emaillistverify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Emaillistverify Automation via Rube MCP + +Automate Emaillistverify operations through Composio's Emaillistverify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/emaillistverify](https://composio.dev/toolkits/emaillistverify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Emaillistverify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `emaillistverify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `emaillistverify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Emaillistverify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Emaillistverify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["emaillistverify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Emaillistverify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `emaillistverify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/emailoctopus-automation/SKILL.md b/emailoctopus-automation/SKILL.md new file mode 100644 index 0000000..67bfb3e --- /dev/null +++ b/emailoctopus-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: emailoctopus-automation +description: "Automate Emailoctopus tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Emailoctopus Automation via Rube MCP + +Automate Emailoctopus operations through Composio's Emailoctopus toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/emailoctopus](https://composio.dev/toolkits/emailoctopus) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Emailoctopus connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `emailoctopus` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `emailoctopus` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Emailoctopus operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Emailoctopus task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["emailoctopus"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Emailoctopus-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `emailoctopus` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/emelia-automation/SKILL.md b/emelia-automation/SKILL.md new file mode 100644 index 0000000..f439ba2 --- /dev/null +++ b/emelia-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: emelia-automation +description: "Automate Emelia tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Emelia Automation via Rube MCP + +Automate Emelia operations through Composio's Emelia toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/emelia](https://composio.dev/toolkits/emelia) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Emelia connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `emelia` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `emelia` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Emelia operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Emelia task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["emelia"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Emelia-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `emelia` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/encodian-automation/SKILL.md b/encodian-automation/SKILL.md new file mode 100644 index 0000000..3bab40b --- /dev/null +++ b/encodian-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: encodian-automation +description: "Automate Encodian tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Encodian Automation via Rube MCP + +Automate Encodian operations through Composio's Encodian toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/encodian](https://composio.dev/toolkits/encodian) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Encodian connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `encodian` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `encodian` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Encodian operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Encodian task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["encodian"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Encodian-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `encodian` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/endorsal-automation/SKILL.md b/endorsal-automation/SKILL.md new file mode 100644 index 0000000..197b9dc --- /dev/null +++ b/endorsal-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: endorsal-automation +description: "Automate Endorsal tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Endorsal Automation via Rube MCP + +Automate Endorsal operations through Composio's Endorsal toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/endorsal](https://composio.dev/toolkits/endorsal) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Endorsal connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `endorsal` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `endorsal` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Endorsal operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Endorsal task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["endorsal"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Endorsal-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `endorsal` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/enginemailer-automation/SKILL.md b/enginemailer-automation/SKILL.md new file mode 100644 index 0000000..28ac8a0 --- /dev/null +++ b/enginemailer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: enginemailer-automation +description: "Automate Enginemailer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Enginemailer Automation via Rube MCP + +Automate Enginemailer operations through Composio's Enginemailer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/enginemailer](https://composio.dev/toolkits/enginemailer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Enginemailer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `enginemailer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `enginemailer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Enginemailer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Enginemailer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["enginemailer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Enginemailer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `enginemailer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/enigma-automation/SKILL.md b/enigma-automation/SKILL.md new file mode 100644 index 0000000..cda8171 --- /dev/null +++ b/enigma-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: enigma-automation +description: "Automate Enigma tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Enigma Automation via Rube MCP + +Automate Enigma operations through Composio's Enigma toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/enigma](https://composio.dev/toolkits/enigma) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Enigma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `enigma` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `enigma` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Enigma operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Enigma task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["enigma"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Enigma-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `enigma` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/entelligence-automation/SKILL.md b/entelligence-automation/SKILL.md new file mode 100644 index 0000000..3e9be30 --- /dev/null +++ b/entelligence-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: entelligence-automation +description: "Automate Entelligence tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Entelligence Automation via Rube MCP + +Automate Entelligence operations through Composio's Entelligence toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/entelligence](https://composio.dev/toolkits/entelligence) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Entelligence connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `entelligence` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `entelligence` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Entelligence operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Entelligence task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["entelligence"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Entelligence-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `entelligence` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/eodhd-apis-automation/SKILL.md b/eodhd-apis-automation/SKILL.md new file mode 100644 index 0000000..55784e7 --- /dev/null +++ b/eodhd-apis-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: eodhd-apis-automation +description: "Automate Eodhd Apis tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Eodhd Apis Automation via Rube MCP + +Automate Eodhd Apis operations through Composio's Eodhd Apis toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/eodhd_apis](https://composio.dev/toolkits/eodhd_apis) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Eodhd Apis connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `eodhd_apis` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `eodhd_apis` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Eodhd Apis operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Eodhd Apis task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["eodhd_apis"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Eodhd Apis-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `eodhd_apis` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/epic-games-automation/SKILL.md b/epic-games-automation/SKILL.md new file mode 100644 index 0000000..8c9fcdb --- /dev/null +++ b/epic-games-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: epic-games-automation +description: "Automate Epic Games tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Epic Games Automation via Rube MCP + +Automate Epic Games operations through Composio's Epic Games toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/epic_games](https://composio.dev/toolkits/epic_games) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Epic Games connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `epic_games` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `epic_games` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Epic Games operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Epic Games task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["epic_games"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Epic Games-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `epic_games` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/esignatures-io-automation/SKILL.md b/esignatures-io-automation/SKILL.md new file mode 100644 index 0000000..514a1ee --- /dev/null +++ b/esignatures-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: esignatures-io-automation +description: "Automate Esignatures IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Esignatures IO Automation via Rube MCP + +Automate Esignatures IO operations through Composio's Esignatures IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/esignatures_io](https://composio.dev/toolkits/esignatures_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Esignatures IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `esignatures_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `esignatures_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Esignatures IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Esignatures IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["esignatures_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Esignatures IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `esignatures_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/espocrm-automation/SKILL.md b/espocrm-automation/SKILL.md new file mode 100644 index 0000000..4e65268 --- /dev/null +++ b/espocrm-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: espocrm-automation +description: "Automate Espocrm tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Espocrm Automation via Rube MCP + +Automate Espocrm operations through Composio's Espocrm toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/espocrm](https://composio.dev/toolkits/espocrm) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Espocrm connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `espocrm` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `espocrm` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Espocrm operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Espocrm task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["espocrm"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Espocrm-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `espocrm` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/esputnik-automation/SKILL.md b/esputnik-automation/SKILL.md new file mode 100644 index 0000000..7397442 --- /dev/null +++ b/esputnik-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: esputnik-automation +description: "Automate Esputnik tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Esputnik Automation via Rube MCP + +Automate Esputnik operations through Composio's Esputnik toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/esputnik](https://composio.dev/toolkits/esputnik) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Esputnik connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `esputnik` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `esputnik` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Esputnik operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Esputnik task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["esputnik"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Esputnik-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `esputnik` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/etermin-automation/SKILL.md b/etermin-automation/SKILL.md new file mode 100644 index 0000000..4547db1 --- /dev/null +++ b/etermin-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: etermin-automation +description: "Automate Etermin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Etermin Automation via Rube MCP + +Automate Etermin operations through Composio's Etermin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/etermin](https://composio.dev/toolkits/etermin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Etermin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `etermin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `etermin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Etermin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Etermin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["etermin"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Etermin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `etermin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/evenium-automation/SKILL.md b/evenium-automation/SKILL.md new file mode 100644 index 0000000..b9dc686 --- /dev/null +++ b/evenium-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: evenium-automation +description: "Automate Evenium tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Evenium Automation via Rube MCP + +Automate Evenium operations through Composio's Evenium toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/evenium](https://composio.dev/toolkits/evenium) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Evenium connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `evenium` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `evenium` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Evenium operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Evenium task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["evenium"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Evenium-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `evenium` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/eventbrite-automation/SKILL.md b/eventbrite-automation/SKILL.md new file mode 100644 index 0000000..0c16e7c --- /dev/null +++ b/eventbrite-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: eventbrite-automation +description: "Automate Eventbrite tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Eventbrite Automation via Rube MCP + +Automate Eventbrite operations through Composio's Eventbrite toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/eventbrite](https://composio.dev/toolkits/eventbrite) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Eventbrite connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `eventbrite` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `eventbrite` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Eventbrite operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Eventbrite task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["eventbrite"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Eventbrite-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `eventbrite` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/eventee-automation/SKILL.md b/eventee-automation/SKILL.md new file mode 100644 index 0000000..4bc0517 --- /dev/null +++ b/eventee-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: eventee-automation +description: "Automate Eventee tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Eventee Automation via Rube MCP + +Automate Eventee operations through Composio's Eventee toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/eventee](https://composio.dev/toolkits/eventee) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Eventee connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `eventee` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `eventee` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Eventee operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Eventee task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["eventee"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Eventee-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `eventee` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/eventzilla-automation/SKILL.md b/eventzilla-automation/SKILL.md new file mode 100644 index 0000000..6f2600a --- /dev/null +++ b/eventzilla-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: eventzilla-automation +description: "Automate Eventzilla tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Eventzilla Automation via Rube MCP + +Automate Eventzilla operations through Composio's Eventzilla toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/eventzilla](https://composio.dev/toolkits/eventzilla) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Eventzilla connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `eventzilla` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `eventzilla` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Eventzilla operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Eventzilla task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["eventzilla"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Eventzilla-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `eventzilla` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/everhour-automation/SKILL.md b/everhour-automation/SKILL.md new file mode 100644 index 0000000..ef7bc5f --- /dev/null +++ b/everhour-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: everhour-automation +description: "Automate Everhour tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Everhour Automation via Rube MCP + +Automate Everhour operations through Composio's Everhour toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/everhour](https://composio.dev/toolkits/everhour) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Everhour connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `everhour` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `everhour` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Everhour operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Everhour task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["everhour"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Everhour-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `everhour` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/eversign-automation/SKILL.md b/eversign-automation/SKILL.md new file mode 100644 index 0000000..88b5a9f --- /dev/null +++ b/eversign-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: eversign-automation +description: "Automate Eversign tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Eversign Automation via Rube MCP + +Automate Eversign operations through Composio's Eversign toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/eversign](https://composio.dev/toolkits/eversign) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Eversign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `eversign` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `eversign` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Eversign operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Eversign task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["eversign"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Eversign-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `eversign` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/exa-automation/SKILL.md b/exa-automation/SKILL.md new file mode 100644 index 0000000..886e92d --- /dev/null +++ b/exa-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: exa-automation +description: "Automate Exa tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Exa Automation via Rube MCP + +Automate Exa operations through Composio's Exa toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/exa](https://composio.dev/toolkits/exa) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Exa connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `exa` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `exa` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Exa operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Exa task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["exa"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Exa-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `exa` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/excel-automation/SKILL.md b/excel-automation/SKILL.md new file mode 100644 index 0000000..3b39fad --- /dev/null +++ b/excel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: excel-automation +description: "Automate Excel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Excel Automation via Rube MCP + +Automate Excel operations through Composio's Excel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/excel](https://composio.dev/toolkits/excel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Excel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `excel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `excel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Excel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Excel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["excel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Excel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `excel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/exist-automation/SKILL.md b/exist-automation/SKILL.md new file mode 100644 index 0000000..7ef45ba --- /dev/null +++ b/exist-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: exist-automation +description: "Automate Exist tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Exist Automation via Rube MCP + +Automate Exist operations through Composio's Exist toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/exist](https://composio.dev/toolkits/exist) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Exist connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `exist` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `exist` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Exist operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Exist task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["exist"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Exist-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `exist` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/expofp-automation/SKILL.md b/expofp-automation/SKILL.md new file mode 100644 index 0000000..5589928 --- /dev/null +++ b/expofp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: expofp-automation +description: "Automate Expofp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Expofp Automation via Rube MCP + +Automate Expofp operations through Composio's Expofp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/expofp](https://composio.dev/toolkits/expofp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Expofp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `expofp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `expofp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Expofp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Expofp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["expofp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Expofp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `expofp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/extracta-ai-automation/SKILL.md b/extracta-ai-automation/SKILL.md new file mode 100644 index 0000000..63f75c4 --- /dev/null +++ b/extracta-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: extracta-ai-automation +description: "Automate Extracta AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Extracta AI Automation via Rube MCP + +Automate Extracta AI operations through Composio's Extracta AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/extracta_ai](https://composio.dev/toolkits/extracta_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Extracta AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `extracta_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `extracta_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Extracta AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Extracta AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["extracta_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Extracta AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `extracta_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/facebook-automation/SKILL.md b/facebook-automation/SKILL.md new file mode 100644 index 0000000..aedd3de --- /dev/null +++ b/facebook-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: facebook-automation +description: "Automate Facebook tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Facebook Automation via Rube MCP + +Automate Facebook operations through Composio's Facebook toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/facebook](https://composio.dev/toolkits/facebook) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Facebook connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `facebook` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `facebook` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Facebook operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Facebook task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["facebook"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Facebook-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `facebook` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/faceup-automation/SKILL.md b/faceup-automation/SKILL.md new file mode 100644 index 0000000..5302a19 --- /dev/null +++ b/faceup-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: faceup-automation +description: "Automate Faceup tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Faceup Automation via Rube MCP + +Automate Faceup operations through Composio's Faceup toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/faceup](https://composio.dev/toolkits/faceup) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Faceup connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `faceup` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `faceup` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Faceup operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Faceup task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["faceup"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Faceup-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `faceup` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/factorial-automation/SKILL.md b/factorial-automation/SKILL.md new file mode 100644 index 0000000..306c812 --- /dev/null +++ b/factorial-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: factorial-automation +description: "Automate Factorial tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Factorial Automation via Rube MCP + +Automate Factorial operations through Composio's Factorial toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/factorial](https://composio.dev/toolkits/factorial) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Factorial connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `factorial` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `factorial` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Factorial operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Factorial task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["factorial"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Factorial-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `factorial` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/feathery-automation/SKILL.md b/feathery-automation/SKILL.md new file mode 100644 index 0000000..67055f6 --- /dev/null +++ b/feathery-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: feathery-automation +description: "Automate Feathery tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Feathery Automation via Rube MCP + +Automate Feathery operations through Composio's Feathery toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/feathery](https://composio.dev/toolkits/feathery) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Feathery connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `feathery` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `feathery` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Feathery operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Feathery task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["feathery"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Feathery-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `feathery` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/felt-automation/SKILL.md b/felt-automation/SKILL.md new file mode 100644 index 0000000..a269c81 --- /dev/null +++ b/felt-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: felt-automation +description: "Automate Felt tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Felt Automation via Rube MCP + +Automate Felt operations through Composio's Felt toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/felt](https://composio.dev/toolkits/felt) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Felt connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `felt` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `felt` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Felt operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Felt task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["felt"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Felt-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `felt` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fibery-automation/SKILL.md b/fibery-automation/SKILL.md new file mode 100644 index 0000000..90fa97c --- /dev/null +++ b/fibery-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fibery-automation +description: "Automate Fibery tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fibery Automation via Rube MCP + +Automate Fibery operations through Composio's Fibery toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fibery](https://composio.dev/toolkits/fibery) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fibery connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fibery` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fibery` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fibery operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fibery task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fibery"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fibery-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fibery` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fidel-api-automation/SKILL.md b/fidel-api-automation/SKILL.md new file mode 100644 index 0000000..2a79618 --- /dev/null +++ b/fidel-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fidel-api-automation +description: "Automate Fidel API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fidel API Automation via Rube MCP + +Automate Fidel API operations through Composio's Fidel API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fidel_api](https://composio.dev/toolkits/fidel_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fidel API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fidel_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fidel_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fidel API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fidel API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fidel_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fidel API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fidel_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/figma-automation/SKILL.md b/figma-automation/SKILL.md index b2f6bf3..86bab70 100644 --- a/figma-automation/SKILL.md +++ b/figma-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Figma operations through Composio's Figma toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/figma](https://composio.dev/toolkits/figma) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -179,3 +181,6 @@ Extract IDs from Figma URLs: | Team styles | FIGMA_GET_TEAM_STYLES | team_id | | File styles | FIGMA_GET_FILE_STYLES | file_key | | Image fills | FIGMA_GET_IMAGE_FILLS | file_key | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/files-com-automation/SKILL.md b/files-com-automation/SKILL.md new file mode 100644 index 0000000..3bd46b6 --- /dev/null +++ b/files-com-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: files-com-automation +description: "Automate Files Com tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Files Com Automation via Rube MCP + +Automate Files Com operations through Composio's Files Com toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/files_com](https://composio.dev/toolkits/files_com) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Files Com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `files_com` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `files_com` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Files Com operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Files Com task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["files_com"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Files Com-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `files_com` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fillout-forms-automation/SKILL.md b/fillout-forms-automation/SKILL.md new file mode 100644 index 0000000..17c9ae5 --- /dev/null +++ b/fillout-forms-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fillout-forms-automation +description: "Automate Fillout tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fillout Automation via Rube MCP + +Automate Fillout operations through Composio's Fillout toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fillout_forms](https://composio.dev/toolkits/fillout_forms) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fillout connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fillout_forms` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fillout_forms` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fillout operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fillout task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fillout_forms"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fillout-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fillout_forms` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fillout_forms-automation/SKILL.md b/fillout_forms-automation/SKILL.md new file mode 100644 index 0000000..64fd957 --- /dev/null +++ b/fillout_forms-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: fillout_forms-automation +description: "Automate Fillout tasks via Rube MCP (Composio): forms, submissions, workflows, and form builder. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fillout Automation via Rube MCP + +Automate Fillout operations through Composio's Fillout toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fillout_forms](https://composio.dev/toolkits/fillout_forms) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fillout connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fillout_forms` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fillout_forms` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "forms, submissions, workflows, and form builder", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Fillout +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Fillout Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Fillout tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Fillout Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Fillout operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Fillout connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fillout-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fillout_forms` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/fillout_forms](https://composio.dev/toolkits/fillout_forms) diff --git a/finage-automation/SKILL.md b/finage-automation/SKILL.md new file mode 100644 index 0000000..24badea --- /dev/null +++ b/finage-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: finage-automation +description: "Automate Finage tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Finage Automation via Rube MCP + +Automate Finage operations through Composio's Finage toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/finage](https://composio.dev/toolkits/finage) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Finage connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `finage` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `finage` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Finage operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Finage task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["finage"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Finage-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `finage` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/findymail-automation/SKILL.md b/findymail-automation/SKILL.md new file mode 100644 index 0000000..3562abd --- /dev/null +++ b/findymail-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: findymail-automation +description: "Automate Findymail tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Findymail Automation via Rube MCP + +Automate Findymail operations through Composio's Findymail toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/findymail](https://composio.dev/toolkits/findymail) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Findymail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `findymail` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `findymail` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Findymail operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Findymail task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["findymail"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Findymail-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `findymail` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/finerworks-automation/SKILL.md b/finerworks-automation/SKILL.md new file mode 100644 index 0000000..eb4db42 --- /dev/null +++ b/finerworks-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: finerworks-automation +description: "Automate Finerworks tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Finerworks Automation via Rube MCP + +Automate Finerworks operations through Composio's Finerworks toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/finerworks](https://composio.dev/toolkits/finerworks) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Finerworks connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `finerworks` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `finerworks` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Finerworks operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Finerworks task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["finerworks"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Finerworks-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `finerworks` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fingertip-automation/SKILL.md b/fingertip-automation/SKILL.md new file mode 100644 index 0000000..bdf84cd --- /dev/null +++ b/fingertip-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fingertip-automation +description: "Automate Fingertip tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fingertip Automation via Rube MCP + +Automate Fingertip operations through Composio's Fingertip toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fingertip](https://composio.dev/toolkits/fingertip) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fingertip connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fingertip` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fingertip` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fingertip operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fingertip task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fingertip"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fingertip-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fingertip` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/finmei-automation/SKILL.md b/finmei-automation/SKILL.md new file mode 100644 index 0000000..992382a --- /dev/null +++ b/finmei-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: finmei-automation +description: "Automate Finmei tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Finmei Automation via Rube MCP + +Automate Finmei operations through Composio's Finmei toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/finmei](https://composio.dev/toolkits/finmei) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Finmei connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `finmei` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `finmei` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Finmei operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Finmei task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["finmei"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Finmei-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `finmei` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fireberry-automation/SKILL.md b/fireberry-automation/SKILL.md new file mode 100644 index 0000000..0165bb0 --- /dev/null +++ b/fireberry-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fireberry-automation +description: "Automate Fireberry tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fireberry Automation via Rube MCP + +Automate Fireberry operations through Composio's Fireberry toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fireberry](https://composio.dev/toolkits/fireberry) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fireberry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fireberry` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fireberry` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fireberry operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fireberry task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fireberry"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fireberry-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fireberry` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/firecrawl-automation/SKILL.md b/firecrawl-automation/SKILL.md new file mode 100644 index 0000000..49a6699 --- /dev/null +++ b/firecrawl-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: firecrawl-automation +description: "Automate Firecrawl tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Firecrawl Automation via Rube MCP + +Automate Firecrawl operations through Composio's Firecrawl toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/firecrawl](https://composio.dev/toolkits/firecrawl) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Firecrawl connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `firecrawl` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `firecrawl` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Firecrawl operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Firecrawl task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["firecrawl"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Firecrawl-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `firecrawl` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fireflies-automation/SKILL.md b/fireflies-automation/SKILL.md new file mode 100644 index 0000000..7e01f74 --- /dev/null +++ b/fireflies-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fireflies-automation +description: "Automate Fireflies tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fireflies Automation via Rube MCP + +Automate Fireflies operations through Composio's Fireflies toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fireflies](https://composio.dev/toolkits/fireflies) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fireflies connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fireflies` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fireflies` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fireflies operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fireflies task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fireflies"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fireflies-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fireflies` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/firmao-automation/SKILL.md b/firmao-automation/SKILL.md new file mode 100644 index 0000000..b09c687 --- /dev/null +++ b/firmao-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: firmao-automation +description: "Automate Firmao tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Firmao Automation via Rube MCP + +Automate Firmao operations through Composio's Firmao toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/firmao](https://composio.dev/toolkits/firmao) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Firmao connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `firmao` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `firmao` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Firmao operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Firmao task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["firmao"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Firmao-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `firmao` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fitbit-automation/SKILL.md b/fitbit-automation/SKILL.md new file mode 100644 index 0000000..ece8d16 --- /dev/null +++ b/fitbit-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fitbit-automation +description: "Automate Fitbit tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fitbit Automation via Rube MCP + +Automate Fitbit operations through Composio's Fitbit toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fitbit](https://composio.dev/toolkits/fitbit) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fitbit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fitbit` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fitbit` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fitbit operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fitbit task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fitbit"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fitbit-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fitbit` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fixer-automation/SKILL.md b/fixer-automation/SKILL.md new file mode 100644 index 0000000..adc2c88 --- /dev/null +++ b/fixer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fixer-automation +description: "Automate Fixer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fixer Automation via Rube MCP + +Automate Fixer operations through Composio's Fixer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fixer](https://composio.dev/toolkits/fixer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fixer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fixer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fixer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fixer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fixer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fixer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fixer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fixer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fixer-io-automation/SKILL.md b/fixer-io-automation/SKILL.md new file mode 100644 index 0000000..f91f21f --- /dev/null +++ b/fixer-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fixer-io-automation +description: "Automate Fixer IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fixer IO Automation via Rube MCP + +Automate Fixer IO operations through Composio's Fixer IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fixer_io](https://composio.dev/toolkits/fixer_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fixer IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fixer_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fixer_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fixer IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fixer IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fixer_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fixer IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fixer_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/flexisign-automation/SKILL.md b/flexisign-automation/SKILL.md new file mode 100644 index 0000000..5513714 --- /dev/null +++ b/flexisign-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: flexisign-automation +description: "Automate Flexisign tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Flexisign Automation via Rube MCP + +Automate Flexisign operations through Composio's Flexisign toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/flexisign](https://composio.dev/toolkits/flexisign) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Flexisign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `flexisign` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `flexisign` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Flexisign operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Flexisign task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["flexisign"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Flexisign-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `flexisign` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/flowiseai-automation/SKILL.md b/flowiseai-automation/SKILL.md new file mode 100644 index 0000000..94992d0 --- /dev/null +++ b/flowiseai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: flowiseai-automation +description: "Automate Flowiseai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Flowiseai Automation via Rube MCP + +Automate Flowiseai operations through Composio's Flowiseai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/flowiseai](https://composio.dev/toolkits/flowiseai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Flowiseai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `flowiseai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `flowiseai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Flowiseai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Flowiseai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["flowiseai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Flowiseai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `flowiseai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/flutterwave-automation/SKILL.md b/flutterwave-automation/SKILL.md new file mode 100644 index 0000000..aff1120 --- /dev/null +++ b/flutterwave-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: flutterwave-automation +description: "Automate Flutterwave tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Flutterwave Automation via Rube MCP + +Automate Flutterwave operations through Composio's Flutterwave toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/flutterwave](https://composio.dev/toolkits/flutterwave) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Flutterwave connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `flutterwave` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `flutterwave` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Flutterwave operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Flutterwave task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["flutterwave"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Flutterwave-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `flutterwave` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fluxguard-automation/SKILL.md b/fluxguard-automation/SKILL.md new file mode 100644 index 0000000..57100c9 --- /dev/null +++ b/fluxguard-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fluxguard-automation +description: "Automate Fluxguard tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fluxguard Automation via Rube MCP + +Automate Fluxguard operations through Composio's Fluxguard toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fluxguard](https://composio.dev/toolkits/fluxguard) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fluxguard connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fluxguard` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fluxguard` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fluxguard operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fluxguard task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fluxguard"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fluxguard-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fluxguard` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/folk-automation/SKILL.md b/folk-automation/SKILL.md new file mode 100644 index 0000000..2bbd26d --- /dev/null +++ b/folk-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: folk-automation +description: "Automate Folk tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Folk Automation via Rube MCP + +Automate Folk operations through Composio's Folk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/folk](https://composio.dev/toolkits/folk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Folk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `folk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `folk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Folk operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Folk task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["folk"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Folk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `folk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fomo-automation/SKILL.md b/fomo-automation/SKILL.md new file mode 100644 index 0000000..4ac4034 --- /dev/null +++ b/fomo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fomo-automation +description: "Automate Fomo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fomo Automation via Rube MCP + +Automate Fomo operations through Composio's Fomo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fomo](https://composio.dev/toolkits/fomo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fomo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fomo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fomo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fomo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fomo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fomo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fomo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fomo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/forcemanager-automation/SKILL.md b/forcemanager-automation/SKILL.md new file mode 100644 index 0000000..00a70bc --- /dev/null +++ b/forcemanager-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: forcemanager-automation +description: "Automate Forcemanager tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Forcemanager Automation via Rube MCP + +Automate Forcemanager operations through Composio's Forcemanager toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/forcemanager](https://composio.dev/toolkits/forcemanager) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Forcemanager connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `forcemanager` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `forcemanager` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Forcemanager operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Forcemanager task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["forcemanager"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Forcemanager-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `forcemanager` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/formbricks-automation/SKILL.md b/formbricks-automation/SKILL.md new file mode 100644 index 0000000..6546332 --- /dev/null +++ b/formbricks-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: formbricks-automation +description: "Automate Formbricks tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Formbricks Automation via Rube MCP + +Automate Formbricks operations through Composio's Formbricks toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/formbricks](https://composio.dev/toolkits/formbricks) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Formbricks connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `formbricks` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `formbricks` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Formbricks operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Formbricks task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["formbricks"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Formbricks-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `formbricks` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/formcarry-automation/SKILL.md b/formcarry-automation/SKILL.md new file mode 100644 index 0000000..e2a4de7 --- /dev/null +++ b/formcarry-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: formcarry-automation +description: "Automate Formcarry tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Formcarry Automation via Rube MCP + +Automate Formcarry operations through Composio's Formcarry toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/formcarry](https://composio.dev/toolkits/formcarry) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Formcarry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `formcarry` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `formcarry` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Formcarry operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Formcarry task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["formcarry"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Formcarry-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `formcarry` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/formdesk-automation/SKILL.md b/formdesk-automation/SKILL.md new file mode 100644 index 0000000..d4e7c04 --- /dev/null +++ b/formdesk-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: formdesk-automation +description: "Automate Formdesk tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Formdesk Automation via Rube MCP + +Automate Formdesk operations through Composio's Formdesk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/formdesk](https://composio.dev/toolkits/formdesk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Formdesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `formdesk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `formdesk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Formdesk operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Formdesk task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["formdesk"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Formdesk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `formdesk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/formsite-automation/SKILL.md b/formsite-automation/SKILL.md new file mode 100644 index 0000000..8959dd1 --- /dev/null +++ b/formsite-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: formsite-automation +description: "Automate Formsite tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Formsite Automation via Rube MCP + +Automate Formsite operations through Composio's Formsite toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/formsite](https://composio.dev/toolkits/formsite) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Formsite connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `formsite` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `formsite` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Formsite operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Formsite task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["formsite"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Formsite-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `formsite` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/foursquare-automation/SKILL.md b/foursquare-automation/SKILL.md new file mode 100644 index 0000000..9388753 --- /dev/null +++ b/foursquare-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: foursquare-automation +description: "Automate Foursquare tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Foursquare Automation via Rube MCP + +Automate Foursquare operations through Composio's Foursquare toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/foursquare](https://composio.dev/toolkits/foursquare) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Foursquare connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `foursquare` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `foursquare` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Foursquare operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Foursquare task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["foursquare"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Foursquare-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `foursquare` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fraudlabs-pro-automation/SKILL.md b/fraudlabs-pro-automation/SKILL.md new file mode 100644 index 0000000..0fb89ac --- /dev/null +++ b/fraudlabs-pro-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fraudlabs-pro-automation +description: "Automate Fraudlabs Pro tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fraudlabs Pro Automation via Rube MCP + +Automate Fraudlabs Pro operations through Composio's Fraudlabs Pro toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fraudlabs_pro](https://composio.dev/toolkits/fraudlabs_pro) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fraudlabs Pro connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fraudlabs_pro` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fraudlabs_pro` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fraudlabs Pro operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fraudlabs Pro task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fraudlabs_pro"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fraudlabs Pro-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fraudlabs_pro` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/freshbooks-automation/SKILL.md b/freshbooks-automation/SKILL.md new file mode 100644 index 0000000..3d72c3e --- /dev/null +++ b/freshbooks-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: freshbooks-automation +description: "Automate Freshbooks tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Freshbooks Automation via Rube MCP + +Automate Freshbooks operations through Composio's Freshbooks toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/freshbooks](https://composio.dev/toolkits/freshbooks) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Freshbooks connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshbooks` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `freshbooks` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Freshbooks operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Freshbooks task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["freshbooks"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Freshbooks-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `freshbooks` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/freshdesk-automation/SKILL.md b/freshdesk-automation/SKILL.md index f57a07b..fd11b62 100644 --- a/freshdesk-automation/SKILL.md +++ b/freshdesk-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Freshdesk customer support workflows including ticket management, contact and company operations, notes, replies, and ticket search through Composio's Freshdesk toolkit. +**Toolkit docs**: [composio.dev/toolkits/freshdesk](https://composio.dev/toolkits/freshdesk) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -217,3 +219,6 @@ Freshdesk uses page-based pagination: | List companies | `FRESHDESK_GET_COMPANIES` | `page` | | List ticket fields | `FRESHDESK_LIST_TICKET_FIELDS` | (none) | | List company fields | `FRESHDESK_LIST_COMPANY_FIELDS` | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/freshservice-automation/SKILL.md b/freshservice-automation/SKILL.md index 18aeb0d..4060de8 100644 --- a/freshservice-automation/SKILL.md +++ b/freshservice-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/freshservice](https://composio.dev/toolkits/freshservice) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -211,3 +213,6 @@ Automate Freshservice IT Service Management operations through Composio's Freshs | Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields | | Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description | | Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/front-automation/SKILL.md b/front-automation/SKILL.md new file mode 100644 index 0000000..22884ac --- /dev/null +++ b/front-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: front-automation +description: "Automate Front tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Front Automation via Rube MCP + +Automate Front operations through Composio's Front toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/front](https://composio.dev/toolkits/front) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Front connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `front` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `front` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Front operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Front task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["front"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Front-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `front` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/fullenrich-automation/SKILL.md b/fullenrich-automation/SKILL.md new file mode 100644 index 0000000..aa6a7e9 --- /dev/null +++ b/fullenrich-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: fullenrich-automation +description: "Automate Fullenrich tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Fullenrich Automation via Rube MCP + +Automate Fullenrich operations through Composio's Fullenrich toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/fullenrich](https://composio.dev/toolkits/fullenrich) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Fullenrich connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `fullenrich` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `fullenrich` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Fullenrich operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Fullenrich task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["fullenrich"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Fullenrich-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `fullenrich` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gagelist-automation/SKILL.md b/gagelist-automation/SKILL.md new file mode 100644 index 0000000..772734e --- /dev/null +++ b/gagelist-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gagelist-automation +description: "Automate Gagelist tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gagelist Automation via Rube MCP + +Automate Gagelist operations through Composio's Gagelist toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gagelist](https://composio.dev/toolkits/gagelist) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gagelist connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gagelist` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gagelist` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gagelist operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gagelist task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gagelist"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gagelist-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gagelist` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gamma-automation/SKILL.md b/gamma-automation/SKILL.md new file mode 100644 index 0000000..9f01a3a --- /dev/null +++ b/gamma-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gamma-automation +description: "Automate Gamma tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gamma Automation via Rube MCP + +Automate Gamma operations through Composio's Gamma toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gamma](https://composio.dev/toolkits/gamma) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gamma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gamma` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gamma` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gamma operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gamma task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gamma"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gamma-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gamma` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gan-ai-automation/SKILL.md b/gan-ai-automation/SKILL.md new file mode 100644 index 0000000..fc3fc04 --- /dev/null +++ b/gan-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gan-ai-automation +description: "Automate Gan AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gan AI Automation via Rube MCP + +Automate Gan AI operations through Composio's Gan AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gan_ai](https://composio.dev/toolkits/gan_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gan AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gan_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gan_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gan AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gan AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gan_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gan AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gan_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gatherup-automation/SKILL.md b/gatherup-automation/SKILL.md new file mode 100644 index 0000000..4b85a7e --- /dev/null +++ b/gatherup-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gatherup-automation +description: "Automate Gatherup tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gatherup Automation via Rube MCP + +Automate Gatherup operations through Composio's Gatherup toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gatherup](https://composio.dev/toolkits/gatherup) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gatherup connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gatherup` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gatherup` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gatherup operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gatherup task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gatherup"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gatherup-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gatherup` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gemini-automation/SKILL.md b/gemini-automation/SKILL.md new file mode 100644 index 0000000..ff827db --- /dev/null +++ b/gemini-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gemini-automation +description: "Automate Gemini tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gemini Automation via Rube MCP + +Automate Gemini operations through Composio's Gemini toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gemini](https://composio.dev/toolkits/gemini) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gemini connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gemini` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gemini` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gemini operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gemini task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gemini"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gemini-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gemini` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gender-api-automation/SKILL.md b/gender-api-automation/SKILL.md new file mode 100644 index 0000000..aec80f3 --- /dev/null +++ b/gender-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gender-api-automation +description: "Automate Gender API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gender API Automation via Rube MCP + +Automate Gender API operations through Composio's Gender API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gender_api](https://composio.dev/toolkits/gender_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gender API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gender_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gender_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gender API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gender API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gender_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gender API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gender_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/genderapi-io-automation/SKILL.md b/genderapi-io-automation/SKILL.md new file mode 100644 index 0000000..f515d35 --- /dev/null +++ b/genderapi-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: genderapi-io-automation +description: "Automate Genderapi IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Genderapi IO Automation via Rube MCP + +Automate Genderapi IO operations through Composio's Genderapi IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/genderapi_io](https://composio.dev/toolkits/genderapi_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Genderapi IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `genderapi_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `genderapi_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Genderapi IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Genderapi IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["genderapi_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Genderapi IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `genderapi_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/genderize-automation/SKILL.md b/genderize-automation/SKILL.md new file mode 100644 index 0000000..20e9322 --- /dev/null +++ b/genderize-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: genderize-automation +description: "Automate Genderize tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Genderize Automation via Rube MCP + +Automate Genderize operations through Composio's Genderize toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/genderize](https://composio.dev/toolkits/genderize) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Genderize connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `genderize` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `genderize` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Genderize operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Genderize task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["genderize"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Genderize-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `genderize` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/geoapify-automation/SKILL.md b/geoapify-automation/SKILL.md new file mode 100644 index 0000000..487a6a4 --- /dev/null +++ b/geoapify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: geoapify-automation +description: "Automate Geoapify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Geoapify Automation via Rube MCP + +Automate Geoapify operations through Composio's Geoapify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/geoapify](https://composio.dev/toolkits/geoapify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Geoapify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `geoapify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `geoapify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Geoapify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Geoapify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["geoapify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Geoapify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `geoapify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/geocodio-automation/SKILL.md b/geocodio-automation/SKILL.md new file mode 100644 index 0000000..2b405f7 --- /dev/null +++ b/geocodio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: geocodio-automation +description: "Automate Geocodio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Geocodio Automation via Rube MCP + +Automate Geocodio operations through Composio's Geocodio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/geocodio](https://composio.dev/toolkits/geocodio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Geocodio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `geocodio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `geocodio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Geocodio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Geocodio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["geocodio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Geocodio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `geocodio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/geokeo-automation/SKILL.md b/geokeo-automation/SKILL.md new file mode 100644 index 0000000..f47bf18 --- /dev/null +++ b/geokeo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: geokeo-automation +description: "Automate Geokeo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Geokeo Automation via Rube MCP + +Automate Geokeo operations through Composio's Geokeo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/geokeo](https://composio.dev/toolkits/geokeo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Geokeo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `geokeo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `geokeo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Geokeo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Geokeo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["geokeo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Geokeo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `geokeo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/getform-automation/SKILL.md b/getform-automation/SKILL.md new file mode 100644 index 0000000..7dc9223 --- /dev/null +++ b/getform-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: getform-automation +description: "Automate Getform tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Getform Automation via Rube MCP + +Automate Getform operations through Composio's Getform toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/getform](https://composio.dev/toolkits/getform) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Getform connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `getform` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `getform` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Getform operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Getform task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["getform"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Getform-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `getform` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gift-up-automation/SKILL.md b/gift-up-automation/SKILL.md new file mode 100644 index 0000000..f95b2cf --- /dev/null +++ b/gift-up-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gift-up-automation +description: "Automate Gift Up tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gift Up Automation via Rube MCP + +Automate Gift Up operations through Composio's Gift Up toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gift_up](https://composio.dev/toolkits/gift_up) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gift Up connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gift_up` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gift_up` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gift Up operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gift Up task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gift_up"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gift Up-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gift_up` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gigasheet-automation/SKILL.md b/gigasheet-automation/SKILL.md new file mode 100644 index 0000000..30d89c2 --- /dev/null +++ b/gigasheet-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gigasheet-automation +description: "Automate Gigasheet tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gigasheet Automation via Rube MCP + +Automate Gigasheet operations through Composio's Gigasheet toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gigasheet](https://composio.dev/toolkits/gigasheet) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gigasheet connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gigasheet` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gigasheet` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gigasheet operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gigasheet task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gigasheet"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gigasheet-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gigasheet` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/giphy-automation/SKILL.md b/giphy-automation/SKILL.md new file mode 100644 index 0000000..57197ff --- /dev/null +++ b/giphy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: giphy-automation +description: "Automate Giphy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Giphy Automation via Rube MCP + +Automate Giphy operations through Composio's Giphy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/giphy](https://composio.dev/toolkits/giphy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Giphy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `giphy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `giphy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Giphy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Giphy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["giphy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Giphy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `giphy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gist-automation/SKILL.md b/gist-automation/SKILL.md new file mode 100644 index 0000000..1445e20 --- /dev/null +++ b/gist-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gist-automation +description: "Automate Gist tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gist Automation via Rube MCP + +Automate Gist operations through Composio's Gist toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gist](https://composio.dev/toolkits/gist) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gist connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gist` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gist` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gist operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gist task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gist"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gist-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gist` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/github-automation/SKILL.md b/github-automation/SKILL.md index 4b58c67..778ffeb 100644 --- a/github-automation/SKILL.md +++ b/github-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate GitHub repository management, issue tracking, pull request workflows, branch operations, and CI/CD through Composio's GitHub toolkit. +**Toolkit docs**: [composio.dev/toolkits/github](https://composio.dev/toolkits/github) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -225,3 +227,6 @@ All list endpoints use page-based pagination: | Check CI | `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` | `owner`, `repo`, ref | | List collaborators | `GITHUB_LIST_REPOSITORY_COLLABORATORS` | `owner`, `repo` | | Branch protection | `GITHUB_GET_BRANCH_PROTECTION` | `owner`, `repo`, `branch` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gitlab-automation/SKILL.md b/gitlab-automation/SKILL.md index c3476e0..c44ea96 100644 --- a/gitlab-automation/SKILL.md +++ b/gitlab-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate GitLab operations including project management, issue tracking, merge request workflows, CI/CD pipeline monitoring, branch management, and user administration through Composio's GitLab toolkit. +**Toolkit docs**: [composio.dev/toolkits/gitlab](https://composio.dev/toolkits/gitlab) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -252,3 +254,6 @@ When using project paths as identifiers: | User status | `GITLAB_GET_USERS_ID_STATUS` | user ID | | List project members | `GITLAB_LIST_ALL_PROJECT_MEMBERS` | `id`, `query`, `state` | | List project users | `GITLAB_LIST_PROJECT_USERS` | `id`, `search` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/givebutter-automation/SKILL.md b/givebutter-automation/SKILL.md new file mode 100644 index 0000000..2753eea --- /dev/null +++ b/givebutter-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: givebutter-automation +description: "Automate Givebutter tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Givebutter Automation via Rube MCP + +Automate Givebutter operations through Composio's Givebutter toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/givebutter](https://composio.dev/toolkits/givebutter) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Givebutter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `givebutter` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `givebutter` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Givebutter operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Givebutter task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["givebutter"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Givebutter-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `givebutter` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gladia-automation/SKILL.md b/gladia-automation/SKILL.md new file mode 100644 index 0000000..7e6a259 --- /dev/null +++ b/gladia-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gladia-automation +description: "Automate Gladia tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gladia Automation via Rube MCP + +Automate Gladia operations through Composio's Gladia toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gladia](https://composio.dev/toolkits/gladia) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gladia connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gladia` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gladia` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gladia operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gladia task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gladia"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gladia-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gladia` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gleap-automation/SKILL.md b/gleap-automation/SKILL.md new file mode 100644 index 0000000..d5647b8 --- /dev/null +++ b/gleap-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gleap-automation +description: "Automate Gleap tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gleap Automation via Rube MCP + +Automate Gleap operations through Composio's Gleap toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gleap](https://composio.dev/toolkits/gleap) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gleap connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gleap` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gleap` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gleap operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gleap task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gleap"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gleap-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gleap` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/globalping-automation/SKILL.md b/globalping-automation/SKILL.md new file mode 100644 index 0000000..237fa29 --- /dev/null +++ b/globalping-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: globalping-automation +description: "Automate Globalping tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Globalping Automation via Rube MCP + +Automate Globalping operations through Composio's Globalping toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/globalping](https://composio.dev/toolkits/globalping) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Globalping connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `globalping` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `globalping` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Globalping operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Globalping task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["globalping"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Globalping-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `globalping` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gmail-automation/SKILL.md b/gmail-automation/SKILL.md index 3708bc4..074b1e1 100644 --- a/gmail-automation/SKILL.md +++ b/gmail-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Gmail operations through Composio's Gmail toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/gmail](https://composio.dev/toolkits/gmail) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -267,4 +269,6 @@ Automate Gmail operations through Composio's Gmail toolkit via Rube MCP. | Send draft | GMAIL_SEND_DRAFT | draft_id | | Get attachment | GMAIL_GET_ATTACHMENT | message_id, attachment_id | | Search contacts | GMAIL_SEARCH_PEOPLE | query | -| Get profile | GMAIL_GET_PROFILE | (none) | \ No newline at end of file +| Get profile | GMAIL_GET_PROFILE | (none) | +--- +*Powered by [Composio](https://composio.dev)* diff --git a/go-to-webinar-automation/SKILL.md b/go-to-webinar-automation/SKILL.md new file mode 100644 index 0000000..57bcd6f --- /dev/null +++ b/go-to-webinar-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: go-to-webinar-automation +description: "Automate GoToWebinar tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# GoToWebinar Automation via Rube MCP + +Automate GoToWebinar operations through Composio's GoToWebinar toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/go_to_webinar](https://composio.dev/toolkits/go_to_webinar) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active GoToWebinar connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `go_to_webinar` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `go_to_webinar` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "GoToWebinar operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific GoToWebinar task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["go_to_webinar"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with GoToWebinar-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `go_to_webinar` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/godial-automation/SKILL.md b/godial-automation/SKILL.md new file mode 100644 index 0000000..23c98ee --- /dev/null +++ b/godial-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: godial-automation +description: "Automate Godial tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Godial Automation via Rube MCP + +Automate Godial operations through Composio's Godial toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/godial](https://composio.dev/toolkits/godial) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Godial connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `godial` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `godial` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Godial operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Godial task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["godial"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Godial-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `godial` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gong-automation/SKILL.md b/gong-automation/SKILL.md new file mode 100644 index 0000000..30b48bf --- /dev/null +++ b/gong-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gong-automation +description: "Automate Gong tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gong Automation via Rube MCP + +Automate Gong operations through Composio's Gong toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gong](https://composio.dev/toolkits/gong) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gong connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gong` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gong` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gong operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gong task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gong"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gong-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gong` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/goodbits-automation/SKILL.md b/goodbits-automation/SKILL.md new file mode 100644 index 0000000..52366ad --- /dev/null +++ b/goodbits-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: goodbits-automation +description: "Automate Goodbits tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Goodbits Automation via Rube MCP + +Automate Goodbits operations through Composio's Goodbits toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/goodbits](https://composio.dev/toolkits/goodbits) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Goodbits connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `goodbits` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `goodbits` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Goodbits operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Goodbits task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["goodbits"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Goodbits-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `goodbits` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/goody-automation/SKILL.md b/goody-automation/SKILL.md new file mode 100644 index 0000000..9b9504b --- /dev/null +++ b/goody-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: goody-automation +description: "Automate Goody tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Goody Automation via Rube MCP + +Automate Goody operations through Composio's Goody toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/goody](https://composio.dev/toolkits/goody) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Goody connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `goody` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `goody` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Goody operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Goody task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["goody"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Goody-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `goody` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-address-validation-automation/SKILL.md b/google-address-validation-automation/SKILL.md new file mode 100644 index 0000000..e08c8d7 --- /dev/null +++ b/google-address-validation-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: google-address-validation-automation +description: "Automate Google Address Validation tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Address Validation Automation via Rube MCP + +Automate Google Address Validation operations through Composio's Google Address Validation toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_address_validation](https://composio.dev/toolkits/google_address_validation) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Address Validation connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_address_validation` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_address_validation` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Address Validation operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Address Validation task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["google_address_validation"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Address Validation-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_address_validation` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-admin-automation/SKILL.md b/google-admin-automation/SKILL.md new file mode 100644 index 0000000..14f93f9 --- /dev/null +++ b/google-admin-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: google-admin-automation +description: "Automate Google Admin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Admin Automation via Rube MCP + +Automate Google Admin operations through Composio's Google Admin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_admin](https://composio.dev/toolkits/google_admin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Admin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Admin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Admin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["google_admin"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Admin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-analytics-automation/SKILL.md b/google-analytics-automation/SKILL.md index 68aa6c1..2f55abe 100644 --- a/google-analytics-automation/SKILL.md +++ b/google-analytics-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Google Analytics 4 (GA4) reporting and property management through Composio's Google Analytics toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/google_analytics](https://composio.dev/toolkits/google_analytics) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -225,3 +227,6 @@ Automate Google Analytics 4 (GA4) reporting and property management through Comp | Pivot report | GOOGLE_ANALYTICS_RUN_PIVOT_REPORT | property, dateRanges, pivots | | Funnel report | GOOGLE_ANALYTICS_RUN_FUNNEL_REPORT | property, dateRanges, funnel | | List key events | GOOGLE_ANALYTICS_LIST_KEY_EVENTS | parent, pageSize | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-calendar-automation/SKILL.md b/google-calendar-automation/SKILL.md index 0240d85..2561d9b 100644 --- a/google-calendar-automation/SKILL.md +++ b/google-calendar-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Google Calendar workflows including event creation, scheduling, availability checks, attendee management, and calendar browsing through Composio's Google Calendar toolkit. +**Toolkit docs**: [composio.dev/toolkits/googlecalendar](https://composio.dev/toolkits/googlecalendar) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -174,3 +176,6 @@ Automate Google Calendar workflows including event creation, scheduling, availab | Remove attendee | `GOOGLECALENDAR_REMOVE_ATTENDEE` | `event_id`, `attendee_email` | | Get current time | `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` | `timezone` | | Get calendar | `GOOGLECALENDAR_GET_CALENDAR` | `calendar_id` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-classroom-automation/SKILL.md b/google-classroom-automation/SKILL.md new file mode 100644 index 0000000..60d152d --- /dev/null +++ b/google-classroom-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: google-classroom-automation +description: "Automate Google Classroom tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Classroom Automation via Rube MCP + +Automate Google Classroom operations through Composio's Google Classroom toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_classroom](https://composio.dev/toolkits/google_classroom) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Classroom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_classroom` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_classroom` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Classroom operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Classroom task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["google_classroom"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Classroom-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_classroom` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-cloud-vision-automation/SKILL.md b/google-cloud-vision-automation/SKILL.md new file mode 100644 index 0000000..74046c6 --- /dev/null +++ b/google-cloud-vision-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: google-cloud-vision-automation +description: "Automate Google Cloud Vision tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Cloud Vision Automation via Rube MCP + +Automate Google Cloud Vision operations through Composio's Google Cloud Vision toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_cloud_vision](https://composio.dev/toolkits/google_cloud_vision) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Cloud Vision connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_cloud_vision` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_cloud_vision` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Cloud Vision operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Cloud Vision task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["google_cloud_vision"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Cloud Vision-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_cloud_vision` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-drive-automation/SKILL.md b/google-drive-automation/SKILL.md index e546f3d..64ac888 100644 --- a/google-drive-automation/SKILL.md +++ b/google-drive-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Google Drive workflows including file upload/download, search, folder management, sharing/permissions, and organization through Composio's Google Drive toolkit. +**Toolkit docs**: [composio.dev/toolkits/googledrive](https://composio.dev/toolkits/googledrive) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -191,3 +193,6 @@ For Google Workspace files, set `mime_type` to export: | List shared drives | `GOOGLEDRIVE_LIST_SHARED_DRIVES` | `pageSize` | | Drive info | `GOOGLEDRIVE_GET_ABOUT` | (none) | | Create shortcut | `GOOGLEDRIVE_CREATE_SHORTCUT_TO_FILE` | target file_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-maps-automation/SKILL.md b/google-maps-automation/SKILL.md new file mode 100644 index 0000000..f3dd31b --- /dev/null +++ b/google-maps-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: google-maps-automation +description: "Automate Google Maps tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Maps Automation via Rube MCP + +Automate Google Maps operations through Composio's Google Maps toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_maps](https://composio.dev/toolkits/google_maps) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Maps connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_maps` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_maps` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Maps operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Maps task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["google_maps"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Maps-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_maps` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google-search-console-automation/SKILL.md b/google-search-console-automation/SKILL.md new file mode 100644 index 0000000..35b50a4 --- /dev/null +++ b/google-search-console-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: google-search-console-automation +description: "Automate Google Search Console tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Search Console Automation via Rube MCP + +Automate Google Search Console operations through Composio's Google Search Console toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_search_console](https://composio.dev/toolkits/google_search_console) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Search Console connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_search_console` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_search_console` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Search Console operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Search Console task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["google_search_console"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Search Console-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_search_console` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/google_admin-automation/SKILL.md b/google_admin-automation/SKILL.md new file mode 100644 index 0000000..4e0cf23 --- /dev/null +++ b/google_admin-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: google_admin-automation +description: "Automate Google Admin tasks via Rube MCP (Composio): user management, org units, groups, and domain administration. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Admin Automation via Rube MCP + +Automate Google Admin operations through Composio's Google Admin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_admin](https://composio.dev/toolkits/google_admin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Admin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "user management, org units, groups, and domain administration", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Google Admin +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Google Admin Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Google Admin tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Google Admin Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Google Admin operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Google Admin connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Admin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/google_admin](https://composio.dev/toolkits/google_admin) diff --git a/google_classroom-automation/SKILL.md b/google_classroom-automation/SKILL.md new file mode 100644 index 0000000..0c42f54 --- /dev/null +++ b/google_classroom-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: google_classroom-automation +description: "Automate Google Classroom tasks via Rube MCP (Composio): course management, assignments, student rosters, and announcements. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Classroom Automation via Rube MCP + +Automate Google Classroom operations through Composio's Google Classroom toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_classroom](https://composio.dev/toolkits/google_classroom) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Classroom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_classroom` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_classroom` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "course management, assignments, student rosters, and announcements", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Google Classroom +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Google Classroom Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Google Classroom tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Google Classroom Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Google Classroom operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Google Classroom connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Classroom-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_classroom` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/google_classroom](https://composio.dev/toolkits/google_classroom) diff --git a/google_maps-automation/SKILL.md b/google_maps-automation/SKILL.md new file mode 100644 index 0000000..a2f4d51 --- /dev/null +++ b/google_maps-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: google_maps-automation +description: "Automate Google Maps tasks via Rube MCP (Composio): geocoding, directions, place search, and distance calculations. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Maps Automation via Rube MCP + +Automate Google Maps operations through Composio's Google Maps toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_maps](https://composio.dev/toolkits/google_maps) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Maps connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_maps` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_maps` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "geocoding, directions, place search, and distance calculations", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Google Maps +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Google Maps Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Google Maps tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Google Maps Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Google Maps operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Google Maps connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Maps-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_maps` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/google_maps](https://composio.dev/toolkits/google_maps) diff --git a/google_search_console-automation/SKILL.md b/google_search_console-automation/SKILL.md new file mode 100644 index 0000000..d383af6 --- /dev/null +++ b/google_search_console-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: google_search_console-automation +description: "Automate Google Search Console tasks via Rube MCP (Composio): search performance, URL inspection, sitemaps, and indexing status. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Search Console Automation via Rube MCP + +Automate Google Search Console operations through Composio's Google Search Console toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/google_search_console](https://composio.dev/toolkits/google_search_console) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Search Console connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_search_console` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_search_console` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "search performance, URL inspection, sitemaps, and indexing status", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Google Search Console +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Google Search Console Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Google Search Console tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Google Search Console Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Google Search Console operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Google Search Console connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Search Console-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_search_console` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/google_search_console](https://composio.dev/toolkits/google_search_console) diff --git a/googleads-automation/SKILL.md b/googleads-automation/SKILL.md new file mode 100644 index 0000000..7df4323 --- /dev/null +++ b/googleads-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googleads-automation +description: "Automate Google Ads tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Ads Automation via Rube MCP + +Automate Google Ads operations through Composio's Google Ads toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googleads](https://composio.dev/toolkits/googleads) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Ads connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googleads` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googleads` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Ads operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Ads task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googleads"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Ads-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googleads` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googlebigquery-automation/SKILL.md b/googlebigquery-automation/SKILL.md new file mode 100644 index 0000000..581afd8 --- /dev/null +++ b/googlebigquery-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googlebigquery-automation +description: "Automate Google BigQuery tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google BigQuery Automation via Rube MCP + +Automate Google BigQuery operations through Composio's Google BigQuery toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googlebigquery](https://composio.dev/toolkits/googlebigquery) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google BigQuery connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlebigquery` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlebigquery` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google BigQuery operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google BigQuery task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googlebigquery"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google BigQuery-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googlebigquery` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googlecalendar-automation/SKILL.md b/googlecalendar-automation/SKILL.md new file mode 100644 index 0000000..f12a0fb --- /dev/null +++ b/googlecalendar-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googlecalendar-automation +description: "Automate Google Calendar tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Calendar Automation via Rube MCP + +Automate Google Calendar operations through Composio's Google Calendar toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googlecalendar](https://composio.dev/toolkits/googlecalendar) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Calendar connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlecalendar` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlecalendar` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Calendar operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Calendar task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googlecalendar"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Calendar-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googlecalendar` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googledocs-automation/SKILL.md b/googledocs-automation/SKILL.md new file mode 100644 index 0000000..d7c945f --- /dev/null +++ b/googledocs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googledocs-automation +description: "Automate Google Docs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Docs Automation via Rube MCP + +Automate Google Docs operations through Composio's Google Docs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googledocs](https://composio.dev/toolkits/googledocs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Docs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googledocs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googledocs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Docs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Docs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googledocs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Docs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googledocs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googledrive-automation/SKILL.md b/googledrive-automation/SKILL.md new file mode 100644 index 0000000..88df43c --- /dev/null +++ b/googledrive-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googledrive-automation +description: "Automate Google Drive tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Drive Automation via Rube MCP + +Automate Google Drive operations through Composio's Google Drive toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googledrive](https://composio.dev/toolkits/googledrive) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Drive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googledrive` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googledrive` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Drive operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Drive task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googledrive"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Drive-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googledrive` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googlemeet-automation/SKILL.md b/googlemeet-automation/SKILL.md new file mode 100644 index 0000000..198c07a --- /dev/null +++ b/googlemeet-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googlemeet-automation +description: "Automate Google Meet tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Meet Automation via Rube MCP + +Automate Google Meet operations through Composio's Google Meet toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googlemeet](https://composio.dev/toolkits/googlemeet) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Meet connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlemeet` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlemeet` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Meet operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Meet task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googlemeet"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Meet-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googlemeet` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googlephotos-automation/SKILL.md b/googlephotos-automation/SKILL.md new file mode 100644 index 0000000..fc7a8cf --- /dev/null +++ b/googlephotos-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googlephotos-automation +description: "Automate Google Photos tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Photos Automation via Rube MCP + +Automate Google Photos operations through Composio's Google Photos toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googlephotos](https://composio.dev/toolkits/googlephotos) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Photos connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlephotos` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlephotos` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Photos operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Photos task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googlephotos"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Photos-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googlephotos` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googlesheets-automation/SKILL.md b/googlesheets-automation/SKILL.md index 2e2f892..0d83b3a 100644 --- a/googlesheets-automation/SKILL.md +++ b/googlesheets-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Google Sheets workflows including reading/writing data, managing spreadsheets and tabs, formatting cells, filtering rows, and upserting records through Composio's Google Sheets toolkit. +**Toolkit docs**: [composio.dev/toolkits/googlesheets](https://composio.dev/toolkits/googlesheets) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -195,3 +197,6 @@ Google Sheets enforces strict rate limits: | Delete rows/cols | `GOOGLESHEETS_DELETE_DIMENSION` | `spreadsheet_id`, `sheet_name`, dimension | | Spreadsheet info | `GOOGLESHEETS_GET_SPREADSHEET_INFO` | `spreadsheet_id` | | Update tab props | `GOOGLESHEETS_UPDATE_SHEET_PROPERTIES` | `spreadsheetId`, properties | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googleslides-automation/SKILL.md b/googleslides-automation/SKILL.md new file mode 100644 index 0000000..97f13e8 --- /dev/null +++ b/googleslides-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googleslides-automation +description: "Automate Google Slides tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Slides Automation via Rube MCP + +Automate Google Slides operations through Composio's Google Slides toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googleslides](https://composio.dev/toolkits/googleslides) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Slides connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googleslides` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googleslides` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Slides operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Slides task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googleslides"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Slides-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googleslides` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googlesuper-automation/SKILL.md b/googlesuper-automation/SKILL.md new file mode 100644 index 0000000..ca30f8c --- /dev/null +++ b/googlesuper-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googlesuper-automation +description: "Automate Google Super tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Super Automation via Rube MCP + +Automate Google Super operations through Composio's Google Super toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googlesuper](https://composio.dev/toolkits/googlesuper) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Super connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlesuper` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlesuper` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Super operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Super task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googlesuper"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Super-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googlesuper` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/googletasks-automation/SKILL.md b/googletasks-automation/SKILL.md new file mode 100644 index 0000000..70e9736 --- /dev/null +++ b/googletasks-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: googletasks-automation +description: "Automate Google Tasks tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Google Tasks Automation via Rube MCP + +Automate Google Tasks operations through Composio's Google Tasks toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/googletasks](https://composio.dev/toolkits/googletasks) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Google Tasks connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googletasks` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googletasks` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Google Tasks operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Google Tasks task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["googletasks"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Google Tasks-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `googletasks` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gorgias-automation/SKILL.md b/gorgias-automation/SKILL.md new file mode 100644 index 0000000..e93a629 --- /dev/null +++ b/gorgias-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gorgias-automation +description: "Automate Gorgias tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gorgias Automation via Rube MCP + +Automate Gorgias operations through Composio's Gorgias toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gorgias](https://composio.dev/toolkits/gorgias) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gorgias connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gorgias` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gorgias` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gorgias operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gorgias task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gorgias"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gorgias-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gorgias` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gosquared-automation/SKILL.md b/gosquared-automation/SKILL.md new file mode 100644 index 0000000..dfac20e --- /dev/null +++ b/gosquared-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gosquared-automation +description: "Automate Gosquared tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gosquared Automation via Rube MCP + +Automate Gosquared operations through Composio's Gosquared toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gosquared](https://composio.dev/toolkits/gosquared) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gosquared connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gosquared` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gosquared` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gosquared operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gosquared task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gosquared"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gosquared-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gosquared` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/grafbase-automation/SKILL.md b/grafbase-automation/SKILL.md new file mode 100644 index 0000000..732c776 --- /dev/null +++ b/grafbase-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: grafbase-automation +description: "Automate Grafbase tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Grafbase Automation via Rube MCP + +Automate Grafbase operations through Composio's Grafbase toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/grafbase](https://composio.dev/toolkits/grafbase) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Grafbase connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `grafbase` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `grafbase` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Grafbase operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Grafbase task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["grafbase"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Grafbase-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `grafbase` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/graphhopper-automation/SKILL.md b/graphhopper-automation/SKILL.md new file mode 100644 index 0000000..ed5dd90 --- /dev/null +++ b/graphhopper-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: graphhopper-automation +description: "Automate Graphhopper tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Graphhopper Automation via Rube MCP + +Automate Graphhopper operations through Composio's Graphhopper toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/graphhopper](https://composio.dev/toolkits/graphhopper) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Graphhopper connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `graphhopper` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `graphhopper` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Graphhopper operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Graphhopper task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["graphhopper"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Graphhopper-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `graphhopper` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/griptape-automation/SKILL.md b/griptape-automation/SKILL.md new file mode 100644 index 0000000..a6f06dd --- /dev/null +++ b/griptape-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: griptape-automation +description: "Automate Griptape tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Griptape Automation via Rube MCP + +Automate Griptape operations through Composio's Griptape toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/griptape](https://composio.dev/toolkits/griptape) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Griptape connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `griptape` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `griptape` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Griptape operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Griptape task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["griptape"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Griptape-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `griptape` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/grist-automation/SKILL.md b/grist-automation/SKILL.md new file mode 100644 index 0000000..e0b712e --- /dev/null +++ b/grist-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: grist-automation +description: "Automate Grist tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Grist Automation via Rube MCP + +Automate Grist operations through Composio's Grist toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/grist](https://composio.dev/toolkits/grist) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Grist connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `grist` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `grist` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Grist operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Grist task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["grist"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Grist-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `grist` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/groqcloud-automation/SKILL.md b/groqcloud-automation/SKILL.md new file mode 100644 index 0000000..8cbd783 --- /dev/null +++ b/groqcloud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: groqcloud-automation +description: "Automate Groqcloud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Groqcloud Automation via Rube MCP + +Automate Groqcloud operations through Composio's Groqcloud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/groqcloud](https://composio.dev/toolkits/groqcloud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Groqcloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `groqcloud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `groqcloud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Groqcloud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Groqcloud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["groqcloud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Groqcloud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `groqcloud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/gumroad-automation/SKILL.md b/gumroad-automation/SKILL.md new file mode 100644 index 0000000..63a6839 --- /dev/null +++ b/gumroad-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: gumroad-automation +description: "Automate Gumroad tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Gumroad Automation via Rube MCP + +Automate Gumroad operations through Composio's Gumroad toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/gumroad](https://composio.dev/toolkits/gumroad) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Gumroad connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gumroad` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gumroad` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Gumroad operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Gumroad task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["gumroad"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Gumroad-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `gumroad` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/habitica-automation/SKILL.md b/habitica-automation/SKILL.md new file mode 100644 index 0000000..b91822f --- /dev/null +++ b/habitica-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: habitica-automation +description: "Automate Habitica tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Habitica Automation via Rube MCP + +Automate Habitica operations through Composio's Habitica toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/habitica](https://composio.dev/toolkits/habitica) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Habitica connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `habitica` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `habitica` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Habitica operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Habitica task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["habitica"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Habitica-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `habitica` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hackernews-automation/SKILL.md b/hackernews-automation/SKILL.md new file mode 100644 index 0000000..8776036 --- /dev/null +++ b/hackernews-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hackernews-automation +description: "Automate Hackernews tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hackernews Automation via Rube MCP + +Automate Hackernews operations through Composio's Hackernews toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hackernews](https://composio.dev/toolkits/hackernews) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hackernews connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hackernews` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hackernews` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hackernews operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hackernews task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hackernews"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hackernews-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hackernews` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/happy-scribe-automation/SKILL.md b/happy-scribe-automation/SKILL.md new file mode 100644 index 0000000..3756efc --- /dev/null +++ b/happy-scribe-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: happy-scribe-automation +description: "Automate Happy Scribe tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Happy Scribe Automation via Rube MCP + +Automate Happy Scribe operations through Composio's Happy Scribe toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/happy_scribe](https://composio.dev/toolkits/happy_scribe) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Happy Scribe connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `happy_scribe` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `happy_scribe` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Happy Scribe operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Happy Scribe task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["happy_scribe"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Happy Scribe-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `happy_scribe` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/harvest-automation/SKILL.md b/harvest-automation/SKILL.md new file mode 100644 index 0000000..a5154ba --- /dev/null +++ b/harvest-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: harvest-automation +description: "Automate Harvest tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Harvest Automation via Rube MCP + +Automate Harvest operations through Composio's Harvest toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/harvest](https://composio.dev/toolkits/harvest) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Harvest connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `harvest` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `harvest` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Harvest operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Harvest task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["harvest"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Harvest-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `harvest` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hashnode-automation/SKILL.md b/hashnode-automation/SKILL.md new file mode 100644 index 0000000..31d47bf --- /dev/null +++ b/hashnode-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hashnode-automation +description: "Automate Hashnode tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hashnode Automation via Rube MCP + +Automate Hashnode operations through Composio's Hashnode toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hashnode](https://composio.dev/toolkits/hashnode) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hashnode connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hashnode` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hashnode` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hashnode operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hashnode task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hashnode"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hashnode-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hashnode` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/helcim-automation/SKILL.md b/helcim-automation/SKILL.md new file mode 100644 index 0000000..fc926df --- /dev/null +++ b/helcim-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: helcim-automation +description: "Automate Helcim tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Helcim Automation via Rube MCP + +Automate Helcim operations through Composio's Helcim toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/helcim](https://composio.dev/toolkits/helcim) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Helcim connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `helcim` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `helcim` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Helcim operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Helcim task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["helcim"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Helcim-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `helcim` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/helloleads-automation/SKILL.md b/helloleads-automation/SKILL.md new file mode 100644 index 0000000..795f523 --- /dev/null +++ b/helloleads-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: helloleads-automation +description: "Automate Helloleads tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Helloleads Automation via Rube MCP + +Automate Helloleads operations through Composio's Helloleads toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/helloleads](https://composio.dev/toolkits/helloleads) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Helloleads connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `helloleads` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `helloleads` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Helloleads operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Helloleads task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["helloleads"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Helloleads-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `helloleads` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/helpdesk-automation/SKILL.md b/helpdesk-automation/SKILL.md index 0b2b428..0ded03d 100644 --- a/helpdesk-automation/SKILL.md +++ b/helpdesk-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate HelpDesk ticketing operations through Composio's HelpDesk toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/helpdesk](https://composio.dev/toolkits/helpdesk) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -164,3 +166,6 @@ Backward pagination: | List views | HELPDESK_LIST_VIEWS | (none) | | List canned responses | HELPDESK_LIST_CANNED_RESPONSES | (none) | | List custom fields | HELPDESK_LIST_CUSTOM_FIELDS | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/helpwise-automation/SKILL.md b/helpwise-automation/SKILL.md new file mode 100644 index 0000000..495d737 --- /dev/null +++ b/helpwise-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: helpwise-automation +description: "Automate Helpwise tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Helpwise Automation via Rube MCP + +Automate Helpwise operations through Composio's Helpwise toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/helpwise](https://composio.dev/toolkits/helpwise) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Helpwise connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `helpwise` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `helpwise` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Helpwise operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Helpwise task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["helpwise"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Helpwise-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `helpwise` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/here-automation/SKILL.md b/here-automation/SKILL.md new file mode 100644 index 0000000..7cf32fc --- /dev/null +++ b/here-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: here-automation +description: "Automate Here tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Here Automation via Rube MCP + +Automate Here operations through Composio's Here toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/here](https://composio.dev/toolkits/here) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Here connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `here` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `here` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Here operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Here task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["here"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Here-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `here` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/heygen-automation/SKILL.md b/heygen-automation/SKILL.md new file mode 100644 index 0000000..8afe35c --- /dev/null +++ b/heygen-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: heygen-automation +description: "Automate Heygen tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Heygen Automation via Rube MCP + +Automate Heygen operations through Composio's Heygen toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/heygen](https://composio.dev/toolkits/heygen) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Heygen connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `heygen` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `heygen` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Heygen operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Heygen task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["heygen"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Heygen-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `heygen` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/heyreach-automation/SKILL.md b/heyreach-automation/SKILL.md new file mode 100644 index 0000000..99b5274 --- /dev/null +++ b/heyreach-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: heyreach-automation +description: "Automate Heyreach tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Heyreach Automation via Rube MCP + +Automate Heyreach operations through Composio's Heyreach toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/heyreach](https://composio.dev/toolkits/heyreach) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Heyreach connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `heyreach` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `heyreach` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Heyreach operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Heyreach task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["heyreach"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Heyreach-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `heyreach` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/heyzine-automation/SKILL.md b/heyzine-automation/SKILL.md new file mode 100644 index 0000000..a5b57a5 --- /dev/null +++ b/heyzine-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: heyzine-automation +description: "Automate Heyzine tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Heyzine Automation via Rube MCP + +Automate Heyzine operations through Composio's Heyzine toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/heyzine](https://composio.dev/toolkits/heyzine) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Heyzine connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `heyzine` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `heyzine` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Heyzine operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Heyzine task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["heyzine"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Heyzine-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `heyzine` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/highergov-automation/SKILL.md b/highergov-automation/SKILL.md new file mode 100644 index 0000000..a717590 --- /dev/null +++ b/highergov-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: highergov-automation +description: "Automate Highergov tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Highergov Automation via Rube MCP + +Automate Highergov operations through Composio's Highergov toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/highergov](https://composio.dev/toolkits/highergov) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Highergov connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `highergov` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `highergov` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Highergov operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Highergov task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["highergov"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Highergov-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `highergov` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/highlevel-automation/SKILL.md b/highlevel-automation/SKILL.md new file mode 100644 index 0000000..5a63f70 --- /dev/null +++ b/highlevel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: highlevel-automation +description: "Automate Highlevel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Highlevel Automation via Rube MCP + +Automate Highlevel operations through Composio's Highlevel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/highlevel](https://composio.dev/toolkits/highlevel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Highlevel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `highlevel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `highlevel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Highlevel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Highlevel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["highlevel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Highlevel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `highlevel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/honeybadger-automation/SKILL.md b/honeybadger-automation/SKILL.md new file mode 100644 index 0000000..6e210c1 --- /dev/null +++ b/honeybadger-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: honeybadger-automation +description: "Automate Honeybadger tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Honeybadger Automation via Rube MCP + +Automate Honeybadger operations through Composio's Honeybadger toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/honeybadger](https://composio.dev/toolkits/honeybadger) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Honeybadger connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `honeybadger` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `honeybadger` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Honeybadger operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Honeybadger task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["honeybadger"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Honeybadger-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `honeybadger` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/honeyhive-automation/SKILL.md b/honeyhive-automation/SKILL.md new file mode 100644 index 0000000..59dc5e3 --- /dev/null +++ b/honeyhive-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: honeyhive-automation +description: "Automate Honeyhive tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Honeyhive Automation via Rube MCP + +Automate Honeyhive operations through Composio's Honeyhive toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/honeyhive](https://composio.dev/toolkits/honeyhive) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Honeyhive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `honeyhive` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `honeyhive` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Honeyhive operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Honeyhive task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["honeyhive"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Honeyhive-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `honeyhive` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hookdeck-automation/SKILL.md b/hookdeck-automation/SKILL.md new file mode 100644 index 0000000..b4c1e5e --- /dev/null +++ b/hookdeck-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hookdeck-automation +description: "Automate Hookdeck tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hookdeck Automation via Rube MCP + +Automate Hookdeck operations through Composio's Hookdeck toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hookdeck](https://composio.dev/toolkits/hookdeck) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hookdeck connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hookdeck` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hookdeck` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hookdeck operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hookdeck task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hookdeck"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hookdeck-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hookdeck` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hotspotsystem-automation/SKILL.md b/hotspotsystem-automation/SKILL.md new file mode 100644 index 0000000..e292193 --- /dev/null +++ b/hotspotsystem-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hotspotsystem-automation +description: "Automate Hotspotsystem tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hotspotsystem Automation via Rube MCP + +Automate Hotspotsystem operations through Composio's Hotspotsystem toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hotspotsystem](https://composio.dev/toolkits/hotspotsystem) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hotspotsystem connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hotspotsystem` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hotspotsystem` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hotspotsystem operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hotspotsystem task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hotspotsystem"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hotspotsystem-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hotspotsystem` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/html-to-image-automation/SKILL.md b/html-to-image-automation/SKILL.md new file mode 100644 index 0000000..8110b68 --- /dev/null +++ b/html-to-image-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: html-to-image-automation +description: "Automate Html To Image tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Html To Image Automation via Rube MCP + +Automate Html To Image operations through Composio's Html To Image toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/html_to_image](https://composio.dev/toolkits/html_to_image) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Html To Image connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `html_to_image` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `html_to_image` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Html To Image operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Html To Image task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["html_to_image"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Html To Image-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `html_to_image` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hubspot-automation/SKILL.md b/hubspot-automation/SKILL.md index 653eec3..247f165 100644 --- a/hubspot-automation/SKILL.md +++ b/hubspot-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate HubSpot CRM workflows including contact/company management, deal pipeline tracking, ticket search, and custom property creation through Composio's HubSpot toolkit. +**Toolkit docs**: [composio.dev/toolkits/hubspot](https://composio.dev/toolkits/hubspot) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -175,4 +177,6 @@ Automate HubSpot CRM workflows including contact/company management, deal pipeli | List properties | `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` | `objectType` | | Create property | `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` | `objectType, name, label, type, fieldType` | | Get owners | `HUBSPOT_RETRIEVE_OWNERS` | None | -| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None | \ No newline at end of file +| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None | +--- +*Powered by [Composio](https://composio.dev)* diff --git a/humanitix-automation/SKILL.md b/humanitix-automation/SKILL.md new file mode 100644 index 0000000..d2803c2 --- /dev/null +++ b/humanitix-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: humanitix-automation +description: "Automate Humanitix tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Humanitix Automation via Rube MCP + +Automate Humanitix operations through Composio's Humanitix toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/humanitix](https://composio.dev/toolkits/humanitix) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Humanitix connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `humanitix` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `humanitix` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Humanitix operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Humanitix task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["humanitix"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Humanitix-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `humanitix` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/humanloop-automation/SKILL.md b/humanloop-automation/SKILL.md new file mode 100644 index 0000000..2ba6388 --- /dev/null +++ b/humanloop-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: humanloop-automation +description: "Automate Humanloop tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Humanloop Automation via Rube MCP + +Automate Humanloop operations through Composio's Humanloop toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/humanloop](https://composio.dev/toolkits/humanloop) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Humanloop connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `humanloop` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `humanloop` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Humanloop operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Humanloop task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["humanloop"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Humanloop-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `humanloop` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hunter-automation/SKILL.md b/hunter-automation/SKILL.md new file mode 100644 index 0000000..c2e39c6 --- /dev/null +++ b/hunter-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hunter-automation +description: "Automate Hunter tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hunter Automation via Rube MCP + +Automate Hunter operations through Composio's Hunter toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hunter](https://composio.dev/toolkits/hunter) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hunter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hunter` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hunter` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hunter operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hunter task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hunter"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hunter-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hunter` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hypeauditor-automation/SKILL.md b/hypeauditor-automation/SKILL.md new file mode 100644 index 0000000..6437e5d --- /dev/null +++ b/hypeauditor-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hypeauditor-automation +description: "Automate Hypeauditor tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hypeauditor Automation via Rube MCP + +Automate Hypeauditor operations through Composio's Hypeauditor toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hypeauditor](https://composio.dev/toolkits/hypeauditor) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hypeauditor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hypeauditor` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hypeauditor` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hypeauditor operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hypeauditor task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hypeauditor"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hypeauditor-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hypeauditor` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hyperbrowser-automation/SKILL.md b/hyperbrowser-automation/SKILL.md new file mode 100644 index 0000000..660aa07 --- /dev/null +++ b/hyperbrowser-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hyperbrowser-automation +description: "Automate Hyperbrowser tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hyperbrowser Automation via Rube MCP + +Automate Hyperbrowser operations through Composio's Hyperbrowser toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hyperbrowser](https://composio.dev/toolkits/hyperbrowser) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hyperbrowser connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hyperbrowser` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hyperbrowser` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hyperbrowser operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hyperbrowser task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hyperbrowser"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hyperbrowser-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hyperbrowser` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hyperise-automation/SKILL.md b/hyperise-automation/SKILL.md new file mode 100644 index 0000000..1dc6e5c --- /dev/null +++ b/hyperise-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hyperise-automation +description: "Automate Hyperise tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hyperise Automation via Rube MCP + +Automate Hyperise operations through Composio's Hyperise toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hyperise](https://composio.dev/toolkits/hyperise) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hyperise connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hyperise` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hyperise` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hyperise operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hyperise task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hyperise"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hyperise-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hyperise` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/hystruct-automation/SKILL.md b/hystruct-automation/SKILL.md new file mode 100644 index 0000000..d318a8c --- /dev/null +++ b/hystruct-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: hystruct-automation +description: "Automate Hystruct tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Hystruct Automation via Rube MCP + +Automate Hystruct operations through Composio's Hystruct toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/hystruct](https://composio.dev/toolkits/hystruct) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Hystruct connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hystruct` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hystruct` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Hystruct operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Hystruct task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["hystruct"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Hystruct-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `hystruct` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/icims-talent-cloud-automation/SKILL.md b/icims-talent-cloud-automation/SKILL.md new file mode 100644 index 0000000..58b4659 --- /dev/null +++ b/icims-talent-cloud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: icims-talent-cloud-automation +description: "Automate Icims Talent Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Icims Talent Cloud Automation via Rube MCP + +Automate Icims Talent Cloud operations through Composio's Icims Talent Cloud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/icims_talent_cloud](https://composio.dev/toolkits/icims_talent_cloud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Icims Talent Cloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `icims_talent_cloud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `icims_talent_cloud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Icims Talent Cloud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Icims Talent Cloud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["icims_talent_cloud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Icims Talent Cloud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `icims_talent_cloud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/icypeas-automation/SKILL.md b/icypeas-automation/SKILL.md new file mode 100644 index 0000000..1f2eff7 --- /dev/null +++ b/icypeas-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: icypeas-automation +description: "Automate Icypeas tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Icypeas Automation via Rube MCP + +Automate Icypeas operations through Composio's Icypeas toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/icypeas](https://composio.dev/toolkits/icypeas) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Icypeas connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `icypeas` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `icypeas` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Icypeas operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Icypeas task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["icypeas"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Icypeas-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `icypeas` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/idea-scale-automation/SKILL.md b/idea-scale-automation/SKILL.md new file mode 100644 index 0000000..6bd7ca0 --- /dev/null +++ b/idea-scale-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: idea-scale-automation +description: "Automate Idea Scale tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Idea Scale Automation via Rube MCP + +Automate Idea Scale operations through Composio's Idea Scale toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/idea_scale](https://composio.dev/toolkits/idea_scale) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Idea Scale connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `idea_scale` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `idea_scale` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Idea Scale operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Idea Scale task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["idea_scale"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Idea Scale-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `idea_scale` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/identitycheck-automation/SKILL.md b/identitycheck-automation/SKILL.md new file mode 100644 index 0000000..ddf1d21 --- /dev/null +++ b/identitycheck-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: identitycheck-automation +description: "Automate Identitycheck tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Identitycheck Automation via Rube MCP + +Automate Identitycheck operations through Composio's Identitycheck toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/identitycheck](https://composio.dev/toolkits/identitycheck) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Identitycheck connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `identitycheck` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `identitycheck` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Identitycheck operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Identitycheck task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["identitycheck"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Identitycheck-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `identitycheck` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ignisign-automation/SKILL.md b/ignisign-automation/SKILL.md new file mode 100644 index 0000000..47592dd --- /dev/null +++ b/ignisign-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ignisign-automation +description: "Automate Ignisign tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ignisign Automation via Rube MCP + +Automate Ignisign operations through Composio's Ignisign toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ignisign](https://composio.dev/toolkits/ignisign) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ignisign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ignisign` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ignisign` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ignisign operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ignisign task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ignisign"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ignisign-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ignisign` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/imagekit-io-automation/SKILL.md b/imagekit-io-automation/SKILL.md new file mode 100644 index 0000000..1f860dd --- /dev/null +++ b/imagekit-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: imagekit-io-automation +description: "Automate Imagekit IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Imagekit IO Automation via Rube MCP + +Automate Imagekit IO operations through Composio's Imagekit IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/imagekit_io](https://composio.dev/toolkits/imagekit_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Imagekit IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `imagekit_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `imagekit_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Imagekit IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Imagekit IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["imagekit_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Imagekit IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `imagekit_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/imgbb-automation/SKILL.md b/imgbb-automation/SKILL.md new file mode 100644 index 0000000..9ac19f7 --- /dev/null +++ b/imgbb-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: imgbb-automation +description: "Automate Imgbb tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Imgbb Automation via Rube MCP + +Automate Imgbb operations through Composio's Imgbb toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/imgbb](https://composio.dev/toolkits/imgbb) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Imgbb connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `imgbb` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `imgbb` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Imgbb operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Imgbb task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["imgbb"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Imgbb-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `imgbb` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/imgix-automation/SKILL.md b/imgix-automation/SKILL.md new file mode 100644 index 0000000..8f8a375 --- /dev/null +++ b/imgix-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: imgix-automation +description: "Automate Imgix tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Imgix Automation via Rube MCP + +Automate Imgix operations through Composio's Imgix toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/imgix](https://composio.dev/toolkits/imgix) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Imgix connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `imgix` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `imgix` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Imgix operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Imgix task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["imgix"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Imgix-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `imgix` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/influxdb-cloud-automation/SKILL.md b/influxdb-cloud-automation/SKILL.md new file mode 100644 index 0000000..dc9e9ed --- /dev/null +++ b/influxdb-cloud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: influxdb-cloud-automation +description: "Automate Influxdb Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Influxdb Cloud Automation via Rube MCP + +Automate Influxdb Cloud operations through Composio's Influxdb Cloud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/influxdb_cloud](https://composio.dev/toolkits/influxdb_cloud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Influxdb Cloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `influxdb_cloud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `influxdb_cloud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Influxdb Cloud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Influxdb Cloud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["influxdb_cloud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Influxdb Cloud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `influxdb_cloud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/insighto-ai-automation/SKILL.md b/insighto-ai-automation/SKILL.md new file mode 100644 index 0000000..442c63e --- /dev/null +++ b/insighto-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: insighto-ai-automation +description: "Automate Insighto AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Insighto AI Automation via Rube MCP + +Automate Insighto AI operations through Composio's Insighto AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/insighto_ai](https://composio.dev/toolkits/insighto_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Insighto AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `insighto_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `insighto_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Insighto AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Insighto AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["insighto_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Insighto AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `insighto_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/instacart-automation/SKILL.md b/instacart-automation/SKILL.md new file mode 100644 index 0000000..52c9a8e --- /dev/null +++ b/instacart-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: instacart-automation +description: "Automate Instacart tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Instacart Automation via Rube MCP + +Automate Instacart operations through Composio's Instacart toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/instacart](https://composio.dev/toolkits/instacart) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Instacart connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `instacart` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `instacart` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Instacart operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Instacart task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["instacart"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Instacart-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `instacart` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/instagram-automation/SKILL.md b/instagram-automation/SKILL.md index 31a27d0..91522f6 100644 --- a/instagram-automation/SKILL.md +++ b/instagram-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Instagram operations through Composio's Instagram toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/instagram](https://composio.dev/toolkits/instagram) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -190,3 +192,6 @@ Automate Instagram operations through Composio's Instagram toolkit via Rube MCP. | Get publishing limit | INSTAGRAM_GET_IG_USER_CONTENT_PUBLISHING_LIMIT | ig_user_id | | Get media comments | INSTAGRAM_GET_IG_MEDIA_COMMENTS | ig_media_id | | Get carousel children | INSTAGRAM_GET_IG_MEDIA_CHILDREN | ig_media_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/instantly-automation/SKILL.md b/instantly-automation/SKILL.md new file mode 100644 index 0000000..2620a23 --- /dev/null +++ b/instantly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: instantly-automation +description: "Automate Instantly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Instantly Automation via Rube MCP + +Automate Instantly operations through Composio's Instantly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/instantly](https://composio.dev/toolkits/instantly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Instantly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `instantly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `instantly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Instantly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Instantly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["instantly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Instantly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `instantly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/intelliprint-automation/SKILL.md b/intelliprint-automation/SKILL.md new file mode 100644 index 0000000..6ec88fb --- /dev/null +++ b/intelliprint-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: intelliprint-automation +description: "Automate Intelliprint tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Intelliprint Automation via Rube MCP + +Automate Intelliprint operations through Composio's Intelliprint toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/intelliprint](https://composio.dev/toolkits/intelliprint) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Intelliprint connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `intelliprint` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intelliprint` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Intelliprint operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Intelliprint task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["intelliprint"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Intelliprint-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `intelliprint` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/intercom-automation/SKILL.md b/intercom-automation/SKILL.md index 84435ac..97edb8a 100644 --- a/intercom-automation/SKILL.md +++ b/intercom-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Intercom operations through Composio's Intercom toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/intercom](https://composio.dev/toolkits/intercom) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -246,3 +248,6 @@ Automate Intercom operations through Composio's Intercom toolkit via Rube MCP. | Company segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES | company_id | | Get counts | INTERCOM_GET_COUNTS | type, count | | List companies | INTERCOM_LIST_ALL_COMPANIES | page, per_page | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/interzoid-automation/SKILL.md b/interzoid-automation/SKILL.md new file mode 100644 index 0000000..4708b84 --- /dev/null +++ b/interzoid-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: interzoid-automation +description: "Automate Interzoid tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Interzoid Automation via Rube MCP + +Automate Interzoid operations through Composio's Interzoid toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/interzoid](https://composio.dev/toolkits/interzoid) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Interzoid connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `interzoid` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `interzoid` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Interzoid operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Interzoid task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["interzoid"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Interzoid-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `interzoid` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ip2location-automation/SKILL.md b/ip2location-automation/SKILL.md new file mode 100644 index 0000000..29772cd --- /dev/null +++ b/ip2location-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ip2location-automation +description: "Automate Ip2location tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ip2location Automation via Rube MCP + +Automate Ip2location operations through Composio's Ip2location toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ip2location](https://composio.dev/toolkits/ip2location) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ip2location connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ip2location operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ip2location task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ip2location"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ip2location-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ip2location-io-automation/SKILL.md b/ip2location-io-automation/SKILL.md new file mode 100644 index 0000000..002f18a --- /dev/null +++ b/ip2location-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ip2location-io-automation +description: "Automate Ip2location IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ip2location IO Automation via Rube MCP + +Automate Ip2location IO operations through Composio's Ip2location IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ip2location_io](https://composio.dev/toolkits/ip2location_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ip2location IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ip2location IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ip2location IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ip2location_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ip2location IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ip2proxy-automation/SKILL.md b/ip2proxy-automation/SKILL.md new file mode 100644 index 0000000..cd3b59d --- /dev/null +++ b/ip2proxy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ip2proxy-automation +description: "Automate Ip2proxy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ip2proxy Automation via Rube MCP + +Automate Ip2proxy operations through Composio's Ip2proxy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ip2proxy](https://composio.dev/toolkits/ip2proxy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ip2proxy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2proxy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2proxy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ip2proxy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ip2proxy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ip2proxy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ip2proxy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2proxy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ip2whois-automation/SKILL.md b/ip2whois-automation/SKILL.md new file mode 100644 index 0000000..daa5060 --- /dev/null +++ b/ip2whois-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ip2whois-automation +description: "Automate Ip2whois tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ip2whois Automation via Rube MCP + +Automate Ip2whois operations through Composio's Ip2whois toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ip2whois](https://composio.dev/toolkits/ip2whois) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ip2whois connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2whois` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2whois` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ip2whois operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ip2whois task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ip2whois"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ip2whois-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2whois` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ipdata-co-automation/SKILL.md b/ipdata-co-automation/SKILL.md new file mode 100644 index 0000000..47076a2 --- /dev/null +++ b/ipdata-co-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ipdata-co-automation +description: "Automate Ipdata co tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ipdata co Automation via Rube MCP + +Automate Ipdata co operations through Composio's Ipdata co toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ipdata_co](https://composio.dev/toolkits/ipdata_co) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ipdata co connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ipdata_co` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ipdata_co` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ipdata co operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ipdata co task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ipdata_co"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ipdata co-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ipdata_co` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ipinfo-io-automation/SKILL.md b/ipinfo-io-automation/SKILL.md new file mode 100644 index 0000000..09d0c38 --- /dev/null +++ b/ipinfo-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ipinfo-io-automation +description: "Automate Ipinfo IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ipinfo IO Automation via Rube MCP + +Automate Ipinfo IO operations through Composio's Ipinfo IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ipinfo_io](https://composio.dev/toolkits/ipinfo_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ipinfo IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ipinfo_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ipinfo_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ipinfo IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ipinfo IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ipinfo_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ipinfo IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ipinfo_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/iqair-airvisual-automation/SKILL.md b/iqair-airvisual-automation/SKILL.md new file mode 100644 index 0000000..1171aab --- /dev/null +++ b/iqair-airvisual-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: iqair-airvisual-automation +description: "Automate Iqair Airvisual tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Iqair Airvisual Automation via Rube MCP + +Automate Iqair Airvisual operations through Composio's Iqair Airvisual toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/iqair_airvisual](https://composio.dev/toolkits/iqair_airvisual) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Iqair Airvisual connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `iqair_airvisual` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `iqair_airvisual` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Iqair Airvisual operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Iqair Airvisual task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["iqair_airvisual"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Iqair Airvisual-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `iqair_airvisual` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/jigsawstack-automation/SKILL.md b/jigsawstack-automation/SKILL.md new file mode 100644 index 0000000..cc5c468 --- /dev/null +++ b/jigsawstack-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: jigsawstack-automation +description: "Automate Jigsawstack tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Jigsawstack Automation via Rube MCP + +Automate Jigsawstack operations through Composio's Jigsawstack toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/jigsawstack](https://composio.dev/toolkits/jigsawstack) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Jigsawstack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jigsawstack` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jigsawstack` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Jigsawstack operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Jigsawstack task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["jigsawstack"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Jigsawstack-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `jigsawstack` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/jira-automation/SKILL.md b/jira-automation/SKILL.md index 88b503f..d3554ef 100644 --- a/jira-automation/SKILL.md +++ b/jira-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Jira operations through Composio's Jira toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/jira](https://composio.dev/toolkits/jira) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -183,3 +185,6 @@ Automate Jira operations through Composio's Jira toolkit via Rube MCP. | List filters | JIRA_LIST_FILTERS | (none) | | Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey | | Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/jobnimbus-automation/SKILL.md b/jobnimbus-automation/SKILL.md new file mode 100644 index 0000000..e4bf30c --- /dev/null +++ b/jobnimbus-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: jobnimbus-automation +description: "Automate Jobnimbus tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Jobnimbus Automation via Rube MCP + +Automate Jobnimbus operations through Composio's Jobnimbus toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/jobnimbus](https://composio.dev/toolkits/jobnimbus) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Jobnimbus connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jobnimbus` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jobnimbus` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Jobnimbus operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Jobnimbus task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["jobnimbus"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Jobnimbus-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `jobnimbus` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/jotform-automation/SKILL.md b/jotform-automation/SKILL.md new file mode 100644 index 0000000..2b1da90 --- /dev/null +++ b/jotform-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: jotform-automation +description: "Automate Jotform tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Jotform Automation via Rube MCP + +Automate Jotform operations through Composio's Jotform toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/jotform](https://composio.dev/toolkits/jotform) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Jotform connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jotform` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jotform` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Jotform operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Jotform task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["jotform"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Jotform-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `jotform` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/jumpcloud-automation/SKILL.md b/jumpcloud-automation/SKILL.md new file mode 100644 index 0000000..9abb4af --- /dev/null +++ b/jumpcloud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: jumpcloud-automation +description: "Automate Jumpcloud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Jumpcloud Automation via Rube MCP + +Automate Jumpcloud operations through Composio's Jumpcloud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/jumpcloud](https://composio.dev/toolkits/jumpcloud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Jumpcloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jumpcloud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jumpcloud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Jumpcloud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Jumpcloud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["jumpcloud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Jumpcloud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `jumpcloud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/junglescout-automation/SKILL.md b/junglescout-automation/SKILL.md new file mode 100644 index 0000000..86f7ceb --- /dev/null +++ b/junglescout-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: junglescout-automation +description: "Automate Junglescout tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Junglescout Automation via Rube MCP + +Automate Junglescout operations through Composio's Junglescout toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/junglescout](https://composio.dev/toolkits/junglescout) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Junglescout connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `junglescout` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `junglescout` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Junglescout operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Junglescout task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["junglescout"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Junglescout-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `junglescout` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kadoa-automation/SKILL.md b/kadoa-automation/SKILL.md new file mode 100644 index 0000000..0838ea6 --- /dev/null +++ b/kadoa-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kadoa-automation +description: "Automate Kadoa tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kadoa Automation via Rube MCP + +Automate Kadoa operations through Composio's Kadoa toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kadoa](https://composio.dev/toolkits/kadoa) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kadoa connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kadoa` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kadoa` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kadoa operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kadoa task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kadoa"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kadoa-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kadoa` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kaggle-automation/SKILL.md b/kaggle-automation/SKILL.md new file mode 100644 index 0000000..e43364d --- /dev/null +++ b/kaggle-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kaggle-automation +description: "Automate Kaggle tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kaggle Automation via Rube MCP + +Automate Kaggle operations through Composio's Kaggle toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kaggle](https://composio.dev/toolkits/kaggle) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kaggle connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kaggle` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kaggle` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kaggle operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kaggle task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kaggle"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kaggle-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kaggle` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kaleido-automation/SKILL.md b/kaleido-automation/SKILL.md new file mode 100644 index 0000000..e6243a6 --- /dev/null +++ b/kaleido-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kaleido-automation +description: "Automate Kaleido tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kaleido Automation via Rube MCP + +Automate Kaleido operations through Composio's Kaleido toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kaleido](https://composio.dev/toolkits/kaleido) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kaleido connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kaleido` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kaleido` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kaleido operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kaleido task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kaleido"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kaleido-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kaleido` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/keap-automation/SKILL.md b/keap-automation/SKILL.md new file mode 100644 index 0000000..eca259f --- /dev/null +++ b/keap-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: keap-automation +description: "Automate Keap tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Keap Automation via Rube MCP + +Automate Keap operations through Composio's Keap toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/keap](https://composio.dev/toolkits/keap) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Keap connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `keap` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `keap` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Keap operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Keap task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["keap"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Keap-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `keap` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/keen-io-automation/SKILL.md b/keen-io-automation/SKILL.md new file mode 100644 index 0000000..4eb43b4 --- /dev/null +++ b/keen-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: keen-io-automation +description: "Automate Keen IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Keen IO Automation via Rube MCP + +Automate Keen IO operations through Composio's Keen IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/keen_io](https://composio.dev/toolkits/keen_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Keen IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `keen_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `keen_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Keen IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Keen IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["keen_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Keen IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `keen_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kickbox-automation/SKILL.md b/kickbox-automation/SKILL.md new file mode 100644 index 0000000..00862ca --- /dev/null +++ b/kickbox-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kickbox-automation +description: "Automate Kickbox tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kickbox Automation via Rube MCP + +Automate Kickbox operations through Composio's Kickbox toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kickbox](https://composio.dev/toolkits/kickbox) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kickbox connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kickbox` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kickbox` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kickbox operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kickbox task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kickbox"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kickbox-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kickbox` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kit-automation/SKILL.md b/kit-automation/SKILL.md new file mode 100644 index 0000000..36da0b4 --- /dev/null +++ b/kit-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kit-automation +description: "Automate Kit tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kit Automation via Rube MCP + +Automate Kit operations through Composio's Kit toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kit](https://composio.dev/toolkits/kit) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kit` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kit` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kit operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kit task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kit"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kit-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kit` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/klaviyo-automation/SKILL.md b/klaviyo-automation/SKILL.md index d5dc32d..d7e2a97 100644 --- a/klaviyo-automation/SKILL.md +++ b/klaviyo-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Klaviyo email and SMS marketing operations through Composio's Klaviyo toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/klaviyo](https://composio.dev/toolkits/klaviyo) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -188,3 +190,6 @@ fields__template=['name', 'html', 'text'] | Get campaign message | KLAVIYO_GET_CAMPAIGN_MESSAGE | id, fields__campaign__message | | Get campaign tags | KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS | id | | Get send job status | KLAVIYO_GET_CAMPAIGN_SEND_JOB | id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/klipfolio-automation/SKILL.md b/klipfolio-automation/SKILL.md new file mode 100644 index 0000000..63c93fd --- /dev/null +++ b/klipfolio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: klipfolio-automation +description: "Automate Klipfolio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Klipfolio Automation via Rube MCP + +Automate Klipfolio operations through Composio's Klipfolio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/klipfolio](https://composio.dev/toolkits/klipfolio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Klipfolio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `klipfolio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `klipfolio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Klipfolio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Klipfolio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["klipfolio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Klipfolio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `klipfolio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ko-fi-automation/SKILL.md b/ko-fi-automation/SKILL.md new file mode 100644 index 0000000..397c7db --- /dev/null +++ b/ko-fi-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ko-fi-automation +description: "Automate Ko Fi tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ko Fi Automation via Rube MCP + +Automate Ko Fi operations through Composio's Ko Fi toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ko_fi](https://composio.dev/toolkits/ko_fi) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ko Fi connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ko_fi` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ko_fi` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ko Fi operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ko Fi task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ko_fi"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ko Fi-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ko_fi` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kommo-automation/SKILL.md b/kommo-automation/SKILL.md new file mode 100644 index 0000000..38c4b63 --- /dev/null +++ b/kommo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kommo-automation +description: "Automate Kommo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kommo Automation via Rube MCP + +Automate Kommo operations through Composio's Kommo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kommo](https://composio.dev/toolkits/kommo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kommo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kommo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kommo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kommo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kommo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kommo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kommo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kommo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kontent-ai-automation/SKILL.md b/kontent-ai-automation/SKILL.md new file mode 100644 index 0000000..26bf3eb --- /dev/null +++ b/kontent-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kontent-ai-automation +description: "Automate Kontent AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kontent AI Automation via Rube MCP + +Automate Kontent AI operations through Composio's Kontent AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kontent_ai](https://composio.dev/toolkits/kontent_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kontent AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kontent_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kontent_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kontent AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kontent AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kontent_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kontent AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kontent_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/kraken-io-automation/SKILL.md b/kraken-io-automation/SKILL.md new file mode 100644 index 0000000..c18b0d7 --- /dev/null +++ b/kraken-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: kraken-io-automation +description: "Automate Kraken IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Kraken IO Automation via Rube MCP + +Automate Kraken IO operations through Composio's Kraken IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/kraken_io](https://composio.dev/toolkits/kraken_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Kraken IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `kraken_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `kraken_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Kraken IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Kraken IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["kraken_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Kraken IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `kraken_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/l2s-automation/SKILL.md b/l2s-automation/SKILL.md new file mode 100644 index 0000000..23bbdb2 --- /dev/null +++ b/l2s-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: l2s-automation +description: "Automate L2s tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# L2s Automation via Rube MCP + +Automate L2s operations through Composio's L2s toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/l2s](https://composio.dev/toolkits/l2s) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active L2s connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `l2s` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `l2s` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "L2s operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific L2s task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["l2s"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with L2s-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `l2s` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/labs64-netlicensing-automation/SKILL.md b/labs64-netlicensing-automation/SKILL.md new file mode 100644 index 0000000..78aee58 --- /dev/null +++ b/labs64-netlicensing-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: labs64-netlicensing-automation +description: "Automate Labs64 Netlicensing tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Labs64 Netlicensing Automation via Rube MCP + +Automate Labs64 Netlicensing operations through Composio's Labs64 Netlicensing toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/labs64_netlicensing](https://composio.dev/toolkits/labs64_netlicensing) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Labs64 Netlicensing connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `labs64_netlicensing` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `labs64_netlicensing` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Labs64 Netlicensing operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Labs64 Netlicensing task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["labs64_netlicensing"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Labs64 Netlicensing-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `labs64_netlicensing` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/landbot-automation/SKILL.md b/landbot-automation/SKILL.md new file mode 100644 index 0000000..0470075 --- /dev/null +++ b/landbot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: landbot-automation +description: "Automate Landbot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Landbot Automation via Rube MCP + +Automate Landbot operations through Composio's Landbot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/landbot](https://composio.dev/toolkits/landbot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Landbot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `landbot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `landbot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Landbot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Landbot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["landbot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Landbot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `landbot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/langbase-automation/SKILL.md b/langbase-automation/SKILL.md new file mode 100644 index 0000000..1e29c24 --- /dev/null +++ b/langbase-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: langbase-automation +description: "Automate Langbase tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Langbase Automation via Rube MCP + +Automate Langbase operations through Composio's Langbase toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/langbase](https://composio.dev/toolkits/langbase) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Langbase connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `langbase` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `langbase` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Langbase operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Langbase task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["langbase"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Langbase-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `langbase` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lastpass-automation/SKILL.md b/lastpass-automation/SKILL.md new file mode 100644 index 0000000..36ffdbf --- /dev/null +++ b/lastpass-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lastpass-automation +description: "Automate Lastpass tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lastpass Automation via Rube MCP + +Automate Lastpass operations through Composio's Lastpass toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lastpass](https://composio.dev/toolkits/lastpass) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lastpass connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lastpass` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lastpass` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lastpass operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lastpass task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lastpass"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lastpass-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lastpass` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/launch-darkly-automation/SKILL.md b/launch-darkly-automation/SKILL.md new file mode 100644 index 0000000..87df268 --- /dev/null +++ b/launch-darkly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: launch-darkly-automation +description: "Automate LaunchDarkly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# LaunchDarkly Automation via Rube MCP + +Automate LaunchDarkly operations through Composio's LaunchDarkly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/launch_darkly](https://composio.dev/toolkits/launch_darkly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active LaunchDarkly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `launch_darkly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `launch_darkly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "LaunchDarkly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific LaunchDarkly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["launch_darkly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with LaunchDarkly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `launch_darkly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/launch_darkly-automation/SKILL.md b/launch_darkly-automation/SKILL.md new file mode 100644 index 0000000..4500f91 --- /dev/null +++ b/launch_darkly-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: launch_darkly-automation +description: "Automate LaunchDarkly tasks via Rube MCP (Composio): feature flags, environments, segments, and rollout management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# LaunchDarkly Automation via Rube MCP + +Automate LaunchDarkly operations through Composio's LaunchDarkly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/launch_darkly](https://composio.dev/toolkits/launch_darkly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active LaunchDarkly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `launch_darkly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `launch_darkly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "feature flags, environments, segments, and rollout management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for LaunchDarkly +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available LaunchDarkly Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available LaunchDarkly tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute LaunchDarkly Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple LaunchDarkly operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the LaunchDarkly connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with LaunchDarkly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `launch_darkly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/launch_darkly](https://composio.dev/toolkits/launch_darkly) diff --git a/leadfeeder-automation/SKILL.md b/leadfeeder-automation/SKILL.md new file mode 100644 index 0000000..8f8f0ea --- /dev/null +++ b/leadfeeder-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: leadfeeder-automation +description: "Automate Leadfeeder tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Leadfeeder Automation via Rube MCP + +Automate Leadfeeder operations through Composio's Leadfeeder toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/leadfeeder](https://composio.dev/toolkits/leadfeeder) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Leadfeeder connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `leadfeeder` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `leadfeeder` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Leadfeeder operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Leadfeeder task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["leadfeeder"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Leadfeeder-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `leadfeeder` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/leadoku-automation/SKILL.md b/leadoku-automation/SKILL.md new file mode 100644 index 0000000..9cd69ee --- /dev/null +++ b/leadoku-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: leadoku-automation +description: "Automate Leadoku tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Leadoku Automation via Rube MCP + +Automate Leadoku operations through Composio's Leadoku toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/leadoku](https://composio.dev/toolkits/leadoku) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Leadoku connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `leadoku` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `leadoku` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Leadoku operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Leadoku task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["leadoku"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Leadoku-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `leadoku` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/leiga-automation/SKILL.md b/leiga-automation/SKILL.md new file mode 100644 index 0000000..c0cec46 --- /dev/null +++ b/leiga-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: leiga-automation +description: "Automate Leiga tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Leiga Automation via Rube MCP + +Automate Leiga operations through Composio's Leiga toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/leiga](https://composio.dev/toolkits/leiga) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Leiga connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `leiga` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `leiga` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Leiga operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Leiga task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["leiga"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Leiga-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `leiga` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lemlist-automation/SKILL.md b/lemlist-automation/SKILL.md new file mode 100644 index 0000000..9854f7d --- /dev/null +++ b/lemlist-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lemlist-automation +description: "Automate Lemlist tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lemlist Automation via Rube MCP + +Automate Lemlist operations through Composio's Lemlist toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lemlist](https://composio.dev/toolkits/lemlist) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lemlist connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lemlist` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lemlist` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lemlist operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lemlist task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lemlist"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lemlist-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lemlist` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lemon-squeezy-automation/SKILL.md b/lemon-squeezy-automation/SKILL.md new file mode 100644 index 0000000..0a0bbcd --- /dev/null +++ b/lemon-squeezy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lemon-squeezy-automation +description: "Automate Lemon Squeezy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lemon Squeezy Automation via Rube MCP + +Automate Lemon Squeezy operations through Composio's Lemon Squeezy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lemon_squeezy](https://composio.dev/toolkits/lemon_squeezy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lemon Squeezy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lemon_squeezy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lemon_squeezy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lemon Squeezy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lemon Squeezy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lemon_squeezy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lemon Squeezy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lemon_squeezy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lemon_squeezy-automation/SKILL.md b/lemon_squeezy-automation/SKILL.md new file mode 100644 index 0000000..bddd5a5 --- /dev/null +++ b/lemon_squeezy-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: lemon_squeezy-automation +description: "Automate Lemon Squeezy tasks via Rube MCP (Composio): products, orders, subscriptions, checkouts, and digital sales. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lemon Squeezy Automation via Rube MCP + +Automate Lemon Squeezy operations through Composio's Lemon Squeezy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lemon_squeezy](https://composio.dev/toolkits/lemon_squeezy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lemon Squeezy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lemon_squeezy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lemon_squeezy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "products, orders, subscriptions, checkouts, and digital sales", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Lemon Squeezy +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Lemon Squeezy Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Lemon Squeezy tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Lemon Squeezy Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Lemon Squeezy operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Lemon Squeezy connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lemon Squeezy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lemon_squeezy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/lemon_squeezy](https://composio.dev/toolkits/lemon_squeezy) diff --git a/lessonspace-automation/SKILL.md b/lessonspace-automation/SKILL.md new file mode 100644 index 0000000..2c66f3c --- /dev/null +++ b/lessonspace-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lessonspace-automation +description: "Automate Lessonspace tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lessonspace Automation via Rube MCP + +Automate Lessonspace operations through Composio's Lessonspace toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lessonspace](https://composio.dev/toolkits/lessonspace) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lessonspace connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lessonspace` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lessonspace` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lessonspace operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lessonspace task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lessonspace"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lessonspace-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lessonspace` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lever-automation/SKILL.md b/lever-automation/SKILL.md new file mode 100644 index 0000000..377593b --- /dev/null +++ b/lever-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lever-automation +description: "Automate Lever tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lever Automation via Rube MCP + +Automate Lever operations through Composio's Lever toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lever](https://composio.dev/toolkits/lever) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lever connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lever` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lever` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lever operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lever task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lever"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lever-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lever` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lever-sandbox-automation/SKILL.md b/lever-sandbox-automation/SKILL.md new file mode 100644 index 0000000..a0b1619 --- /dev/null +++ b/lever-sandbox-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lever-sandbox-automation +description: "Automate Lever Sandbox tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lever Sandbox Automation via Rube MCP + +Automate Lever Sandbox operations through Composio's Lever Sandbox toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lever_sandbox](https://composio.dev/toolkits/lever_sandbox) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lever Sandbox connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lever_sandbox` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lever_sandbox` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lever Sandbox operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lever Sandbox task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lever_sandbox"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lever Sandbox-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lever_sandbox` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/leverly-automation/SKILL.md b/leverly-automation/SKILL.md new file mode 100644 index 0000000..bf52fe9 --- /dev/null +++ b/leverly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: leverly-automation +description: "Automate Leverly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Leverly Automation via Rube MCP + +Automate Leverly operations through Composio's Leverly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/leverly](https://composio.dev/toolkits/leverly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Leverly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `leverly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `leverly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Leverly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Leverly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["leverly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Leverly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `leverly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lexoffice-automation/SKILL.md b/lexoffice-automation/SKILL.md new file mode 100644 index 0000000..66f7143 --- /dev/null +++ b/lexoffice-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lexoffice-automation +description: "Automate Lexoffice tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lexoffice Automation via Rube MCP + +Automate Lexoffice operations through Composio's Lexoffice toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lexoffice](https://composio.dev/toolkits/lexoffice) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lexoffice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lexoffice` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lexoffice` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lexoffice operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lexoffice task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lexoffice"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lexoffice-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lexoffice` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/linear-automation/SKILL.md b/linear-automation/SKILL.md index b69374f..bd87bd4 100644 --- a/linear-automation/SKILL.md +++ b/linear-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Linear operations through Composio's Linear toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/linear](https://composio.dev/toolkits/linear) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -176,3 +178,6 @@ Automate Linear operations through Composio's Linear toolkit via Rube MCP. | List users | LINEAR_LIST_LINEAR_USERS | (none) | | Current user | LINEAR_GET_CURRENT_USER | (none) | | Run GraphQL | LINEAR_RUN_QUERY_OR_MUTATION | query, variables | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/linguapop-automation/SKILL.md b/linguapop-automation/SKILL.md new file mode 100644 index 0000000..1df1a01 --- /dev/null +++ b/linguapop-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: linguapop-automation +description: "Automate Linguapop tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Linguapop Automation via Rube MCP + +Automate Linguapop operations through Composio's Linguapop toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/linguapop](https://composio.dev/toolkits/linguapop) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Linguapop connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linguapop` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linguapop` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Linguapop operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Linguapop task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["linguapop"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Linguapop-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `linguapop` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/linkedin-automation/SKILL.md b/linkedin-automation/SKILL.md index db24741..df25535 100644 --- a/linkedin-automation/SKILL.md +++ b/linkedin-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate LinkedIn operations through Composio's LinkedIn toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/linkedin](https://composio.dev/toolkits/linkedin) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -173,3 +175,6 @@ Automate LinkedIn operations through Composio's LinkedIn toolkit via Rube MCP. | Get uploaded images | LINKEDIN_GET_IMAGES | image_id | | Delete post | LINKEDIN_DELETE_LINKED_IN_POST | post_id | | Comment on post | LINKEDIN_CREATE_COMMENT_ON_POST | post_id, text, actor | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/linkhut-automation/SKILL.md b/linkhut-automation/SKILL.md new file mode 100644 index 0000000..7402447 --- /dev/null +++ b/linkhut-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: linkhut-automation +description: "Automate Linkhut tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Linkhut Automation via Rube MCP + +Automate Linkhut operations through Composio's Linkhut toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/linkhut](https://composio.dev/toolkits/linkhut) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Linkhut connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linkhut` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linkhut` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Linkhut operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Linkhut task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["linkhut"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Linkhut-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `linkhut` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/linkup-automation/SKILL.md b/linkup-automation/SKILL.md new file mode 100644 index 0000000..16cde6a --- /dev/null +++ b/linkup-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: linkup-automation +description: "Automate Linkup tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Linkup Automation via Rube MCP + +Automate Linkup operations through Composio's Linkup toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/linkup](https://composio.dev/toolkits/linkup) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Linkup connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linkup` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linkup` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Linkup operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Linkup task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["linkup"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Linkup-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `linkup` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/listclean-automation/SKILL.md b/listclean-automation/SKILL.md new file mode 100644 index 0000000..983050e --- /dev/null +++ b/listclean-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: listclean-automation +description: "Automate Listclean tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Listclean Automation via Rube MCP + +Automate Listclean operations through Composio's Listclean toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/listclean](https://composio.dev/toolkits/listclean) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Listclean connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `listclean` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `listclean` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Listclean operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Listclean task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["listclean"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Listclean-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `listclean` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/listennotes-automation/SKILL.md b/listennotes-automation/SKILL.md new file mode 100644 index 0000000..5e1b442 --- /dev/null +++ b/listennotes-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: listennotes-automation +description: "Automate Listennotes tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Listennotes Automation via Rube MCP + +Automate Listennotes operations through Composio's Listennotes toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/listennotes](https://composio.dev/toolkits/listennotes) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Listennotes connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `listennotes` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `listennotes` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Listennotes operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Listennotes task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["listennotes"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Listennotes-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `listennotes` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/livesession-automation/SKILL.md b/livesession-automation/SKILL.md new file mode 100644 index 0000000..0fb6712 --- /dev/null +++ b/livesession-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: livesession-automation +description: "Automate Livesession tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Livesession Automation via Rube MCP + +Automate Livesession operations through Composio's Livesession toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/livesession](https://composio.dev/toolkits/livesession) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Livesession connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `livesession` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `livesession` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Livesession operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Livesession task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["livesession"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Livesession-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `livesession` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lmnt-automation/SKILL.md b/lmnt-automation/SKILL.md new file mode 100644 index 0000000..d8e6faa --- /dev/null +++ b/lmnt-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lmnt-automation +description: "Automate Lmnt tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lmnt Automation via Rube MCP + +Automate Lmnt operations through Composio's Lmnt toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lmnt](https://composio.dev/toolkits/lmnt) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lmnt connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lmnt` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lmnt` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lmnt operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lmnt task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lmnt"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lmnt-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lmnt` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/lodgify-automation/SKILL.md b/lodgify-automation/SKILL.md new file mode 100644 index 0000000..b878146 --- /dev/null +++ b/lodgify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: lodgify-automation +description: "Automate Lodgify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Lodgify Automation via Rube MCP + +Automate Lodgify operations through Composio's Lodgify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/lodgify](https://composio.dev/toolkits/lodgify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Lodgify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `lodgify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `lodgify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Lodgify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Lodgify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["lodgify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Lodgify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `lodgify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/logo-dev-automation/SKILL.md b/logo-dev-automation/SKILL.md new file mode 100644 index 0000000..35283a8 --- /dev/null +++ b/logo-dev-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: logo-dev-automation +description: "Automate Logo Dev tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Logo Dev Automation via Rube MCP + +Automate Logo Dev operations through Composio's Logo Dev toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/logo_dev](https://composio.dev/toolkits/logo_dev) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Logo Dev connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `logo_dev` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `logo_dev` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Logo Dev operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Logo Dev task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["logo_dev"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Logo Dev-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `logo_dev` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/loomio-automation/SKILL.md b/loomio-automation/SKILL.md new file mode 100644 index 0000000..edf0b34 --- /dev/null +++ b/loomio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: loomio-automation +description: "Automate Loomio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Loomio Automation via Rube MCP + +Automate Loomio operations through Composio's Loomio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/loomio](https://composio.dev/toolkits/loomio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Loomio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `loomio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `loomio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Loomio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Loomio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["loomio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Loomio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `loomio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/loyverse-automation/SKILL.md b/loyverse-automation/SKILL.md new file mode 100644 index 0000000..7fad652 --- /dev/null +++ b/loyverse-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: loyverse-automation +description: "Automate Loyverse tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Loyverse Automation via Rube MCP + +Automate Loyverse operations through Composio's Loyverse toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/loyverse](https://composio.dev/toolkits/loyverse) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Loyverse connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `loyverse` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `loyverse` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Loyverse operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Loyverse task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["loyverse"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Loyverse-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `loyverse` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/magnetic-automation/SKILL.md b/magnetic-automation/SKILL.md new file mode 100644 index 0000000..5e4155d --- /dev/null +++ b/magnetic-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: magnetic-automation +description: "Automate Magnetic tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Magnetic Automation via Rube MCP + +Automate Magnetic operations through Composio's Magnetic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/magnetic](https://composio.dev/toolkits/magnetic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Magnetic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `magnetic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `magnetic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Magnetic operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Magnetic task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["magnetic"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Magnetic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `magnetic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailbluster-automation/SKILL.md b/mailbluster-automation/SKILL.md new file mode 100644 index 0000000..c1ddc1d --- /dev/null +++ b/mailbluster-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mailbluster-automation +description: "Automate Mailbluster tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mailbluster Automation via Rube MCP + +Automate Mailbluster operations through Composio's Mailbluster toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mailbluster](https://composio.dev/toolkits/mailbluster) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mailbluster connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailbluster` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailbluster` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mailbluster operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mailbluster task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mailbluster"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mailbluster-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mailbluster` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailboxlayer-automation/SKILL.md b/mailboxlayer-automation/SKILL.md new file mode 100644 index 0000000..c83442e --- /dev/null +++ b/mailboxlayer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mailboxlayer-automation +description: "Automate Mailboxlayer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mailboxlayer Automation via Rube MCP + +Automate Mailboxlayer operations through Composio's Mailboxlayer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mailboxlayer](https://composio.dev/toolkits/mailboxlayer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mailboxlayer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailboxlayer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailboxlayer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mailboxlayer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mailboxlayer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mailboxlayer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mailboxlayer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mailboxlayer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailcheck-automation/SKILL.md b/mailcheck-automation/SKILL.md new file mode 100644 index 0000000..1d07d58 --- /dev/null +++ b/mailcheck-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mailcheck-automation +description: "Automate Mailcheck tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mailcheck Automation via Rube MCP + +Automate Mailcheck operations through Composio's Mailcheck toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mailcheck](https://composio.dev/toolkits/mailcheck) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mailcheck connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailcheck` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailcheck` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mailcheck operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mailcheck task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mailcheck"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mailcheck-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mailcheck` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailchimp-automation/SKILL.md b/mailchimp-automation/SKILL.md index c313766..f7497b7 100644 --- a/mailchimp-automation/SKILL.md +++ b/mailchimp-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Mailchimp email marketing workflows including campaign creation and sending, audience/list management, subscriber operations, segmentation, and performance analytics through Composio's Mailchimp toolkit. +**Toolkit docs**: [composio.dev/toolkits/mailchimp](https://composio.dev/toolkits/mailchimp) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -229,3 +231,6 @@ subscriber_hash = hashlib.md5(email.lower().encode()).hexdigest() | Subscriber activity | `MAILCHIMP_GET_SUBSCRIBER_EMAIL_ACTIVITY` | `campaign_id`, `subscriber_hash` | | Member recent activity | `MAILCHIMP_VIEW_RECENT_ACTIVITY` | `list_id`, `subscriber_hash` | | Campaign content | `MAILCHIMP_GET_CAMPAIGN_CONTENT` | `campaign_id` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailcoach-automation/SKILL.md b/mailcoach-automation/SKILL.md new file mode 100644 index 0000000..cc95b66 --- /dev/null +++ b/mailcoach-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mailcoach-automation +description: "Automate Mailcoach tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mailcoach Automation via Rube MCP + +Automate Mailcoach operations through Composio's Mailcoach toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mailcoach](https://composio.dev/toolkits/mailcoach) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mailcoach connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailcoach` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailcoach` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mailcoach operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mailcoach task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mailcoach"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mailcoach-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mailcoach` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailerlite-automation/SKILL.md b/mailerlite-automation/SKILL.md new file mode 100644 index 0000000..73be9ef --- /dev/null +++ b/mailerlite-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mailerlite-automation +description: "Automate Mailerlite tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mailerlite Automation via Rube MCP + +Automate Mailerlite operations through Composio's Mailerlite toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mailerlite](https://composio.dev/toolkits/mailerlite) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mailerlite connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailerlite` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailerlite` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mailerlite operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mailerlite task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mailerlite"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mailerlite-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mailerlite` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailersend-automation/SKILL.md b/mailersend-automation/SKILL.md new file mode 100644 index 0000000..ba26156 --- /dev/null +++ b/mailersend-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mailersend-automation +description: "Automate Mailersend tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mailersend Automation via Rube MCP + +Automate Mailersend operations through Composio's Mailersend toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mailersend](https://composio.dev/toolkits/mailersend) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mailersend connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailersend` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailersend` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mailersend operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mailersend task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mailersend"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mailersend-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mailersend` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mails-so-automation/SKILL.md b/mails-so-automation/SKILL.md new file mode 100644 index 0000000..dafdbc8 --- /dev/null +++ b/mails-so-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mails-so-automation +description: "Automate Mails So tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mails So Automation via Rube MCP + +Automate Mails So operations through Composio's Mails So toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mails_so](https://composio.dev/toolkits/mails_so) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mails So connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mails_so` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mails_so` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mails So operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mails So task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mails_so"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mails So-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mails_so` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mailsoftly-automation/SKILL.md b/mailsoftly-automation/SKILL.md new file mode 100644 index 0000000..e56c29c --- /dev/null +++ b/mailsoftly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mailsoftly-automation +description: "Automate Mailsoftly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mailsoftly Automation via Rube MCP + +Automate Mailsoftly operations through Composio's Mailsoftly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mailsoftly](https://composio.dev/toolkits/mailsoftly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mailsoftly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailsoftly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailsoftly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mailsoftly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mailsoftly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mailsoftly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mailsoftly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mailsoftly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/maintainx-automation/SKILL.md b/maintainx-automation/SKILL.md new file mode 100644 index 0000000..988be8e --- /dev/null +++ b/maintainx-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: maintainx-automation +description: "Automate Maintainx tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Maintainx Automation via Rube MCP + +Automate Maintainx operations through Composio's Maintainx toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/maintainx](https://composio.dev/toolkits/maintainx) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Maintainx connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `maintainx` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `maintainx` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Maintainx operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Maintainx task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["maintainx"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Maintainx-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `maintainx` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/make-automation/SKILL.md b/make-automation/SKILL.md index 8d40bce..ebcfb02 100644 --- a/make-automation/SKILL.md +++ b/make-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Make (formerly Integromat) operations through Composio's Make toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/make](https://composio.dev/toolkits/make) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -199,3 +201,6 @@ Instead of relying solely on Make's toolkit, build equivalent automation directl 3. Connect all required toolkits 4. Build the workflow step-by-step using individual app tools 5. Save as a recipe via RUBE_CREATE_UPDATE_RECIPE for reuse + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/many-chat-automation/SKILL.md b/many-chat-automation/SKILL.md new file mode 100644 index 0000000..bd6824d --- /dev/null +++ b/many-chat-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: many-chat-automation +description: "Automate ManyChat tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# ManyChat Automation via Rube MCP + +Automate ManyChat operations through Composio's ManyChat toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/many_chat](https://composio.dev/toolkits/many_chat) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active ManyChat connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `many_chat` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `many_chat` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "ManyChat operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific ManyChat task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["many_chat"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with ManyChat-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `many_chat` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/many_chat-automation/SKILL.md b/many_chat-automation/SKILL.md new file mode 100644 index 0000000..a59b7ef --- /dev/null +++ b/many_chat-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: many_chat-automation +description: "Automate ManyChat tasks via Rube MCP (Composio): chatbot flows, subscribers, broadcasts, and messenger automation. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# ManyChat Automation via Rube MCP + +Automate ManyChat operations through Composio's ManyChat toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/many_chat](https://composio.dev/toolkits/many_chat) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active ManyChat connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `many_chat` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `many_chat` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "chatbot flows, subscribers, broadcasts, and messenger automation", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for ManyChat +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available ManyChat Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available ManyChat tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute ManyChat Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple ManyChat operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the ManyChat connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with ManyChat-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `many_chat` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/many_chat](https://composio.dev/toolkits/many_chat) diff --git a/mapbox-automation/SKILL.md b/mapbox-automation/SKILL.md new file mode 100644 index 0000000..ddf1dcf --- /dev/null +++ b/mapbox-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mapbox-automation +description: "Automate Mapbox tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mapbox Automation via Rube MCP + +Automate Mapbox operations through Composio's Mapbox toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mapbox](https://composio.dev/toolkits/mapbox) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mapbox connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mapbox` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mapbox` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mapbox operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mapbox task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mapbox"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mapbox-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mapbox` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mapulus-automation/SKILL.md b/mapulus-automation/SKILL.md new file mode 100644 index 0000000..41661c8 --- /dev/null +++ b/mapulus-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mapulus-automation +description: "Automate Mapulus tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mapulus Automation via Rube MCP + +Automate Mapulus operations through Composio's Mapulus toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mapulus](https://composio.dev/toolkits/mapulus) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mapulus connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mapulus` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mapulus` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mapulus operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mapulus task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mapulus"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mapulus-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mapulus` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mboum-automation/SKILL.md b/mboum-automation/SKILL.md new file mode 100644 index 0000000..1b56133 --- /dev/null +++ b/mboum-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mboum-automation +description: "Automate Mboum tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mboum Automation via Rube MCP + +Automate Mboum operations through Composio's Mboum toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mboum](https://composio.dev/toolkits/mboum) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mboum connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mboum` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mboum` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mboum operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mboum task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mboum"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mboum-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mboum` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/melo-automation/SKILL.md b/melo-automation/SKILL.md new file mode 100644 index 0000000..cecfc50 --- /dev/null +++ b/melo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: melo-automation +description: "Automate Melo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Melo Automation via Rube MCP + +Automate Melo operations through Composio's Melo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/melo](https://composio.dev/toolkits/melo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Melo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `melo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `melo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Melo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Melo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["melo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Melo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `melo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mem-automation/SKILL.md b/mem-automation/SKILL.md new file mode 100644 index 0000000..bceac58 --- /dev/null +++ b/mem-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mem-automation +description: "Automate Mem tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mem Automation via Rube MCP + +Automate Mem operations through Composio's Mem toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mem](https://composio.dev/toolkits/mem) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mem connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mem` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mem` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mem operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mem task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mem"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mem-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mem` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mem0-automation/SKILL.md b/mem0-automation/SKILL.md new file mode 100644 index 0000000..af24b4d --- /dev/null +++ b/mem0-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mem0-automation +description: "Automate Mem0 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mem0 Automation via Rube MCP + +Automate Mem0 operations through Composio's Mem0 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mem0](https://composio.dev/toolkits/mem0) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mem0 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mem0` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mem0` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mem0 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mem0 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mem0"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mem0-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mem0` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/memberspot-automation/SKILL.md b/memberspot-automation/SKILL.md new file mode 100644 index 0000000..756e68a --- /dev/null +++ b/memberspot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: memberspot-automation +description: "Automate Memberspot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Memberspot Automation via Rube MCP + +Automate Memberspot operations through Composio's Memberspot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/memberspot](https://composio.dev/toolkits/memberspot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Memberspot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `memberspot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `memberspot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Memberspot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Memberspot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["memberspot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Memberspot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `memberspot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/memberstack-automation/SKILL.md b/memberstack-automation/SKILL.md new file mode 100644 index 0000000..37ff909 --- /dev/null +++ b/memberstack-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: memberstack-automation +description: "Automate Memberstack tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Memberstack Automation via Rube MCP + +Automate Memberstack operations through Composio's Memberstack toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/memberstack](https://composio.dev/toolkits/memberstack) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Memberstack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `memberstack` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `memberstack` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Memberstack operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Memberstack task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["memberstack"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Memberstack-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `memberstack` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/membervault-automation/SKILL.md b/membervault-automation/SKILL.md new file mode 100644 index 0000000..661cd3c --- /dev/null +++ b/membervault-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: membervault-automation +description: "Automate Membervault tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Membervault Automation via Rube MCP + +Automate Membervault operations through Composio's Membervault toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/membervault](https://composio.dev/toolkits/membervault) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Membervault connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `membervault` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `membervault` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Membervault operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Membervault task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["membervault"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Membervault-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `membervault` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/metaads-automation/SKILL.md b/metaads-automation/SKILL.md new file mode 100644 index 0000000..463ea3a --- /dev/null +++ b/metaads-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: metaads-automation +description: "Automate Metaads tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Metaads Automation via Rube MCP + +Automate Metaads operations through Composio's Metaads toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/metaads](https://composio.dev/toolkits/metaads) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Metaads connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `metaads` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `metaads` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Metaads operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Metaads task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["metaads"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Metaads-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `metaads` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/metaphor-automation/SKILL.md b/metaphor-automation/SKILL.md new file mode 100644 index 0000000..89c78e6 --- /dev/null +++ b/metaphor-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: metaphor-automation +description: "Automate Metaphor tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Metaphor Automation via Rube MCP + +Automate Metaphor operations through Composio's Metaphor toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/metaphor](https://composio.dev/toolkits/metaphor) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Metaphor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `metaphor` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `metaphor` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Metaphor operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Metaphor task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["metaphor"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Metaphor-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `metaphor` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mezmo-automation/SKILL.md b/mezmo-automation/SKILL.md new file mode 100644 index 0000000..011eb72 --- /dev/null +++ b/mezmo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mezmo-automation +description: "Automate Mezmo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mezmo Automation via Rube MCP + +Automate Mezmo operations through Composio's Mezmo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mezmo](https://composio.dev/toolkits/mezmo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mezmo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mezmo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mezmo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mezmo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mezmo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mezmo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mezmo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mezmo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/microsoft-clarity-automation/SKILL.md b/microsoft-clarity-automation/SKILL.md new file mode 100644 index 0000000..91febb4 --- /dev/null +++ b/microsoft-clarity-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: microsoft-clarity-automation +description: "Automate Microsoft Clarity tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Microsoft Clarity Automation via Rube MCP + +Automate Microsoft Clarity operations through Composio's Microsoft Clarity toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/microsoft_clarity](https://composio.dev/toolkits/microsoft_clarity) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Microsoft Clarity connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_clarity` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_clarity` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Microsoft Clarity operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Microsoft Clarity task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["microsoft_clarity"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Microsoft Clarity-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_clarity` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/microsoft-teams-automation/SKILL.md b/microsoft-teams-automation/SKILL.md index 33d4149..91cac3c 100644 --- a/microsoft-teams-automation/SKILL.md +++ b/microsoft-teams-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Microsoft Teams operations through Composio's Microsoft Teams toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/microsoft_teams](https://composio.dev/toolkits/microsoft_teams) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -209,3 +211,6 @@ Automate Microsoft Teams operations through Composio's Microsoft Teams toolkit v | Search messages | MICROSOFT_TEAMS_SEARCH_MESSAGES | query | | Get chat message | MICROSOFT_TEAMS_GET_CHAT_MESSAGE | chat_id, message_id | | List joined teams | MICROSOFT_TEAMS_LIST_USER_JOINED_TEAMS | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/microsoft-tenant-automation/SKILL.md b/microsoft-tenant-automation/SKILL.md new file mode 100644 index 0000000..5f412d6 --- /dev/null +++ b/microsoft-tenant-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: microsoft-tenant-automation +description: "Automate Microsoft Tenant tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Microsoft Tenant Automation via Rube MCP + +Automate Microsoft Tenant operations through Composio's Microsoft Tenant toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/microsoft_tenant](https://composio.dev/toolkits/microsoft_tenant) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Microsoft Tenant connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_tenant` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_tenant` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Microsoft Tenant operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Microsoft Tenant task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["microsoft_tenant"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Microsoft Tenant-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_tenant` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/microsoft_clarity-automation/SKILL.md b/microsoft_clarity-automation/SKILL.md new file mode 100644 index 0000000..d180520 --- /dev/null +++ b/microsoft_clarity-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: microsoft_clarity-automation +description: "Automate Microsoft Clarity tasks via Rube MCP (Composio): session recordings, heatmaps, and user behavior analytics. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Microsoft Clarity Automation via Rube MCP + +Automate Microsoft Clarity operations through Composio's Microsoft Clarity toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/microsoft_clarity](https://composio.dev/toolkits/microsoft_clarity) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Microsoft Clarity connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_clarity` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_clarity` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "session recordings, heatmaps, and user behavior analytics", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Microsoft Clarity +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Microsoft Clarity Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Microsoft Clarity tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Microsoft Clarity Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Microsoft Clarity operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Microsoft Clarity connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Microsoft Clarity-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_clarity` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/microsoft_clarity](https://composio.dev/toolkits/microsoft_clarity) diff --git a/minerstat-automation/SKILL.md b/minerstat-automation/SKILL.md new file mode 100644 index 0000000..83f9c27 --- /dev/null +++ b/minerstat-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: minerstat-automation +description: "Automate Minerstat tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Minerstat Automation via Rube MCP + +Automate Minerstat operations through Composio's Minerstat toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/minerstat](https://composio.dev/toolkits/minerstat) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Minerstat connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `minerstat` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `minerstat` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Minerstat operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Minerstat task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["minerstat"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Minerstat-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `minerstat` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/miro-automation/SKILL.md b/miro-automation/SKILL.md index 4bc14f2..77cf784 100644 --- a/miro-automation/SKILL.md +++ b/miro-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Miro whiteboard operations through Composio's Miro toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/miro](https://composio.dev/toolkits/miro) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -203,3 +205,6 @@ Automate Miro whiteboard operations through Composio's Miro toolkit via Rube MCP | Share board | MIRO_SHARE_BOARD | board_id, emails, role | | Get members | MIRO_GET_BOARD_MEMBERS | board_id | | Get connectors | MIRO_GET_CONNECTORS2 | board_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/missive-automation/SKILL.md b/missive-automation/SKILL.md new file mode 100644 index 0000000..50c19ac --- /dev/null +++ b/missive-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: missive-automation +description: "Automate Missive tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Missive Automation via Rube MCP + +Automate Missive operations through Composio's Missive toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/missive](https://composio.dev/toolkits/missive) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Missive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `missive` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `missive` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Missive operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Missive task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["missive"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Missive-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `missive` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mistral-ai-automation/SKILL.md b/mistral-ai-automation/SKILL.md new file mode 100644 index 0000000..9a2121c --- /dev/null +++ b/mistral-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mistral-ai-automation +description: "Automate Mistral AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mistral AI Automation via Rube MCP + +Automate Mistral AI operations through Composio's Mistral AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mistral_ai](https://composio.dev/toolkits/mistral_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mistral AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mistral_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mistral_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mistral AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mistral AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mistral_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mistral AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mistral_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mistral_ai-automation/SKILL.md b/mistral_ai-automation/SKILL.md new file mode 100644 index 0000000..446c72e --- /dev/null +++ b/mistral_ai-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: mistral_ai-automation +description: "Automate Mistral AI tasks via Rube MCP (Composio): completions, embeddings, fine-tuning, and model management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mistral AI Automation via Rube MCP + +Automate Mistral AI operations through Composio's Mistral AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mistral_ai](https://composio.dev/toolkits/mistral_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mistral AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mistral_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mistral_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "completions, embeddings, fine-tuning, and model management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Mistral AI +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Mistral AI Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Mistral AI tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Mistral AI Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Mistral AI operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Mistral AI connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mistral AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mistral_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/mistral_ai](https://composio.dev/toolkits/mistral_ai) diff --git a/mixpanel-automation/SKILL.md b/mixpanel-automation/SKILL.md index 4cdc586..edf3b3c 100644 --- a/mixpanel-automation/SKILL.md +++ b/mixpanel-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/mixpanel](https://composio.dev/toolkits/mixpanel) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -222,3 +224,6 @@ Used in `where` and `on` parameters: | List cohorts | MIXPANEL_COHORTS_LIST | (none) | | JQL query | MIXPANEL_JQL_QUERY | script | | Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mocean-automation/SKILL.md b/mocean-automation/SKILL.md new file mode 100644 index 0000000..998659f --- /dev/null +++ b/mocean-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mocean-automation +description: "Automate Mocean tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mocean Automation via Rube MCP + +Automate Mocean operations through Composio's Mocean toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mocean](https://composio.dev/toolkits/mocean) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mocean connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mocean` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mocean` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mocean operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mocean task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mocean"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mocean-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mocean` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/moco-automation/SKILL.md b/moco-automation/SKILL.md new file mode 100644 index 0000000..055f373 --- /dev/null +++ b/moco-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: moco-automation +description: "Automate Moco tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Moco Automation via Rube MCP + +Automate Moco operations through Composio's Moco toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/moco](https://composio.dev/toolkits/moco) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Moco connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `moco` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `moco` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Moco operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Moco task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["moco"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Moco-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `moco` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/modelry-automation/SKILL.md b/modelry-automation/SKILL.md new file mode 100644 index 0000000..cb8ec6d --- /dev/null +++ b/modelry-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: modelry-automation +description: "Automate Modelry tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Modelry Automation via Rube MCP + +Automate Modelry operations through Composio's Modelry toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/modelry](https://composio.dev/toolkits/modelry) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Modelry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `modelry` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `modelry` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Modelry operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Modelry task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["modelry"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Modelry-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `modelry` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/monday-automation/SKILL.md b/monday-automation/SKILL.md index 67d7ff9..ca3ca4a 100644 --- a/monday-automation/SKILL.md +++ b/monday-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Monday.com work management workflows including board creation, item management, column value updates, group organization, subitems, and update/comment threads through Composio's Monday toolkit. +**Toolkit docs**: [composio.dev/toolkits/monday](https://composio.dev/toolkits/monday) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -231,3 +233,6 @@ Different column types require different value formats: | List subitems | `MONDAY_LIST_SUBITEMS_BY_PARENT` | `parent_item_ids` | | Add comment/update | `MONDAY_CREATE_UPDATE` | `item_id`, `body` | | Raw GraphQL mutation | `MONDAY_CREATE_OBJECT` | `query`, `variables` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/moneybird-automation/SKILL.md b/moneybird-automation/SKILL.md new file mode 100644 index 0000000..0ef7dee --- /dev/null +++ b/moneybird-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: moneybird-automation +description: "Automate Moneybird tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Moneybird Automation via Rube MCP + +Automate Moneybird operations through Composio's Moneybird toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/moneybird](https://composio.dev/toolkits/moneybird) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Moneybird connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `moneybird` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `moneybird` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Moneybird operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Moneybird task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["moneybird"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Moneybird-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `moneybird` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/moonclerk-automation/SKILL.md b/moonclerk-automation/SKILL.md new file mode 100644 index 0000000..5599530 --- /dev/null +++ b/moonclerk-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: moonclerk-automation +description: "Automate Moonclerk tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Moonclerk Automation via Rube MCP + +Automate Moonclerk operations through Composio's Moonclerk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/moonclerk](https://composio.dev/toolkits/moonclerk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Moonclerk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `moonclerk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `moonclerk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Moonclerk operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Moonclerk task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["moonclerk"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Moonclerk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `moonclerk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/moosend-automation/SKILL.md b/moosend-automation/SKILL.md new file mode 100644 index 0000000..4bb09e2 --- /dev/null +++ b/moosend-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: moosend-automation +description: "Automate Moosend tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Moosend Automation via Rube MCP + +Automate Moosend operations through Composio's Moosend toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/moosend](https://composio.dev/toolkits/moosend) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Moosend connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `moosend` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `moosend` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Moosend operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Moosend task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["moosend"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Moosend-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `moosend` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mopinion-automation/SKILL.md b/mopinion-automation/SKILL.md new file mode 100644 index 0000000..e7a2a3d --- /dev/null +++ b/mopinion-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mopinion-automation +description: "Automate Mopinion tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mopinion Automation via Rube MCP + +Automate Mopinion operations through Composio's Mopinion toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mopinion](https://composio.dev/toolkits/mopinion) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mopinion connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mopinion` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mopinion` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mopinion operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mopinion task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mopinion"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mopinion-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mopinion` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/more-trees-automation/SKILL.md b/more-trees-automation/SKILL.md new file mode 100644 index 0000000..ca7ead0 --- /dev/null +++ b/more-trees-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: more-trees-automation +description: "Automate More Trees tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# More Trees Automation via Rube MCP + +Automate More Trees operations through Composio's More Trees toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/more_trees](https://composio.dev/toolkits/more_trees) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active More Trees connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `more_trees` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `more_trees` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "More Trees operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific More Trees task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["more_trees"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with More Trees-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `more_trees` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/moxie-automation/SKILL.md b/moxie-automation/SKILL.md new file mode 100644 index 0000000..7db2e65 --- /dev/null +++ b/moxie-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: moxie-automation +description: "Automate Moxie tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Moxie Automation via Rube MCP + +Automate Moxie operations through Composio's Moxie toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/moxie](https://composio.dev/toolkits/moxie) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Moxie connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `moxie` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `moxie` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Moxie operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Moxie task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["moxie"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Moxie-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `moxie` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/moz-automation/SKILL.md b/moz-automation/SKILL.md new file mode 100644 index 0000000..5133ac1 --- /dev/null +++ b/moz-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: moz-automation +description: "Automate Moz tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Moz Automation via Rube MCP + +Automate Moz operations through Composio's Moz toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/moz](https://composio.dev/toolkits/moz) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Moz connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `moz` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `moz` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Moz operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Moz task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["moz"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Moz-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `moz` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/msg91-automation/SKILL.md b/msg91-automation/SKILL.md new file mode 100644 index 0000000..b060a1d --- /dev/null +++ b/msg91-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: msg91-automation +description: "Automate Msg91 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Msg91 Automation via Rube MCP + +Automate Msg91 operations through Composio's Msg91 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/msg91](https://composio.dev/toolkits/msg91) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Msg91 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `msg91` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `msg91` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Msg91 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Msg91 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["msg91"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Msg91-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `msg91` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mural-automation/SKILL.md b/mural-automation/SKILL.md new file mode 100644 index 0000000..b33170f --- /dev/null +++ b/mural-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mural-automation +description: "Automate Mural tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mural Automation via Rube MCP + +Automate Mural operations through Composio's Mural toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mural](https://composio.dev/toolkits/mural) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mural connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mural` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mural` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mural operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mural task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mural"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mural-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mural` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mx-technologies-automation/SKILL.md b/mx-technologies-automation/SKILL.md new file mode 100644 index 0000000..bc0bf07 --- /dev/null +++ b/mx-technologies-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mx-technologies-automation +description: "Automate MX Technologies tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# MX Technologies Automation via Rube MCP + +Automate MX Technologies operations through Composio's MX Technologies toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mx_technologies](https://composio.dev/toolkits/mx_technologies) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active MX Technologies connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mx_technologies` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mx_technologies` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "MX Technologies operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific MX Technologies task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mx_technologies"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with MX Technologies-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mx_technologies` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/mx-toolbox-automation/SKILL.md b/mx-toolbox-automation/SKILL.md new file mode 100644 index 0000000..d1db90b --- /dev/null +++ b/mx-toolbox-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: mx-toolbox-automation +description: "Automate Mx Toolbox tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Mx Toolbox Automation via Rube MCP + +Automate Mx Toolbox operations through Composio's Mx Toolbox toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/mx_toolbox](https://composio.dev/toolkits/mx_toolbox) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Mx Toolbox connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mx_toolbox` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mx_toolbox` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Mx Toolbox operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Mx Toolbox task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["mx_toolbox"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Mx Toolbox-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mx_toolbox` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/nango-automation/SKILL.md b/nango-automation/SKILL.md new file mode 100644 index 0000000..ac7e4b7 --- /dev/null +++ b/nango-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: nango-automation +description: "Automate Nango tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Nango Automation via Rube MCP + +Automate Nango operations through Composio's Nango toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/nango](https://composio.dev/toolkits/nango) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Nango connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `nango` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `nango` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Nango operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Nango task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["nango"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Nango-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `nango` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/nano-nets-automation/SKILL.md b/nano-nets-automation/SKILL.md new file mode 100644 index 0000000..8d73abf --- /dev/null +++ b/nano-nets-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: nano-nets-automation +description: "Automate Nano Nets tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Nano Nets Automation via Rube MCP + +Automate Nano Nets operations through Composio's Nano Nets toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/nano_nets](https://composio.dev/toolkits/nano_nets) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Nano Nets connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `nano_nets` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `nano_nets` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Nano Nets operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Nano Nets task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["nano_nets"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Nano Nets-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `nano_nets` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/nasa-automation/SKILL.md b/nasa-automation/SKILL.md new file mode 100644 index 0000000..7f8826b --- /dev/null +++ b/nasa-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: nasa-automation +description: "Automate Nasa tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Nasa Automation via Rube MCP + +Automate Nasa operations through Composio's Nasa toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/nasa](https://composio.dev/toolkits/nasa) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Nasa connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `nasa` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `nasa` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Nasa operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Nasa task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["nasa"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Nasa-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `nasa` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/nasdaq-automation/SKILL.md b/nasdaq-automation/SKILL.md new file mode 100644 index 0000000..38f147b --- /dev/null +++ b/nasdaq-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: nasdaq-automation +description: "Automate Nasdaq tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Nasdaq Automation via Rube MCP + +Automate Nasdaq operations through Composio's Nasdaq toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/nasdaq](https://composio.dev/toolkits/nasdaq) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Nasdaq connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `nasdaq` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `nasdaq` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Nasdaq operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Nasdaq task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["nasdaq"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Nasdaq-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `nasdaq` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ncscale-automation/SKILL.md b/ncscale-automation/SKILL.md new file mode 100644 index 0000000..587ac5f --- /dev/null +++ b/ncscale-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ncscale-automation +description: "Automate Ncscale tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ncscale Automation via Rube MCP + +Automate Ncscale operations through Composio's Ncscale toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ncscale](https://composio.dev/toolkits/ncscale) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ncscale connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ncscale` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ncscale` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ncscale operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ncscale task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ncscale"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ncscale-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ncscale` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/needle-automation/SKILL.md b/needle-automation/SKILL.md new file mode 100644 index 0000000..c9b55ef --- /dev/null +++ b/needle-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: needle-automation +description: "Automate Needle tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Needle Automation via Rube MCP + +Automate Needle operations through Composio's Needle toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/needle](https://composio.dev/toolkits/needle) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Needle connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `needle` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `needle` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Needle operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Needle task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["needle"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Needle-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `needle` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/neon-automation/SKILL.md b/neon-automation/SKILL.md new file mode 100644 index 0000000..9262f14 --- /dev/null +++ b/neon-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: neon-automation +description: "Automate Neon tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Neon Automation via Rube MCP + +Automate Neon operations through Composio's Neon toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/neon](https://composio.dev/toolkits/neon) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Neon connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `neon` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `neon` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Neon operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Neon task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["neon"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Neon-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `neon` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/netsuite-automation/SKILL.md b/netsuite-automation/SKILL.md new file mode 100644 index 0000000..2dbd2c6 --- /dev/null +++ b/netsuite-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: netsuite-automation +description: "Automate Netsuite tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Netsuite Automation via Rube MCP + +Automate Netsuite operations through Composio's Netsuite toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/netsuite](https://composio.dev/toolkits/netsuite) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Netsuite connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `netsuite` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `netsuite` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Netsuite operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Netsuite task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["netsuite"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Netsuite-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `netsuite` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/neuronwriter-automation/SKILL.md b/neuronwriter-automation/SKILL.md new file mode 100644 index 0000000..fb9dfa6 --- /dev/null +++ b/neuronwriter-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: neuronwriter-automation +description: "Automate Neuronwriter tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Neuronwriter Automation via Rube MCP + +Automate Neuronwriter operations through Composio's Neuronwriter toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/neuronwriter](https://composio.dev/toolkits/neuronwriter) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Neuronwriter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `neuronwriter` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `neuronwriter` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Neuronwriter operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Neuronwriter task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["neuronwriter"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Neuronwriter-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `neuronwriter` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/neutrino-automation/SKILL.md b/neutrino-automation/SKILL.md new file mode 100644 index 0000000..ec1d596 --- /dev/null +++ b/neutrino-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: neutrino-automation +description: "Automate Neutrino tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Neutrino Automation via Rube MCP + +Automate Neutrino operations through Composio's Neutrino toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/neutrino](https://composio.dev/toolkits/neutrino) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Neutrino connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `neutrino` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `neutrino` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Neutrino operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Neutrino task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["neutrino"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Neutrino-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `neutrino` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/neverbounce-automation/SKILL.md b/neverbounce-automation/SKILL.md new file mode 100644 index 0000000..653ae38 --- /dev/null +++ b/neverbounce-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: neverbounce-automation +description: "Automate Neverbounce tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Neverbounce Automation via Rube MCP + +Automate Neverbounce operations through Composio's Neverbounce toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/neverbounce](https://composio.dev/toolkits/neverbounce) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Neverbounce connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `neverbounce` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `neverbounce` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Neverbounce operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Neverbounce task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["neverbounce"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Neverbounce-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `neverbounce` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/new-relic-automation/SKILL.md b/new-relic-automation/SKILL.md new file mode 100644 index 0000000..a1309b2 --- /dev/null +++ b/new-relic-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: new-relic-automation +description: "Automate New Relic tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# New Relic Automation via Rube MCP + +Automate New Relic operations through Composio's New Relic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/new_relic](https://composio.dev/toolkits/new_relic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active New Relic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `new_relic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `new_relic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "New Relic operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific New Relic task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["new_relic"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with New Relic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `new_relic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/new_relic-automation/SKILL.md b/new_relic-automation/SKILL.md new file mode 100644 index 0000000..3c2ac3d --- /dev/null +++ b/new_relic-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: new_relic-automation +description: "Automate New Relic tasks via Rube MCP (Composio): APM, alerts, dashboards, NRQL queries, and infrastructure monitoring. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# New Relic Automation via Rube MCP + +Automate New Relic operations through Composio's New Relic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/new_relic](https://composio.dev/toolkits/new_relic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active New Relic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `new_relic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `new_relic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "APM, alerts, dashboards, NRQL queries, and infrastructure monitoring", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for New Relic +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available New Relic Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available New Relic tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute New Relic Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple New Relic operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the New Relic connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with New Relic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `new_relic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/new_relic](https://composio.dev/toolkits/new_relic) diff --git a/news-api-automation/SKILL.md b/news-api-automation/SKILL.md new file mode 100644 index 0000000..b5ea0d8 --- /dev/null +++ b/news-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: news-api-automation +description: "Automate News API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# News API Automation via Rube MCP + +Automate News API operations through Composio's News API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/news_api](https://composio.dev/toolkits/news_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active News API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `news_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `news_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "News API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific News API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["news_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with News API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `news_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/nextdns-automation/SKILL.md b/nextdns-automation/SKILL.md new file mode 100644 index 0000000..f6e87cd --- /dev/null +++ b/nextdns-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: nextdns-automation +description: "Automate Nextdns tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Nextdns Automation via Rube MCP + +Automate Nextdns operations through Composio's Nextdns toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/nextdns](https://composio.dev/toolkits/nextdns) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Nextdns connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `nextdns` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `nextdns` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Nextdns operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Nextdns task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["nextdns"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Nextdns-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `nextdns` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ngrok-automation/SKILL.md b/ngrok-automation/SKILL.md new file mode 100644 index 0000000..8065109 --- /dev/null +++ b/ngrok-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ngrok-automation +description: "Automate Ngrok tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ngrok Automation via Rube MCP + +Automate Ngrok operations through Composio's Ngrok toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ngrok](https://composio.dev/toolkits/ngrok) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ngrok connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ngrok` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ngrok` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ngrok operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ngrok task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ngrok"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ngrok-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ngrok` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ninox-automation/SKILL.md b/ninox-automation/SKILL.md new file mode 100644 index 0000000..402b762 --- /dev/null +++ b/ninox-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ninox-automation +description: "Automate Ninox tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ninox Automation via Rube MCP + +Automate Ninox operations through Composio's Ninox toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ninox](https://composio.dev/toolkits/ninox) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ninox connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ninox` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ninox` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ninox operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ninox task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ninox"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ninox-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ninox` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/nocrm-io-automation/SKILL.md b/nocrm-io-automation/SKILL.md new file mode 100644 index 0000000..0e9f41d --- /dev/null +++ b/nocrm-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: nocrm-io-automation +description: "Automate Nocrm IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Nocrm IO Automation via Rube MCP + +Automate Nocrm IO operations through Composio's Nocrm IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/nocrm_io](https://composio.dev/toolkits/nocrm_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Nocrm IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `nocrm_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `nocrm_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Nocrm IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Nocrm IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["nocrm_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Nocrm IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `nocrm_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/notion-automation/SKILL.md b/notion-automation/SKILL.md index b5236cc..dc37411 100644 --- a/notion-automation/SKILL.md +++ b/notion-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Notion operations through Composio's Notion toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/notion](https://composio.dev/toolkits/notion) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -213,3 +215,6 @@ Automate Notion operations through Composio's Notion toolkit via Rube MCP. | List users | NOTION_LIST_USERS | (none) | | Create comment | NOTION_CREATE_COMMENT | page_id, rich_text | | List comments | NOTION_FETCH_COMMENTS | page_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/npm-automation/SKILL.md b/npm-automation/SKILL.md new file mode 100644 index 0000000..fbbcbf5 --- /dev/null +++ b/npm-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: npm-automation +description: "Automate NPM tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# NPM Automation via Rube MCP + +Automate NPM operations through Composio's NPM toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/npm](https://composio.dev/toolkits/npm) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active NPM connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `npm` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `npm` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "NPM operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific NPM task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["npm"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with NPM-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `npm` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ocr-web-service-automation/SKILL.md b/ocr-web-service-automation/SKILL.md new file mode 100644 index 0000000..6892da7 --- /dev/null +++ b/ocr-web-service-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ocr-web-service-automation +description: "Automate OCR Web Service tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# OCR Web Service Automation via Rube MCP + +Automate OCR Web Service operations through Composio's OCR Web Service toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ocr_web_service](https://composio.dev/toolkits/ocr_web_service) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active OCR Web Service connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ocr_web_service` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ocr_web_service` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "OCR Web Service operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific OCR Web Service task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ocr_web_service"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with OCR Web Service-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ocr_web_service` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ocrspace-automation/SKILL.md b/ocrspace-automation/SKILL.md new file mode 100644 index 0000000..5f82166 --- /dev/null +++ b/ocrspace-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ocrspace-automation +description: "Automate Ocrspace tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ocrspace Automation via Rube MCP + +Automate Ocrspace operations through Composio's Ocrspace toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ocrspace](https://composio.dev/toolkits/ocrspace) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ocrspace connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ocrspace` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ocrspace` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ocrspace operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ocrspace task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ocrspace"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ocrspace-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ocrspace` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/omnisend-automation/SKILL.md b/omnisend-automation/SKILL.md new file mode 100644 index 0000000..4ab5038 --- /dev/null +++ b/omnisend-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: omnisend-automation +description: "Automate Omnisend tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Omnisend Automation via Rube MCP + +Automate Omnisend operations through Composio's Omnisend toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/omnisend](https://composio.dev/toolkits/omnisend) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Omnisend connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `omnisend` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `omnisend` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Omnisend operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Omnisend task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["omnisend"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Omnisend-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `omnisend` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/oncehub-automation/SKILL.md b/oncehub-automation/SKILL.md new file mode 100644 index 0000000..45db549 --- /dev/null +++ b/oncehub-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: oncehub-automation +description: "Automate Oncehub tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Oncehub Automation via Rube MCP + +Automate Oncehub operations through Composio's Oncehub toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/oncehub](https://composio.dev/toolkits/oncehub) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Oncehub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `oncehub` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `oncehub` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Oncehub operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Oncehub task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["oncehub"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Oncehub-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `oncehub` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/one-drive-automation/SKILL.md b/one-drive-automation/SKILL.md index 3fcdd64..4f220cc 100644 --- a/one-drive-automation/SKILL.md +++ b/one-drive-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate OneDrive operations including file upload/download, search, folder management, sharing links, permissions management, and drive browsing through Composio's OneDrive toolkit. +**Toolkit docs**: [composio.dev/toolkits/one_drive](https://composio.dev/toolkits/one_drive) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -236,3 +238,6 @@ Most OneDrive tools accept either paths or IDs: | Get quota | `ONE_DRIVE_GET_QUOTA` | (none) | | Track changes | `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` | `site_id`, `token` | | Version history | `ONE_DRIVE_GET_ITEM_VERSIONS` | `item_id` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/onedesk-automation/SKILL.md b/onedesk-automation/SKILL.md new file mode 100644 index 0000000..9f0ccbe --- /dev/null +++ b/onedesk-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: onedesk-automation +description: "Automate Onedesk tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Onedesk Automation via Rube MCP + +Automate Onedesk operations through Composio's Onedesk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/onedesk](https://composio.dev/toolkits/onedesk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Onedesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `onedesk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `onedesk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Onedesk operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Onedesk task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["onedesk"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Onedesk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `onedesk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/onepage-automation/SKILL.md b/onepage-automation/SKILL.md new file mode 100644 index 0000000..3695e0e --- /dev/null +++ b/onepage-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: onepage-automation +description: "Automate Onepage tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Onepage Automation via Rube MCP + +Automate Onepage operations through Composio's Onepage toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/onepage](https://composio.dev/toolkits/onepage) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Onepage connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `onepage` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `onepage` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Onepage operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Onepage task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["onepage"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Onepage-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `onepage` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/onesignal-rest-api-automation/SKILL.md b/onesignal-rest-api-automation/SKILL.md new file mode 100644 index 0000000..807ab8b --- /dev/null +++ b/onesignal-rest-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: onesignal-rest-api-automation +description: "Automate OneSignal tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# OneSignal Automation via Rube MCP + +Automate OneSignal operations through Composio's OneSignal toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/onesignal_rest_api](https://composio.dev/toolkits/onesignal_rest_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active OneSignal connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_rest_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_rest_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "OneSignal operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific OneSignal task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["onesignal_rest_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with OneSignal-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_rest_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/onesignal-user-auth-automation/SKILL.md b/onesignal-user-auth-automation/SKILL.md new file mode 100644 index 0000000..adb1d07 --- /dev/null +++ b/onesignal-user-auth-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: onesignal-user-auth-automation +description: "Automate Onesignal User Auth tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Onesignal User Auth Automation via Rube MCP + +Automate Onesignal User Auth operations through Composio's Onesignal User Auth toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/onesignal_user_auth](https://composio.dev/toolkits/onesignal_user_auth) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Onesignal User Auth connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_user_auth` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_user_auth` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Onesignal User Auth operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Onesignal User Auth task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["onesignal_user_auth"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Onesignal User Auth-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_user_auth` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/onesignal_rest_api-automation/SKILL.md b/onesignal_rest_api-automation/SKILL.md new file mode 100644 index 0000000..82bc226 --- /dev/null +++ b/onesignal_rest_api-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: onesignal_rest_api-automation +description: "Automate OneSignal tasks via Rube MCP (Composio): push notifications, segments, templates, and messaging. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# OneSignal Automation via Rube MCP + +Automate OneSignal operations through Composio's OneSignal toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/onesignal_rest_api](https://composio.dev/toolkits/onesignal_rest_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active OneSignal connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_rest_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_rest_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "push notifications, segments, templates, and messaging", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for OneSignal +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available OneSignal Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available OneSignal tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute OneSignal Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple OneSignal operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the OneSignal connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with OneSignal-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_rest_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/onesignal_rest_api](https://composio.dev/toolkits/onesignal_rest_api) diff --git a/open-sea-automation/SKILL.md b/open-sea-automation/SKILL.md new file mode 100644 index 0000000..8a1e419 --- /dev/null +++ b/open-sea-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: open-sea-automation +description: "Automate Open Sea tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Open Sea Automation via Rube MCP + +Automate Open Sea operations through Composio's Open Sea toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/open_sea](https://composio.dev/toolkits/open_sea) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Open Sea connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `open_sea` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `open_sea` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Open Sea operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Open Sea task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["open_sea"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Open Sea-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `open_sea` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/openai-automation/SKILL.md b/openai-automation/SKILL.md new file mode 100644 index 0000000..37f50d8 --- /dev/null +++ b/openai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: openai-automation +description: "Automate OpenAI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# OpenAI Automation via Rube MCP + +Automate OpenAI operations through Composio's OpenAI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/openai](https://composio.dev/toolkits/openai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active OpenAI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `openai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `openai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "OpenAI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific OpenAI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["openai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with OpenAI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `openai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/opencage-automation/SKILL.md b/opencage-automation/SKILL.md new file mode 100644 index 0000000..d1e07dc --- /dev/null +++ b/opencage-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: opencage-automation +description: "Automate Opencage tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Opencage Automation via Rube MCP + +Automate Opencage operations through Composio's Opencage toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/opencage](https://composio.dev/toolkits/opencage) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Opencage connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `opencage` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `opencage` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Opencage operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Opencage task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["opencage"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Opencage-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `opencage` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/opengraph-io-automation/SKILL.md b/opengraph-io-automation/SKILL.md new file mode 100644 index 0000000..d1104ee --- /dev/null +++ b/opengraph-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: opengraph-io-automation +description: "Automate Opengraph IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Opengraph IO Automation via Rube MCP + +Automate Opengraph IO operations through Composio's Opengraph IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/opengraph_io](https://composio.dev/toolkits/opengraph_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Opengraph IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `opengraph_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `opengraph_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Opengraph IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Opengraph IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["opengraph_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Opengraph IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `opengraph_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/openperplex-automation/SKILL.md b/openperplex-automation/SKILL.md new file mode 100644 index 0000000..0c1fede --- /dev/null +++ b/openperplex-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: openperplex-automation +description: "Automate Openperplex tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Openperplex Automation via Rube MCP + +Automate Openperplex operations through Composio's Openperplex toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/openperplex](https://composio.dev/toolkits/openperplex) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Openperplex connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `openperplex` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `openperplex` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Openperplex operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Openperplex task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["openperplex"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Openperplex-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `openperplex` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/openrouter-automation/SKILL.md b/openrouter-automation/SKILL.md new file mode 100644 index 0000000..ff705ce --- /dev/null +++ b/openrouter-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: openrouter-automation +description: "Automate Openrouter tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Openrouter Automation via Rube MCP + +Automate Openrouter operations through Composio's Openrouter toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/openrouter](https://composio.dev/toolkits/openrouter) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Openrouter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `openrouter` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `openrouter` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Openrouter operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Openrouter task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["openrouter"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Openrouter-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `openrouter` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/openweather-api-automation/SKILL.md b/openweather-api-automation/SKILL.md new file mode 100644 index 0000000..b9d85bb --- /dev/null +++ b/openweather-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: openweather-api-automation +description: "Automate Openweather API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Openweather API Automation via Rube MCP + +Automate Openweather API operations through Composio's Openweather API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/openweather_api](https://composio.dev/toolkits/openweather_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Openweather API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `openweather_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `openweather_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Openweather API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Openweather API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["openweather_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Openweather API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `openweather_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/optimoroute-automation/SKILL.md b/optimoroute-automation/SKILL.md new file mode 100644 index 0000000..5df9a75 --- /dev/null +++ b/optimoroute-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: optimoroute-automation +description: "Automate Optimoroute tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Optimoroute Automation via Rube MCP + +Automate Optimoroute operations through Composio's Optimoroute toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/optimoroute](https://composio.dev/toolkits/optimoroute) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Optimoroute connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `optimoroute` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `optimoroute` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Optimoroute operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Optimoroute task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["optimoroute"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Optimoroute-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `optimoroute` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/outlook-automation/SKILL.md b/outlook-automation/SKILL.md index 288cfc9..dafb200 100644 --- a/outlook-automation/SKILL.md +++ b/outlook-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Microsoft Outlook operations through Composio's Outlook toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/outlook](https://composio.dev/toolkits/outlook) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -189,3 +191,6 @@ Automate Microsoft Outlook operations through Composio's Outlook toolkit via Rub | List contacts | OUTLOOK_LIST_CONTACTS | top, filter | | Create contact | OUTLOOK_CREATE_CONTACT | givenName, emailAddresses | | Contact folders | OUTLOOK_GET_CONTACT_FOLDERS | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/outlook-calendar-automation/SKILL.md b/outlook-calendar-automation/SKILL.md index 4c5f04a..5b9753a 100644 --- a/outlook-calendar-automation/SKILL.md +++ b/outlook-calendar-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Outlook Calendar operations through Composio's Outlook toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/outlook](https://composio.dev/toolkits/outlook) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -234,3 +236,6 @@ filter: "contains(subject, 'Review') and categories/any(c:c eq 'Work')" | Get schedule | OUTLOOK_GET_SCHEDULE | Schedules, StartTime, EndTime | | List calendars | OUTLOOK_LIST_CALENDARS | user_id | | Mailbox settings | OUTLOOK_GET_MAILBOX_SETTINGS | select | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/owl-protocol-automation/SKILL.md b/owl-protocol-automation/SKILL.md new file mode 100644 index 0000000..100e8e8 --- /dev/null +++ b/owl-protocol-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: owl-protocol-automation +description: "Automate Owl Protocol tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Owl Protocol Automation via Rube MCP + +Automate Owl Protocol operations through Composio's Owl Protocol toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/owl_protocol](https://composio.dev/toolkits/owl_protocol) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Owl Protocol connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `owl_protocol` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `owl_protocol` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Owl Protocol operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Owl Protocol task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["owl_protocol"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Owl Protocol-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `owl_protocol` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/page-x-automation/SKILL.md b/page-x-automation/SKILL.md new file mode 100644 index 0000000..3bfba49 --- /dev/null +++ b/page-x-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: page-x-automation +description: "Automate Page X tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Page X Automation via Rube MCP + +Automate Page X operations through Composio's Page X toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/page_x](https://composio.dev/toolkits/page_x) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Page X connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `page_x` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `page_x` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Page X operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Page X task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["page_x"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Page X-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `page_x` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pagerduty-automation/SKILL.md b/pagerduty-automation/SKILL.md index 7b277a7..820b4de 100644 --- a/pagerduty-automation/SKILL.md +++ b/pagerduty-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate PagerDuty incident management and operations through Composio's PagerDuty toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/pagerduty](https://composio.dev/toolkits/pagerduty) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -243,3 +245,6 @@ Automate PagerDuty incident management and operations through Composio's PagerDu | List escalation policies | PAGERDUTY_FETCH_ESCALATION_POLICES_LIST | (none) | | Create escalation policy | PAGERDUTY_CREATE_ESCALATION_POLICY | name, escalation_rules | | Create team | PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS | name, description | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pandadoc-automation/SKILL.md b/pandadoc-automation/SKILL.md new file mode 100644 index 0000000..4f70829 --- /dev/null +++ b/pandadoc-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pandadoc-automation +description: "Automate Pandadoc tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pandadoc Automation via Rube MCP + +Automate Pandadoc operations through Composio's Pandadoc toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pandadoc](https://composio.dev/toolkits/pandadoc) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pandadoc connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pandadoc` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pandadoc` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pandadoc operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pandadoc task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pandadoc"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pandadoc-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pandadoc` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/paradym-automation/SKILL.md b/paradym-automation/SKILL.md new file mode 100644 index 0000000..b96b715 --- /dev/null +++ b/paradym-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: paradym-automation +description: "Automate Paradym tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Paradym Automation via Rube MCP + +Automate Paradym operations through Composio's Paradym toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/paradym](https://composio.dev/toolkits/paradym) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Paradym connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `paradym` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `paradym` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Paradym operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Paradym task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["paradym"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Paradym-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `paradym` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/parallel-automation/SKILL.md b/parallel-automation/SKILL.md new file mode 100644 index 0000000..6182042 --- /dev/null +++ b/parallel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: parallel-automation +description: "Automate Parallel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Parallel Automation via Rube MCP + +Automate Parallel operations through Composio's Parallel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/parallel](https://composio.dev/toolkits/parallel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Parallel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `parallel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `parallel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Parallel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Parallel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["parallel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Parallel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `parallel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/parma-automation/SKILL.md b/parma-automation/SKILL.md new file mode 100644 index 0000000..7632823 --- /dev/null +++ b/parma-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: parma-automation +description: "Automate Parma tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Parma Automation via Rube MCP + +Automate Parma operations through Composio's Parma toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/parma](https://composio.dev/toolkits/parma) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Parma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `parma` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `parma` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Parma operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Parma task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["parma"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Parma-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `parma` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/parsehub-automation/SKILL.md b/parsehub-automation/SKILL.md new file mode 100644 index 0000000..deb4ba7 --- /dev/null +++ b/parsehub-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: parsehub-automation +description: "Automate Parsehub tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Parsehub Automation via Rube MCP + +Automate Parsehub operations through Composio's Parsehub toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/parsehub](https://composio.dev/toolkits/parsehub) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Parsehub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `parsehub` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `parsehub` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Parsehub operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Parsehub task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["parsehub"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Parsehub-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `parsehub` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/parsera-automation/SKILL.md b/parsera-automation/SKILL.md new file mode 100644 index 0000000..fde0982 --- /dev/null +++ b/parsera-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: parsera-automation +description: "Automate Parsera tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Parsera Automation via Rube MCP + +Automate Parsera operations through Composio's Parsera toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/parsera](https://composio.dev/toolkits/parsera) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Parsera connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `parsera` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `parsera` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Parsera operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Parsera task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["parsera"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Parsera-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `parsera` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/parseur-automation/SKILL.md b/parseur-automation/SKILL.md new file mode 100644 index 0000000..f49927e --- /dev/null +++ b/parseur-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: parseur-automation +description: "Automate Parseur tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Parseur Automation via Rube MCP + +Automate Parseur operations through Composio's Parseur toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/parseur](https://composio.dev/toolkits/parseur) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Parseur connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `parseur` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `parseur` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Parseur operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Parseur task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["parseur"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Parseur-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `parseur` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/passcreator-automation/SKILL.md b/passcreator-automation/SKILL.md new file mode 100644 index 0000000..d7a17cb --- /dev/null +++ b/passcreator-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: passcreator-automation +description: "Automate Passcreator tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Passcreator Automation via Rube MCP + +Automate Passcreator operations through Composio's Passcreator toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/passcreator](https://composio.dev/toolkits/passcreator) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Passcreator connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `passcreator` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `passcreator` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Passcreator operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Passcreator task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["passcreator"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Passcreator-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `passcreator` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/passslot-automation/SKILL.md b/passslot-automation/SKILL.md new file mode 100644 index 0000000..1bdab27 --- /dev/null +++ b/passslot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: passslot-automation +description: "Automate Passslot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Passslot Automation via Rube MCP + +Automate Passslot operations through Composio's Passslot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/passslot](https://composio.dev/toolkits/passslot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Passslot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `passslot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `passslot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Passslot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Passslot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["passslot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Passslot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `passslot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/payhip-automation/SKILL.md b/payhip-automation/SKILL.md new file mode 100644 index 0000000..99789f6 --- /dev/null +++ b/payhip-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: payhip-automation +description: "Automate Payhip tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Payhip Automation via Rube MCP + +Automate Payhip operations through Composio's Payhip toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/payhip](https://composio.dev/toolkits/payhip) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Payhip connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `payhip` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `payhip` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Payhip operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Payhip task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["payhip"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Payhip-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `payhip` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pdf-api-io-automation/SKILL.md b/pdf-api-io-automation/SKILL.md new file mode 100644 index 0000000..64a7b7d --- /dev/null +++ b/pdf-api-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pdf-api-io-automation +description: "Automate PDF API IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# PDF API IO Automation via Rube MCP + +Automate PDF API IO operations through Composio's PDF API IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pdf_api_io](https://composio.dev/toolkits/pdf_api_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active PDF API IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_api_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_api_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "PDF API IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific PDF API IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pdf_api_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with PDF API IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_api_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pdf-co-automation/SKILL.md b/pdf-co-automation/SKILL.md new file mode 100644 index 0000000..027462b --- /dev/null +++ b/pdf-co-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pdf-co-automation +description: "Automate PDF co tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# PDF co Automation via Rube MCP + +Automate PDF co operations through Composio's PDF co toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pdf_co](https://composio.dev/toolkits/pdf_co) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active PDF co connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_co` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_co` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "PDF co operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific PDF co task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pdf_co"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with PDF co-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf_co` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pdf4me-automation/SKILL.md b/pdf4me-automation/SKILL.md new file mode 100644 index 0000000..75d6b89 --- /dev/null +++ b/pdf4me-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pdf4me-automation +description: "Automate Pdf4me tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pdf4me Automation via Rube MCP + +Automate Pdf4me operations through Composio's Pdf4me toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pdf4me](https://composio.dev/toolkits/pdf4me) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pdf4me connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf4me` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf4me` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pdf4me operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pdf4me task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pdf4me"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pdf4me-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pdf4me` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pdfless-automation/SKILL.md b/pdfless-automation/SKILL.md new file mode 100644 index 0000000..a8ae20b --- /dev/null +++ b/pdfless-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pdfless-automation +description: "Automate Pdfless tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pdfless Automation via Rube MCP + +Automate Pdfless operations through Composio's Pdfless toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pdfless](https://composio.dev/toolkits/pdfless) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pdfless connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pdfless` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pdfless` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pdfless operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pdfless task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pdfless"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pdfless-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pdfless` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pdfmonkey-automation/SKILL.md b/pdfmonkey-automation/SKILL.md new file mode 100644 index 0000000..22cd4bd --- /dev/null +++ b/pdfmonkey-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pdfmonkey-automation +description: "Automate Pdfmonkey tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pdfmonkey Automation via Rube MCP + +Automate Pdfmonkey operations through Composio's Pdfmonkey toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pdfmonkey](https://composio.dev/toolkits/pdfmonkey) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pdfmonkey connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pdfmonkey` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pdfmonkey` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pdfmonkey operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pdfmonkey task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pdfmonkey"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pdfmonkey-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pdfmonkey` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/peopledatalabs-automation/SKILL.md b/peopledatalabs-automation/SKILL.md new file mode 100644 index 0000000..b6247bb --- /dev/null +++ b/peopledatalabs-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: peopledatalabs-automation +description: "Automate Peopledatalabs tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Peopledatalabs Automation via Rube MCP + +Automate Peopledatalabs operations through Composio's Peopledatalabs toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/peopledatalabs](https://composio.dev/toolkits/peopledatalabs) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Peopledatalabs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `peopledatalabs` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `peopledatalabs` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Peopledatalabs operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Peopledatalabs task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["peopledatalabs"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Peopledatalabs-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `peopledatalabs` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/perigon-automation/SKILL.md b/perigon-automation/SKILL.md new file mode 100644 index 0000000..b041451 --- /dev/null +++ b/perigon-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: perigon-automation +description: "Automate Perigon tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Perigon Automation via Rube MCP + +Automate Perigon operations through Composio's Perigon toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/perigon](https://composio.dev/toolkits/perigon) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Perigon connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `perigon` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `perigon` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Perigon operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Perigon task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["perigon"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Perigon-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `perigon` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/perplexityai-automation/SKILL.md b/perplexityai-automation/SKILL.md new file mode 100644 index 0000000..ecb290a --- /dev/null +++ b/perplexityai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: perplexityai-automation +description: "Automate Perplexityai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Perplexityai Automation via Rube MCP + +Automate Perplexityai operations through Composio's Perplexityai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/perplexityai](https://composio.dev/toolkits/perplexityai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Perplexityai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `perplexityai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `perplexityai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Perplexityai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Perplexityai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["perplexityai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Perplexityai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `perplexityai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/persistiq-automation/SKILL.md b/persistiq-automation/SKILL.md new file mode 100644 index 0000000..1760298 --- /dev/null +++ b/persistiq-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: persistiq-automation +description: "Automate Persistiq tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Persistiq Automation via Rube MCP + +Automate Persistiq operations through Composio's Persistiq toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/persistiq](https://composio.dev/toolkits/persistiq) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Persistiq connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `persistiq` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `persistiq` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Persistiq operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Persistiq task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["persistiq"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Persistiq-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `persistiq` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pexels-automation/SKILL.md b/pexels-automation/SKILL.md new file mode 100644 index 0000000..9826635 --- /dev/null +++ b/pexels-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pexels-automation +description: "Automate Pexels tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pexels Automation via Rube MCP + +Automate Pexels operations through Composio's Pexels toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pexels](https://composio.dev/toolkits/pexels) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pexels connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pexels` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pexels` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pexels operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pexels task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pexels"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pexels-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pexels` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/phantombuster-automation/SKILL.md b/phantombuster-automation/SKILL.md new file mode 100644 index 0000000..7701824 --- /dev/null +++ b/phantombuster-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: phantombuster-automation +description: "Automate Phantombuster tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Phantombuster Automation via Rube MCP + +Automate Phantombuster operations through Composio's Phantombuster toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/phantombuster](https://composio.dev/toolkits/phantombuster) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Phantombuster connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `phantombuster` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `phantombuster` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Phantombuster operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Phantombuster task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["phantombuster"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Phantombuster-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `phantombuster` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/piggy-automation/SKILL.md b/piggy-automation/SKILL.md new file mode 100644 index 0000000..bcbd872 --- /dev/null +++ b/piggy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: piggy-automation +description: "Automate Piggy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Piggy Automation via Rube MCP + +Automate Piggy operations through Composio's Piggy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/piggy](https://composio.dev/toolkits/piggy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Piggy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `piggy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `piggy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Piggy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Piggy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["piggy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Piggy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `piggy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/piloterr-automation/SKILL.md b/piloterr-automation/SKILL.md new file mode 100644 index 0000000..159191d --- /dev/null +++ b/piloterr-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: piloterr-automation +description: "Automate Piloterr tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Piloterr Automation via Rube MCP + +Automate Piloterr operations through Composio's Piloterr toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/piloterr](https://composio.dev/toolkits/piloterr) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Piloterr connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `piloterr` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `piloterr` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Piloterr operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Piloterr task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["piloterr"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Piloterr-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `piloterr` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pilvio-automation/SKILL.md b/pilvio-automation/SKILL.md new file mode 100644 index 0000000..a4e9cbb --- /dev/null +++ b/pilvio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pilvio-automation +description: "Automate Pilvio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pilvio Automation via Rube MCP + +Automate Pilvio operations through Composio's Pilvio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pilvio](https://composio.dev/toolkits/pilvio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pilvio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pilvio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pilvio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pilvio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pilvio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pilvio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pilvio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pilvio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pingdom-automation/SKILL.md b/pingdom-automation/SKILL.md new file mode 100644 index 0000000..62bc17f --- /dev/null +++ b/pingdom-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pingdom-automation +description: "Automate Pingdom tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pingdom Automation via Rube MCP + +Automate Pingdom operations through Composio's Pingdom toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pingdom](https://composio.dev/toolkits/pingdom) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pingdom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pingdom` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pingdom` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pingdom operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pingdom task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pingdom"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pingdom-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pingdom` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pipedrive-automation/SKILL.md b/pipedrive-automation/SKILL.md index dd9b02b..643c060 100644 --- a/pipedrive-automation/SKILL.md +++ b/pipedrive-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Pipedrive CRM workflows including deal management, contact and organization operations, activity scheduling, notes, and pipeline/stage queries through Composio's Pipedrive toolkit. +**Toolkit docs**: [composio.dev/toolkits/pipedrive](https://composio.dev/toolkits/pipedrive) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -222,3 +224,6 @@ Most list endpoints use offset-based pagination: | Deals in pipeline | `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` | `id`, `stage_id` | | Deals in stage | `PIPEDRIVE_GET_DEALS_IN_A_STAGE` | `id`, `start`, `limit` | | Add product to deal | `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` | `id`, `product_id`, `item_price` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pipeline-crm-automation/SKILL.md b/pipeline-crm-automation/SKILL.md new file mode 100644 index 0000000..5961b16 --- /dev/null +++ b/pipeline-crm-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pipeline-crm-automation +description: "Automate Pipeline CRM tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pipeline CRM Automation via Rube MCP + +Automate Pipeline CRM operations through Composio's Pipeline CRM toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pipeline_crm](https://composio.dev/toolkits/pipeline_crm) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pipeline CRM connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pipeline_crm` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pipeline_crm` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pipeline CRM operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pipeline CRM task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pipeline_crm"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pipeline CRM-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pipeline_crm` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/placekey-automation/SKILL.md b/placekey-automation/SKILL.md new file mode 100644 index 0000000..824385e --- /dev/null +++ b/placekey-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: placekey-automation +description: "Automate Placekey tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Placekey Automation via Rube MCP + +Automate Placekey operations through Composio's Placekey toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/placekey](https://composio.dev/toolkits/placekey) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Placekey connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `placekey` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `placekey` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Placekey operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Placekey task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["placekey"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Placekey-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `placekey` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/placid-automation/SKILL.md b/placid-automation/SKILL.md new file mode 100644 index 0000000..6620147 --- /dev/null +++ b/placid-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: placid-automation +description: "Automate Placid tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Placid Automation via Rube MCP + +Automate Placid operations through Composio's Placid toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/placid](https://composio.dev/toolkits/placid) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Placid connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `placid` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `placid` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Placid operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Placid task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["placid"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Placid-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `placid` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/plain-automation/SKILL.md b/plain-automation/SKILL.md new file mode 100644 index 0000000..8f68543 --- /dev/null +++ b/plain-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: plain-automation +description: "Automate Plain tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Plain Automation via Rube MCP + +Automate Plain operations through Composio's Plain toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/plain](https://composio.dev/toolkits/plain) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Plain connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `plain` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `plain` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Plain operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Plain task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["plain"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Plain-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `plain` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/plasmic-automation/SKILL.md b/plasmic-automation/SKILL.md new file mode 100644 index 0000000..4928626 --- /dev/null +++ b/plasmic-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: plasmic-automation +description: "Automate Plasmic tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Plasmic Automation via Rube MCP + +Automate Plasmic operations through Composio's Plasmic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/plasmic](https://composio.dev/toolkits/plasmic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Plasmic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `plasmic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `plasmic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Plasmic operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Plasmic task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["plasmic"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Plasmic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `plasmic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/platerecognizer-automation/SKILL.md b/platerecognizer-automation/SKILL.md new file mode 100644 index 0000000..fdc9636 --- /dev/null +++ b/platerecognizer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: platerecognizer-automation +description: "Automate Platerecognizer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Platerecognizer Automation via Rube MCP + +Automate Platerecognizer operations through Composio's Platerecognizer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/platerecognizer](https://composio.dev/toolkits/platerecognizer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Platerecognizer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `platerecognizer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `platerecognizer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Platerecognizer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Platerecognizer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["platerecognizer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Platerecognizer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `platerecognizer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/plisio-automation/SKILL.md b/plisio-automation/SKILL.md new file mode 100644 index 0000000..582fb1e --- /dev/null +++ b/plisio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: plisio-automation +description: "Automate Plisio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Plisio Automation via Rube MCP + +Automate Plisio operations through Composio's Plisio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/plisio](https://composio.dev/toolkits/plisio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Plisio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `plisio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `plisio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Plisio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Plisio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["plisio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Plisio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `plisio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/polygon-automation/SKILL.md b/polygon-automation/SKILL.md new file mode 100644 index 0000000..c2e8195 --- /dev/null +++ b/polygon-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: polygon-automation +description: "Automate Polygon tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Polygon Automation via Rube MCP + +Automate Polygon operations through Composio's Polygon toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/polygon](https://composio.dev/toolkits/polygon) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Polygon connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `polygon` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `polygon` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Polygon operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Polygon task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["polygon"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Polygon-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `polygon` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/polygon-io-automation/SKILL.md b/polygon-io-automation/SKILL.md new file mode 100644 index 0000000..7681dd5 --- /dev/null +++ b/polygon-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: polygon-io-automation +description: "Automate Polygon IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Polygon IO Automation via Rube MCP + +Automate Polygon IO operations through Composio's Polygon IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/polygon_io](https://composio.dev/toolkits/polygon_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Polygon IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `polygon_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `polygon_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Polygon IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Polygon IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["polygon_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Polygon IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `polygon_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/poptin-automation/SKILL.md b/poptin-automation/SKILL.md new file mode 100644 index 0000000..7a7cd35 --- /dev/null +++ b/poptin-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: poptin-automation +description: "Automate Poptin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Poptin Automation via Rube MCP + +Automate Poptin operations through Composio's Poptin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/poptin](https://composio.dev/toolkits/poptin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Poptin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `poptin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `poptin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Poptin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Poptin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["poptin"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Poptin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `poptin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/postgrid-automation/SKILL.md b/postgrid-automation/SKILL.md new file mode 100644 index 0000000..4ea98e3 --- /dev/null +++ b/postgrid-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: postgrid-automation +description: "Automate Postgrid tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Postgrid Automation via Rube MCP + +Automate Postgrid operations through Composio's Postgrid toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/postgrid](https://composio.dev/toolkits/postgrid) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Postgrid connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `postgrid` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `postgrid` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Postgrid operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Postgrid task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["postgrid"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Postgrid-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `postgrid` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/postgrid-verify-automation/SKILL.md b/postgrid-verify-automation/SKILL.md new file mode 100644 index 0000000..1ef88fd --- /dev/null +++ b/postgrid-verify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: postgrid-verify-automation +description: "Automate Postgrid Verify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Postgrid Verify Automation via Rube MCP + +Automate Postgrid Verify operations through Composio's Postgrid Verify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/postgrid_verify](https://composio.dev/toolkits/postgrid_verify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Postgrid Verify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `postgrid_verify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `postgrid_verify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Postgrid Verify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Postgrid Verify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["postgrid_verify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Postgrid Verify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `postgrid_verify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/posthog-automation/SKILL.md b/posthog-automation/SKILL.md index a8fb095..34b3fa2 100644 --- a/posthog-automation/SKILL.md +++ b/posthog-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate PostHog product analytics and feature flag management through Composio's PostHog toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/posthog](https://composio.dev/toolkits/posthog) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -222,3 +224,6 @@ Feature flags support sophisticated targeting: | List projects | POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION | organization_id | | Who am I | POSTHOG_WHOAMI | (none) | | User profile | POSTHOG_RETRIEVE_CURRENT_USER_PROFILE | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/postmark-automation/SKILL.md b/postmark-automation/SKILL.md index 4a0b0b4..2e2fca5 100644 --- a/postmark-automation/SKILL.md +++ b/postmark-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Postmark transactional email operations through Composio's Postmark toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/postmark](https://composio.dev/toolkits/postmark) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -185,3 +187,6 @@ Automate Postmark transactional email operations through Composio's Postmark too | Tracked email counts | POSTMARK_GET_TRACKED_EMAIL_COUNTS | fromdate, todate, tag | | Get server config | POSTMARK_GET_SERVER | (none) | | Edit server config | POSTMARK_EDIT_SERVER | Name, TrackOpens, TrackLinks | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/precoro-automation/SKILL.md b/precoro-automation/SKILL.md new file mode 100644 index 0000000..0edfb9c --- /dev/null +++ b/precoro-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: precoro-automation +description: "Automate Precoro tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Precoro Automation via Rube MCP + +Automate Precoro operations through Composio's Precoro toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/precoro](https://composio.dev/toolkits/precoro) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Precoro connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `precoro` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `precoro` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Precoro operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Precoro task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["precoro"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Precoro-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `precoro` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/prerender-automation/SKILL.md b/prerender-automation/SKILL.md new file mode 100644 index 0000000..c6dda58 --- /dev/null +++ b/prerender-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: prerender-automation +description: "Automate Prerender tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Prerender Automation via Rube MCP + +Automate Prerender operations through Composio's Prerender toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/prerender](https://composio.dev/toolkits/prerender) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Prerender connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `prerender` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `prerender` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Prerender operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Prerender task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["prerender"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Prerender-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `prerender` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/printautopilot-automation/SKILL.md b/printautopilot-automation/SKILL.md new file mode 100644 index 0000000..bf243fa --- /dev/null +++ b/printautopilot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: printautopilot-automation +description: "Automate Printautopilot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Printautopilot Automation via Rube MCP + +Automate Printautopilot operations through Composio's Printautopilot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/printautopilot](https://composio.dev/toolkits/printautopilot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Printautopilot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `printautopilot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `printautopilot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Printautopilot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Printautopilot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["printautopilot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Printautopilot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `printautopilot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/prisma-automation/SKILL.md b/prisma-automation/SKILL.md new file mode 100644 index 0000000..3f9fecc --- /dev/null +++ b/prisma-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: prisma-automation +description: "Automate Prisma tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Prisma Automation via Rube MCP + +Automate Prisma operations through Composio's Prisma toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/prisma](https://composio.dev/toolkits/prisma) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Prisma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `prisma` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `prisma` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Prisma operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Prisma task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["prisma"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Prisma-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `prisma` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/prismic-automation/SKILL.md b/prismic-automation/SKILL.md new file mode 100644 index 0000000..af1f38c --- /dev/null +++ b/prismic-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: prismic-automation +description: "Automate Prismic tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Prismic Automation via Rube MCP + +Automate Prismic operations through Composio's Prismic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/prismic](https://composio.dev/toolkits/prismic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Prismic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `prismic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `prismic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Prismic operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Prismic task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["prismic"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Prismic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `prismic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/process-street-automation/SKILL.md b/process-street-automation/SKILL.md new file mode 100644 index 0000000..a5634c8 --- /dev/null +++ b/process-street-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: process-street-automation +description: "Automate Process Street tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Process Street Automation via Rube MCP + +Automate Process Street operations through Composio's Process Street toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/process_street](https://composio.dev/toolkits/process_street) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Process Street connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `process_street` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `process_street` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Process Street operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Process Street task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["process_street"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Process Street-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `process_street` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/procfu-automation/SKILL.md b/procfu-automation/SKILL.md new file mode 100644 index 0000000..0e5e61a --- /dev/null +++ b/procfu-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: procfu-automation +description: "Automate Procfu tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Procfu Automation via Rube MCP + +Automate Procfu operations through Composio's Procfu toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/procfu](https://composio.dev/toolkits/procfu) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Procfu connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `procfu` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `procfu` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Procfu operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Procfu task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["procfu"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Procfu-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `procfu` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/productboard-automation/SKILL.md b/productboard-automation/SKILL.md new file mode 100644 index 0000000..b809f11 --- /dev/null +++ b/productboard-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: productboard-automation +description: "Automate Productboard tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Productboard Automation via Rube MCP + +Automate Productboard operations through Composio's Productboard toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/productboard](https://composio.dev/toolkits/productboard) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Productboard connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `productboard` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `productboard` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Productboard operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Productboard task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["productboard"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Productboard-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `productboard` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/productlane-automation/SKILL.md b/productlane-automation/SKILL.md new file mode 100644 index 0000000..e36f646 --- /dev/null +++ b/productlane-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: productlane-automation +description: "Automate Productlane tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Productlane Automation via Rube MCP + +Automate Productlane operations through Composio's Productlane toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/productlane](https://composio.dev/toolkits/productlane) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Productlane connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `productlane` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `productlane` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Productlane operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Productlane task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["productlane"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Productlane-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `productlane` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/project-bubble-automation/SKILL.md b/project-bubble-automation/SKILL.md new file mode 100644 index 0000000..55f93d7 --- /dev/null +++ b/project-bubble-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: project-bubble-automation +description: "Automate Project Bubble tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Project Bubble Automation via Rube MCP + +Automate Project Bubble operations through Composio's Project Bubble toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/project_bubble](https://composio.dev/toolkits/project_bubble) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Project Bubble connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `project_bubble` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `project_bubble` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Project Bubble operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Project Bubble task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["project_bubble"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Project Bubble-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `project_bubble` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/proofly-automation/SKILL.md b/proofly-automation/SKILL.md new file mode 100644 index 0000000..b6212fb --- /dev/null +++ b/proofly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: proofly-automation +description: "Automate Proofly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Proofly Automation via Rube MCP + +Automate Proofly operations through Composio's Proofly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/proofly](https://composio.dev/toolkits/proofly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Proofly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `proofly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `proofly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Proofly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Proofly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["proofly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Proofly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `proofly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/proxiedmail-automation/SKILL.md b/proxiedmail-automation/SKILL.md new file mode 100644 index 0000000..8206d2f --- /dev/null +++ b/proxiedmail-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: proxiedmail-automation +description: "Automate Proxiedmail tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Proxiedmail Automation via Rube MCP + +Automate Proxiedmail operations through Composio's Proxiedmail toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/proxiedmail](https://composio.dev/toolkits/proxiedmail) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Proxiedmail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `proxiedmail` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `proxiedmail` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Proxiedmail operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Proxiedmail task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["proxiedmail"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Proxiedmail-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `proxiedmail` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pushbullet-automation/SKILL.md b/pushbullet-automation/SKILL.md new file mode 100644 index 0000000..5118f82 --- /dev/null +++ b/pushbullet-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pushbullet-automation +description: "Automate Pushbullet tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pushbullet Automation via Rube MCP + +Automate Pushbullet operations through Composio's Pushbullet toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pushbullet](https://composio.dev/toolkits/pushbullet) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pushbullet connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pushbullet` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pushbullet` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pushbullet operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pushbullet task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pushbullet"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pushbullet-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pushbullet` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/pushover-automation/SKILL.md b/pushover-automation/SKILL.md new file mode 100644 index 0000000..2d23ad0 --- /dev/null +++ b/pushover-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: pushover-automation +description: "Automate Pushover tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Pushover Automation via Rube MCP + +Automate Pushover operations through Composio's Pushover toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/pushover](https://composio.dev/toolkits/pushover) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Pushover connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pushover` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pushover` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Pushover operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Pushover task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["pushover"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Pushover-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `pushover` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/quaderno-automation/SKILL.md b/quaderno-automation/SKILL.md new file mode 100644 index 0000000..bc0b060 --- /dev/null +++ b/quaderno-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: quaderno-automation +description: "Automate Quaderno tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Quaderno Automation via Rube MCP + +Automate Quaderno operations through Composio's Quaderno toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/quaderno](https://composio.dev/toolkits/quaderno) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Quaderno connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `quaderno` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `quaderno` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Quaderno operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Quaderno task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["quaderno"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Quaderno-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `quaderno` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/qualaroo-automation/SKILL.md b/qualaroo-automation/SKILL.md new file mode 100644 index 0000000..1da1ad3 --- /dev/null +++ b/qualaroo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: qualaroo-automation +description: "Automate Qualaroo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Qualaroo Automation via Rube MCP + +Automate Qualaroo operations through Composio's Qualaroo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/qualaroo](https://composio.dev/toolkits/qualaroo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Qualaroo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `qualaroo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `qualaroo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Qualaroo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Qualaroo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["qualaroo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Qualaroo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `qualaroo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/quickbooks-automation/SKILL.md b/quickbooks-automation/SKILL.md new file mode 100644 index 0000000..1080fc0 --- /dev/null +++ b/quickbooks-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: quickbooks-automation +description: "Automate Quickbooks tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Quickbooks Automation via Rube MCP + +Automate Quickbooks operations through Composio's Quickbooks toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/quickbooks](https://composio.dev/toolkits/quickbooks) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Quickbooks connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `quickbooks` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `quickbooks` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Quickbooks operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Quickbooks task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["quickbooks"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Quickbooks-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `quickbooks` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/radar-automation/SKILL.md b/radar-automation/SKILL.md new file mode 100644 index 0000000..0a2c08d --- /dev/null +++ b/radar-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: radar-automation +description: "Automate Radar tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Radar Automation via Rube MCP + +Automate Radar operations through Composio's Radar toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/radar](https://composio.dev/toolkits/radar) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Radar connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `radar` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `radar` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Radar operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Radar task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["radar"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Radar-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `radar` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/rafflys-automation/SKILL.md b/rafflys-automation/SKILL.md new file mode 100644 index 0000000..84b6688 --- /dev/null +++ b/rafflys-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: rafflys-automation +description: "Automate Rafflys tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Rafflys Automation via Rube MCP + +Automate Rafflys operations through Composio's Rafflys toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/rafflys](https://composio.dev/toolkits/rafflys) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Rafflys connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rafflys` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rafflys` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Rafflys operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Rafflys task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["rafflys"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Rafflys-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `rafflys` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ragic-automation/SKILL.md b/ragic-automation/SKILL.md new file mode 100644 index 0000000..e2b1529 --- /dev/null +++ b/ragic-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ragic-automation +description: "Automate Ragic tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ragic Automation via Rube MCP + +Automate Ragic operations through Composio's Ragic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ragic](https://composio.dev/toolkits/ragic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ragic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ragic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ragic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ragic operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ragic task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ragic"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ragic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ragic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/raisely-automation/SKILL.md b/raisely-automation/SKILL.md new file mode 100644 index 0000000..bdc70ee --- /dev/null +++ b/raisely-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: raisely-automation +description: "Automate Raisely tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Raisely Automation via Rube MCP + +Automate Raisely operations through Composio's Raisely toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/raisely](https://composio.dev/toolkits/raisely) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Raisely connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `raisely` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `raisely` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Raisely operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Raisely task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["raisely"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Raisely-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `raisely` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ramp-automation/SKILL.md b/ramp-automation/SKILL.md new file mode 100644 index 0000000..325e6fe --- /dev/null +++ b/ramp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ramp-automation +description: "Automate Ramp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ramp Automation via Rube MCP + +Automate Ramp operations through Composio's Ramp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ramp](https://composio.dev/toolkits/ramp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ramp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ramp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ramp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ramp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ramp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ramp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ramp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ramp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ravenseotools-automation/SKILL.md b/ravenseotools-automation/SKILL.md new file mode 100644 index 0000000..c231011 --- /dev/null +++ b/ravenseotools-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ravenseotools-automation +description: "Automate Ravenseotools tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ravenseotools Automation via Rube MCP + +Automate Ravenseotools operations through Composio's Ravenseotools toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ravenseotools](https://composio.dev/toolkits/ravenseotools) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ravenseotools connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ravenseotools` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ravenseotools` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ravenseotools operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ravenseotools task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ravenseotools"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ravenseotools-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ravenseotools` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/re-amaze-automation/SKILL.md b/re-amaze-automation/SKILL.md new file mode 100644 index 0000000..4d8d04e --- /dev/null +++ b/re-amaze-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: re-amaze-automation +description: "Automate Re Amaze tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Re Amaze Automation via Rube MCP + +Automate Re Amaze operations through Composio's Re Amaze toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/re_amaze](https://composio.dev/toolkits/re_amaze) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Re Amaze connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `re_amaze` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `re_amaze` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Re Amaze operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Re Amaze task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["re_amaze"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Re Amaze-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `re_amaze` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/realphonevalidation-automation/SKILL.md b/realphonevalidation-automation/SKILL.md new file mode 100644 index 0000000..ac0348d --- /dev/null +++ b/realphonevalidation-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: realphonevalidation-automation +description: "Automate Realphonevalidation tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Realphonevalidation Automation via Rube MCP + +Automate Realphonevalidation operations through Composio's Realphonevalidation toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/realphonevalidation](https://composio.dev/toolkits/realphonevalidation) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Realphonevalidation connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `realphonevalidation` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `realphonevalidation` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Realphonevalidation operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Realphonevalidation task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["realphonevalidation"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Realphonevalidation-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `realphonevalidation` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/recallai-automation/SKILL.md b/recallai-automation/SKILL.md new file mode 100644 index 0000000..69170c1 --- /dev/null +++ b/recallai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: recallai-automation +description: "Automate Recallai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Recallai Automation via Rube MCP + +Automate Recallai operations through Composio's Recallai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/recallai](https://composio.dev/toolkits/recallai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Recallai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `recallai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `recallai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Recallai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Recallai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["recallai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Recallai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `recallai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/recruitee-automation/SKILL.md b/recruitee-automation/SKILL.md new file mode 100644 index 0000000..a217196 --- /dev/null +++ b/recruitee-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: recruitee-automation +description: "Automate Recruitee tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Recruitee Automation via Rube MCP + +Automate Recruitee operations through Composio's Recruitee toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/recruitee](https://composio.dev/toolkits/recruitee) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Recruitee connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `recruitee` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `recruitee` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Recruitee operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Recruitee task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["recruitee"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Recruitee-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `recruitee` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/reddit-automation/SKILL.md b/reddit-automation/SKILL.md index 7730337..ebc1557 100644 --- a/reddit-automation/SKILL.md +++ b/reddit-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Reddit operations through Composio's Reddit toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/reddit](https://composio.dev/toolkits/reddit) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -210,3 +212,6 @@ t5_ = Subreddit | Get specific comment | REDDIT_RETRIEVE_SPECIFIC_COMMENT | comment_id | | List post flairs | REDDIT_LIST_SUBREDDIT_POST_FLAIRS | subreddit | | Get user flair | REDDIT_GET_USER_FLAIR | subreddit | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/refiner-automation/SKILL.md b/refiner-automation/SKILL.md new file mode 100644 index 0000000..245213b --- /dev/null +++ b/refiner-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: refiner-automation +description: "Automate Refiner tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Refiner Automation via Rube MCP + +Automate Refiner operations through Composio's Refiner toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/refiner](https://composio.dev/toolkits/refiner) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Refiner connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `refiner` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `refiner` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Refiner operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Refiner task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["refiner"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Refiner-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `refiner` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/remarkety-automation/SKILL.md b/remarkety-automation/SKILL.md new file mode 100644 index 0000000..e247442 --- /dev/null +++ b/remarkety-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: remarkety-automation +description: "Automate Remarkety tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Remarkety Automation via Rube MCP + +Automate Remarkety operations through Composio's Remarkety toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/remarkety](https://composio.dev/toolkits/remarkety) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Remarkety connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `remarkety` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `remarkety` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Remarkety operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Remarkety task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["remarkety"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Remarkety-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `remarkety` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/remote-retrieval-automation/SKILL.md b/remote-retrieval-automation/SKILL.md new file mode 100644 index 0000000..9c84f74 --- /dev/null +++ b/remote-retrieval-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: remote-retrieval-automation +description: "Automate Remote Retrieval tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Remote Retrieval Automation via Rube MCP + +Automate Remote Retrieval operations through Composio's Remote Retrieval toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/remote_retrieval](https://composio.dev/toolkits/remote_retrieval) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Remote Retrieval connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `remote_retrieval` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `remote_retrieval` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Remote Retrieval operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Remote Retrieval task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["remote_retrieval"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Remote Retrieval-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `remote_retrieval` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/remove-bg-automation/SKILL.md b/remove-bg-automation/SKILL.md new file mode 100644 index 0000000..9bbb61e --- /dev/null +++ b/remove-bg-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: remove-bg-automation +description: "Automate Remove Bg tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Remove Bg Automation via Rube MCP + +Automate Remove Bg operations through Composio's Remove Bg toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/remove_bg](https://composio.dev/toolkits/remove_bg) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Remove Bg connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `remove_bg` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `remove_bg` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Remove Bg operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Remove Bg task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["remove_bg"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Remove Bg-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `remove_bg` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/render-automation/SKILL.md b/render-automation/SKILL.md index 5ae052b..dabd3c1 100644 --- a/render-automation/SKILL.md +++ b/render-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Render cloud platform operations through Composio's Render toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/render](https://composio.dev/toolkits/render) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -179,3 +181,6 @@ Automate Render cloud platform operations through Composio's Render toolkit via | Trigger deploy | RENDER_TRIGGER_DEPLOY | serviceId, clearCache | | Get deploy status | RENDER_RETRIEVE_DEPLOY | serviceId, deployId | | List projects | RENDER_LIST_PROJECTS | limit, cursor | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/renderform-automation/SKILL.md b/renderform-automation/SKILL.md new file mode 100644 index 0000000..9aee89e --- /dev/null +++ b/renderform-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: renderform-automation +description: "Automate Renderform tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Renderform Automation via Rube MCP + +Automate Renderform operations through Composio's Renderform toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/renderform](https://composio.dev/toolkits/renderform) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Renderform connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `renderform` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `renderform` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Renderform operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Renderform task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["renderform"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Renderform-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `renderform` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/repairshopr-automation/SKILL.md b/repairshopr-automation/SKILL.md new file mode 100644 index 0000000..6cc63e8 --- /dev/null +++ b/repairshopr-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: repairshopr-automation +description: "Automate Repairshopr tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Repairshopr Automation via Rube MCP + +Automate Repairshopr operations through Composio's Repairshopr toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/repairshopr](https://composio.dev/toolkits/repairshopr) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Repairshopr connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `repairshopr` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `repairshopr` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Repairshopr operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Repairshopr task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["repairshopr"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Repairshopr-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `repairshopr` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/replicate-automation/SKILL.md b/replicate-automation/SKILL.md new file mode 100644 index 0000000..fef7ffb --- /dev/null +++ b/replicate-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: replicate-automation +description: "Automate Replicate tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Replicate Automation via Rube MCP + +Automate Replicate operations through Composio's Replicate toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/replicate](https://composio.dev/toolkits/replicate) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Replicate connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `replicate` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `replicate` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Replicate operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Replicate task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["replicate"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Replicate-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `replicate` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/reply-automation/SKILL.md b/reply-automation/SKILL.md new file mode 100644 index 0000000..8dbc31e --- /dev/null +++ b/reply-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: reply-automation +description: "Automate Reply tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Reply Automation via Rube MCP + +Automate Reply operations through Composio's Reply toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/reply](https://composio.dev/toolkits/reply) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Reply connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `reply` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `reply` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Reply operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Reply task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["reply"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Reply-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `reply` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/reply-io-automation/SKILL.md b/reply-io-automation/SKILL.md new file mode 100644 index 0000000..3041346 --- /dev/null +++ b/reply-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: reply-io-automation +description: "Automate Reply IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Reply IO Automation via Rube MCP + +Automate Reply IO operations through Composio's Reply IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/reply_io](https://composio.dev/toolkits/reply_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Reply IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `reply_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `reply_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Reply IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Reply IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["reply_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Reply IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `reply_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/resend-automation/SKILL.md b/resend-automation/SKILL.md new file mode 100644 index 0000000..91030c4 --- /dev/null +++ b/resend-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: resend-automation +description: "Automate Resend tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Resend Automation via Rube MCP + +Automate Resend operations through Composio's Resend toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/resend](https://composio.dev/toolkits/resend) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Resend connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `resend` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `resend` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Resend operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Resend task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["resend"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Resend-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `resend` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/respond-io-automation/SKILL.md b/respond-io-automation/SKILL.md new file mode 100644 index 0000000..fe4258e --- /dev/null +++ b/respond-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: respond-io-automation +description: "Automate Respond IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Respond IO Automation via Rube MCP + +Automate Respond IO operations through Composio's Respond IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/respond_io](https://composio.dev/toolkits/respond_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Respond IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `respond_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `respond_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Respond IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Respond IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["respond_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Respond IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `respond_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/retailed-automation/SKILL.md b/retailed-automation/SKILL.md new file mode 100644 index 0000000..dc29b71 --- /dev/null +++ b/retailed-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: retailed-automation +description: "Automate Retailed tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Retailed Automation via Rube MCP + +Automate Retailed operations through Composio's Retailed toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/retailed](https://composio.dev/toolkits/retailed) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Retailed connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `retailed` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `retailed` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Retailed operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Retailed task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["retailed"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Retailed-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `retailed` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/retellai-automation/SKILL.md b/retellai-automation/SKILL.md new file mode 100644 index 0000000..258565b --- /dev/null +++ b/retellai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: retellai-automation +description: "Automate Retellai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Retellai Automation via Rube MCP + +Automate Retellai operations through Composio's Retellai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/retellai](https://composio.dev/toolkits/retellai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Retellai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `retellai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `retellai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Retellai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Retellai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["retellai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Retellai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `retellai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/retently-automation/SKILL.md b/retently-automation/SKILL.md new file mode 100644 index 0000000..6f15806 --- /dev/null +++ b/retently-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: retently-automation +description: "Automate Retently tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Retently Automation via Rube MCP + +Automate Retently operations through Composio's Retently toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/retently](https://composio.dev/toolkits/retently) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Retently connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `retently` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `retently` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Retently operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Retently task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["retently"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Retently-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `retently` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/rev-ai-automation/SKILL.md b/rev-ai-automation/SKILL.md new file mode 100644 index 0000000..e83e89c --- /dev/null +++ b/rev-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: rev-ai-automation +description: "Automate Rev AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Rev AI Automation via Rube MCP + +Automate Rev AI operations through Composio's Rev AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/rev_ai](https://composio.dev/toolkits/rev_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Rev AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rev_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rev_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Rev AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Rev AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["rev_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Rev AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `rev_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/revolt-automation/SKILL.md b/revolt-automation/SKILL.md new file mode 100644 index 0000000..a690fa5 --- /dev/null +++ b/revolt-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: revolt-automation +description: "Automate Revolt tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Revolt Automation via Rube MCP + +Automate Revolt operations through Composio's Revolt toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/revolt](https://composio.dev/toolkits/revolt) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Revolt connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `revolt` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `revolt` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Revolt operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Revolt task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["revolt"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Revolt-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `revolt` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ring-central-automation/SKILL.md b/ring-central-automation/SKILL.md new file mode 100644 index 0000000..2c028fa --- /dev/null +++ b/ring-central-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ring-central-automation +description: "Automate RingCentral tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# RingCentral Automation via Rube MCP + +Automate RingCentral operations through Composio's RingCentral toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ring_central](https://composio.dev/toolkits/ring_central) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active RingCentral connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ring_central` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ring_central` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "RingCentral operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific RingCentral task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ring_central"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with RingCentral-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ring_central` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ring_central-automation/SKILL.md b/ring_central-automation/SKILL.md new file mode 100644 index 0000000..809ab46 --- /dev/null +++ b/ring_central-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: ring_central-automation +description: "Automate RingCentral tasks via Rube MCP (Composio): calls, messages, meetings, and unified communications. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# RingCentral Automation via Rube MCP + +Automate RingCentral operations through Composio's RingCentral toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ring_central](https://composio.dev/toolkits/ring_central) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active RingCentral connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ring_central` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ring_central` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "calls, messages, meetings, and unified communications", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for RingCentral +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available RingCentral Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available RingCentral tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute RingCentral Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple RingCentral operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the RingCentral connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with RingCentral-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ring_central` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/ring_central](https://composio.dev/toolkits/ring_central) diff --git a/rippling-automation/SKILL.md b/rippling-automation/SKILL.md new file mode 100644 index 0000000..db5ebcb --- /dev/null +++ b/rippling-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: rippling-automation +description: "Automate Rippling tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Rippling Automation via Rube MCP + +Automate Rippling operations through Composio's Rippling toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/rippling](https://composio.dev/toolkits/rippling) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Rippling connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rippling` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rippling` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Rippling operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Rippling task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["rippling"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Rippling-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `rippling` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ritekit-automation/SKILL.md b/ritekit-automation/SKILL.md new file mode 100644 index 0000000..9504527 --- /dev/null +++ b/ritekit-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ritekit-automation +description: "Automate Ritekit tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ritekit Automation via Rube MCP + +Automate Ritekit operations through Composio's Ritekit toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ritekit](https://composio.dev/toolkits/ritekit) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ritekit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ritekit` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ritekit` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ritekit operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ritekit task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ritekit"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ritekit-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ritekit` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/rkvst-automation/SKILL.md b/rkvst-automation/SKILL.md new file mode 100644 index 0000000..6d3efde --- /dev/null +++ b/rkvst-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: rkvst-automation +description: "Automate Rkvst tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Rkvst Automation via Rube MCP + +Automate Rkvst operations through Composio's Rkvst toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/rkvst](https://composio.dev/toolkits/rkvst) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Rkvst connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rkvst` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rkvst` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Rkvst operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Rkvst task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["rkvst"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Rkvst-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `rkvst` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/rocketlane-automation/SKILL.md b/rocketlane-automation/SKILL.md new file mode 100644 index 0000000..152d782 --- /dev/null +++ b/rocketlane-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: rocketlane-automation +description: "Automate Rocketlane tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Rocketlane Automation via Rube MCP + +Automate Rocketlane operations through Composio's Rocketlane toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/rocketlane](https://composio.dev/toolkits/rocketlane) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Rocketlane connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rocketlane` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rocketlane` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Rocketlane operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Rocketlane task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["rocketlane"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Rocketlane-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `rocketlane` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/rootly-automation/SKILL.md b/rootly-automation/SKILL.md new file mode 100644 index 0000000..6b788e9 --- /dev/null +++ b/rootly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: rootly-automation +description: "Automate Rootly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Rootly Automation via Rube MCP + +Automate Rootly operations through Composio's Rootly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/rootly](https://composio.dev/toolkits/rootly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Rootly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rootly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rootly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Rootly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Rootly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["rootly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Rootly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `rootly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/rosette-text-analytics-automation/SKILL.md b/rosette-text-analytics-automation/SKILL.md new file mode 100644 index 0000000..6760530 --- /dev/null +++ b/rosette-text-analytics-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: rosette-text-analytics-automation +description: "Automate Rosette Text Analytics tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Rosette Text Analytics Automation via Rube MCP + +Automate Rosette Text Analytics operations through Composio's Rosette Text Analytics toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/rosette_text_analytics](https://composio.dev/toolkits/rosette_text_analytics) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Rosette Text Analytics connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rosette_text_analytics` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rosette_text_analytics` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Rosette Text Analytics operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Rosette Text Analytics task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["rosette_text_analytics"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Rosette Text Analytics-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `rosette_text_analytics` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/route4me-automation/SKILL.md b/route4me-automation/SKILL.md new file mode 100644 index 0000000..e3a6666 --- /dev/null +++ b/route4me-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: route4me-automation +description: "Automate Route4me tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Route4me Automation via Rube MCP + +Automate Route4me operations through Composio's Route4me toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/route4me](https://composio.dev/toolkits/route4me) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Route4me connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `route4me` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `route4me` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Route4me operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Route4me task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["route4me"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Route4me-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `route4me` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/safetyculture-automation/SKILL.md b/safetyculture-automation/SKILL.md new file mode 100644 index 0000000..0686c36 --- /dev/null +++ b/safetyculture-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: safetyculture-automation +description: "Automate Safetyculture tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Safetyculture Automation via Rube MCP + +Automate Safetyculture operations through Composio's Safetyculture toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/safetyculture](https://composio.dev/toolkits/safetyculture) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Safetyculture connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `safetyculture` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `safetyculture` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Safetyculture operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Safetyculture task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["safetyculture"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Safetyculture-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `safetyculture` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sage-automation/SKILL.md b/sage-automation/SKILL.md new file mode 100644 index 0000000..dbd475a --- /dev/null +++ b/sage-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sage-automation +description: "Automate Sage tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sage Automation via Rube MCP + +Automate Sage operations through Composio's Sage toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sage](https://composio.dev/toolkits/sage) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sage connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sage` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sage` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sage operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sage task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sage"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sage-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sage` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/salesforce-automation/SKILL.md b/salesforce-automation/SKILL.md index 1fd9fbf..4697bf4 100644 --- a/salesforce-automation/SKILL.md +++ b/salesforce-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Salesforce CRM operations through Composio's Salesforce toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/salesforce](https://composio.dev/toolkits/salesforce) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -188,3 +190,6 @@ SELECT Id, Name FROM Opportunity WHERE CloseDate = NEXT_MONTH | Custom objects | SALESFORCE_GET_ALL_CUSTOM_OBJECTS | (none) | | Create record | SALESFORCE_CREATE_A_RECORD | object_type, fields | | Transfer ownership | SALESFORCE_MASS_TRANSFER_OWNERSHIP | records, new_owner | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/salesforce-marketing-cloud-automation/SKILL.md b/salesforce-marketing-cloud-automation/SKILL.md new file mode 100644 index 0000000..b59cadc --- /dev/null +++ b/salesforce-marketing-cloud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: salesforce-marketing-cloud-automation +description: "Automate Salesforce Marketing Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Salesforce Marketing Cloud Automation via Rube MCP + +Automate Salesforce Marketing Cloud operations through Composio's Salesforce Marketing Cloud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/salesforce_marketing_cloud](https://composio.dev/toolkits/salesforce_marketing_cloud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Salesforce Marketing Cloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_marketing_cloud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_marketing_cloud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Salesforce Marketing Cloud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Salesforce Marketing Cloud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["salesforce_marketing_cloud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Salesforce Marketing Cloud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_marketing_cloud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/salesforce-service-cloud-automation/SKILL.md b/salesforce-service-cloud-automation/SKILL.md new file mode 100644 index 0000000..63cd666 --- /dev/null +++ b/salesforce-service-cloud-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: salesforce-service-cloud-automation +description: "Automate Salesforce Service Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Salesforce Service Cloud Automation via Rube MCP + +Automate Salesforce Service Cloud operations through Composio's Salesforce Service Cloud toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/salesforce_service_cloud](https://composio.dev/toolkits/salesforce_service_cloud) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Salesforce Service Cloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_service_cloud` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_service_cloud` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Salesforce Service Cloud operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Salesforce Service Cloud task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["salesforce_service_cloud"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Salesforce Service Cloud-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_service_cloud` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/salesmate-automation/SKILL.md b/salesmate-automation/SKILL.md new file mode 100644 index 0000000..0b647f0 --- /dev/null +++ b/salesmate-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: salesmate-automation +description: "Automate Salesmate tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Salesmate Automation via Rube MCP + +Automate Salesmate operations through Composio's Salesmate toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/salesmate](https://composio.dev/toolkits/salesmate) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Salesmate connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `salesmate` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `salesmate` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Salesmate operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Salesmate task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["salesmate"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Salesmate-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `salesmate` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sap-successfactors-automation/SKILL.md b/sap-successfactors-automation/SKILL.md new file mode 100644 index 0000000..6725b25 --- /dev/null +++ b/sap-successfactors-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sap-successfactors-automation +description: "Automate SAP SuccessFactors tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SAP SuccessFactors Automation via Rube MCP + +Automate SAP SuccessFactors operations through Composio's SAP SuccessFactors toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sap_successfactors](https://composio.dev/toolkits/sap_successfactors) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SAP SuccessFactors connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sap_successfactors` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sap_successfactors` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "SAP SuccessFactors operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific SAP SuccessFactors task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sap_successfactors"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SAP SuccessFactors-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sap_successfactors` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/satismeter-automation/SKILL.md b/satismeter-automation/SKILL.md new file mode 100644 index 0000000..8d68ef5 --- /dev/null +++ b/satismeter-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: satismeter-automation +description: "Automate Satismeter tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Satismeter Automation via Rube MCP + +Automate Satismeter operations through Composio's Satismeter toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/satismeter](https://composio.dev/toolkits/satismeter) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Satismeter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `satismeter` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `satismeter` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Satismeter operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Satismeter task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["satismeter"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Satismeter-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `satismeter` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/scrape-do-automation/SKILL.md b/scrape-do-automation/SKILL.md new file mode 100644 index 0000000..4cc6309 --- /dev/null +++ b/scrape-do-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: scrape-do-automation +description: "Automate Scrape Do tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Scrape Do Automation via Rube MCP + +Automate Scrape Do operations through Composio's Scrape Do toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/scrape_do](https://composio.dev/toolkits/scrape_do) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Scrape Do connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `scrape_do` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `scrape_do` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Scrape Do operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Scrape Do task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["scrape_do"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Scrape Do-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `scrape_do` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/scrapegraph-ai-automation/SKILL.md b/scrapegraph-ai-automation/SKILL.md new file mode 100644 index 0000000..8b515d2 --- /dev/null +++ b/scrapegraph-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: scrapegraph-ai-automation +description: "Automate Scrapegraph AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Scrapegraph AI Automation via Rube MCP + +Automate Scrapegraph AI operations through Composio's Scrapegraph AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/scrapegraph_ai](https://composio.dev/toolkits/scrapegraph_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Scrapegraph AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapegraph_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapegraph_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Scrapegraph AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Scrapegraph AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["scrapegraph_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Scrapegraph AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapegraph_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/scrapfly-automation/SKILL.md b/scrapfly-automation/SKILL.md new file mode 100644 index 0000000..fb9f40a --- /dev/null +++ b/scrapfly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: scrapfly-automation +description: "Automate Scrapfly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Scrapfly Automation via Rube MCP + +Automate Scrapfly operations through Composio's Scrapfly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/scrapfly](https://composio.dev/toolkits/scrapfly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Scrapfly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapfly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapfly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Scrapfly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Scrapfly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["scrapfly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Scrapfly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapfly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/scrapingant-automation/SKILL.md b/scrapingant-automation/SKILL.md new file mode 100644 index 0000000..19c6e35 --- /dev/null +++ b/scrapingant-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: scrapingant-automation +description: "Automate Scrapingant tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Scrapingant Automation via Rube MCP + +Automate Scrapingant operations through Composio's Scrapingant toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/scrapingant](https://composio.dev/toolkits/scrapingant) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Scrapingant connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapingant` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapingant` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Scrapingant operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Scrapingant task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["scrapingant"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Scrapingant-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapingant` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/scrapingbee-automation/SKILL.md b/scrapingbee-automation/SKILL.md new file mode 100644 index 0000000..41bd749 --- /dev/null +++ b/scrapingbee-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: scrapingbee-automation +description: "Automate Scrapingbee tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Scrapingbee Automation via Rube MCP + +Automate Scrapingbee operations through Composio's Scrapingbee toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/scrapingbee](https://composio.dev/toolkits/scrapingbee) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Scrapingbee connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapingbee` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapingbee` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Scrapingbee operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Scrapingbee task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["scrapingbee"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Scrapingbee-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `scrapingbee` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/screenshot-fyi-automation/SKILL.md b/screenshot-fyi-automation/SKILL.md new file mode 100644 index 0000000..c20663d --- /dev/null +++ b/screenshot-fyi-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: screenshot-fyi-automation +description: "Automate Screenshot Fyi tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Screenshot Fyi Automation via Rube MCP + +Automate Screenshot Fyi operations through Composio's Screenshot Fyi toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/screenshot_fyi](https://composio.dev/toolkits/screenshot_fyi) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Screenshot Fyi connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `screenshot_fyi` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `screenshot_fyi` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Screenshot Fyi operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Screenshot Fyi task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["screenshot_fyi"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Screenshot Fyi-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `screenshot_fyi` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/screenshotone-automation/SKILL.md b/screenshotone-automation/SKILL.md new file mode 100644 index 0000000..a9f30b6 --- /dev/null +++ b/screenshotone-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: screenshotone-automation +description: "Automate Screenshotone tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Screenshotone Automation via Rube MCP + +Automate Screenshotone operations through Composio's Screenshotone toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/screenshotone](https://composio.dev/toolkits/screenshotone) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Screenshotone connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `screenshotone` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `screenshotone` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Screenshotone operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Screenshotone task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["screenshotone"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Screenshotone-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `screenshotone` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/seat-geek-automation/SKILL.md b/seat-geek-automation/SKILL.md new file mode 100644 index 0000000..9334728 --- /dev/null +++ b/seat-geek-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: seat-geek-automation +description: "Automate Seat Geek tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Seat Geek Automation via Rube MCP + +Automate Seat Geek operations through Composio's Seat Geek toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/seat_geek](https://composio.dev/toolkits/seat_geek) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Seat Geek connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `seat_geek` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `seat_geek` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Seat Geek operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Seat Geek task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["seat_geek"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Seat Geek-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `seat_geek` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/securitytrails-automation/SKILL.md b/securitytrails-automation/SKILL.md new file mode 100644 index 0000000..d3fb003 --- /dev/null +++ b/securitytrails-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: securitytrails-automation +description: "Automate Securitytrails tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Securitytrails Automation via Rube MCP + +Automate Securitytrails operations through Composio's Securitytrails toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/securitytrails](https://composio.dev/toolkits/securitytrails) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Securitytrails connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `securitytrails` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `securitytrails` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Securitytrails operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Securitytrails task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["securitytrails"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Securitytrails-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `securitytrails` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/segment-automation/SKILL.md b/segment-automation/SKILL.md index 1b5bb19..9313dcc 100644 --- a/segment-automation/SKILL.md +++ b/segment-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/segment](https://composio.dev/toolkits/segment) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -223,3 +225,6 @@ Segment recommends consistent event naming: | Source schema | SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE | sourceId | | Update source | SEGMENT_UPDATE_SOURCE | sourceId | | Warehouses | SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE | sourceId | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/segmetrics-automation/SKILL.md b/segmetrics-automation/SKILL.md new file mode 100644 index 0000000..330425f --- /dev/null +++ b/segmetrics-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: segmetrics-automation +description: "Automate Segmetrics tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Segmetrics Automation via Rube MCP + +Automate Segmetrics operations through Composio's Segmetrics toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/segmetrics](https://composio.dev/toolkits/segmetrics) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Segmetrics connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segmetrics` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `segmetrics` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Segmetrics operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Segmetrics task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["segmetrics"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Segmetrics-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `segmetrics` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/seismic-automation/SKILL.md b/seismic-automation/SKILL.md new file mode 100644 index 0000000..17960d4 --- /dev/null +++ b/seismic-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: seismic-automation +description: "Automate Seismic tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Seismic Automation via Rube MCP + +Automate Seismic operations through Composio's Seismic toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/seismic](https://composio.dev/toolkits/seismic) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Seismic connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `seismic` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `seismic` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Seismic operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Seismic task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["seismic"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Seismic-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `seismic` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/semanticscholar-automation/SKILL.md b/semanticscholar-automation/SKILL.md new file mode 100644 index 0000000..33a2146 --- /dev/null +++ b/semanticscholar-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: semanticscholar-automation +description: "Automate Semanticscholar tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Semanticscholar Automation via Rube MCP + +Automate Semanticscholar operations through Composio's Semanticscholar toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/semanticscholar](https://composio.dev/toolkits/semanticscholar) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Semanticscholar connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `semanticscholar` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `semanticscholar` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Semanticscholar operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Semanticscholar task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["semanticscholar"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Semanticscholar-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `semanticscholar` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/semrush-automation/SKILL.md b/semrush-automation/SKILL.md new file mode 100644 index 0000000..e334515 --- /dev/null +++ b/semrush-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: semrush-automation +description: "Automate Semrush tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Semrush Automation via Rube MCP + +Automate Semrush operations through Composio's Semrush toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/semrush](https://composio.dev/toolkits/semrush) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Semrush connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `semrush` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `semrush` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Semrush operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Semrush task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["semrush"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Semrush-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `semrush` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sendbird-ai-chabot-automation/SKILL.md b/sendbird-ai-chabot-automation/SKILL.md new file mode 100644 index 0000000..bbc0bf0 --- /dev/null +++ b/sendbird-ai-chabot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sendbird-ai-chabot-automation +description: "Automate Sendbird AI Chabot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sendbird AI Chabot Automation via Rube MCP + +Automate Sendbird AI Chabot operations through Composio's Sendbird AI Chabot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sendbird_ai_chabot](https://composio.dev/toolkits/sendbird_ai_chabot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sendbird AI Chabot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendbird_ai_chabot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendbird_ai_chabot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sendbird AI Chabot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sendbird AI Chabot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sendbird_ai_chabot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sendbird AI Chabot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sendbird_ai_chabot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sendbird-automation/SKILL.md b/sendbird-automation/SKILL.md new file mode 100644 index 0000000..dfa3857 --- /dev/null +++ b/sendbird-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sendbird-automation +description: "Automate Sendbird tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sendbird Automation via Rube MCP + +Automate Sendbird operations through Composio's Sendbird toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sendbird](https://composio.dev/toolkits/sendbird) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sendbird connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendbird` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendbird` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sendbird operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sendbird task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sendbird"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sendbird-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sendbird` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sendfox-automation/SKILL.md b/sendfox-automation/SKILL.md new file mode 100644 index 0000000..d2faee3 --- /dev/null +++ b/sendfox-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sendfox-automation +description: "Automate Sendfox tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sendfox Automation via Rube MCP + +Automate Sendfox operations through Composio's Sendfox toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sendfox](https://composio.dev/toolkits/sendfox) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sendfox connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendfox` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendfox` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sendfox operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sendfox task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sendfox"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sendfox-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sendfox` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sendgrid-automation/SKILL.md b/sendgrid-automation/SKILL.md index 4b59f12..37f1cdc 100644 --- a/sendgrid-automation/SKILL.md +++ b/sendgrid-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate SendGrid email delivery workflows including marketing campaigns (Single Sends), contact and list management, sender identity setup, and email analytics through Composio's SendGrid toolkit. +**Toolkit docs**: [composio.dev/toolkits/sendgrid](https://composio.dev/toolkits/sendgrid) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -226,3 +228,6 @@ Contact operations (`ADD_OR_UPDATE_A_CONTACT`, `IMPORT_CONTACTS`) are asynchrono | Suppression groups | `SENDGRID_GET_SUPPRESSION_GROUPS` | (none) | | Get template | `SENDGRID_RETRIEVE_A_SINGLE_TRANSACTIONAL_TEMPLATE` | `template_id` | | Duplicate template | `SENDGRID_DUPLICATE_A_TRANSACTIONAL_TEMPLATE` | `template_id`, `name` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sendlane-automation/SKILL.md b/sendlane-automation/SKILL.md new file mode 100644 index 0000000..2948a01 --- /dev/null +++ b/sendlane-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sendlane-automation +description: "Automate Sendlane tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sendlane Automation via Rube MCP + +Automate Sendlane operations through Composio's Sendlane toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sendlane](https://composio.dev/toolkits/sendlane) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sendlane connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendlane` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendlane` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sendlane operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sendlane task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sendlane"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sendlane-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sendlane` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sendloop-automation/SKILL.md b/sendloop-automation/SKILL.md new file mode 100644 index 0000000..6dc607e --- /dev/null +++ b/sendloop-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sendloop-automation +description: "Automate Sendloop tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sendloop Automation via Rube MCP + +Automate Sendloop operations through Composio's Sendloop toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sendloop](https://composio.dev/toolkits/sendloop) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sendloop connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendloop` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendloop` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sendloop operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sendloop task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sendloop"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sendloop-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sendloop` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sendspark-automation/SKILL.md b/sendspark-automation/SKILL.md new file mode 100644 index 0000000..6235ae5 --- /dev/null +++ b/sendspark-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sendspark-automation +description: "Automate Sendspark tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sendspark Automation via Rube MCP + +Automate Sendspark operations through Composio's Sendspark toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sendspark](https://composio.dev/toolkits/sendspark) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sendspark connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendspark` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendspark` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sendspark operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sendspark task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sendspark"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sendspark-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sendspark` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sensibo-automation/SKILL.md b/sensibo-automation/SKILL.md new file mode 100644 index 0000000..245dac6 --- /dev/null +++ b/sensibo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sensibo-automation +description: "Automate Sensibo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sensibo Automation via Rube MCP + +Automate Sensibo operations through Composio's Sensibo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sensibo](https://composio.dev/toolkits/sensibo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sensibo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sensibo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sensibo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sensibo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sensibo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sensibo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sensibo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sensibo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sentry-automation/SKILL.md b/sentry-automation/SKILL.md index ce12eec..0f5da0e 100644 --- a/sentry-automation/SKILL.md +++ b/sentry-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/sentry](https://composio.dev/toolkits/sentry) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -230,3 +232,6 @@ Automate Sentry error tracking and monitoring operations through Composio's Sent | Deploy release | SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG | organization_id_or_slug, version | | List releases | SENTRY_LIST_ORGANIZATION_RELEASES | organization_id_or_slug | | Update monitor | SENTRY_UPDATE_A_MONITOR | organization_id_or_slug, monitor_id_or_slug | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/seqera-automation/SKILL.md b/seqera-automation/SKILL.md new file mode 100644 index 0000000..017c00e --- /dev/null +++ b/seqera-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: seqera-automation +description: "Automate Seqera tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Seqera Automation via Rube MCP + +Automate Seqera operations through Composio's Seqera toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/seqera](https://composio.dev/toolkits/seqera) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Seqera connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `seqera` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `seqera` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Seqera operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Seqera task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["seqera"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Seqera-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `seqera` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/serpapi-automation/SKILL.md b/serpapi-automation/SKILL.md new file mode 100644 index 0000000..42ca790 --- /dev/null +++ b/serpapi-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: serpapi-automation +description: "Automate Serpapi tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Serpapi Automation via Rube MCP + +Automate Serpapi operations through Composio's Serpapi toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/serpapi](https://composio.dev/toolkits/serpapi) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Serpapi connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `serpapi` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `serpapi` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Serpapi operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Serpapi task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["serpapi"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Serpapi-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `serpapi` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/serpdog-automation/SKILL.md b/serpdog-automation/SKILL.md new file mode 100644 index 0000000..25ad2b1 --- /dev/null +++ b/serpdog-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: serpdog-automation +description: "Automate Serpdog tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Serpdog Automation via Rube MCP + +Automate Serpdog operations through Composio's Serpdog toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/serpdog](https://composio.dev/toolkits/serpdog) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Serpdog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `serpdog` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `serpdog` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Serpdog operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Serpdog task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["serpdog"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Serpdog-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `serpdog` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/serply-automation/SKILL.md b/serply-automation/SKILL.md new file mode 100644 index 0000000..c5b4cd4 --- /dev/null +++ b/serply-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: serply-automation +description: "Automate Serply tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Serply Automation via Rube MCP + +Automate Serply operations through Composio's Serply toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/serply](https://composio.dev/toolkits/serply) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Serply connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `serply` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `serply` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Serply operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Serply task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["serply"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Serply-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `serply` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/servicem8-automation/SKILL.md b/servicem8-automation/SKILL.md new file mode 100644 index 0000000..6175ee0 --- /dev/null +++ b/servicem8-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: servicem8-automation +description: "Automate Servicem8 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Servicem8 Automation via Rube MCP + +Automate Servicem8 operations through Composio's Servicem8 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/servicem8](https://composio.dev/toolkits/servicem8) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Servicem8 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `servicem8` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `servicem8` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Servicem8 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Servicem8 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["servicem8"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Servicem8-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `servicem8` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sevdesk-automation/SKILL.md b/sevdesk-automation/SKILL.md new file mode 100644 index 0000000..d322199 --- /dev/null +++ b/sevdesk-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sevdesk-automation +description: "Automate Sevdesk tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sevdesk Automation via Rube MCP + +Automate Sevdesk operations through Composio's Sevdesk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sevdesk](https://composio.dev/toolkits/sevdesk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sevdesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sevdesk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sevdesk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sevdesk operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sevdesk task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sevdesk"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sevdesk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sevdesk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/share-point-automation/SKILL.md b/share-point-automation/SKILL.md new file mode 100644 index 0000000..dfa6066 --- /dev/null +++ b/share-point-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: share-point-automation +description: "Automate SharePoint tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SharePoint Automation via Rube MCP + +Automate SharePoint operations through Composio's SharePoint toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/share_point](https://composio.dev/toolkits/share_point) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SharePoint connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `share_point` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `share_point` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "SharePoint operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific SharePoint task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["share_point"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SharePoint-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `share_point` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/share_point-automation/SKILL.md b/share_point-automation/SKILL.md new file mode 100644 index 0000000..8bdfaf0 --- /dev/null +++ b/share_point-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: share_point-automation +description: "Automate SharePoint tasks via Rube MCP (Composio): document libraries, sites, lists, and content management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SharePoint Automation via Rube MCP + +Automate SharePoint operations through Composio's SharePoint toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/share_point](https://composio.dev/toolkits/share_point) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SharePoint connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `share_point` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `share_point` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "document libraries, sites, lists, and content management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for SharePoint +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available SharePoint Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available SharePoint tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute SharePoint Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple SharePoint operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the SharePoint connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SharePoint-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `share_point` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/share_point](https://composio.dev/toolkits/share_point) diff --git a/shipengine-automation/SKILL.md b/shipengine-automation/SKILL.md new file mode 100644 index 0000000..83023d6 --- /dev/null +++ b/shipengine-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: shipengine-automation +description: "Automate Shipengine tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Shipengine Automation via Rube MCP + +Automate Shipengine operations through Composio's Shipengine toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/shipengine](https://composio.dev/toolkits/shipengine) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Shipengine connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `shipengine` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `shipengine` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Shipengine operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Shipengine task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["shipengine"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Shipengine-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `shipengine` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/shopify-automation/SKILL.md b/shopify-automation/SKILL.md index 882206f..1f4f0be 100644 --- a/shopify-automation/SKILL.md +++ b/shopify-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Shopify operations through Composio's Shopify toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/shopify](https://composio.dev/toolkits/shopify) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -166,3 +168,6 @@ For advanced operations: | Fulfillment | SHOPIFY_GET_FULFILLMENT | order_id, fulfillment_id | | GraphQL | SHOPIFY_GRAPH_QL_QUERY | query | | Bulk query | SHOPIFY_BULK_QUERY_OPERATION | query | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/short-io-automation/SKILL.md b/short-io-automation/SKILL.md new file mode 100644 index 0000000..e68178f --- /dev/null +++ b/short-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: short-io-automation +description: "Automate Short IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Short IO Automation via Rube MCP + +Automate Short IO operations through Composio's Short IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/short_io](https://composio.dev/toolkits/short_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Short IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `short_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `short_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Short IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Short IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["short_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Short IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `short_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/short-menu-automation/SKILL.md b/short-menu-automation/SKILL.md new file mode 100644 index 0000000..dfe4db6 --- /dev/null +++ b/short-menu-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: short-menu-automation +description: "Automate Short Menu tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Short Menu Automation via Rube MCP + +Automate Short Menu operations through Composio's Short Menu toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/short_menu](https://composio.dev/toolkits/short_menu) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Short Menu connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `short_menu` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `short_menu` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Short Menu operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Short Menu task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["short_menu"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Short Menu-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `short_menu` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/shortcut-automation/SKILL.md b/shortcut-automation/SKILL.md new file mode 100644 index 0000000..536acba --- /dev/null +++ b/shortcut-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: shortcut-automation +description: "Automate Shortcut tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Shortcut Automation via Rube MCP + +Automate Shortcut operations through Composio's Shortcut toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/shortcut](https://composio.dev/toolkits/shortcut) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Shortcut connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `shortcut` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `shortcut` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Shortcut operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Shortcut task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["shortcut"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Shortcut-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `shortcut` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/shorten-rest-automation/SKILL.md b/shorten-rest-automation/SKILL.md new file mode 100644 index 0000000..7e8704a --- /dev/null +++ b/shorten-rest-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: shorten-rest-automation +description: "Automate Shorten Rest tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Shorten Rest Automation via Rube MCP + +Automate Shorten Rest operations through Composio's Shorten Rest toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/shorten_rest](https://composio.dev/toolkits/shorten_rest) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Shorten Rest connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `shorten_rest` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `shorten_rest` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Shorten Rest operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Shorten Rest task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["shorten_rest"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Shorten Rest-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `shorten_rest` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/shortpixel-automation/SKILL.md b/shortpixel-automation/SKILL.md new file mode 100644 index 0000000..c412ed0 --- /dev/null +++ b/shortpixel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: shortpixel-automation +description: "Automate Shortpixel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Shortpixel Automation via Rube MCP + +Automate Shortpixel operations through Composio's Shortpixel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/shortpixel](https://composio.dev/toolkits/shortpixel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Shortpixel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `shortpixel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `shortpixel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Shortpixel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Shortpixel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["shortpixel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Shortpixel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `shortpixel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/shotstack-automation/SKILL.md b/shotstack-automation/SKILL.md new file mode 100644 index 0000000..1a97425 --- /dev/null +++ b/shotstack-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: shotstack-automation +description: "Automate Shotstack tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Shotstack Automation via Rube MCP + +Automate Shotstack operations through Composio's Shotstack toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/shotstack](https://composio.dev/toolkits/shotstack) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Shotstack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `shotstack` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `shotstack` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Shotstack operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Shotstack task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["shotstack"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Shotstack-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `shotstack` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sidetracker-automation/SKILL.md b/sidetracker-automation/SKILL.md new file mode 100644 index 0000000..b67fd47 --- /dev/null +++ b/sidetracker-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sidetracker-automation +description: "Automate Sidetracker tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sidetracker Automation via Rube MCP + +Automate Sidetracker operations through Composio's Sidetracker toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sidetracker](https://composio.dev/toolkits/sidetracker) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sidetracker connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sidetracker` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sidetracker` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sidetracker operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sidetracker task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sidetracker"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sidetracker-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sidetracker` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/signaturely-automation/SKILL.md b/signaturely-automation/SKILL.md new file mode 100644 index 0000000..c7fa834 --- /dev/null +++ b/signaturely-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: signaturely-automation +description: "Automate Signaturely tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Signaturely Automation via Rube MCP + +Automate Signaturely operations through Composio's Signaturely toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/signaturely](https://composio.dev/toolkits/signaturely) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Signaturely connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `signaturely` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `signaturely` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Signaturely operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Signaturely task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["signaturely"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Signaturely-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `signaturely` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/signpath-automation/SKILL.md b/signpath-automation/SKILL.md new file mode 100644 index 0000000..f604fa2 --- /dev/null +++ b/signpath-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: signpath-automation +description: "Automate Signpath tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Signpath Automation via Rube MCP + +Automate Signpath operations through Composio's Signpath toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/signpath](https://composio.dev/toolkits/signpath) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Signpath connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `signpath` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `signpath` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Signpath operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Signpath task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["signpath"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Signpath-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `signpath` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/signwell-automation/SKILL.md b/signwell-automation/SKILL.md new file mode 100644 index 0000000..6047758 --- /dev/null +++ b/signwell-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: signwell-automation +description: "Automate Signwell tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Signwell Automation via Rube MCP + +Automate Signwell operations through Composio's Signwell toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/signwell](https://composio.dev/toolkits/signwell) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Signwell connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `signwell` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `signwell` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Signwell operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Signwell task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["signwell"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Signwell-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `signwell` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/similarweb-digitalrank-api-automation/SKILL.md b/similarweb-digitalrank-api-automation/SKILL.md new file mode 100644 index 0000000..b24516d --- /dev/null +++ b/similarweb-digitalrank-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: similarweb-digitalrank-api-automation +description: "Automate SimilarWeb tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SimilarWeb Automation via Rube MCP + +Automate SimilarWeb operations through Composio's SimilarWeb toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/similarweb_digitalrank_api](https://composio.dev/toolkits/similarweb_digitalrank_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SimilarWeb connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `similarweb_digitalrank_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `similarweb_digitalrank_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "SimilarWeb operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific SimilarWeb task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["similarweb_digitalrank_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SimilarWeb-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `similarweb_digitalrank_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/similarweb_digitalrank_api-automation/SKILL.md b/similarweb_digitalrank_api-automation/SKILL.md new file mode 100644 index 0000000..2b18766 --- /dev/null +++ b/similarweb_digitalrank_api-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: similarweb_digitalrank_api-automation +description: "Automate SimilarWeb tasks via Rube MCP (Composio): website traffic, rankings, and digital market intelligence. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SimilarWeb Automation via Rube MCP + +Automate SimilarWeb operations through Composio's SimilarWeb toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/similarweb_digitalrank_api](https://composio.dev/toolkits/similarweb_digitalrank_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SimilarWeb connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `similarweb_digitalrank_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `similarweb_digitalrank_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "website traffic, rankings, and digital market intelligence", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for SimilarWeb +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available SimilarWeb Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available SimilarWeb tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute SimilarWeb Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple SimilarWeb operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the SimilarWeb connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SimilarWeb-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `similarweb_digitalrank_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/similarweb_digitalrank_api](https://composio.dev/toolkits/similarweb_digitalrank_api) diff --git a/simla-com-automation/SKILL.md b/simla-com-automation/SKILL.md new file mode 100644 index 0000000..de200b4 --- /dev/null +++ b/simla-com-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: simla-com-automation +description: "Automate Simla Com tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Simla Com Automation via Rube MCP + +Automate Simla Com operations through Composio's Simla Com toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/simla_com](https://composio.dev/toolkits/simla_com) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Simla Com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `simla_com` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `simla_com` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Simla Com operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Simla Com task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["simla_com"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Simla Com-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `simla_com` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/simple-analytics-automation/SKILL.md b/simple-analytics-automation/SKILL.md new file mode 100644 index 0000000..4fc29ba --- /dev/null +++ b/simple-analytics-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: simple-analytics-automation +description: "Automate Simple Analytics tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Simple Analytics Automation via Rube MCP + +Automate Simple Analytics operations through Composio's Simple Analytics toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/simple_analytics](https://composio.dev/toolkits/simple_analytics) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Simple Analytics connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `simple_analytics` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `simple_analytics` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Simple Analytics operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Simple Analytics task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["simple_analytics"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Simple Analytics-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `simple_analytics` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/simplesat-automation/SKILL.md b/simplesat-automation/SKILL.md new file mode 100644 index 0000000..ea3fa21 --- /dev/null +++ b/simplesat-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: simplesat-automation +description: "Automate Simplesat tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Simplesat Automation via Rube MCP + +Automate Simplesat operations through Composio's Simplesat toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/simplesat](https://composio.dev/toolkits/simplesat) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Simplesat connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `simplesat` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `simplesat` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Simplesat operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Simplesat task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["simplesat"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Simplesat-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `simplesat` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sitespeakai-automation/SKILL.md b/sitespeakai-automation/SKILL.md new file mode 100644 index 0000000..4469cf5 --- /dev/null +++ b/sitespeakai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sitespeakai-automation +description: "Automate Sitespeakai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sitespeakai Automation via Rube MCP + +Automate Sitespeakai operations through Composio's Sitespeakai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sitespeakai](https://composio.dev/toolkits/sitespeakai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sitespeakai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sitespeakai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sitespeakai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sitespeakai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sitespeakai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sitespeakai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sitespeakai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sitespeakai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/skyfire-automation/SKILL.md b/skyfire-automation/SKILL.md new file mode 100644 index 0000000..00f5f37 --- /dev/null +++ b/skyfire-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: skyfire-automation +description: "Automate Skyfire tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Skyfire Automation via Rube MCP + +Automate Skyfire operations through Composio's Skyfire toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/skyfire](https://composio.dev/toolkits/skyfire) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Skyfire connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `skyfire` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `skyfire` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Skyfire operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Skyfire task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["skyfire"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Skyfire-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `skyfire` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/slack-automation/SKILL.md b/slack-automation/SKILL.md index d41811a..b88c8fa 100644 --- a/slack-automation/SKILL.md +++ b/slack-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit. +**Toolkit docs**: [composio.dev/toolkits/slack](https://composio.dev/toolkits/slack) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -187,3 +189,6 @@ Most list endpoints use cursor-based pagination: | Get channel info | `SLACK_RETRIEVE_CONVERSATION_INFORMATION` | channel ID | | Channel history | `SLACK_FETCH_CONVERSATION_HISTORY` | `channel`, `oldest`, `latest` | | Workspace info | `SLACK_FETCH_TEAM_INFO` | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/slackbot-automation/SKILL.md b/slackbot-automation/SKILL.md new file mode 100644 index 0000000..9d46236 --- /dev/null +++ b/slackbot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: slackbot-automation +description: "Automate Slackbot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Slackbot Automation via Rube MCP + +Automate Slackbot operations through Composio's Slackbot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/slackbot](https://composio.dev/toolkits/slackbot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Slackbot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `slackbot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `slackbot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Slackbot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Slackbot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["slackbot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Slackbot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `slackbot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/smartproxy-automation/SKILL.md b/smartproxy-automation/SKILL.md new file mode 100644 index 0000000..286cf10 --- /dev/null +++ b/smartproxy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: smartproxy-automation +description: "Automate Smartproxy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Smartproxy Automation via Rube MCP + +Automate Smartproxy operations through Composio's Smartproxy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/smartproxy](https://composio.dev/toolkits/smartproxy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Smartproxy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `smartproxy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `smartproxy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Smartproxy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Smartproxy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["smartproxy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Smartproxy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `smartproxy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/smartrecruiters-automation/SKILL.md b/smartrecruiters-automation/SKILL.md new file mode 100644 index 0000000..0c190d2 --- /dev/null +++ b/smartrecruiters-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: smartrecruiters-automation +description: "Automate Smartrecruiters tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Smartrecruiters Automation via Rube MCP + +Automate Smartrecruiters operations through Composio's Smartrecruiters toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/smartrecruiters](https://composio.dev/toolkits/smartrecruiters) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Smartrecruiters connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `smartrecruiters` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `smartrecruiters` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Smartrecruiters operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Smartrecruiters task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["smartrecruiters"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Smartrecruiters-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `smartrecruiters` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sms-alert-automation/SKILL.md b/sms-alert-automation/SKILL.md new file mode 100644 index 0000000..4ef728d --- /dev/null +++ b/sms-alert-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sms-alert-automation +description: "Automate SMS Alert tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SMS Alert Automation via Rube MCP + +Automate SMS Alert operations through Composio's SMS Alert toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sms_alert](https://composio.dev/toolkits/sms_alert) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SMS Alert connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sms_alert` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sms_alert` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "SMS Alert operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific SMS Alert task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sms_alert"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SMS Alert-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sms_alert` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/smtp2go-automation/SKILL.md b/smtp2go-automation/SKILL.md new file mode 100644 index 0000000..42f4790 --- /dev/null +++ b/smtp2go-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: smtp2go-automation +description: "Automate Smtp2go tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Smtp2go Automation via Rube MCP + +Automate Smtp2go operations through Composio's Smtp2go toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/smtp2go](https://composio.dev/toolkits/smtp2go) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Smtp2go connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `smtp2go` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `smtp2go` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Smtp2go operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Smtp2go task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["smtp2go"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Smtp2go-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `smtp2go` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/smugmug-automation/SKILL.md b/smugmug-automation/SKILL.md new file mode 100644 index 0000000..565367e --- /dev/null +++ b/smugmug-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: smugmug-automation +description: "Automate Smugmug tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Smugmug Automation via Rube MCP + +Automate Smugmug operations through Composio's Smugmug toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/smugmug](https://composio.dev/toolkits/smugmug) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Smugmug connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `smugmug` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `smugmug` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Smugmug operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Smugmug task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["smugmug"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Smugmug-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `smugmug` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/snowflake-automation/SKILL.md b/snowflake-automation/SKILL.md new file mode 100644 index 0000000..91bb19d --- /dev/null +++ b/snowflake-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: snowflake-automation +description: "Automate Snowflake tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Snowflake Automation via Rube MCP + +Automate Snowflake operations through Composio's Snowflake toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/snowflake](https://composio.dev/toolkits/snowflake) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Snowflake connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `snowflake` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `snowflake` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Snowflake operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Snowflake task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["snowflake"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Snowflake-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `snowflake` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sourcegraph-automation/SKILL.md b/sourcegraph-automation/SKILL.md new file mode 100644 index 0000000..759531a --- /dev/null +++ b/sourcegraph-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sourcegraph-automation +description: "Automate Sourcegraph tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sourcegraph Automation via Rube MCP + +Automate Sourcegraph operations through Composio's Sourcegraph toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sourcegraph](https://composio.dev/toolkits/sourcegraph) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sourcegraph connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sourcegraph` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sourcegraph` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sourcegraph operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sourcegraph task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sourcegraph"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sourcegraph-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sourcegraph` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/splitwise-automation/SKILL.md b/splitwise-automation/SKILL.md new file mode 100644 index 0000000..aa2864d --- /dev/null +++ b/splitwise-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: splitwise-automation +description: "Automate Splitwise tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Splitwise Automation via Rube MCP + +Automate Splitwise operations through Composio's Splitwise toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/splitwise](https://composio.dev/toolkits/splitwise) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Splitwise connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `splitwise` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `splitwise` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Splitwise operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Splitwise task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["splitwise"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Splitwise-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `splitwise` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/spoki-automation/SKILL.md b/spoki-automation/SKILL.md new file mode 100644 index 0000000..775d800 --- /dev/null +++ b/spoki-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: spoki-automation +description: "Automate Spoki tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Spoki Automation via Rube MCP + +Automate Spoki operations through Composio's Spoki toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/spoki](https://composio.dev/toolkits/spoki) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Spoki connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `spoki` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `spoki` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Spoki operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Spoki task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["spoki"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Spoki-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `spoki` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/spondyr-automation/SKILL.md b/spondyr-automation/SKILL.md new file mode 100644 index 0000000..d658d7c --- /dev/null +++ b/spondyr-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: spondyr-automation +description: "Automate Spondyr tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Spondyr Automation via Rube MCP + +Automate Spondyr operations through Composio's Spondyr toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/spondyr](https://composio.dev/toolkits/spondyr) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Spondyr connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `spondyr` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `spondyr` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Spondyr operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Spondyr task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["spondyr"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Spondyr-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `spondyr` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/spotify-automation/SKILL.md b/spotify-automation/SKILL.md new file mode 100644 index 0000000..d248d0d --- /dev/null +++ b/spotify-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: spotify-automation +description: "Automate Spotify tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Spotify Automation via Rube MCP + +Automate Spotify operations through Composio's Spotify toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/spotify](https://composio.dev/toolkits/spotify) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Spotify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `spotify` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `spotify` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Spotify operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Spotify task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["spotify"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Spotify-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `spotify` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/spotlightr-automation/SKILL.md b/spotlightr-automation/SKILL.md new file mode 100644 index 0000000..aa3493c --- /dev/null +++ b/spotlightr-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: spotlightr-automation +description: "Automate Spotlightr tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Spotlightr Automation via Rube MCP + +Automate Spotlightr operations through Composio's Spotlightr toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/spotlightr](https://composio.dev/toolkits/spotlightr) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Spotlightr connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `spotlightr` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `spotlightr` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Spotlightr operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Spotlightr task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["spotlightr"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Spotlightr-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `spotlightr` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/square-automation/SKILL.md b/square-automation/SKILL.md index 6fd77f8..d50b36b 100644 --- a/square-automation/SKILL.md +++ b/square-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/square](https://composio.dev/toolkits/square) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -174,3 +176,6 @@ Automate Square payment processing, order management, and invoicing through Comp | List invoices | SQUARE_LIST_INVOICES | location_id, cursor | | Get invoice | SQUARE_GET_INVOICE | invoice_id | | Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sslmate-cert-spotter-api-automation/SKILL.md b/sslmate-cert-spotter-api-automation/SKILL.md new file mode 100644 index 0000000..1d6c548 --- /dev/null +++ b/sslmate-cert-spotter-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sslmate-cert-spotter-api-automation +description: "Automate Sslmate Cert Spotter API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sslmate Cert Spotter API Automation via Rube MCP + +Automate Sslmate Cert Spotter API operations through Composio's Sslmate Cert Spotter API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sslmate_cert_spotter_api](https://composio.dev/toolkits/sslmate_cert_spotter_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sslmate Cert Spotter API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sslmate_cert_spotter_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sslmate_cert_spotter_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sslmate Cert Spotter API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sslmate Cert Spotter API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sslmate_cert_spotter_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sslmate Cert Spotter API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sslmate_cert_spotter_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/stack-exchange-automation/SKILL.md b/stack-exchange-automation/SKILL.md new file mode 100644 index 0000000..2b6ff3b --- /dev/null +++ b/stack-exchange-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: stack-exchange-automation +description: "Automate Stack Exchange tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Stack Exchange Automation via Rube MCP + +Automate Stack Exchange operations through Composio's Stack Exchange toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/stack_exchange](https://composio.dev/toolkits/stack_exchange) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Stack Exchange connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `stack_exchange` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `stack_exchange` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Stack Exchange operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Stack Exchange task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["stack_exchange"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Stack Exchange-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `stack_exchange` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/stannp-automation/SKILL.md b/stannp-automation/SKILL.md new file mode 100644 index 0000000..0f3bb69 --- /dev/null +++ b/stannp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: stannp-automation +description: "Automate Stannp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Stannp Automation via Rube MCP + +Automate Stannp operations through Composio's Stannp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/stannp](https://composio.dev/toolkits/stannp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Stannp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `stannp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `stannp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Stannp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Stannp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["stannp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Stannp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `stannp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/starton-automation/SKILL.md b/starton-automation/SKILL.md new file mode 100644 index 0000000..2661f6e --- /dev/null +++ b/starton-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: starton-automation +description: "Automate Starton tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Starton Automation via Rube MCP + +Automate Starton operations through Composio's Starton toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/starton](https://composio.dev/toolkits/starton) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Starton connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `starton` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `starton` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Starton operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Starton task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["starton"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Starton-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `starton` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/statuscake-automation/SKILL.md b/statuscake-automation/SKILL.md new file mode 100644 index 0000000..c22aca1 --- /dev/null +++ b/statuscake-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: statuscake-automation +description: "Automate Statuscake tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Statuscake Automation via Rube MCP + +Automate Statuscake operations through Composio's Statuscake toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/statuscake](https://composio.dev/toolkits/statuscake) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Statuscake connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `statuscake` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `statuscake` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Statuscake operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Statuscake task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["statuscake"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Statuscake-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `statuscake` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/storeganise-automation/SKILL.md b/storeganise-automation/SKILL.md new file mode 100644 index 0000000..a4a09aa --- /dev/null +++ b/storeganise-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: storeganise-automation +description: "Automate Storeganise tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Storeganise Automation via Rube MCP + +Automate Storeganise operations through Composio's Storeganise toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/storeganise](https://composio.dev/toolkits/storeganise) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Storeganise connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `storeganise` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `storeganise` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Storeganise operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Storeganise task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["storeganise"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Storeganise-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `storeganise` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/storerocket-automation/SKILL.md b/storerocket-automation/SKILL.md new file mode 100644 index 0000000..b0b7238 --- /dev/null +++ b/storerocket-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: storerocket-automation +description: "Automate Storerocket tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Storerocket Automation via Rube MCP + +Automate Storerocket operations through Composio's Storerocket toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/storerocket](https://composio.dev/toolkits/storerocket) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Storerocket connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `storerocket` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `storerocket` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Storerocket operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Storerocket task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["storerocket"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Storerocket-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `storerocket` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/stormglass-io-automation/SKILL.md b/stormglass-io-automation/SKILL.md new file mode 100644 index 0000000..66dbe43 --- /dev/null +++ b/stormglass-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: stormglass-io-automation +description: "Automate Stormglass IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Stormglass IO Automation via Rube MCP + +Automate Stormglass IO operations through Composio's Stormglass IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/stormglass_io](https://composio.dev/toolkits/stormglass_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Stormglass IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `stormglass_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `stormglass_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Stormglass IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Stormglass IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["stormglass_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Stormglass IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `stormglass_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/strava-automation/SKILL.md b/strava-automation/SKILL.md new file mode 100644 index 0000000..777656b --- /dev/null +++ b/strava-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: strava-automation +description: "Automate Strava tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Strava Automation via Rube MCP + +Automate Strava operations through Composio's Strava toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/strava](https://composio.dev/toolkits/strava) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Strava connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `strava` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `strava` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Strava operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Strava task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["strava"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Strava-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `strava` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/streamtime-automation/SKILL.md b/streamtime-automation/SKILL.md new file mode 100644 index 0000000..b33ede3 --- /dev/null +++ b/streamtime-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: streamtime-automation +description: "Automate Streamtime tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Streamtime Automation via Rube MCP + +Automate Streamtime operations through Composio's Streamtime toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/streamtime](https://composio.dev/toolkits/streamtime) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Streamtime connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `streamtime` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `streamtime` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Streamtime operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Streamtime task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["streamtime"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Streamtime-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `streamtime` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/stripe-automation/SKILL.md b/stripe-automation/SKILL.md index 8128b6a..bed6392 100644 --- a/stripe-automation/SKILL.md +++ b/stripe-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Stripe payment operations through Composio's Stripe toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/stripe](https://composio.dev/toolkits/stripe) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -196,3 +198,6 @@ Stripe uses smallest currency unit: | Payment methods | STRIPE_LIST_CUSTOMER_PAYMENT_METHODS | customer | | Checkout session | STRIPE_CREATE_CHECKOUT_SESSION | line_items | | List payment intents | STRIPE_LIST_PAYMENT_INTENTS | customer | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/supabase-automation/SKILL.md b/supabase-automation/SKILL.md index 6248776..1934423 100644 --- a/supabase-automation/SKILL.md +++ b/supabase-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Supabase operations including database queries, table schema inspection, SQL execution, project and organization management, storage buckets, edge functions, and service health monitoring through Composio's Supabase toolkit. +**Toolkit docs**: [composio.dev/toolkits/supabase](https://composio.dev/toolkits/supabase) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -234,3 +236,6 @@ Automate Supabase operations including database queries, table schema inspection | Get edge function | `SUPABASE_RETRIEVE_A_FUNCTION` | `ref`, function slug | | List storage buckets | `SUPABASE_LISTS_ALL_BUCKETS` | `ref` | | List DB branches | `SUPABASE_LIST_ALL_DATABASE_BRANCHES` | `ref` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/supadata-automation/SKILL.md b/supadata-automation/SKILL.md new file mode 100644 index 0000000..4a626f5 --- /dev/null +++ b/supadata-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: supadata-automation +description: "Automate Supadata tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Supadata Automation via Rube MCP + +Automate Supadata operations through Composio's Supadata toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/supadata](https://composio.dev/toolkits/supadata) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Supadata connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `supadata` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `supadata` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Supadata operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Supadata task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["supadata"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Supadata-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `supadata` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/superchat-automation/SKILL.md b/superchat-automation/SKILL.md new file mode 100644 index 0000000..fbc208f --- /dev/null +++ b/superchat-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: superchat-automation +description: "Automate Superchat tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Superchat Automation via Rube MCP + +Automate Superchat operations through Composio's Superchat toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/superchat](https://composio.dev/toolkits/superchat) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Superchat connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `superchat` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `superchat` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Superchat operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Superchat task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["superchat"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Superchat-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `superchat` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/supportbee-automation/SKILL.md b/supportbee-automation/SKILL.md new file mode 100644 index 0000000..08c6983 --- /dev/null +++ b/supportbee-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: supportbee-automation +description: "Automate Supportbee tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Supportbee Automation via Rube MCP + +Automate Supportbee operations through Composio's Supportbee toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/supportbee](https://composio.dev/toolkits/supportbee) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Supportbee connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `supportbee` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `supportbee` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Supportbee operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Supportbee task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["supportbee"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Supportbee-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `supportbee` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/supportivekoala-automation/SKILL.md b/supportivekoala-automation/SKILL.md new file mode 100644 index 0000000..a3dcf9a --- /dev/null +++ b/supportivekoala-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: supportivekoala-automation +description: "Automate Supportivekoala tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Supportivekoala Automation via Rube MCP + +Automate Supportivekoala operations through Composio's Supportivekoala toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/supportivekoala](https://composio.dev/toolkits/supportivekoala) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Supportivekoala connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `supportivekoala` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `supportivekoala` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Supportivekoala operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Supportivekoala task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["supportivekoala"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Supportivekoala-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `supportivekoala` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/survey-monkey-automation/SKILL.md b/survey-monkey-automation/SKILL.md new file mode 100644 index 0000000..0bf5c5c --- /dev/null +++ b/survey-monkey-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: survey-monkey-automation +description: "Automate SurveyMonkey tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SurveyMonkey Automation via Rube MCP + +Automate SurveyMonkey operations through Composio's SurveyMonkey toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/survey_monkey](https://composio.dev/toolkits/survey_monkey) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SurveyMonkey connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `survey_monkey` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `survey_monkey` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "SurveyMonkey operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific SurveyMonkey task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["survey_monkey"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SurveyMonkey-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `survey_monkey` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/survey_monkey-automation/SKILL.md b/survey_monkey-automation/SKILL.md new file mode 100644 index 0000000..b83a9d3 --- /dev/null +++ b/survey_monkey-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: survey_monkey-automation +description: "Automate SurveyMonkey tasks via Rube MCP (Composio): surveys, responses, collectors, and survey analytics. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# SurveyMonkey Automation via Rube MCP + +Automate SurveyMonkey operations through Composio's SurveyMonkey toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/survey_monkey](https://composio.dev/toolkits/survey_monkey) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active SurveyMonkey connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `survey_monkey` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `survey_monkey` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "surveys, responses, collectors, and survey analytics", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for SurveyMonkey +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available SurveyMonkey Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available SurveyMonkey tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute SurveyMonkey Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple SurveyMonkey operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the SurveyMonkey connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with SurveyMonkey-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `survey_monkey` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/survey_monkey](https://composio.dev/toolkits/survey_monkey) diff --git a/svix-automation/SKILL.md b/svix-automation/SKILL.md new file mode 100644 index 0000000..e177615 --- /dev/null +++ b/svix-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: svix-automation +description: "Automate Svix tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Svix Automation via Rube MCP + +Automate Svix operations through Composio's Svix toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/svix](https://composio.dev/toolkits/svix) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Svix connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `svix` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `svix` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Svix operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Svix task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["svix"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Svix-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `svix` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/sympla-automation/SKILL.md b/sympla-automation/SKILL.md new file mode 100644 index 0000000..ab1675b --- /dev/null +++ b/sympla-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: sympla-automation +description: "Automate Sympla tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Sympla Automation via Rube MCP + +Automate Sympla operations through Composio's Sympla toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/sympla](https://composio.dev/toolkits/sympla) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Sympla connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sympla` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sympla` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Sympla operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Sympla task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["sympla"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Sympla-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sympla` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/synthflow-ai-automation/SKILL.md b/synthflow-ai-automation/SKILL.md new file mode 100644 index 0000000..28c20fa --- /dev/null +++ b/synthflow-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: synthflow-ai-automation +description: "Automate Synthflow AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Synthflow AI Automation via Rube MCP + +Automate Synthflow AI operations through Composio's Synthflow AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/synthflow_ai](https://composio.dev/toolkits/synthflow_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Synthflow AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `synthflow_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `synthflow_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Synthflow AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Synthflow AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["synthflow_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Synthflow AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `synthflow_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/taggun-automation/SKILL.md b/taggun-automation/SKILL.md new file mode 100644 index 0000000..ffaaf7a --- /dev/null +++ b/taggun-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: taggun-automation +description: "Automate Taggun tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Taggun Automation via Rube MCP + +Automate Taggun operations through Composio's Taggun toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/taggun](https://composio.dev/toolkits/taggun) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Taggun connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `taggun` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `taggun` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Taggun operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Taggun task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["taggun"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Taggun-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `taggun` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/talenthr-automation/SKILL.md b/talenthr-automation/SKILL.md new file mode 100644 index 0000000..936d503 --- /dev/null +++ b/talenthr-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: talenthr-automation +description: "Automate Talenthr tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Talenthr Automation via Rube MCP + +Automate Talenthr operations through Composio's Talenthr toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/talenthr](https://composio.dev/toolkits/talenthr) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Talenthr connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `talenthr` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `talenthr` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Talenthr operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Talenthr task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["talenthr"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Talenthr-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `talenthr` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tally-automation/SKILL.md b/tally-automation/SKILL.md new file mode 100644 index 0000000..900fd62 --- /dev/null +++ b/tally-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tally-automation +description: "Automate Tally tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tally Automation via Rube MCP + +Automate Tally operations through Composio's Tally toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tally](https://composio.dev/toolkits/tally) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tally connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tally` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tally` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tally operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tally task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tally"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tally-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tally` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tapfiliate-automation/SKILL.md b/tapfiliate-automation/SKILL.md new file mode 100644 index 0000000..20f38db --- /dev/null +++ b/tapfiliate-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tapfiliate-automation +description: "Automate Tapfiliate tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tapfiliate Automation via Rube MCP + +Automate Tapfiliate operations through Composio's Tapfiliate toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tapfiliate](https://composio.dev/toolkits/tapfiliate) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tapfiliate connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tapfiliate` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tapfiliate` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tapfiliate operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tapfiliate task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tapfiliate"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tapfiliate-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tapfiliate` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tapform-automation/SKILL.md b/tapform-automation/SKILL.md new file mode 100644 index 0000000..fade454 --- /dev/null +++ b/tapform-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tapform-automation +description: "Automate Tapform tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tapform Automation via Rube MCP + +Automate Tapform operations through Composio's Tapform toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tapform](https://composio.dev/toolkits/tapform) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tapform connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tapform` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tapform` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tapform operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tapform task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tapform"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tapform-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tapform` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tavily-automation/SKILL.md b/tavily-automation/SKILL.md new file mode 100644 index 0000000..0f8a214 --- /dev/null +++ b/tavily-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tavily-automation +description: "Automate Tavily tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tavily Automation via Rube MCP + +Automate Tavily operations through Composio's Tavily toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tavily](https://composio.dev/toolkits/tavily) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tavily connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tavily` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tavily` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tavily operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tavily task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tavily"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tavily-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tavily` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/taxjar-automation/SKILL.md b/taxjar-automation/SKILL.md new file mode 100644 index 0000000..43d145b --- /dev/null +++ b/taxjar-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: taxjar-automation +description: "Automate Taxjar tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Taxjar Automation via Rube MCP + +Automate Taxjar operations through Composio's Taxjar toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/taxjar](https://composio.dev/toolkits/taxjar) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Taxjar connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `taxjar` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `taxjar` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Taxjar operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Taxjar task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["taxjar"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Taxjar-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `taxjar` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/teamcamp-automation/SKILL.md b/teamcamp-automation/SKILL.md new file mode 100644 index 0000000..576cab9 --- /dev/null +++ b/teamcamp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: teamcamp-automation +description: "Automate Teamcamp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Teamcamp Automation via Rube MCP + +Automate Teamcamp operations through Composio's Teamcamp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/teamcamp](https://composio.dev/toolkits/teamcamp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Teamcamp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `teamcamp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `teamcamp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Teamcamp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Teamcamp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["teamcamp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Teamcamp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `teamcamp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/telegram-automation/SKILL.md b/telegram-automation/SKILL.md index e2079cb..ef24a6e 100644 --- a/telegram-automation/SKILL.md +++ b/telegram-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Telegram operations through Composio's Telegram toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/telegram](https://composio.dev/toolkits/telegram) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -217,3 +219,6 @@ Automate Telegram operations through Composio's Telegram toolkit via Rube MCP. | Get chat history | TELEGRAM_GET_CHAT_HISTORY | chat_id | | Set bot commands | TELEGRAM_SET_MY_COMMANDS | commands | | Answer callback | TELEGRAM_ANSWER_CALLBACK_QUERY | callback_query_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/telnyx-automation/SKILL.md b/telnyx-automation/SKILL.md new file mode 100644 index 0000000..8d417ef --- /dev/null +++ b/telnyx-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: telnyx-automation +description: "Automate Telnyx tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Telnyx Automation via Rube MCP + +Automate Telnyx operations through Composio's Telnyx toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/telnyx](https://composio.dev/toolkits/telnyx) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Telnyx connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `telnyx` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `telnyx` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Telnyx operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Telnyx task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["telnyx"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Telnyx-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `telnyx` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/teltel-automation/SKILL.md b/teltel-automation/SKILL.md new file mode 100644 index 0000000..12229f7 --- /dev/null +++ b/teltel-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: teltel-automation +description: "Automate Teltel tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Teltel Automation via Rube MCP + +Automate Teltel operations through Composio's Teltel toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/teltel](https://composio.dev/toolkits/teltel) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Teltel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `teltel` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `teltel` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Teltel operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Teltel task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["teltel"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Teltel-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `teltel` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/templated-automation/SKILL.md b/templated-automation/SKILL.md new file mode 100644 index 0000000..69ef6de --- /dev/null +++ b/templated-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: templated-automation +description: "Automate Templated tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Templated Automation via Rube MCP + +Automate Templated operations through Composio's Templated toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/templated](https://composio.dev/toolkits/templated) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Templated connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `templated` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `templated` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Templated operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Templated task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["templated"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Templated-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `templated` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/test-app-automation/SKILL.md b/test-app-automation/SKILL.md new file mode 100644 index 0000000..cc9423d --- /dev/null +++ b/test-app-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: test-app-automation +description: "Automate Test App tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Test App Automation via Rube MCP + +Automate Test App operations through Composio's Test App toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/test_app](https://composio.dev/toolkits/test_app) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Test App connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `test_app` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `test_app` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Test App operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Test App task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["test_app"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Test App-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `test_app` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/text-to-pdf-automation/SKILL.md b/text-to-pdf-automation/SKILL.md new file mode 100644 index 0000000..9d23e33 --- /dev/null +++ b/text-to-pdf-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: text-to-pdf-automation +description: "Automate Text To PDF tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Text To PDF Automation via Rube MCP + +Automate Text To PDF operations through Composio's Text To PDF toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/text_to_pdf](https://composio.dev/toolkits/text_to_pdf) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Text To PDF connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `text_to_pdf` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `text_to_pdf` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Text To PDF operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Text To PDF task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["text_to_pdf"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Text To PDF-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `text_to_pdf` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/textcortex-automation/SKILL.md b/textcortex-automation/SKILL.md new file mode 100644 index 0000000..871b91e --- /dev/null +++ b/textcortex-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: textcortex-automation +description: "Automate Textcortex tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Textcortex Automation via Rube MCP + +Automate Textcortex operations through Composio's Textcortex toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/textcortex](https://composio.dev/toolkits/textcortex) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Textcortex connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `textcortex` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `textcortex` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Textcortex operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Textcortex task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["textcortex"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Textcortex-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `textcortex` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/textit-automation/SKILL.md b/textit-automation/SKILL.md new file mode 100644 index 0000000..370842c --- /dev/null +++ b/textit-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: textit-automation +description: "Automate Textit tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Textit Automation via Rube MCP + +Automate Textit operations through Composio's Textit toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/textit](https://composio.dev/toolkits/textit) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Textit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `textit` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `textit` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Textit operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Textit task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["textit"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Textit-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `textit` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/textrazor-automation/SKILL.md b/textrazor-automation/SKILL.md new file mode 100644 index 0000000..dcdcbf7 --- /dev/null +++ b/textrazor-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: textrazor-automation +description: "Automate Textrazor tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Textrazor Automation via Rube MCP + +Automate Textrazor operations through Composio's Textrazor toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/textrazor](https://composio.dev/toolkits/textrazor) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Textrazor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `textrazor` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `textrazor` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Textrazor operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Textrazor task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["textrazor"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Textrazor-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `textrazor` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/thanks-io-automation/SKILL.md b/thanks-io-automation/SKILL.md new file mode 100644 index 0000000..1797bc2 --- /dev/null +++ b/thanks-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: thanks-io-automation +description: "Automate Thanks IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Thanks IO Automation via Rube MCP + +Automate Thanks IO operations through Composio's Thanks IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/thanks_io](https://composio.dev/toolkits/thanks_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Thanks IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `thanks_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `thanks_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Thanks IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Thanks IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["thanks_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Thanks IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `thanks_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/the-odds-api-automation/SKILL.md b/the-odds-api-automation/SKILL.md new file mode 100644 index 0000000..b2401eb --- /dev/null +++ b/the-odds-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: the-odds-api-automation +description: "Automate The Odds API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# The Odds API Automation via Rube MCP + +Automate The Odds API operations through Composio's The Odds API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/the_odds_api](https://composio.dev/toolkits/the_odds_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active The Odds API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `the_odds_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `the_odds_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "The Odds API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific The Odds API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["the_odds_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with The Odds API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `the_odds_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ticketmaster-automation/SKILL.md b/ticketmaster-automation/SKILL.md new file mode 100644 index 0000000..55ac578 --- /dev/null +++ b/ticketmaster-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ticketmaster-automation +description: "Automate Ticketmaster tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ticketmaster Automation via Rube MCP + +Automate Ticketmaster operations through Composio's Ticketmaster toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ticketmaster](https://composio.dev/toolkits/ticketmaster) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ticketmaster connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ticketmaster` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ticketmaster` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ticketmaster operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ticketmaster task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ticketmaster"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ticketmaster-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ticketmaster` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ticktick-automation/SKILL.md b/ticktick-automation/SKILL.md new file mode 100644 index 0000000..9f66e0b --- /dev/null +++ b/ticktick-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ticktick-automation +description: "Automate Ticktick tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ticktick Automation via Rube MCP + +Automate Ticktick operations through Composio's Ticktick toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ticktick](https://composio.dev/toolkits/ticktick) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ticktick connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ticktick` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ticktick` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ticktick operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ticktick task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ticktick"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ticktick-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ticktick` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tiktok-automation/SKILL.md b/tiktok-automation/SKILL.md index 2cc63d5..29512b6 100644 --- a/tiktok-automation/SKILL.md +++ b/tiktok-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate TikTok content creation and profile operations through Composio's TikTok toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/tiktok](https://composio.dev/toolkits/tiktok) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -176,3 +178,6 @@ Automate TikTok content creation and profile operations through Composio's TikTo | Get user stats | TIKTOK_GET_USER_STATS | (none) | | Get basic info | TIKTOK_GET_USER_BASIC_INFO | (none) | | Check publish status | TIKTOK_FETCH_PUBLISH_STATUS | publish_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/timecamp-automation/SKILL.md b/timecamp-automation/SKILL.md new file mode 100644 index 0000000..c311982 --- /dev/null +++ b/timecamp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: timecamp-automation +description: "Automate Timecamp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Timecamp Automation via Rube MCP + +Automate Timecamp operations through Composio's Timecamp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/timecamp](https://composio.dev/toolkits/timecamp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Timecamp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `timecamp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `timecamp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Timecamp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Timecamp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["timecamp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Timecamp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `timecamp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/timekit-automation/SKILL.md b/timekit-automation/SKILL.md new file mode 100644 index 0000000..3765b8a --- /dev/null +++ b/timekit-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: timekit-automation +description: "Automate Timekit tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Timekit Automation via Rube MCP + +Automate Timekit operations through Composio's Timekit toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/timekit](https://composio.dev/toolkits/timekit) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Timekit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `timekit` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `timekit` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Timekit operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Timekit task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["timekit"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Timekit-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `timekit` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/timelinesai-automation/SKILL.md b/timelinesai-automation/SKILL.md new file mode 100644 index 0000000..25a0a84 --- /dev/null +++ b/timelinesai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: timelinesai-automation +description: "Automate Timelinesai tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Timelinesai Automation via Rube MCP + +Automate Timelinesai operations through Composio's Timelinesai toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/timelinesai](https://composio.dev/toolkits/timelinesai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Timelinesai connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `timelinesai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `timelinesai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Timelinesai operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Timelinesai task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["timelinesai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Timelinesai-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `timelinesai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/timelink-automation/SKILL.md b/timelink-automation/SKILL.md new file mode 100644 index 0000000..6edaa5c --- /dev/null +++ b/timelink-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: timelink-automation +description: "Automate Timelink tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Timelink Automation via Rube MCP + +Automate Timelink operations through Composio's Timelink toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/timelink](https://composio.dev/toolkits/timelink) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Timelink connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `timelink` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `timelink` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Timelink operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Timelink task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["timelink"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Timelink-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `timelink` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/timely-automation/SKILL.md b/timely-automation/SKILL.md new file mode 100644 index 0000000..c66eca2 --- /dev/null +++ b/timely-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: timely-automation +description: "Automate Timely tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Timely Automation via Rube MCP + +Automate Timely operations through Composio's Timely toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/timely](https://composio.dev/toolkits/timely) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Timely connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `timely` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `timely` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Timely operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Timely task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["timely"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Timely-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `timely` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tinyurl-automation/SKILL.md b/tinyurl-automation/SKILL.md new file mode 100644 index 0000000..ba8f18f --- /dev/null +++ b/tinyurl-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tinyurl-automation +description: "Automate Tinyurl tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tinyurl Automation via Rube MCP + +Automate Tinyurl operations through Composio's Tinyurl toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tinyurl](https://composio.dev/toolkits/tinyurl) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tinyurl connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tinyurl` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tinyurl` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tinyurl operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tinyurl task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tinyurl"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tinyurl-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tinyurl` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tisane-automation/SKILL.md b/tisane-automation/SKILL.md new file mode 100644 index 0000000..4da0732 --- /dev/null +++ b/tisane-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tisane-automation +description: "Automate Tisane tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tisane Automation via Rube MCP + +Automate Tisane operations through Composio's Tisane toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tisane](https://composio.dev/toolkits/tisane) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tisane connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tisane` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tisane` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tisane operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tisane task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tisane"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tisane-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tisane` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/todoist-automation/SKILL.md b/todoist-automation/SKILL.md index 424e923..7fd2ff1 100644 --- a/todoist-automation/SKILL.md +++ b/todoist-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Todoist operations including task creation and management, project organization, section management, filtering, and bulk task workflows through Composio's Todoist toolkit. +**Toolkit docs**: [composio.dev/toolkits/todoist](https://composio.dev/toolkits/todoist) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -229,3 +231,6 @@ Always resolve human-readable names to IDs before operations: | Delete task | `TODOIST_DELETE_TASK` | `task_id` | | Completed tasks | `TODOIST_GET_COMPLETED_TASKS_BY_COMPLETION_DATE` | `since`, `until` | | List filters | `TODOIST_LIST_FILTERS` | `sync_token` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/toggl-automation/SKILL.md b/toggl-automation/SKILL.md new file mode 100644 index 0000000..893843e --- /dev/null +++ b/toggl-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: toggl-automation +description: "Automate Toggl tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Toggl Automation via Rube MCP + +Automate Toggl operations through Composio's Toggl toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/toggl](https://composio.dev/toolkits/toggl) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Toggl connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `toggl` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `toggl` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Toggl operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Toggl task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["toggl"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Toggl-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `toggl` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/token-metrics-automation/SKILL.md b/token-metrics-automation/SKILL.md new file mode 100644 index 0000000..aa37de3 --- /dev/null +++ b/token-metrics-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: token-metrics-automation +description: "Automate Token Metrics tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Token Metrics Automation via Rube MCP + +Automate Token Metrics operations through Composio's Token Metrics toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/token_metrics](https://composio.dev/toolkits/token_metrics) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Token Metrics connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `token_metrics` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `token_metrics` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Token Metrics operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Token Metrics task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["token_metrics"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Token Metrics-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `token_metrics` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tomba-automation/SKILL.md b/tomba-automation/SKILL.md new file mode 100644 index 0000000..d33258b --- /dev/null +++ b/tomba-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tomba-automation +description: "Automate Tomba tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tomba Automation via Rube MCP + +Automate Tomba operations through Composio's Tomba toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tomba](https://composio.dev/toolkits/tomba) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tomba connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tomba` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tomba` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tomba operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tomba task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tomba"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tomba-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tomba` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tomtom-automation/SKILL.md b/tomtom-automation/SKILL.md new file mode 100644 index 0000000..3ff1249 --- /dev/null +++ b/tomtom-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tomtom-automation +description: "Automate Tomtom tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tomtom Automation via Rube MCP + +Automate Tomtom operations through Composio's Tomtom toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tomtom](https://composio.dev/toolkits/tomtom) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tomtom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tomtom` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tomtom` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tomtom operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tomtom task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tomtom"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tomtom-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tomtom` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/toneden-automation/SKILL.md b/toneden-automation/SKILL.md new file mode 100644 index 0000000..15327f2 --- /dev/null +++ b/toneden-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: toneden-automation +description: "Automate Toneden tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Toneden Automation via Rube MCP + +Automate Toneden operations through Composio's Toneden toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/toneden](https://composio.dev/toolkits/toneden) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Toneden connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `toneden` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `toneden` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Toneden operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Toneden task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["toneden"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Toneden-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `toneden` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tpscheck-automation/SKILL.md b/tpscheck-automation/SKILL.md new file mode 100644 index 0000000..474b713 --- /dev/null +++ b/tpscheck-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tpscheck-automation +description: "Automate Tpscheck tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Tpscheck Automation via Rube MCP + +Automate Tpscheck operations through Composio's Tpscheck toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tpscheck](https://composio.dev/toolkits/tpscheck) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Tpscheck connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tpscheck` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tpscheck` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Tpscheck operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Tpscheck task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tpscheck"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Tpscheck-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tpscheck` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/trello-automation/SKILL.md b/trello-automation/SKILL.md index 5f48626..61251ba 100644 --- a/trello-automation/SKILL.md +++ b/trello-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Trello board management, card creation, and team workflows through Composio's Rube MCP integration. +**Toolkit docs**: [composio.dev/toolkits/trello](https://composio.dev/toolkits/trello) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -178,4 +180,6 @@ Most list endpoints return all items. For boards with 1000+ cards, use `limit` a | Assign member | TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD | idCard, value (member ID) | | Attach file/URL | TRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD | idCard, url OR file | | Get board members | TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD | idBoard | -| Batch read | TRELLO_GET_BATCH | urls (comma-separated paths) | \ No newline at end of file +| Batch read | TRELLO_GET_BATCH | urls (comma-separated paths) | +--- +*Powered by [Composio](https://composio.dev)* diff --git a/triggercmd-automation/SKILL.md b/triggercmd-automation/SKILL.md new file mode 100644 index 0000000..284c068 --- /dev/null +++ b/triggercmd-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: triggercmd-automation +description: "Automate Triggercmd tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Triggercmd Automation via Rube MCP + +Automate Triggercmd operations through Composio's Triggercmd toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/triggercmd](https://composio.dev/toolkits/triggercmd) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Triggercmd connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `triggercmd` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `triggercmd` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Triggercmd operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Triggercmd task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["triggercmd"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Triggercmd-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `triggercmd` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/tripadvisor-content-api-automation/SKILL.md b/tripadvisor-content-api-automation/SKILL.md new file mode 100644 index 0000000..097a141 --- /dev/null +++ b/tripadvisor-content-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: tripadvisor-content-api-automation +description: "Automate TripAdvisor tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# TripAdvisor Automation via Rube MCP + +Automate TripAdvisor operations through Composio's TripAdvisor toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/tripadvisor_content_api](https://composio.dev/toolkits/tripadvisor_content_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active TripAdvisor connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tripadvisor_content_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tripadvisor_content_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "TripAdvisor operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific TripAdvisor task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["tripadvisor_content_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with TripAdvisor-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `tripadvisor_content_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/turbot-pipes-automation/SKILL.md b/turbot-pipes-automation/SKILL.md new file mode 100644 index 0000000..f587903 --- /dev/null +++ b/turbot-pipes-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: turbot-pipes-automation +description: "Automate Turbot Pipes tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Turbot Pipes Automation via Rube MCP + +Automate Turbot Pipes operations through Composio's Turbot Pipes toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/turbot_pipes](https://composio.dev/toolkits/turbot_pipes) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Turbot Pipes connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `turbot_pipes` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `turbot_pipes` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Turbot Pipes operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Turbot Pipes task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["turbot_pipes"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Turbot Pipes-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `turbot_pipes` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/turso-automation/SKILL.md b/turso-automation/SKILL.md new file mode 100644 index 0000000..57f5a3d --- /dev/null +++ b/turso-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: turso-automation +description: "Automate Turso tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Turso Automation via Rube MCP + +Automate Turso operations through Composio's Turso toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/turso](https://composio.dev/toolkits/turso) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Turso connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `turso` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `turso` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Turso operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Turso task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["turso"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Turso-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `turso` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/twelve-data-automation/SKILL.md b/twelve-data-automation/SKILL.md new file mode 100644 index 0000000..7e5fe2d --- /dev/null +++ b/twelve-data-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: twelve-data-automation +description: "Automate Twelve Data tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Twelve Data Automation via Rube MCP + +Automate Twelve Data operations through Composio's Twelve Data toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/twelve_data](https://composio.dev/toolkits/twelve_data) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Twelve Data connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `twelve_data` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `twelve_data` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Twelve Data operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Twelve Data task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["twelve_data"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Twelve Data-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `twelve_data` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/twitch-automation/SKILL.md b/twitch-automation/SKILL.md new file mode 100644 index 0000000..be80494 --- /dev/null +++ b/twitch-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: twitch-automation +description: "Automate Twitch tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Twitch Automation via Rube MCP + +Automate Twitch operations through Composio's Twitch toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/twitch](https://composio.dev/toolkits/twitch) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Twitch connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `twitch` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `twitch` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Twitch operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Twitch task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["twitch"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Twitch-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `twitch` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/twitter-automation/SKILL.md b/twitter-automation/SKILL.md index 4add3fc..f2aef18 100644 --- a/twitter-automation/SKILL.md +++ b/twitter-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Twitter/X operations through Composio's Twitter toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/twitter](https://composio.dev/toolkits/twitter) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -229,3 +231,6 @@ Automate Twitter/X operations through Composio's Twitter toolkit via Rube MCP. | Pinned lists | TWITTER_GET_A_USER_S_PINNED_LISTS | id | | Followed lists | TWITTER_GET_USER_S_FOLLOWED_LISTS | id | | List details | TWITTER_LIST_LOOKUP_BY_LIST_ID | list_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/twocaptcha-automation/SKILL.md b/twocaptcha-automation/SKILL.md new file mode 100644 index 0000000..5970ab6 --- /dev/null +++ b/twocaptcha-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: twocaptcha-automation +description: "Automate Twocaptcha tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Twocaptcha Automation via Rube MCP + +Automate Twocaptcha operations through Composio's Twocaptcha toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/twocaptcha](https://composio.dev/toolkits/twocaptcha) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Twocaptcha connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `twocaptcha` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `twocaptcha` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Twocaptcha operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Twocaptcha task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["twocaptcha"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Twocaptcha-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `twocaptcha` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/typefully-automation/SKILL.md b/typefully-automation/SKILL.md new file mode 100644 index 0000000..3a8c22e --- /dev/null +++ b/typefully-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: typefully-automation +description: "Automate Typefully tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Typefully Automation via Rube MCP + +Automate Typefully operations through Composio's Typefully toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/typefully](https://composio.dev/toolkits/typefully) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Typefully connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `typefully` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `typefully` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Typefully operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Typefully task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["typefully"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Typefully-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `typefully` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/typless-automation/SKILL.md b/typless-automation/SKILL.md new file mode 100644 index 0000000..cfb339a --- /dev/null +++ b/typless-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: typless-automation +description: "Automate Typless tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Typless Automation via Rube MCP + +Automate Typless operations through Composio's Typless toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/typless](https://composio.dev/toolkits/typless) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Typless connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `typless` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `typless` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Typless operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Typless task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["typless"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Typless-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `typless` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/u301-automation/SKILL.md b/u301-automation/SKILL.md new file mode 100644 index 0000000..97b5130 --- /dev/null +++ b/u301-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: u301-automation +description: "Automate U301 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# U301 Automation via Rube MCP + +Automate U301 operations through Composio's U301 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/u301](https://composio.dev/toolkits/u301) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active U301 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `u301` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `u301` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "U301 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific U301 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["u301"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with U301-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `u301` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/unione-automation/SKILL.md b/unione-automation/SKILL.md new file mode 100644 index 0000000..0917476 --- /dev/null +++ b/unione-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: unione-automation +description: "Automate Unione tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Unione Automation via Rube MCP + +Automate Unione operations through Composio's Unione toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/unione](https://composio.dev/toolkits/unione) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Unione connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `unione` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `unione` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Unione operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Unione task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["unione"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Unione-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `unione` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/updown-io-automation/SKILL.md b/updown-io-automation/SKILL.md new file mode 100644 index 0000000..7f50b5d --- /dev/null +++ b/updown-io-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: updown-io-automation +description: "Automate Updown IO tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Updown IO Automation via Rube MCP + +Automate Updown IO operations through Composio's Updown IO toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/updown_io](https://composio.dev/toolkits/updown_io) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Updown IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `updown_io` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `updown_io` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Updown IO operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Updown IO task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["updown_io"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Updown IO-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `updown_io` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/uploadcare-automation/SKILL.md b/uploadcare-automation/SKILL.md new file mode 100644 index 0000000..1f780f1 --- /dev/null +++ b/uploadcare-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: uploadcare-automation +description: "Automate Uploadcare tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Uploadcare Automation via Rube MCP + +Automate Uploadcare operations through Composio's Uploadcare toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/uploadcare](https://composio.dev/toolkits/uploadcare) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Uploadcare connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `uploadcare` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `uploadcare` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Uploadcare operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Uploadcare task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["uploadcare"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Uploadcare-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `uploadcare` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/uptimerobot-automation/SKILL.md b/uptimerobot-automation/SKILL.md new file mode 100644 index 0000000..2c63be3 --- /dev/null +++ b/uptimerobot-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: uptimerobot-automation +description: "Automate Uptimerobot tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Uptimerobot Automation via Rube MCP + +Automate Uptimerobot operations through Composio's Uptimerobot toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/uptimerobot](https://composio.dev/toolkits/uptimerobot) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Uptimerobot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `uptimerobot` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `uptimerobot` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Uptimerobot operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Uptimerobot task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["uptimerobot"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Uptimerobot-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `uptimerobot` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/userlist-automation/SKILL.md b/userlist-automation/SKILL.md new file mode 100644 index 0000000..98774d0 --- /dev/null +++ b/userlist-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: userlist-automation +description: "Automate Userlist tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Userlist Automation via Rube MCP + +Automate Userlist operations through Composio's Userlist toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/userlist](https://composio.dev/toolkits/userlist) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Userlist connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `userlist` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `userlist` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Userlist operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Userlist task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["userlist"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Userlist-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `userlist` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/v0-automation/SKILL.md b/v0-automation/SKILL.md new file mode 100644 index 0000000..4bf6e9b --- /dev/null +++ b/v0-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: v0-automation +description: "Automate V0 tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# V0 Automation via Rube MCP + +Automate V0 operations through Composio's V0 toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/v0](https://composio.dev/toolkits/v0) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active V0 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `v0` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `v0` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "V0 operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific V0 task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["v0"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with V0-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `v0` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/venly-automation/SKILL.md b/venly-automation/SKILL.md new file mode 100644 index 0000000..e1056c6 --- /dev/null +++ b/venly-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: venly-automation +description: "Automate Venly tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Venly Automation via Rube MCP + +Automate Venly operations through Composio's Venly toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/venly](https://composio.dev/toolkits/venly) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Venly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `venly` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `venly` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Venly operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Venly task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["venly"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Venly-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `venly` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/veo-automation/SKILL.md b/veo-automation/SKILL.md new file mode 100644 index 0000000..80d3872 --- /dev/null +++ b/veo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: veo-automation +description: "Automate Veo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Veo Automation via Rube MCP + +Automate Veo operations through Composio's Veo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/veo](https://composio.dev/toolkits/veo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Veo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `veo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `veo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Veo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Veo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["veo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Veo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `veo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/vercel-automation/SKILL.md b/vercel-automation/SKILL.md index 9ebee5c..08badbb 100644 --- a/vercel-automation/SKILL.md +++ b/vercel-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Vercel platform operations through Composio's Vercel toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/vercel](https://composio.dev/toolkits/vercel) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -224,3 +226,6 @@ Automate Vercel platform operations through Composio's Vercel toolkit via Rube M | List teams | VERCEL_LIST_TEAMS | (none) | | Get team | VERCEL_GET_TEAM | teamId | | Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/verifiedemail-automation/SKILL.md b/verifiedemail-automation/SKILL.md new file mode 100644 index 0000000..162cabb --- /dev/null +++ b/verifiedemail-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: verifiedemail-automation +description: "Automate Verifiedemail tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Verifiedemail Automation via Rube MCP + +Automate Verifiedemail operations through Composio's Verifiedemail toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/verifiedemail](https://composio.dev/toolkits/verifiedemail) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Verifiedemail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `verifiedemail` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `verifiedemail` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Verifiedemail operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Verifiedemail task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["verifiedemail"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Verifiedemail-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `verifiedemail` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/veriphone-automation/SKILL.md b/veriphone-automation/SKILL.md new file mode 100644 index 0000000..ea73d3e --- /dev/null +++ b/veriphone-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: veriphone-automation +description: "Automate Veriphone tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Veriphone Automation via Rube MCP + +Automate Veriphone operations through Composio's Veriphone toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/veriphone](https://composio.dev/toolkits/veriphone) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Veriphone connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `veriphone` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `veriphone` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Veriphone operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Veriphone task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["veriphone"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Veriphone-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `veriphone` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/vero-automation/SKILL.md b/vero-automation/SKILL.md new file mode 100644 index 0000000..44ce557 --- /dev/null +++ b/vero-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: vero-automation +description: "Automate Vero tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Vero Automation via Rube MCP + +Automate Vero operations through Composio's Vero toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/vero](https://composio.dev/toolkits/vero) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Vero connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `vero` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `vero` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Vero operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Vero task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["vero"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Vero-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `vero` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/vestaboard-automation/SKILL.md b/vestaboard-automation/SKILL.md new file mode 100644 index 0000000..73420df --- /dev/null +++ b/vestaboard-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: vestaboard-automation +description: "Automate Vestaboard tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Vestaboard Automation via Rube MCP + +Automate Vestaboard operations through Composio's Vestaboard toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/vestaboard](https://composio.dev/toolkits/vestaboard) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Vestaboard connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `vestaboard` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `vestaboard` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Vestaboard operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Vestaboard task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["vestaboard"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Vestaboard-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `vestaboard` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/virustotal-automation/SKILL.md b/virustotal-automation/SKILL.md new file mode 100644 index 0000000..81925fe --- /dev/null +++ b/virustotal-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: virustotal-automation +description: "Automate Virustotal tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Virustotal Automation via Rube MCP + +Automate Virustotal operations through Composio's Virustotal toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/virustotal](https://composio.dev/toolkits/virustotal) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Virustotal connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `virustotal` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `virustotal` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Virustotal operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Virustotal task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["virustotal"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Virustotal-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `virustotal` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/visme-automation/SKILL.md b/visme-automation/SKILL.md new file mode 100644 index 0000000..de6646a --- /dev/null +++ b/visme-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: visme-automation +description: "Automate Visme tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Visme Automation via Rube MCP + +Automate Visme operations through Composio's Visme toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/visme](https://composio.dev/toolkits/visme) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Visme connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `visme` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `visme` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Visme operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Visme task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["visme"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Visme-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `visme` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/waboxapp-automation/SKILL.md b/waboxapp-automation/SKILL.md new file mode 100644 index 0000000..a925050 --- /dev/null +++ b/waboxapp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: waboxapp-automation +description: "Automate Waboxapp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Waboxapp Automation via Rube MCP + +Automate Waboxapp operations through Composio's Waboxapp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/waboxapp](https://composio.dev/toolkits/waboxapp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Waboxapp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `waboxapp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `waboxapp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Waboxapp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Waboxapp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["waboxapp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Waboxapp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `waboxapp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wachete-automation/SKILL.md b/wachete-automation/SKILL.md new file mode 100644 index 0000000..2e5842a --- /dev/null +++ b/wachete-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: wachete-automation +description: "Automate Wachete tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wachete Automation via Rube MCP + +Automate Wachete operations through Composio's Wachete toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wachete](https://composio.dev/toolkits/wachete) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wachete connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wachete` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wachete` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Wachete operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Wachete task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["wachete"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wachete-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wachete` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/waiverfile-automation/SKILL.md b/waiverfile-automation/SKILL.md new file mode 100644 index 0000000..666647c --- /dev/null +++ b/waiverfile-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: waiverfile-automation +description: "Automate Waiverfile tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Waiverfile Automation via Rube MCP + +Automate Waiverfile operations through Composio's Waiverfile toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/waiverfile](https://composio.dev/toolkits/waiverfile) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Waiverfile connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `waiverfile` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `waiverfile` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Waiverfile operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Waiverfile task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["waiverfile"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Waiverfile-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `waiverfile` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wakatime-automation/SKILL.md b/wakatime-automation/SKILL.md new file mode 100644 index 0000000..f8dfb5a --- /dev/null +++ b/wakatime-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: wakatime-automation +description: "Automate Wakatime tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wakatime Automation via Rube MCP + +Automate Wakatime operations through Composio's Wakatime toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wakatime](https://composio.dev/toolkits/wakatime) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wakatime connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wakatime` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wakatime` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Wakatime operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Wakatime task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["wakatime"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wakatime-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wakatime` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wati-automation/SKILL.md b/wati-automation/SKILL.md new file mode 100644 index 0000000..d3ea9da --- /dev/null +++ b/wati-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: wati-automation +description: "Automate Wati tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wati Automation via Rube MCP + +Automate Wati operations through Composio's Wati toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wati](https://composio.dev/toolkits/wati) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wati connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wati` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wati` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Wati operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Wati task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["wati"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wati-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wati` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wave-accounting-automation/SKILL.md b/wave-accounting-automation/SKILL.md new file mode 100644 index 0000000..59d8a33 --- /dev/null +++ b/wave-accounting-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: wave-accounting-automation +description: "Automate Wave Accounting tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wave Accounting Automation via Rube MCP + +Automate Wave Accounting operations through Composio's Wave Accounting toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wave_accounting](https://composio.dev/toolkits/wave_accounting) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wave Accounting connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wave_accounting` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wave_accounting` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Wave Accounting operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Wave Accounting task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["wave_accounting"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wave Accounting-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wave_accounting` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wave_accounting-automation/SKILL.md b/wave_accounting-automation/SKILL.md new file mode 100644 index 0000000..89cc739 --- /dev/null +++ b/wave_accounting-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: wave_accounting-automation +description: "Automate Wave Accounting tasks via Rube MCP (Composio): invoices, customers, payments, and small business accounting. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wave Accounting Automation via Rube MCP + +Automate Wave Accounting operations through Composio's Wave Accounting toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wave_accounting](https://composio.dev/toolkits/wave_accounting) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wave Accounting connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wave_accounting` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wave_accounting` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "invoices, customers, payments, and small business accounting", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Wave Accounting +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Wave Accounting Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Wave Accounting tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Wave Accounting Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Wave Accounting operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Wave Accounting connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wave Accounting-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wave_accounting` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/wave_accounting](https://composio.dev/toolkits/wave_accounting) diff --git a/weathermap-automation/SKILL.md b/weathermap-automation/SKILL.md new file mode 100644 index 0000000..4d286b9 --- /dev/null +++ b/weathermap-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: weathermap-automation +description: "Automate Weathermap tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Weathermap Automation via Rube MCP + +Automate Weathermap operations through Composio's Weathermap toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/weathermap](https://composio.dev/toolkits/weathermap) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Weathermap connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `weathermap` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `weathermap` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Weathermap operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Weathermap task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["weathermap"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Weathermap-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `weathermap` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/webex-automation/SKILL.md b/webex-automation/SKILL.md new file mode 100644 index 0000000..ce1827d --- /dev/null +++ b/webex-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: webex-automation +description: "Automate Webex tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Webex Automation via Rube MCP + +Automate Webex operations through Composio's Webex toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/webex](https://composio.dev/toolkits/webex) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Webex connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `webex` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `webex` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Webex operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Webex task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["webex"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Webex-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `webex` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/webflow-automation/SKILL.md b/webflow-automation/SKILL.md index 2d3a7e7..e319e31 100644 --- a/webflow-automation/SKILL.md +++ b/webflow-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Webflow operations including CMS collection management, site publishing, page inspection, asset uploads, and ecommerce order retrieval through Composio's Webflow toolkit. +**Toolkit docs**: [composio.dev/toolkits/webflow](https://composio.dev/toolkits/webflow) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -234,3 +236,6 @@ Typical CMS content creation flow: | Upload asset | `WEBFLOW_UPLOAD_ASSET` | `site_id`, `file_name`, `file_content`, `content_type`, `md5` | | List orders | `WEBFLOW_LIST_ORDERS` | `site_id`, `status` | | Get order | `WEBFLOW_GET_ORDER` | `site_id`, `order_id` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/webscraping-ai-automation/SKILL.md b/webscraping-ai-automation/SKILL.md new file mode 100644 index 0000000..11f406c --- /dev/null +++ b/webscraping-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: webscraping-ai-automation +description: "Automate Webscraping AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Webscraping AI Automation via Rube MCP + +Automate Webscraping AI operations through Composio's Webscraping AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/webscraping_ai](https://composio.dev/toolkits/webscraping_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Webscraping AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `webscraping_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `webscraping_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Webscraping AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Webscraping AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["webscraping_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Webscraping AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `webscraping_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/webvizio-automation/SKILL.md b/webvizio-automation/SKILL.md new file mode 100644 index 0000000..58d8c12 --- /dev/null +++ b/webvizio-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: webvizio-automation +description: "Automate Webvizio tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Webvizio Automation via Rube MCP + +Automate Webvizio operations through Composio's Webvizio toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/webvizio](https://composio.dev/toolkits/webvizio) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Webvizio connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `webvizio` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `webvizio` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Webvizio operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Webvizio task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["webvizio"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Webvizio-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `webvizio` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/whatsapp-automation/SKILL.md b/whatsapp-automation/SKILL.md index 11d31a525..95ef137 100644 --- a/whatsapp-automation/SKILL.md +++ b/whatsapp-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate WhatsApp Business operations through Composio's WhatsApp toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/whatsapp](https://composio.dev/toolkits/whatsapp) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -212,3 +214,6 @@ Automate WhatsApp Business operations through Composio's WhatsApp toolkit via Ru | Create template | WHATSAPP_CREATE_MESSAGE_TEMPLATE | template_name, category, language | | List templates | WHATSAPP_GET_MESSAGE_TEMPLATES | (none) | | Check template status | WHATSAPP_GET_TEMPLATE_STATUS | template_id | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/whautomate-automation/SKILL.md b/whautomate-automation/SKILL.md new file mode 100644 index 0000000..7f21d80 --- /dev/null +++ b/whautomate-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: whautomate-automation +description: "Automate Whautomate tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Whautomate Automation via Rube MCP + +Automate Whautomate operations through Composio's Whautomate toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/whautomate](https://composio.dev/toolkits/whautomate) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Whautomate connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `whautomate` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `whautomate` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Whautomate operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Whautomate task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["whautomate"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Whautomate-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `whautomate` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/winston-ai-automation/SKILL.md b/winston-ai-automation/SKILL.md new file mode 100644 index 0000000..6274741 --- /dev/null +++ b/winston-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: winston-ai-automation +description: "Automate Winston AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Winston AI Automation via Rube MCP + +Automate Winston AI operations through Composio's Winston AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/winston_ai](https://composio.dev/toolkits/winston_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Winston AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `winston_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `winston_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Winston AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Winston AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["winston_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Winston AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `winston_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wit-ai-automation/SKILL.md b/wit-ai-automation/SKILL.md new file mode 100644 index 0000000..d1a1d39 --- /dev/null +++ b/wit-ai-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: wit-ai-automation +description: "Automate Wit AI tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wit AI Automation via Rube MCP + +Automate Wit AI operations through Composio's Wit AI toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wit_ai](https://composio.dev/toolkits/wit_ai) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wit AI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wit_ai` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wit_ai` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Wit AI operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Wit AI task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["wit_ai"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wit AI-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wit_ai` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wiz-automation/SKILL.md b/wiz-automation/SKILL.md new file mode 100644 index 0000000..394be4d --- /dev/null +++ b/wiz-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: wiz-automation +description: "Automate Wiz tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wiz Automation via Rube MCP + +Automate Wiz operations through Composio's Wiz toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wiz](https://composio.dev/toolkits/wiz) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wiz connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wiz` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wiz` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Wiz operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Wiz task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["wiz"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wiz-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wiz` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wolfram-alpha-api-automation/SKILL.md b/wolfram-alpha-api-automation/SKILL.md new file mode 100644 index 0000000..88a1b98 --- /dev/null +++ b/wolfram-alpha-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: wolfram-alpha-api-automation +description: "Automate Wolfram Alpha API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Wolfram Alpha API Automation via Rube MCP + +Automate Wolfram Alpha API operations through Composio's Wolfram Alpha API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/wolfram_alpha_api](https://composio.dev/toolkits/wolfram_alpha_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Wolfram Alpha API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wolfram_alpha_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wolfram_alpha_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Wolfram Alpha API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Wolfram Alpha API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["wolfram_alpha_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Wolfram Alpha API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `wolfram_alpha_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/woodpecker-co-automation/SKILL.md b/woodpecker-co-automation/SKILL.md new file mode 100644 index 0000000..eb41151 --- /dev/null +++ b/woodpecker-co-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: woodpecker-co-automation +description: "Automate Woodpecker co tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Woodpecker co Automation via Rube MCP + +Automate Woodpecker co operations through Composio's Woodpecker co toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/woodpecker_co](https://composio.dev/toolkits/woodpecker_co) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Woodpecker co connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `woodpecker_co` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `woodpecker_co` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Woodpecker co operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Woodpecker co task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["woodpecker_co"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Woodpecker co-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `woodpecker_co` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/workable-automation/SKILL.md b/workable-automation/SKILL.md new file mode 100644 index 0000000..b9d9e56 --- /dev/null +++ b/workable-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: workable-automation +description: "Automate Workable tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Workable Automation via Rube MCP + +Automate Workable operations through Composio's Workable toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/workable](https://composio.dev/toolkits/workable) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Workable connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `workable` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `workable` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Workable operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Workable task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["workable"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Workable-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `workable` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/workday-automation/SKILL.md b/workday-automation/SKILL.md new file mode 100644 index 0000000..98acd20 --- /dev/null +++ b/workday-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: workday-automation +description: "Automate Workday tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Workday Automation via Rube MCP + +Automate Workday operations through Composio's Workday toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/workday](https://composio.dev/toolkits/workday) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Workday connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `workday` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `workday` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Workday operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Workday task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["workday"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Workday-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `workday` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/workiom-automation/SKILL.md b/workiom-automation/SKILL.md new file mode 100644 index 0000000..d681d9a --- /dev/null +++ b/workiom-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: workiom-automation +description: "Automate Workiom tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Workiom Automation via Rube MCP + +Automate Workiom operations through Composio's Workiom toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/workiom](https://composio.dev/toolkits/workiom) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Workiom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `workiom` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `workiom` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Workiom operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Workiom task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["workiom"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Workiom-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `workiom` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/worksnaps-automation/SKILL.md b/worksnaps-automation/SKILL.md new file mode 100644 index 0000000..d570899 --- /dev/null +++ b/worksnaps-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: worksnaps-automation +description: "Automate Worksnaps tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Worksnaps Automation via Rube MCP + +Automate Worksnaps operations through Composio's Worksnaps toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/worksnaps](https://composio.dev/toolkits/worksnaps) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Worksnaps connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `worksnaps` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `worksnaps` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Worksnaps operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Worksnaps task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["worksnaps"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Worksnaps-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `worksnaps` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/wrike-automation/SKILL.md b/wrike-automation/SKILL.md index bb8f6ed..7680960 100644 --- a/wrike-automation/SKILL.md +++ b/wrike-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Wrike project management operations through Composio's Wrike toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/wrike](https://composio.dev/toolkits/wrike) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -231,3 +233,6 @@ Automate Wrike project management operations through Composio's Wrike toolkit vi | Delete space | WRIKE_DELETE_SPACE | spaceId | | Get contacts | WRIKE_GET_CONTACTS | (none) | | Invite user | WRIKE_CREATE_INVITATION | email, role | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/writer-automation/SKILL.md b/writer-automation/SKILL.md new file mode 100644 index 0000000..cd24b5c --- /dev/null +++ b/writer-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: writer-automation +description: "Automate Writer tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Writer Automation via Rube MCP + +Automate Writer operations through Composio's Writer toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/writer](https://composio.dev/toolkits/writer) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Writer connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `writer` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `writer` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Writer operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Writer task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["writer"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Writer-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `writer` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/xero-automation/SKILL.md b/xero-automation/SKILL.md new file mode 100644 index 0000000..42f6776 --- /dev/null +++ b/xero-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: xero-automation +description: "Automate Xero tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Xero Automation via Rube MCP + +Automate Xero operations through Composio's Xero toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/xero](https://composio.dev/toolkits/xero) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Xero connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `xero` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `xero` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Xero operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Xero task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["xero"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Xero-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `xero` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/y-gy-automation/SKILL.md b/y-gy-automation/SKILL.md new file mode 100644 index 0000000..d5cccf4 --- /dev/null +++ b/y-gy-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: y-gy-automation +description: "Automate Y Gy tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Y Gy Automation via Rube MCP + +Automate Y Gy operations through Composio's Y Gy toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/y_gy](https://composio.dev/toolkits/y_gy) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Y Gy connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `y_gy` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `y_gy` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Y Gy operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Y Gy task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["y_gy"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Y Gy-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `y_gy` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/yandex-automation/SKILL.md b/yandex-automation/SKILL.md new file mode 100644 index 0000000..fcf8783 --- /dev/null +++ b/yandex-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: yandex-automation +description: "Automate Yandex tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Yandex Automation via Rube MCP + +Automate Yandex operations through Composio's Yandex toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/yandex](https://composio.dev/toolkits/yandex) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Yandex connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `yandex` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `yandex` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Yandex operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Yandex task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["yandex"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Yandex-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `yandex` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/yelp-automation/SKILL.md b/yelp-automation/SKILL.md new file mode 100644 index 0000000..091b044 --- /dev/null +++ b/yelp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: yelp-automation +description: "Automate Yelp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Yelp Automation via Rube MCP + +Automate Yelp operations through Composio's Yelp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/yelp](https://composio.dev/toolkits/yelp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Yelp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `yelp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `yelp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Yelp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Yelp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["yelp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Yelp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `yelp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/ynab-automation/SKILL.md b/ynab-automation/SKILL.md new file mode 100644 index 0000000..ddbca2c --- /dev/null +++ b/ynab-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: ynab-automation +description: "Automate Ynab tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Ynab Automation via Rube MCP + +Automate Ynab operations through Composio's Ynab toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/ynab](https://composio.dev/toolkits/ynab) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Ynab connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ynab` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ynab` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Ynab operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Ynab task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["ynab"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Ynab-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ynab` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/yousearch-automation/SKILL.md b/yousearch-automation/SKILL.md new file mode 100644 index 0000000..1bbc056 --- /dev/null +++ b/yousearch-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: yousearch-automation +description: "Automate Yousearch tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Yousearch Automation via Rube MCP + +Automate Yousearch operations through Composio's Yousearch toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/yousearch](https://composio.dev/toolkits/yousearch) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Yousearch connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `yousearch` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `yousearch` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Yousearch operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Yousearch task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["yousearch"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Yousearch-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `yousearch` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/youtube-automation/SKILL.md b/youtube-automation/SKILL.md index 4d9d8ae..f30e3c6 100644 --- a/youtube-automation/SKILL.md +++ b/youtube-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate YouTube operations through Composio's YouTube toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/youtube](https://composio.dev/toolkits/youtube) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -216,3 +218,6 @@ Automate YouTube operations through Composio's YouTube toolkit via Rube MCP. | List subscriptions | YOUTUBE_LIST_USER_SUBSCRIPTIONS | (check schema) | | List comments | YOUTUBE_LIST_COMMENT_THREADS | videoId | | Channel activities | YOUTUBE_GET_CHANNEL_ACTIVITIES | (check schema) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zendesk-automation/SKILL.md b/zendesk-automation/SKILL.md index 92cc508..a9df20d 100644 --- a/zendesk-automation/SKILL.md +++ b/zendesk-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Zendesk operations through Composio's Zendesk toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/zendesk](https://composio.dev/toolkits/zendesk) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -213,3 +215,6 @@ new -> open -> pending -> solved -> closed | Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name | | Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name | | Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zenrows-automation/SKILL.md b/zenrows-automation/SKILL.md new file mode 100644 index 0000000..0496d94 --- /dev/null +++ b/zenrows-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zenrows-automation +description: "Automate Zenrows tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zenrows Automation via Rube MCP + +Automate Zenrows operations through Composio's Zenrows toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zenrows](https://composio.dev/toolkits/zenrows) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zenrows connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zenrows` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zenrows` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zenrows operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zenrows task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zenrows"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zenrows-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zenrows` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zenserp-automation/SKILL.md b/zenserp-automation/SKILL.md new file mode 100644 index 0000000..22fc8fc --- /dev/null +++ b/zenserp-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zenserp-automation +description: "Automate Zenserp tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zenserp Automation via Rube MCP + +Automate Zenserp operations through Composio's Zenserp toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zenserp](https://composio.dev/toolkits/zenserp) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zenserp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zenserp` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zenserp` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zenserp operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zenserp task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zenserp"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zenserp-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zenserp` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zeplin-automation/SKILL.md b/zeplin-automation/SKILL.md new file mode 100644 index 0000000..d2f9250 --- /dev/null +++ b/zeplin-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zeplin-automation +description: "Automate Zeplin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zeplin Automation via Rube MCP + +Automate Zeplin operations through Composio's Zeplin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zeplin](https://composio.dev/toolkits/zeplin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zeplin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zeplin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zeplin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zeplin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zeplin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zeplin"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zeplin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zeplin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zerobounce-automation/SKILL.md b/zerobounce-automation/SKILL.md new file mode 100644 index 0000000..a75677d --- /dev/null +++ b/zerobounce-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zerobounce-automation +description: "Automate Zerobounce tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zerobounce Automation via Rube MCP + +Automate Zerobounce operations through Composio's Zerobounce toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zerobounce](https://composio.dev/toolkits/zerobounce) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zerobounce connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zerobounce` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zerobounce` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zerobounce operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zerobounce task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zerobounce"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zerobounce-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zerobounce` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-automation/SKILL.md b/zoho-automation/SKILL.md new file mode 100644 index 0000000..44a70f5 --- /dev/null +++ b/zoho-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoho-automation +description: "Automate Zoho tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Automation via Rube MCP + +Automate Zoho operations through Composio's Zoho toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho](https://composio.dev/toolkits/zoho) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoho operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoho task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoho"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-bigin-automation/SKILL.md b/zoho-bigin-automation/SKILL.md new file mode 100644 index 0000000..32fdb8a --- /dev/null +++ b/zoho-bigin-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoho-bigin-automation +description: "Automate Zoho Bigin tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Bigin Automation via Rube MCP + +Automate Zoho Bigin operations through Composio's Zoho Bigin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_bigin](https://composio.dev/toolkits/zoho_bigin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Bigin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_bigin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_bigin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoho Bigin operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoho Bigin task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoho_bigin"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Bigin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_bigin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-books-automation/SKILL.md b/zoho-books-automation/SKILL.md new file mode 100644 index 0000000..71265fa --- /dev/null +++ b/zoho-books-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoho-books-automation +description: "Automate Zoho Books tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Books Automation via Rube MCP + +Automate Zoho Books operations through Composio's Zoho Books toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_books](https://composio.dev/toolkits/zoho_books) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Books connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_books` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_books` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoho Books operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoho Books task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoho_books"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Books-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_books` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-crm-automation/SKILL.md b/zoho-crm-automation/SKILL.md index 3771610..4a5c06f 100644 --- a/zoho-crm-automation/SKILL.md +++ b/zoho-crm-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Zoho CRM operations through Composio's Zoho toolkit via Rube MCP. +**Toolkit docs**: [composio.dev/toolkits/zoho](https://composio.dev/toolkits/zoho) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -204,3 +206,6 @@ criteria: '((Last_Name:equals:Doe)AND(Email:contains:example.com))' | Convert lead | ZOHO_CONVERT_ZOHO_LEAD | lead_id, deal, account, contact | | Create tag | ZOHO_CREATE_ZOHO_TAG | module, tag_name | | Update related records | ZOHO_UPDATE_RELATED_RECORDS | module, record_id, related_module, data | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-desk-automation/SKILL.md b/zoho-desk-automation/SKILL.md new file mode 100644 index 0000000..539f951 --- /dev/null +++ b/zoho-desk-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoho-desk-automation +description: "Automate Zoho Desk tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Desk Automation via Rube MCP + +Automate Zoho Desk operations through Composio's Zoho Desk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_desk](https://composio.dev/toolkits/zoho_desk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Desk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoho Desk operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoho Desk task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoho_desk"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Desk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-inventory-automation/SKILL.md b/zoho-inventory-automation/SKILL.md new file mode 100644 index 0000000..3400c51 --- /dev/null +++ b/zoho-inventory-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoho-inventory-automation +description: "Automate Zoho Inventory tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Inventory Automation via Rube MCP + +Automate Zoho Inventory operations through Composio's Zoho Inventory toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_inventory](https://composio.dev/toolkits/zoho_inventory) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Inventory connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_inventory` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_inventory` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoho Inventory operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoho Inventory task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoho_inventory"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Inventory-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_inventory` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-invoice-automation/SKILL.md b/zoho-invoice-automation/SKILL.md new file mode 100644 index 0000000..7e18105 --- /dev/null +++ b/zoho-invoice-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoho-invoice-automation +description: "Automate Zoho Invoice tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Invoice Automation via Rube MCP + +Automate Zoho Invoice operations through Composio's Zoho Invoice toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_invoice](https://composio.dev/toolkits/zoho_invoice) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Invoice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_invoice` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_invoice` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoho Invoice operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoho Invoice task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoho_invoice"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Invoice-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_invoice` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho-mail-automation/SKILL.md b/zoho-mail-automation/SKILL.md new file mode 100644 index 0000000..7934668 --- /dev/null +++ b/zoho-mail-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoho-mail-automation +description: "Automate Zoho Mail tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Mail Automation via Rube MCP + +Automate Zoho Mail operations through Composio's Zoho Mail toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_mail](https://composio.dev/toolkits/zoho_mail) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Mail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_mail` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_mail` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoho Mail operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoho Mail task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoho_mail"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Mail-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_mail` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoho_bigin-automation/SKILL.md b/zoho_bigin-automation/SKILL.md new file mode 100644 index 0000000..12b2cdd --- /dev/null +++ b/zoho_bigin-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: zoho_bigin-automation +description: "Automate Zoho Bigin tasks via Rube MCP (Composio): pipelines, contacts, companies, products, and small business CRM. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Bigin Automation via Rube MCP + +Automate Zoho Bigin operations through Composio's Zoho Bigin toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_bigin](https://composio.dev/toolkits/zoho_bigin) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Bigin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_bigin` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_bigin` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "pipelines, contacts, companies, products, and small business CRM", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Zoho Bigin +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Zoho Bigin Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Zoho Bigin tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Zoho Bigin Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Zoho Bigin operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Zoho Bigin connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Bigin-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_bigin` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/zoho_bigin](https://composio.dev/toolkits/zoho_bigin) diff --git a/zoho_books-automation/SKILL.md b/zoho_books-automation/SKILL.md new file mode 100644 index 0000000..b257e28 --- /dev/null +++ b/zoho_books-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: zoho_books-automation +description: "Automate Zoho Books tasks via Rube MCP (Composio): invoices, expenses, contacts, payments, and accounting. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Books Automation via Rube MCP + +Automate Zoho Books operations through Composio's Zoho Books toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_books](https://composio.dev/toolkits/zoho_books) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Books connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_books` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_books` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "invoices, expenses, contacts, payments, and accounting", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Zoho Books +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Zoho Books Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Zoho Books tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Zoho Books Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Zoho Books operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Zoho Books connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Books-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_books` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/zoho_books](https://composio.dev/toolkits/zoho_books) diff --git a/zoho_desk-automation/SKILL.md b/zoho_desk-automation/SKILL.md new file mode 100644 index 0000000..53bfc03 --- /dev/null +++ b/zoho_desk-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: zoho_desk-automation +description: "Automate Zoho Desk tasks via Rube MCP (Composio): tickets, contacts, agents, departments, and help desk operations. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Desk Automation via Rube MCP + +Automate Zoho Desk operations through Composio's Zoho Desk toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_desk](https://composio.dev/toolkits/zoho_desk) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Desk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "tickets, contacts, agents, departments, and help desk operations", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Zoho Desk +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Zoho Desk Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Zoho Desk tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Zoho Desk Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Zoho Desk operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Zoho Desk connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Desk-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/zoho_desk](https://composio.dev/toolkits/zoho_desk) diff --git a/zoho_inventory-automation/SKILL.md b/zoho_inventory-automation/SKILL.md new file mode 100644 index 0000000..0941d6c --- /dev/null +++ b/zoho_inventory-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: zoho_inventory-automation +description: "Automate Zoho Inventory tasks via Rube MCP (Composio): items, orders, warehouses, shipments, and stock management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Inventory Automation via Rube MCP + +Automate Zoho Inventory operations through Composio's Zoho Inventory toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_inventory](https://composio.dev/toolkits/zoho_inventory) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Inventory connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_inventory` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_inventory` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "items, orders, warehouses, shipments, and stock management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Zoho Inventory +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Zoho Inventory Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Zoho Inventory tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Zoho Inventory Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Zoho Inventory operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Zoho Inventory connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Inventory-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_inventory` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/zoho_inventory](https://composio.dev/toolkits/zoho_inventory) diff --git a/zoho_invoice-automation/SKILL.md b/zoho_invoice-automation/SKILL.md new file mode 100644 index 0000000..d8a4875 --- /dev/null +++ b/zoho_invoice-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: zoho_invoice-automation +description: "Automate Zoho Invoice tasks via Rube MCP (Composio): invoices, estimates, expenses, clients, and payment tracking. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Invoice Automation via Rube MCP + +Automate Zoho Invoice operations through Composio's Zoho Invoice toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_invoice](https://composio.dev/toolkits/zoho_invoice) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Invoice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_invoice` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_invoice` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "invoices, estimates, expenses, clients, and payment tracking", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Zoho Invoice +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Zoho Invoice Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Zoho Invoice tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Zoho Invoice Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Zoho Invoice operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Zoho Invoice connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Invoice-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_invoice` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/zoho_invoice](https://composio.dev/toolkits/zoho_invoice) diff --git a/zoho_mail-automation/SKILL.md b/zoho_mail-automation/SKILL.md new file mode 100644 index 0000000..bb9b6da --- /dev/null +++ b/zoho_mail-automation/SKILL.md @@ -0,0 +1,110 @@ +--- +name: zoho_mail-automation +description: "Automate Zoho Mail tasks via Rube MCP (Composio): email sending, folders, labels, and mailbox management. Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoho Mail Automation via Rube MCP + +Automate Zoho Mail operations through Composio's Zoho Mail toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoho_mail](https://composio.dev/toolkits/zoho_mail) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoho Mail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_mail` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_mail` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS: queries=[{"use_case": "email sending, folders, labels, and mailbox management", "known_fields": ""}] +``` + +This returns: +- Available tool slugs for Zoho Mail +- Recommended execution plan steps +- Known pitfalls and edge cases +- Input schemas for each tool + +## Core Workflows + +### 1. Discover Available Zoho Mail Tools + +``` +RUBE_SEARCH_TOOLS: + queries: + - use_case: "list all available Zoho Mail tools and capabilities" +``` + +Review the returned tools, their descriptions, and input schemas before proceeding. + +### 2. Execute Zoho Mail Operations + +After discovering tools, execute them via: + +``` +RUBE_MULTI_EXECUTE_TOOL: + tools: + - tool_slug: "" + arguments: {} + memory: {} + sync_response_to_workbench: false +``` + +### 3. Multi-Step Workflows + +For complex workflows involving multiple Zoho Mail operations: + +1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case +2. Execute prerequisite steps first (e.g., fetch before update) +3. Pass data between steps using tool responses +4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing + +## Common Patterns + +### Search Before Action +Always search for existing resources before creating new ones to avoid duplicates. + +### Pagination +Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted. + +### Error Handling +- Check tool responses for errors before proceeding +- If a tool fails, verify the connection is still ACTIVE +- Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired + +### Batch Operations +For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution. + +## Known Pitfalls + +- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. +- **Check connection status**: Ensure the Zoho Mail connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. +- **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. +- **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`. + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoho Mail-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_mail` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +> **Toolkit docs**: [composio.dev/toolkits/zoho_mail](https://composio.dev/toolkits/zoho_mail) diff --git a/zoom-automation/SKILL.md b/zoom-automation/SKILL.md index 2f09259..80b12d7 100644 --- a/zoom-automation/SKILL.md +++ b/zoom-automation/SKILL.md @@ -9,6 +9,8 @@ requires: Automate Zoom operations including meeting scheduling, webinar management, cloud recording retrieval, participant tracking, and usage reporting through Composio's Zoom toolkit. +**Toolkit docs**: [composio.dev/toolkits/zoom](https://composio.dev/toolkits/zoom) + ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) @@ -215,3 +217,6 @@ Most Zoom list endpoints use token-based pagination: | Register for meeting | `ZOOM_ADD_A_MEETING_REGISTRANT` | `meetingId`, participant details | | Register for webinar | `ZOOM_ADD_A_WEBINAR_REGISTRANT` | webinar ID, participant details | | List archived files | `ZOOM_LIST_ARCHIVED_FILES` | `from`, `to` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zoominfo-automation/SKILL.md b/zoominfo-automation/SKILL.md new file mode 100644 index 0000000..5504e7d --- /dev/null +++ b/zoominfo-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zoominfo-automation +description: "Automate Zoominfo tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zoominfo Automation via Rube MCP + +Automate Zoominfo operations through Composio's Zoominfo toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zoominfo](https://composio.dev/toolkits/zoominfo) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zoominfo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoominfo` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoominfo` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zoominfo operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zoominfo task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zoominfo"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zoominfo-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zoominfo` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zylvie-automation/SKILL.md b/zylvie-automation/SKILL.md new file mode 100644 index 0000000..5cc2f7f --- /dev/null +++ b/zylvie-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zylvie-automation +description: "Automate Zylvie tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zylvie Automation via Rube MCP + +Automate Zylvie operations through Composio's Zylvie toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zylvie](https://composio.dev/toolkits/zylvie) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zylvie connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zylvie` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zylvie` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zylvie operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zylvie task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zylvie"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zylvie-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zylvie` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)* diff --git a/zyte-api-automation/SKILL.md b/zyte-api-automation/SKILL.md new file mode 100644 index 0000000..a3f8e24 --- /dev/null +++ b/zyte-api-automation/SKILL.md @@ -0,0 +1,91 @@ +--- +name: zyte-api-automation +description: "Automate Zyte API tasks via Rube MCP (Composio). Always search tools first for current schemas." +requires: + mcp: [rube] +--- + +# Zyte API Automation via Rube MCP + +Automate Zyte API operations through Composio's Zyte API toolkit via Rube MCP. + +**Toolkit docs**: [composio.dev/toolkits/zyte_api](https://composio.dev/toolkits/zyte_api) + +## Prerequisites + +- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) +- Active Zyte API connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zyte_api` +- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas + +## Setup + +**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. + +1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds +2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zyte_api` +3. If connection is not ACTIVE, follow the returned auth link to complete setup +4. Confirm connection status shows ACTIVE before running any workflows + +## Tool Discovery + +Always discover available tools before executing workflows: + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "Zyte API operations", known_fields: ""}] +session: {generate_id: true} +``` + +This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls. + +## Core Workflow Pattern + +### Step 1: Discover Available Tools + +``` +RUBE_SEARCH_TOOLS +queries: [{use_case: "your specific Zyte API task"}] +session: {id: "existing_session_id"} +``` + +### Step 2: Check Connection + +``` +RUBE_MANAGE_CONNECTIONS +toolkits: ["zyte_api"] +session_id: "your_session_id" +``` + +### Step 3: Execute Tools + +``` +RUBE_MULTI_EXECUTE_TOOL +tools: [{ + tool_slug: "TOOL_SLUG_FROM_SEARCH", + arguments: {/* schema-compliant args from search results */} +}] +memory: {} +session_id: "your_session_id" +``` + +## Known Pitfalls + +- **Always search first**: Tool schemas change. Never hardcode tool slugs or arguments without calling `RUBE_SEARCH_TOOLS` +- **Check connection**: Verify `RUBE_MANAGE_CONNECTIONS` shows ACTIVE status before executing tools +- **Schema compliance**: Use exact field names and types from the search results +- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, even if empty (`{}`) +- **Session reuse**: Reuse session IDs within a workflow. Generate new ones for new workflows +- **Pagination**: Check responses for pagination tokens and continue fetching until complete + +## Quick Reference + +| Operation | Approach | +|-----------|----------| +| Find tools | `RUBE_SEARCH_TOOLS` with Zyte API-specific use case | +| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `zyte_api` | +| Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | +| Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | +| Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` | + +--- +*Powered by [Composio](https://composio.dev)*