-
+
@@ -36,8 +36,42 @@
A curated list of practical Claude Skills for enhancing productivity across Claude.ai, Claude Code, and the Claude API.
-> If you want your skills to take actions across 500+ apps, wire them up with [Composio](https://platform.composio.dev/?utm_source=Github&utm_medium=Youtube&utm_campaign=2025-11&utm_content=AwesomeSkills)
+> **Want skills that do more than generate text?** Claude can send emails, create issues, post to Slack, and take actions across 1000+ apps. [See how →](./connect/)
+---
+
+## Quickstart: Connect Claude to 500+ Apps
+
+The **connect-apps** plugin lets Claude perform real actions - send emails, create issues, post to Slack. It handles auth and connects to 500+ apps using Composio under the hood.
+
+### 1. Install the Plugin
+
+```bash
+claude --plugin-dir ./connect-apps-plugin
+```
+
+### 2. Run Setup
+
+```
+/connect-apps:setup
+```
+
+Paste your API key when asked. (Get a free key at [platform.composio.dev](https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills))
+
+### 3. Restart & Try It
+
+```bash
+exit
+claude
+```
+
+> **Want skills that do more than generate text?** Claude can send emails, create issues, post to Slack, and take actions across 1000+ apps. [See how →](./connect/)
+
+If you receive the email, Claude is now connected to 500+ apps.
+
+**[See all supported apps →](https://composio.dev/toolkits)**
+
+---
## Contents
@@ -52,6 +86,7 @@ A curated list of practical Claude Skills for enhancing productivity across Clau
- [Productivity & Organization](#productivity--organization)
- [Collaboration & Project Management](#collaboration--project-management)
- [Security & Systems](#security--systems)
+ - [App Automation via Composio](#app-automation-via-composio)
- [Getting Started](#getting-started)
- [Creating Skills](#creating-skills)
- [Contributing](#contributing)
@@ -74,7 +109,7 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
### Development & Code Tools
-- [artifacts-builder](https://github.com/anthropics/skills/tree/main/web-artifacts-builder) - Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
+- [artifacts-builder](https://github.com/anthropics/skills/tree/main/skills/web-artifacts-builder) - Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
- [aws-skills](https://github.com/zxkane/aws-skills) - AWS development with CDK best practices, cost optimization MCP servers, and serverless/event-driven architecture patterns.
- [Changelog Generator](./changelog-generator/) - Automatically creates user-facing changelogs from git commits by analyzing history and transforming technical commits into customer-friendly release notes.
- [Claude Code Terminal Title](https://github.com/bluzername/claude-code-terminal-title) - Gives each Claud-Code terminal window a dynamic title that describes the work being done so you don't lose track of what window is doing what.
@@ -82,22 +117,27 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
- [FFUF Web Fuzzing](https://github.com/jthack/ffuf_claude_skill) - Integrates the ffuf web fuzzer so Claude can run fuzzing tasks and analyze results for vulnerabilities. *By [@jthack](https://github.com/jthack)*
- [finishing-a-development-branch](https://github.com/obra/superpowers/tree/main/skills/finishing-a-development-branch) - Guides completion of development work by presenting clear options and handling chosen workflow.
- [iOS Simulator](https://github.com/conorluddy/ios-simulator-skill) - Enables Claude to interact with iOS Simulator for testing and debugging iOS applications. *By [@conorluddy](https://github.com/conorluddy)*
+- [jules](https://github.com/sanjay3290/ai-skills/tree/main/skills/jules) - Delegate coding tasks to Google Jules AI agent for async bug fixes, documentation, tests, and feature implementation on GitHub repos. *By [@sanjay3290](https://github.com/sanjay3290)*
+- [LangSmith Fetch](./langsmith-fetch/) - Debug LangChain and LangGraph agents by automatically fetching and analyzing execution traces from LangSmith Studio. First AI observability skill for Claude Code. *By [@OthmanAdi](https://github.com/OthmanAdi)*
- [MCP Builder](./mcp-builder/) - Guides creation of high-quality MCP (Model Context Protocol) servers for integrating external APIs and services with LLMs using Python or TypeScript.
- [move-code-quality-skill](https://github.com/1NickPappas/move-code-quality-skill) - Analyzes Move language packages against the official Move Book Code Quality Checklist for Move 2024 Edition compliance and best practices.
- [Playwright Browser Automation](https://github.com/lackeyjb/playwright-skill) - Model-invoked Playwright automation for testing and validating web applications. *By [@lackeyjb](https://github.com/lackeyjb)*
- [prompt-engineering](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/customaize-agent/skills/prompt-engineering) - Teaches well-known prompt engineering techniques and patterns, including Anthropic best practices and agent persuasion principles.
- [pypict-claude-skill](https://github.com/omkamal/pypict-claude-skill) - Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for requirements or code, generating optimized test suites with pairwise coverage.
+- [reddit-fetch](https://github.com/ykdojo/claude-code-tips/tree/main/skills/reddit-fetch) - Fetches Reddit content via Gemini CLI when WebFetch is blocked or returns 403 errors.
- [Skill Creator](./skill-creator/) - Provides guidance for creating effective Claude Skills that extend capabilities with specialized knowledge, workflows, and tool integrations.
- [Skill Seekers](https://github.com/yusufkaraaslan/Skill_Seekers) - Automatically converts any documentation website into a Claude AI skill in minutes. *By [@yusufkaraaslan](https://github.com/yusufkaraaslan)*
- [software-architecture](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/ddd/skills/software-architecture) - Implements design patterns including Clean Architecture, SOLID principles, and comprehensive software design best practices.
- [subagent-driven-development](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/sadd/skills/subagent-driven-development) - Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.
- [test-driven-development](https://github.com/obra/superpowers/tree/main/skills/test-driven-development) - Use when implementing any feature or bugfix, before writing implementation code.
- [using-git-worktrees](https://github.com/obra/superpowers/blob/main/skills/using-git-worktrees/) - Creates isolated git worktrees with smart directory selection and safety verification.
+- [Connect](./connect/) - Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
- [Webapp Testing](./webapp-testing/) - Tests local web applications using Playwright for verifying frontend functionality, debugging UI behavior, and capturing screenshots.
### Data & Analysis
- [CSV Data Summarizer](https://github.com/coffeefuelbump/csv-data-summarizer-claude-skill) - Automatically analyzes CSV files and generates comprehensive insights with visualizations without requiring user prompts. *By [@coffeefuelbump](https://github.com/coffeefuelbump)*
+- [deep-research](https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research) - Execute autonomous multi-step research using Gemini Deep Research Agent for market analysis, competitive landscaping, and literature reviews. *By [@sanjay3290](https://github.com/sanjay3290)*
- [postgres](https://github.com/sanjay3290/ai-skills/tree/main/skills/postgres) - Execute safe read-only SQL queries against PostgreSQL databases with multi-connection support and defense-in-depth security. *By [@sanjay3290](https://github.com/sanjay3290)*
- [root-cause-tracing](https://github.com/obra/superpowers/tree/main/skills/root-cause-tracing) - Use when errors occur deep in execution and you need to trace back to find the original trigger.
@@ -117,6 +157,7 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
- [family-history-research](https://github.com/emaynard/claude-family-history-research-skill) - Provides assistance with planning family history and genealogy research projects.
- [Meeting Insights Analyzer](./meeting-insights-analyzer/) - Analyzes meeting transcripts to uncover behavioral patterns including conflict avoidance, speaking ratios, filler words, and leadership style.
- [NotebookLM Integration](https://github.com/PleasePrompto/notebooklm-skill) - Lets Claude Code chat directly with NotebookLM for source-grounded answers based exclusively on uploaded documents. *By [@PleasePrompto](https://github.com/PleasePrompto)*
+- [Twitter Algorithm Optimizer](./twitter-algorithm-optimizer/) - Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit tweets to improve engagement and visibility.
### Creative & Media
@@ -135,12 +176,15 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
- [kaizen](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/kaizen/skills/kaizen) - Applies continuous improvement methodology with multiple analytical approaches, based on Japanese Kaizen philosophy and Lean methodology.
- [n8n-skills](https://github.com/haunchen/n8n-skills) - Enables AI assistants to directly understand and operate n8n workflows.
- [Raffle Winner Picker](./raffle-winner-picker/) - Randomly selects winners from lists, spreadsheets, or Google Sheets for giveaways and contests with cryptographically secure randomness.
+- [Tailored Resume Generator](./tailored-resume-generator/) - Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances.
- [ship-learn-next](https://github.com/michalparkola/tapestry-skills-for-claude-code/tree/main/ship-learn-next) - Skill to help iterate on what to build or learn next, based on feedback loops.
- [tapestry](https://github.com/michalparkola/tapestry-skills-for-claude-code/tree/main/tapestry) - Interlink and summarize related documents into knowledge networks.
### Collaboration & Project Management
- [git-pushing](https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/git-pushing) - Automate git operations and repository interactions.
+- [google-workspace-skills](https://github.com/sanjay3290/ai-skills/tree/main/skills) - Suite of Google Workspace integrations: Gmail, Calendar, Chat, Docs, Sheets, Slides, and Drive with cross-platform OAuth. *By [@sanjay3290](https://github.com/sanjay3290)*
+- [outline](https://github.com/sanjay3290/ai-skills/tree/main/skills/outline) - Search, read, create, and manage documents in Outline wiki instances (cloud or self-hosted). *By [@sanjay3290](https://github.com/sanjay3290)*
- [review-implementing](https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/review-implementing) - Evaluate code implementation plans and align with specs.
- [test-fixing](https://github.com/mhattingpete/claude-skills-marketplace/tree/main/engineering-workflow-plugin/skills/test-fixing) - Detect failing tests and propose patches or fixes.
@@ -151,6 +195,122 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
- [metadata-extraction](https://github.com/mhattingpete/claude-skills-marketplace/tree/main/computer-forensics-skills/skills/metadata-extraction) - Extract and analyze file metadata for forensic purposes.
- [threat-hunting-with-sigma-rules](https://github.com/jthack/threat-hunting-with-sigma-rules-skill) - Use Sigma detection rules to hunt for threats and analyze security events.
+### App Automation via Composio
+
+Pre-built workflow skills for 78 SaaS apps via [Rube MCP (Composio)](https://composio.dev). Each skill includes tool sequences, parameter guidance, known pitfalls, and quick reference tables — all using real tool slugs discovered from Composio's API.
+
+**CRM & Sales**
+- [Close Automation](./close-automation/) - Automate Close CRM: leads, contacts, opportunities, activities, and pipelines.
+- [HubSpot Automation](./hubspot-automation/) - Automate HubSpot CRM: contacts, deals, companies, tickets, and email engagement.
+- [Pipedrive Automation](./pipedrive-automation/) - Automate Pipedrive: deals, contacts, organizations, activities, and pipelines.
+- [Salesforce Automation](./salesforce-automation/) - Automate Salesforce: objects, records, SOQL queries, and bulk operations.
+- [Zoho CRM Automation](./zoho-crm-automation/) - Automate Zoho CRM: leads, contacts, deals, accounts, and modules.
+
+**Project Management**
+- [Asana Automation](./asana-automation/) - Automate Asana: tasks, projects, sections, assignments, and workspaces.
+- [Basecamp Automation](./basecamp-automation/) - Automate Basecamp: to-do lists, messages, people, groups, and projects.
+- [ClickUp Automation](./clickup-automation/) - Automate ClickUp: tasks, lists, spaces, goals, and time tracking.
+- [Jira Automation](./jira-automation/) - Automate Jira: issues, projects, boards, sprints, and JQL queries.
+- [Linear Automation](./linear-automation/) - Automate Linear: issues, projects, cycles, teams, and workflows.
+- [Monday Automation](./monday-automation/) - Automate Monday.com: boards, items, columns, groups, and workspaces.
+- [Notion Automation](./notion-automation/) - Automate Notion: pages, databases, blocks, comments, and search.
+- [Todoist Automation](./todoist-automation/) - Automate Todoist: tasks, projects, sections, labels, and filters.
+- [Trello Automation](./trello-automation/) - Automate Trello: boards, cards, lists, members, and checklists.
+- [Wrike Automation](./wrike-automation/) - Automate Wrike: tasks, folders, projects, comments, and workflows.
+
+**Communication**
+- [Discord Automation](./discord-automation/) - Automate Discord: messages, channels, servers, roles, and reactions.
+- [Intercom Automation](./intercom-automation/) - Automate Intercom: conversations, contacts, companies, tickets, and articles.
+- [Microsoft Teams Automation](./microsoft-teams-automation/) - Automate Teams: messages, channels, teams, chats, and meetings.
+- [Slack Automation](./slack-automation/) - Automate Slack: messages, channels, search, reactions, threads, and scheduling.
+- [Telegram Automation](./telegram-automation/) - Automate Telegram: messages, chats, media, groups, and bots.
+- [WhatsApp Automation](./whatsapp-automation/) - Automate WhatsApp: messages, media, templates, groups, and business profiles.
+
+**Email**
+- [Gmail Automation](./gmail-automation/) - Automate Gmail: send/reply, search, labels, drafts, and attachments.
+- [Outlook Automation](./outlook-automation/) - Automate Outlook: emails, folders, contacts, and calendar integration.
+- [Postmark Automation](./postmark-automation/) - Automate Postmark: transactional emails, templates, servers, and delivery stats.
+- [SendGrid Automation](./sendgrid-automation/) - Automate SendGrid: emails, templates, contacts, lists, and campaign stats.
+
+**Code & DevOps**
+- [Bitbucket Automation](./bitbucket-automation/) - Automate Bitbucket: repos, PRs, branches, issues, and workspaces.
+- [CircleCI Automation](./circleci-automation/) - Automate CircleCI: pipelines, workflows, jobs, and project configuration.
+- [Datadog Automation](./datadog-automation/) - Automate Datadog: monitors, dashboards, metrics, incidents, and alerts.
+- [GitHub Automation](./github-automation/) - Automate GitHub: issues, PRs, repos, branches, actions, and code search.
+- [GitLab Automation](./gitlab-automation/) - Automate GitLab: issues, MRs, projects, pipelines, and branches.
+- [PagerDuty Automation](./pagerduty-automation/) - Automate PagerDuty: incidents, services, schedules, escalation policies, and on-call.
+- [Render Automation](./render-automation/) - Automate Render: services, deploys, and project management.
+- [Sentry Automation](./sentry-automation/) - Automate Sentry: issues, events, projects, releases, and alerts.
+- [Supabase Automation](./supabase-automation/) - Automate Supabase: SQL queries, table schemas, edge functions, and storage.
+- [Vercel Automation](./vercel-automation/) - Automate Vercel: deployments, projects, domains, environment variables, and logs.
+
+**Storage & Files**
+- [Box Automation](./box-automation/) - Automate Box: files, folders, search, sharing, collaborations, and sign requests.
+- [Dropbox Automation](./dropbox-automation/) - Automate Dropbox: files, folders, search, sharing, and batch operations.
+- [Google Drive Automation](./google-drive-automation/) - Automate Google Drive: upload, download, search, share, and organize files.
+- [OneDrive Automation](./one-drive-automation/) - Automate OneDrive: files, folders, search, sharing, permissions, and versioning.
+
+**Spreadsheets & Databases**
+- [Airtable Automation](./airtable-automation/) - Automate Airtable: records, tables, bases, views, and field management.
+- [Coda Automation](./coda-automation/) - Automate Coda: docs, tables, rows, formulas, and automations.
+- [Google Sheets Automation](./googlesheets-automation/) - Automate Google Sheets: read/write cells, formatting, formulas, and batch operations.
+
+**Calendar & Scheduling**
+- [Cal.com Automation](./cal-com-automation/) - Automate Cal.com: event types, bookings, availability, and scheduling.
+- [Calendly Automation](./calendly-automation/) - Automate Calendly: events, invitees, event types, scheduling links, and availability.
+- [Google Calendar Automation](./google-calendar-automation/) - Automate Google Calendar: events, attendees, free/busy, and recurring schedules.
+- [Outlook Calendar Automation](./outlook-calendar-automation/) - Automate Outlook Calendar: events, attendees, reminders, and recurring schedules.
+
+**Social Media**
+- [Instagram Automation](./instagram-automation/) - Automate Instagram: posts, stories, comments, media, and business insights.
+- [LinkedIn Automation](./linkedin-automation/) - Automate LinkedIn: posts, profiles, companies, images, and comments.
+- [Reddit Automation](./reddit-automation/) - Automate Reddit: posts, comments, subreddits, voting, and moderation.
+- [TikTok Automation](./tiktok-automation/) - Automate TikTok: video uploads, queries, and creator management.
+- [Twitter Automation](./twitter-automation/) - Automate Twitter/X: tweets, search, users, lists, and engagement.
+- [YouTube Automation](./youtube-automation/) - Automate YouTube: videos, channels, playlists, comments, and subscriptions.
+
+**Marketing & Email Marketing**
+- [ActiveCampaign Automation](./activecampaign-automation/) - Automate ActiveCampaign: contacts, deals, campaigns, lists, and automations.
+- [Brevo Automation](./brevo-automation/) - Automate Brevo: contacts, email campaigns, transactional emails, and lists.
+- [ConvertKit Automation](./convertkit-automation/) - Automate ConvertKit (Kit): subscribers, tags, sequences, broadcasts, and forms.
+- [Klaviyo Automation](./klaviyo-automation/) - Automate Klaviyo: profiles, lists, segments, campaigns, and events.
+- [Mailchimp Automation](./mailchimp-automation/) - Automate Mailchimp: audiences, campaigns, templates, segments, and reports.
+
+**Support & Helpdesk**
+- [Freshdesk Automation](./freshdesk-automation/) - Automate Freshdesk: tickets, contacts, agents, groups, and canned responses.
+- [Freshservice Automation](./freshservice-automation/) - Automate Freshservice: tickets, assets, changes, problems, and service catalog.
+- [Help Scout Automation](./helpdesk-automation/) - Automate Help Scout: conversations, customers, mailboxes, and tags.
+- [Zendesk Automation](./zendesk-automation/) - Automate Zendesk: tickets, users, organizations, search, and macros.
+
+**E-commerce & Payments**
+- [Shopify Automation](./shopify-automation/) - Automate Shopify: products, orders, customers, inventory, and GraphQL queries.
+- [Square Automation](./square-automation/) - Automate Square: payments, customers, catalog, orders, and locations.
+- [Stripe Automation](./stripe-automation/) - Automate Stripe: charges, customers, products, subscriptions, and refunds.
+
+**Design & Collaboration**
+- [Canva Automation](./canva-automation/) - Automate Canva: designs, templates, assets, folders, and brand kits.
+- [Confluence Automation](./confluence-automation/) - Automate Confluence: pages, spaces, search, CQL, labels, and versions.
+- [DocuSign Automation](./docusign-automation/) - Automate DocuSign: envelopes, templates, signing, and document management.
+- [Figma Automation](./figma-automation/) - Automate Figma: files, components, comments, projects, and team management.
+- [Miro Automation](./miro-automation/) - Automate Miro: boards, sticky notes, shapes, connectors, and items.
+- [Webflow Automation](./webflow-automation/) - Automate Webflow: CMS collections, items, sites, publishing, and assets.
+
+**Analytics & Data**
+- [Amplitude Automation](./amplitude-automation/) - Automate Amplitude: events, cohorts, user properties, and analytics queries.
+- [Google Analytics Automation](./google-analytics-automation/) - Automate Google Analytics: reports, dimensions, metrics, and property management.
+- [Mixpanel Automation](./mixpanel-automation/) - Automate Mixpanel: events, funnels, cohorts, annotations, and JQL queries.
+- [PostHog Automation](./posthog-automation/) - Automate PostHog: events, persons, feature flags, insights, and annotations.
+- [Segment Automation](./segment-automation/) - Automate Segment: sources, destinations, tracking, and warehouse connections.
+
+**HR & People**
+- [BambooHR Automation](./bamboohr-automation/) - Automate BambooHR: employees, time off, reports, and directory management.
+
+**Automation Platforms**
+- [Make Automation](./make-automation/) - Automate Make (Integromat): scenarios, connections, and execution management.
+
+**Zoom & Meetings**
+- [Zoom Automation](./zoom-automation/) - Automate Zoom: meetings, recordings, participants, webinars, and reports.
+
## Getting Started
### Using Skills in Claude.ai
@@ -288,9 +448,21 @@ We welcome contributions! Please read our [Contributing Guidelines](CONTRIBUTING
## Join the Community
-- Have questions about integrating Composio with your auth setup? [Hop on a quick call with us](https://calendly.com/thomas-composio/composio-enterprise-setup)
-- [Follow us on Twitter](https://x.com/composio)
-- [Join our Discord](https://discord.com/invite/composio)
+- [Join our Discord](https://discord.com/invite/composio) - Chat with other developers building Claude Skills
+- [Follow on Twitter/X](https://x.com/composio) - Stay updated on new skills and features
+- Questions? [support@composio.dev](mailto:support@composio.dev)
+
+---
+
+
+ Join 20,000+ developers building agents that ship +
+ +
+
+ 
`, `
`, ``, ``, `- `
+- Tables: `
` / ` ` structure
+- Macros: `` for code blocks, etc.
+- Always wrap content in proper XHTML tags
+
+## Known Pitfalls
+
+### ID Formats
+- Space IDs are numeric (e.g., `557060`); space keys are short strings (e.g., `DOCS`)
+- Page IDs are numeric long values for GET_PAGE_BY_ID; some tools accept UUID format
+- `GET_SPACE_BY_ID` requires numeric ID, not the space key
+- `GET_PAGE_BY_ID` takes an integer, not a string
+
+### Rate Limits
+- HTTP 429 can occur on search endpoints; honor Retry-After header
+- Throttle to ~2 requests/second with exponential backoff and jitter
+- Body expansion in CQL_SEARCH reduces result limits to 25-50
+
+### Content Format
+- Content must be Confluence storage format (XHTML), not Markdown or plain text
+- Invalid XHTML will cause page creation/update to fail
+- `CREATE_PAGE` nests body under `body.storage.value`; `UPDATE_PAGE` uses `body.value` + `body.representation`
+
+### Version Conflicts
+- Updates require exact next version number (current + 1)
+- Concurrent edits can cause version conflicts; always fetch current version immediately before updating
+- Title changes during update must still be unique within the space
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List spaces | `CONFLUENCE_GET_SPACES` | `type`, `status`, `limit` |
+| Get space by ID | `CONFLUENCE_GET_SPACE_BY_ID` | `id` |
+| Create space | `CONFLUENCE_CREATE_SPACE` | `key`, `name`, `type` |
+| Space contents | `CONFLUENCE_GET_SPACE_CONTENTS` | `spaceKey`, `type`, `status` |
+| Space properties | `CONFLUENCE_GET_SPACE_PROPERTIES` | `id`, `key` |
+| Search content | `CONFLUENCE_SEARCH_CONTENT` | `query`, `spaceKey`, `limit` |
+| CQL search | `CONFLUENCE_CQL_SEARCH` | `cql`, `expand`, `limit` |
+| List pages | `CONFLUENCE_GET_PAGES` | `spaceId`, `sort`, `limit` |
+| Get page by ID | `CONFLUENCE_GET_PAGE_BY_ID` | `id` (integer) |
+| Create page | `CONFLUENCE_CREATE_PAGE` | `title`, `spaceId`, `body` |
+| Update page | `CONFLUENCE_UPDATE_PAGE` | `id`, `title`, `body`, `version` |
+| Delete page | `CONFLUENCE_DELETE_PAGE` | `id` |
+| Child pages | `CONFLUENCE_GET_CHILD_PAGES` | `id`, `limit`, `sort` |
+| Page ancestors | `CONFLUENCE_GET_PAGE_ANCESTORS` | `id` |
+| Page labels | `CONFLUENCE_GET_LABELS_FOR_PAGE` | `id` |
+| 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/plugins/awesome-claude-skills/connect-apps-plugin/.claude-plugin/plugin.json b/plugins/awesome-claude-skills/connect-apps-plugin/.claude-plugin/plugin.json
new file mode 100644
index 0000000..2055b15
--- /dev/null
+++ b/plugins/awesome-claude-skills/connect-apps-plugin/.claude-plugin/plugin.json
@@ -0,0 +1,8 @@
+{
+ "name": "connect-apps",
+ "description": "Manage auth and connect to 500+ apps using Composio. Perform real actions from Claude Code - send emails, create issues, post messages, and more.",
+ "author": {
+ "name": "Composio",
+ "email": "support@composio.dev"
+ }
+}
diff --git a/plugins/awesome-claude-skills/connect-apps-plugin/README.md b/plugins/awesome-claude-skills/connect-apps-plugin/README.md
new file mode 100644
index 0000000..d4977c9
--- /dev/null
+++ b/plugins/awesome-claude-skills/connect-apps-plugin/README.md
@@ -0,0 +1,47 @@
+# Connect Apps Plugin
+
+Let Claude perform real actions in 500+ apps. Handles auth and connections using Composio under the hood.
+
+## Install
+
+```bash
+claude --plugin-dir ./connect-apps-plugin
+```
+
+Then run the setup:
+```
+/connect-apps:setup
+```
+
+## What You Get
+
+Once installed, Claude can:
+- **Send emails** via Gmail, Outlook
+- **Create issues** on GitHub, GitLab, Jira, Linear
+- **Post messages** to Slack, Discord, Teams
+- **Update docs** in Notion, Google Docs
+- **Manage data** in Sheets, Airtable, databases
+- **And 500+ more actions**
+
+## How It Works
+
+1. Get a free API key from [platform.composio.dev](https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills)
+2. Run `/connect-apps:setup` and paste your key
+3. Restart Claude Code
+4. First time using an app, you'll authorize via OAuth
+5. That's it - Claude can now take real actions
+
+## Try It
+
+After setup, ask Claude:
+```
+Send me a test email at myemail@example.com
+```
+
+---
+
+
+
+ 
+
+
diff --git a/plugins/awesome-claude-skills/connect-apps-plugin/commands/setup.md b/plugins/awesome-claude-skills/connect-apps-plugin/commands/setup.md
new file mode 100644
index 0000000..f9b33cc
--- /dev/null
+++ b/plugins/awesome-claude-skills/connect-apps-plugin/commands/setup.md
@@ -0,0 +1,67 @@
+---
+description: Set up connect-apps - let Claude perform real actions in 500+ apps
+allowed-tools: [Bash, Write, AskUserQuestion]
+---
+
+# Connect Apps Setup
+
+Set up the connect-apps plugin so Claude can take real actions in external apps (Gmail, Slack, GitHub, etc). Uses Composio for auth and app connections.
+
+## Instructions
+
+### Step 1: Ask for API Key
+
+Ask the user for their Composio API key. If they don't have one, tell them to get a free key at: https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills
+
+Just ask for the key directly. Don't ask if they have one first.
+
+### Step 2: Validate & Get MCP URL
+
+Run this command (replace API_KEY_HERE with the actual key):
+
+```bash
+/opt/homebrew/bin/python3.11 -c "
+from composio import Composio
+composio = Composio(api_key='API_KEY_HERE')
+session = composio.create(user_id='claude_user')
+print(session.mcp.url)
+"
+```
+
+If it fails with import error, first run: `pip3 install composio`
+
+### Step 3: Write Config
+
+Write directly to `~/.mcp.json` with this exact format:
+
+```json
+{
+ "connect-apps": {
+ "type": "http",
+ "url": "THE_MCP_URL_FROM_STEP_2",
+ "headers": {
+ "x-api-key": "THE_API_KEY"
+ }
+ }
+}
+```
+
+If ~/.mcp.json already exists with other servers, merge the "connect-apps" key into the existing JSON.
+
+### Step 4: Confirm
+
+Tell the user:
+```
+Setup complete!
+
+To activate: exit and run `claude` again
+
+Then try: "Send me a test email at your@email.com"
+```
+
+## Important
+
+- Do NOT try to edit settings.local.json - MCP servers go in ~/.mcp.json
+- Do NOT search for config locations - just write to ~/.mcp.json
+- Do NOT ask multiple questions - just ask for the API key once
+- Be fast - this should take under 30 seconds
diff --git a/plugins/awesome-claude-skills/connect-apps/SKILL.md b/plugins/awesome-claude-skills/connect-apps/SKILL.md
new file mode 100644
index 0000000..094c77d
--- /dev/null
+++ b/plugins/awesome-claude-skills/connect-apps/SKILL.md
@@ -0,0 +1,80 @@
+---
+name: connect-apps
+description: Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.
+---
+
+# Connect Apps
+
+Connect Claude to 1000+ apps. Actually send emails, create issues, post messages - not just generate text about it.
+
+## Quick Start
+
+### Step 1: Install the Plugin
+
+```
+/plugin install composio-toolrouter
+```
+
+### Step 2: Run Setup
+
+```
+/composio-toolrouter:setup
+```
+
+This will:
+- Ask for your free API key (get one at [platform.composio.dev](https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills))
+- Configure Claude's connection to 1000+ apps
+- Take about 60 seconds
+
+### Step 3: Try It!
+
+After setup, restart Claude Code and try:
+
+```
+Send me a test email at YOUR_EMAIL@example.com
+```
+
+If it works, you're connected!
+
+## What You Can Do
+
+| Ask Claude to... | What happens |
+|------------------|--------------|
+| "Send email to sarah@acme.com about the launch" | Actually sends the email |
+| "Create GitHub issue: fix login bug" | Creates the issue |
+| "Post to Slack #general: deploy complete" | Posts the message |
+| "Add meeting notes to Notion" | Adds to Notion |
+
+## Supported Apps
+
+**Email:** Gmail, Outlook, SendGrid
+**Chat:** Slack, Discord, Teams, Telegram
+**Dev:** GitHub, GitLab, Jira, Linear
+**Docs:** Notion, Google Docs, Confluence
+**Data:** Sheets, Airtable, PostgreSQL
+**And 1000+ more...**
+
+## How It Works
+
+1. You ask Claude to do something
+2. Composio Tool Router finds the right tool
+3. First time? You'll authorize via OAuth (one-time)
+4. Action executes and returns result
+
+## Troubleshooting
+
+- **"Plugin not found"** → Make sure you ran `/plugin install composio-toolrouter`
+- **"Need to authorize"** → Click the OAuth link Claude provides, then say "done"
+- **Action failed** → Check you have permissions in the target app
+
+---
+
+
+ Join 20,000+ developers building agents that ship
+
+
+
+
+
+
+
diff --git a/plugins/awesome-claude-skills/connect/SKILL.md b/plugins/awesome-claude-skills/connect/SKILL.md
new file mode 100644
index 0000000..14e8164
--- /dev/null
+++ b/plugins/awesome-claude-skills/connect/SKILL.md
@@ -0,0 +1,156 @@
+---
+name: connect
+description: Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
+---
+
+# Connect
+
+Connect Claude to any app. Stop generating text about what you could do - actually do it.
+
+## When to Use This Skill
+
+Use this skill when you need Claude to:
+
+- **Send that email** instead of drafting it
+- **Create that issue** instead of describing it
+- **Post that message** instead of suggesting it
+- **Update that database** instead of explaining how
+
+## What Changes
+
+| Without Connect | With Connect |
+|-----------------|--------------|
+| "Here's a draft email..." | Sends the email |
+| "You should create an issue..." | Creates the issue |
+| "Post this to Slack..." | Posts it |
+| "Add this to Notion..." | Adds it |
+
+## Supported Apps
+
+**1000+ integrations** including:
+
+- **Email:** Gmail, Outlook, SendGrid
+- **Chat:** Slack, Discord, Teams, Telegram
+- **Dev:** GitHub, GitLab, Jira, Linear
+- **Docs:** Notion, Google Docs, Confluence
+- **Data:** Sheets, Airtable, PostgreSQL
+- **CRM:** HubSpot, Salesforce, Pipedrive
+- **Storage:** Drive, Dropbox, S3
+- **Social:** Twitter, LinkedIn, Reddit
+
+## Setup
+
+### 1. Get API Key
+
+Get your free key at [platform.composio.dev](https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills)
+
+### 2. Set Environment Variable
+
+```bash
+export COMPOSIO_API_KEY="your-key"
+```
+
+### 3. Install
+
+```bash
+pip install composio # Python
+npm install @composio/core # TypeScript
+```
+
+Done. Claude can now connect to any app.
+
+## Examples
+
+### Send Email
+```
+Email sarah@acme.com - Subject: "Shipped!" Body: "v2.0 is live, let me know if issues"
+```
+
+### Create GitHub Issue
+```
+Create issue in my-org/repo: "Mobile timeout bug" with label:bug
+```
+
+### Post to Slack
+```
+Post to #engineering: "Deploy complete - v2.4.0 live"
+```
+
+### Chain Actions
+```
+Find GitHub issues labeled "bug" from this week, summarize, post to #bugs on Slack
+```
+
+## How It Works
+
+Uses Composio Tool Router:
+
+1. **You ask** Claude to do something
+2. **Tool Router finds** the right tool (1000+ options)
+3. **OAuth handled** automatically
+4. **Action executes** and returns result
+
+### Code
+
+```python
+from composio import Composio
+from claude_agent_sdk.client import ClaudeSDKClient
+from claude_agent_sdk.types import ClaudeAgentOptions
+import os
+
+composio = Composio(api_key=os.environ["COMPOSIO_API_KEY"])
+session = composio.create(user_id="user_123")
+
+options = ClaudeAgentOptions(
+ system_prompt="You can take actions in external apps.",
+ mcp_servers={
+ "composio": {
+ "type": "http",
+ "url": session.mcp.url,
+ "headers": {"x-api-key": os.environ["COMPOSIO_API_KEY"]},
+ }
+ },
+)
+
+async with ClaudeSDKClient(options) as client:
+ await client.query("Send Slack message to #general: Hello!")
+```
+
+## Auth Flow
+
+First time using an app:
+```
+To send emails, I need Gmail access.
+Authorize here: https://...
+Say "connected" when done.
+```
+
+Connection persists after that.
+
+## Framework Support
+
+| Framework | Install |
+|-----------|---------|
+| Claude Agent SDK | `pip install composio claude-agent-sdk` |
+| OpenAI Agents | `pip install composio openai-agents` |
+| Vercel AI | `npm install @composio/core @composio/vercel` |
+| LangChain | `pip install composio-langchain` |
+| Any MCP Client | Use `session.mcp.url` |
+
+## Troubleshooting
+
+- **Auth required** → Click link, authorize, say "connected"
+- **Action failed** → Check permissions in target app
+- **Tool not found** → Be specific: "Slack #general" not "send message"
+
+---
+
+
+ Join 20,000+ developers building agents that ship
+
+
+
+
+
+
+
diff --git a/plugins/awesome-claude-skills/connecteam-automation/SKILL.md b/plugins/awesome-claude-skills/connecteam-automation/SKILL.md
new file mode 100644
index 0000000..0c052a2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/contentful-automation/SKILL.md b/plugins/awesome-claude-skills/contentful-automation/SKILL.md
new file mode 100644
index 0000000..df0e0ff
--- /dev/null
+++ b/plugins/awesome-claude-skills/contentful-automation/SKILL.md
@@ -0,0 +1,106 @@
+---
+name: Contentful Automation
+description: "Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Contentful Automation
+
+Manage your **Contentful** headless CMS spaces directly from Claude Code. List spaces, retrieve metadata, and update space configurations without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/contentful](https://composio.dev/toolkits/contentful)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Contentful account when prompted. The agent will provide an authentication link. Ensure your access token has space management scopes.
+
+---
+
+## Core Workflows
+
+### 1. List All Spaces
+
+Discover all Contentful spaces accessible to your authenticated account. This is typically the first operation since most other actions require a `space_id`.
+
+**Tool:** `CONTENTFUL_LIST_SPACES`
+
+Key parameters:
+- `limit` (1-1000) -- maximum number of spaces to return (default: 100)
+- `skip` -- number of spaces to skip for pagination
+- `order` -- sort by field, e.g., `sys.createdAt` or `-sys.createdAt` for descending
+
+Example prompt: *"List all my Contentful spaces"*
+
+---
+
+### 2. Get Space Details
+
+Retrieve detailed metadata for a specific space including its current `sys.version`, which is required for updates.
+
+**Tool:** `CONTENTFUL_GET_SPACE`
+
+Key parameters:
+- `space_id` (required) -- the ID of the space to retrieve (alphanumeric, 1-64 chars)
+
+Example prompt: *"Get details for Contentful space abc123def"*
+
+---
+
+### 3. Update Space Name
+
+Update the name of a specific space. Requires the current version number for optimistic locking to prevent concurrent modification conflicts.
+
+**Tool:** `CONTENTFUL_UPDATE_SPACE`
+
+Key parameters:
+- `space_id` (required) -- ID of the space to update
+- `name` (required) -- new name for the space (1-255 chars)
+- `version` (required) -- current space version from `sys.version` (must be > 0)
+
+Example prompt: *"Rename Contentful space abc123def to 'Production Content Hub'"*
+
+---
+
+### 4. Audit Space Inventory
+
+Combine space listing and detail retrieval to audit your organization's Contentful spaces.
+
+**Tools:** `CONTENTFUL_LIST_SPACES` then `CONTENTFUL_GET_SPACE`
+
+Workflow:
+1. List all spaces to get IDs and names
+2. Fetch details for each space to get version info, creation dates, and metadata
+
+Example prompt: *"Audit all Contentful spaces -- list them with their creation dates and current versions"*
+
+---
+
+## Known Pitfalls
+
+- **Version conflicts on update:** `CONTENTFUL_UPDATE_SPACE` requires the latest `sys.version` from `CONTENTFUL_GET_SPACE`. If someone else modified the space between your read and write, the update will fail with a version conflict. Always fetch the space immediately before updating.
+- **Pagination for many spaces:** `CONTENTFUL_LIST_SPACES` uses `limit` and `skip` parameters. When you have many spaces, iterate by incrementing `skip` until no more results are returned to avoid missing spaces.
+- **Scope limitations:** These tools only manage space-level metadata (names). They cannot create or modify entries, content types, or assets within a space.
+- **Auth/permissions mismatch:** Updates via `CONTENTFUL_UPDATE_SPACE` will fail if your token lacks space management scopes, even if reads via `CONTENTFUL_GET_SPACE` succeed. Verify your token has write permissions.
+- **Space ID format:** The `space_id` must match the pattern `^[a-zA-Z0-9-_.]{1,64}$`. Invalid characters will be rejected.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `CONTENTFUL_LIST_SPACES` | List all spaces accessible to your account |
+| `CONTENTFUL_GET_SPACE` | Retrieve detailed metadata for a single space |
+| `CONTENTFUL_UPDATE_SPACE` | Update the name of a space (requires version) |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/contentful-graphql-automation/SKILL.md b/plugins/awesome-claude-skills/contentful-graphql-automation/SKILL.md
new file mode 100644
index 0000000..ecbfd3c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/control-d-automation/SKILL.md b/plugins/awesome-claude-skills/control-d-automation/SKILL.md
new file mode 100644
index 0000000..e6be5e5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/conversion-tools-automation/SKILL.md b/plugins/awesome-claude-skills/conversion-tools-automation/SKILL.md
new file mode 100644
index 0000000..1f443a6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/convertapi-automation/SKILL.md b/plugins/awesome-claude-skills/convertapi-automation/SKILL.md
new file mode 100644
index 0000000..c07d1d1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/convertkit-automation/SKILL.md b/plugins/awesome-claude-skills/convertkit-automation/SKILL.md
new file mode 100644
index 0000000..9ec6f21
--- /dev/null
+++ b/plugins/awesome-claude-skills/convertkit-automation/SKILL.md
@@ -0,0 +1,200 @@
+---
+name: convertkit-automation
+description: "Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# ConvertKit (Kit) Automation via Rube MCP
+
+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)
+- 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 Kit authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Search Subscribers
+
+**When to use**: User wants to browse, search, or filter email subscribers
+
+**Tool sequence**:
+1. `KIT_LIST_SUBSCRIBERS` - List subscribers with filters and pagination [Required]
+
+**Key parameters**:
+- `status`: Filter by status ('active' or 'inactive')
+- `email_address`: Exact email to search for
+- `created_after`/`created_before`: Date range filter (YYYY-MM-DD)
+- `updated_after`/`updated_before`: Date range filter (YYYY-MM-DD)
+- `sort_field`: Sort by 'id', 'cancelled_at', or 'updated_at'
+- `sort_order`: 'asc' or 'desc'
+- `per_page`: Results per page (min 1)
+- `after`/`before`: Cursor strings for pagination
+- `include_total_count`: Set to 'true' to get total subscriber count
+
+**Pitfalls**:
+- If `sort_field` is 'cancelled_at', the `status` must be set to 'cancelled'
+- Date filters use YYYY-MM-DD format (no time component)
+- `email_address` is an exact match; partial email search is not supported
+- Pagination uses cursor-based approach with `after`/`before` cursor strings
+- `include_total_count` is a string 'true', not a boolean
+
+### 2. Manage Subscriber Tags
+
+**When to use**: User wants to tag subscribers for segmentation
+
+**Tool sequence**:
+1. `KIT_LIST_SUBSCRIBERS` - Find subscriber ID by email [Prerequisite]
+2. `KIT_TAG_SUBSCRIBER` - Associate a subscriber with a tag [Required]
+3. `KIT_LIST_TAG_SUBSCRIBERS` - List subscribers for a specific tag [Optional]
+
+**Key parameters for tagging**:
+- `tag_id`: Numeric tag ID (required)
+- `subscriber_id`: Numeric subscriber ID (required)
+
+**Pitfalls**:
+- Both `tag_id` and `subscriber_id` must be positive integers
+- Tag IDs must reference existing tags; tags are created via the Kit web UI
+- Tagging an already-tagged subscriber is idempotent (no error)
+- Subscriber IDs are returned from LIST_SUBSCRIBERS; use `email_address` filter to find specific subscribers
+
+### 3. Unsubscribe a Subscriber
+
+**When to use**: User wants to unsubscribe a subscriber from all communications
+
+**Tool sequence**:
+1. `KIT_LIST_SUBSCRIBERS` - Find subscriber ID [Prerequisite]
+2. `KIT_DELETE_SUBSCRIBER` - Unsubscribe the subscriber [Required]
+
+**Key parameters**:
+- `id`: Subscriber ID (required, positive integer)
+
+**Pitfalls**:
+- This permanently unsubscribes the subscriber from ALL email communications
+- The subscriber's historical data is retained but they will no longer receive emails
+- Operation is idempotent; unsubscribing an already-unsubscribed subscriber succeeds without error
+- Returns empty response (HTTP 204 No Content) on success
+- Subscriber ID must exist; non-existent IDs return 404
+
+### 4. List and View Broadcasts
+
+**When to use**: User wants to browse email broadcasts or get details of a specific one
+
+**Tool sequence**:
+1. `KIT_LIST_BROADCASTS` - List all broadcasts with pagination [Required]
+2. `KIT_GET_BROADCAST` - Get detailed information for a specific broadcast [Optional]
+3. `KIT_GET_BROADCAST_STATS` - Get performance statistics for a broadcast [Optional]
+
+**Key parameters for listing**:
+- `per_page`: Results per page (1-500)
+- `after`/`before`: Cursor strings for pagination
+- `include_total_count`: Set to 'true' for total count
+
+**Key parameters for details**:
+- `id`: Broadcast ID (required, positive integer)
+
+**Pitfalls**:
+- `per_page` max is 500 for broadcasts
+- Broadcast stats are only available for sent broadcasts
+- Draft broadcasts will not have stats
+- Broadcast IDs are numeric integers
+
+### 5. Delete a Broadcast
+
+**When to use**: User wants to permanently remove a broadcast
+
+**Tool sequence**:
+1. `KIT_LIST_BROADCASTS` - Find the broadcast to delete [Prerequisite]
+2. `KIT_GET_BROADCAST` - Verify it is the correct broadcast [Optional]
+3. `KIT_DELETE_BROADCAST` - Permanently delete the broadcast [Required]
+
+**Key parameters**:
+- `id`: Broadcast ID (required)
+
+**Pitfalls**:
+- Deletion is permanent and cannot be undone
+- Deleting a sent broadcast removes it but does not unsend the emails
+- Confirm the broadcast ID before deleting
+
+## Common Patterns
+
+### Subscriber Lookup by Email
+
+```
+1. Call KIT_LIST_SUBSCRIBERS with email_address='user@example.com'
+2. Extract subscriber ID from the response
+3. Use ID for tagging, unsubscribing, or other operations
+```
+
+### Pagination
+
+Kit uses cursor-based pagination:
+- Check response for `after` cursor value
+- Pass cursor as `after` parameter in next request
+- Continue until no more cursor is returned
+- Use `include_total_count: 'true'` to track progress
+
+### Tag-Based Segmentation
+
+```
+1. Create tags in Kit web UI
+2. Use KIT_TAG_SUBSCRIBER to assign tags to subscribers
+3. Use KIT_LIST_TAG_SUBSCRIBERS to view subscribers per tag
+```
+
+## Known Pitfalls
+
+**ID Formats**:
+- Subscriber IDs: positive integers (e.g., 3887204736)
+- Tag IDs: positive integers
+- Broadcast IDs: positive integers
+- All IDs are numeric, not strings
+
+**Status Values**:
+- Subscriber statuses: 'active', 'inactive', 'cancelled'
+- Some operations are restricted by status (e.g., sorting by cancelled_at requires status='cancelled')
+
+**String vs Boolean Parameters**:
+- `include_total_count` is a string 'true', not a boolean true
+- `sort_order` is a string enum: 'asc' or 'desc'
+
+**Rate Limits**:
+- Kit API has per-account rate limits
+- Implement backoff on 429 responses
+- Bulk operations should be paced appropriately
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Cursor values are opaque strings; use exactly as returned
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List subscribers | KIT_LIST_SUBSCRIBERS | status, email_address, per_page |
+| Tag subscriber | KIT_TAG_SUBSCRIBER | tag_id, subscriber_id |
+| List tag subscribers | KIT_LIST_TAG_SUBSCRIBERS | tag_id |
+| Unsubscribe | KIT_DELETE_SUBSCRIBER | id |
+| List broadcasts | KIT_LIST_BROADCASTS | per_page, after |
+| 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/plugins/awesome-claude-skills/conveyor-automation/SKILL.md b/plugins/awesome-claude-skills/conveyor-automation/SKILL.md
new file mode 100644
index 0000000..0494461
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/convolo-ai-automation/SKILL.md b/plugins/awesome-claude-skills/convolo-ai-automation/SKILL.md
new file mode 100644
index 0000000..2f91570
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/corrently-automation/SKILL.md b/plugins/awesome-claude-skills/corrently-automation/SKILL.md
new file mode 100644
index 0000000..dcb1449
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/countdown-api-automation/SKILL.md b/plugins/awesome-claude-skills/countdown-api-automation/SKILL.md
new file mode 100644
index 0000000..807c97c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/coupa-automation/SKILL.md b/plugins/awesome-claude-skills/coupa-automation/SKILL.md
new file mode 100644
index 0000000..d00abb4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/craftmypdf-automation/SKILL.md b/plugins/awesome-claude-skills/craftmypdf-automation/SKILL.md
new file mode 100644
index 0000000..52dfa2b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/crowdin-automation/SKILL.md b/plugins/awesome-claude-skills/crowdin-automation/SKILL.md
new file mode 100644
index 0000000..0ec36de
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/crustdata-automation/SKILL.md b/plugins/awesome-claude-skills/crustdata-automation/SKILL.md
new file mode 100644
index 0000000..61d1f7e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/cults-automation/SKILL.md b/plugins/awesome-claude-skills/cults-automation/SKILL.md
new file mode 100644
index 0000000..b28e7f6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/curated-automation/SKILL.md b/plugins/awesome-claude-skills/curated-automation/SKILL.md
new file mode 100644
index 0000000..ea9d2c6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/currents-api-automation/SKILL.md b/plugins/awesome-claude-skills/currents-api-automation/SKILL.md
new file mode 100644
index 0000000..83e3f97
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/customerio-automation/SKILL.md b/plugins/awesome-claude-skills/customerio-automation/SKILL.md
new file mode 100644
index 0000000..a2f3f37
--- /dev/null
+++ b/plugins/awesome-claude-skills/customerio-automation/SKILL.md
@@ -0,0 +1,153 @@
+---
+name: Customer.io Automation
+description: "Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# Customer.io Automation
+
+Automate customer engagement operations -- trigger targeted broadcasts, retrieve delivery metrics, manage audience segments, list newsletters and transactional templates, and inspect trigger execution history -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/customerio](https://composio.dev/toolkits/customerio)
+
+---
+
+## Setup
+
+1. Connect your Customer.io account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `CUSTOMERIO_*` tools become available for execution
+
+---
+
+## Core Workflows
+
+### 1. Trigger a Broadcast
+Manually fire a pre-configured broadcast to a specific audience with personalization data.
+
+**Tool:** `CUSTOMERIO_TRIGGER_BROADCAST`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `broadcast_id` | integer | Yes | Broadcast ID from Customer.io Triggering Details |
+| `ids` | array | No | List of customer IDs to target |
+| `emails` | array | No | List of email addresses to target |
+| `recipients` | object | No | Complex filter with `and`/`or`/`not`/`segment` operators |
+| `per_user_data` | array | No | Per-user personalization with `id`/`email` + `data` |
+| `data` | object | No | Global key-value data for Liquid template personalization |
+| `data_file_url` | string | No | URL to JSON file with per-line user data |
+| `email_add_duplicates` | boolean | No | Allow duplicate recipients (default: false) |
+| `email_ignore_missing` | boolean | No | Skip people without emails (default: false) |
+| `id_ignore_missing` | boolean | No | Skip people without customer IDs (default: false) |
+
+**Important:** Provide exactly ONE audience option: `recipients`, `ids`, `emails`, `per_user_data`, or `data_file_url`. Rate limit: 1 request per 10 seconds per broadcast.
+
+---
+
+### 2. Retrieve Message Delivery Metrics
+Fetch paginated delivery metrics for messages with filtering by campaign, type, and time window.
+
+**Tool:** `CUSTOMERIO_GET_MESSAGES`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `type` | string | No | Message type: `email`, `webhook`, `twilio`, `slack`, `push`, `in_app` |
+| `metric` | string | No | Metric: `attempted`, `sent`, `delivered`, `opened`, `clicked`, `converted` |
+| `campaign_id` | integer | No | Filter by campaign ID |
+| `newsletter_id` | integer | No | Filter by newsletter ID |
+| `action_id` | integer | No | Filter by action ID |
+| `start_ts` | integer | No | Start of time window (Unix timestamp) |
+| `end_ts` | integer | No | End of time window (Unix timestamp) |
+| `limit` | integer | No | Results per page, 1-1000 (default: 50) |
+| `start` | string | No | Pagination token from previous response `next` value |
+| `drafts` | boolean | No | Return draft messages instead of active/sent |
+
+---
+
+### 3. List Audience Segments
+Retrieve all segments defined in your workspace for audience analysis and broadcast targeting.
+
+**Tool:** `CUSTOMERIO_GET_SEGMENTS`
+
+```
+No parameters required -- returns all segments with IDs and metadata.
+```
+
+Use segment IDs when targeting broadcasts via the `recipients.segment.id` filter.
+
+---
+
+### 4. List Newsletters
+Paginate through all newsletter metadata for tracking and analysis.
+
+**Tool:** `CUSTOMERIO_LIST_NEWSLETTERS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `limit` | integer | No | Max per page, 1-100 |
+| `sort` | string | No | `asc` (chronological) or `desc` (reverse) |
+| `start` | string | No | Pagination cursor from previous response `next` value |
+
+---
+
+### 5. Discover Transactional Message Templates
+List all transactional message templates to find IDs for sending via the API.
+
+**Tool:** `CUSTOMERIO_LIST_TRANSACTIONAL_MESSAGES`
+
+```
+No parameters required -- returns template IDs and trigger names.
+```
+
+---
+
+### 6. Inspect Broadcast Trigger History
+Review all trigger executions for a broadcast and inspect individual trigger details.
+
+**Tools:** `CUSTOMERIO_GET_TRIGGERS` and `CUSTOMERIO_GET_TRIGGER`
+
+**List all triggers for a broadcast:**
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `broadcast_id` | integer | Yes | The broadcast/campaign ID |
+
+**Get a specific trigger:**
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `broadcast_id` | integer | Yes | The campaign/broadcast ID |
+| `trigger_id` | string | Yes | Trigger identifier (e.g., `456` or `5-37`) |
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **Mutually exclusive audience params** | `CUSTOMERIO_TRIGGER_BROADCAST` requires exactly ONE of `recipients`, `ids`, `emails`, `per_user_data`, or `data_file_url` -- providing multiple causes errors |
+| **Rate limiting on broadcasts** | Broadcasts are limited to 1 trigger request per 10 seconds per broadcast ID |
+| **Unix timestamp format** | `start_ts` and `end_ts` in `CUSTOMERIO_GET_MESSAGES` must be Unix timestamps, not ISO strings |
+| **Pagination tokens** | Messages and newsletters use cursor-based pagination via the `start` parameter -- use the `next` value from previous responses |
+| **Segment ID resolution** | To target a segment in a broadcast, first fetch segment IDs via `CUSTOMERIO_GET_SEGMENTS`, then reference by ID in `recipients.segment.id` |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `CUSTOMERIO_TRIGGER_BROADCAST` | Trigger a broadcast to a defined audience |
+| `CUSTOMERIO_GET_MESSAGES` | Retrieve message delivery metrics with filters |
+| `CUSTOMERIO_GET_SEGMENTS` | List all audience segments |
+| `CUSTOMERIO_GET_SEGMENT_DETAILS` | Get details for a specific segment |
+| `CUSTOMERIO_LIST_NEWSLETTERS` | Paginate through newsletters |
+| `CUSTOMERIO_LIST_TRANSACTIONAL_MESSAGES` | List transactional message templates |
+| `CUSTOMERIO_GET_TRIGGERS` | List all trigger executions for a broadcast |
+| `CUSTOMERIO_GET_TRIGGER` | Inspect a specific trigger execution |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/customgpt-automation/SKILL.md b/plugins/awesome-claude-skills/customgpt-automation/SKILL.md
new file mode 100644
index 0000000..ec956c1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/customjs-automation/SKILL.md b/plugins/awesome-claude-skills/customjs-automation/SKILL.md
new file mode 100644
index 0000000..9083e54
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/cutt-ly-automation/SKILL.md b/plugins/awesome-claude-skills/cutt-ly-automation/SKILL.md
new file mode 100644
index 0000000..a91a4f2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/d2lbrightspace-automation/SKILL.md b/plugins/awesome-claude-skills/d2lbrightspace-automation/SKILL.md
new file mode 100644
index 0000000..4d9f571
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dadata-ru-automation/SKILL.md b/plugins/awesome-claude-skills/dadata-ru-automation/SKILL.md
new file mode 100644
index 0000000..24dd5f0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/daffy-automation/SKILL.md b/plugins/awesome-claude-skills/daffy-automation/SKILL.md
new file mode 100644
index 0000000..599ba5c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dailybot-automation/SKILL.md b/plugins/awesome-claude-skills/dailybot-automation/SKILL.md
new file mode 100644
index 0000000..a7e9d00
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/datadog-automation/SKILL.md b/plugins/awesome-claude-skills/datadog-automation/SKILL.md
new file mode 100644
index 0000000..92113be
--- /dev/null
+++ b/plugins/awesome-claude-skills/datadog-automation/SKILL.md
@@ -0,0 +1,240 @@
+---
+name: datadog-automation
+description: "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Datadog Automation via Rube MCP
+
+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)
+- Active Datadog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`
+3. If connection is not ACTIVE, follow the returned auth link to complete Datadog authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Query and Explore Metrics
+
+**When to use**: User wants to query metric data or list available metrics
+
+**Tool sequence**:
+1. `DATADOG_LIST_METRICS` - List available metric names [Optional]
+2. `DATADOG_QUERY_METRICS` - Query metric time series data [Required]
+
+**Key parameters**:
+- `query`: Datadog metric query string (e.g., `avg:system.cpu.user{host:web01}`)
+- `from`: Start timestamp (Unix epoch seconds)
+- `to`: End timestamp (Unix epoch seconds)
+- `q`: Search string for listing metrics
+
+**Pitfalls**:
+- Query syntax follows Datadog's metric query format: `aggregation:metric_name{tag_filters}`
+- `from` and `to` are Unix epoch timestamps in seconds, not milliseconds
+- Valid aggregations: `avg`, `sum`, `min`, `max`, `count`
+- Tag filters use curly braces: `{host:web01,env:prod}`
+- Time range should not exceed Datadog's retention limits for the metric type
+
+### 2. Search and Analyze Logs
+
+**When to use**: User wants to search log entries or list log indexes
+
+**Tool sequence**:
+1. `DATADOG_LIST_LOG_INDEXES` - List available log indexes [Optional]
+2. `DATADOG_SEARCH_LOGS` - Search logs with query and filters [Required]
+
+**Key parameters**:
+- `query`: Log search query using Datadog log query syntax
+- `from`: Start time (ISO 8601 or Unix timestamp)
+- `to`: End time (ISO 8601 or Unix timestamp)
+- `sort`: Sort order ('asc' or 'desc')
+- `limit`: Number of log entries to return
+
+**Pitfalls**:
+- Log queries use Datadog's log search syntax: `service:web status:error`
+- Search is limited to retained logs within the configured retention period
+- Large result sets require pagination; check for cursor/page tokens
+- Log indexes control routing and retention; filter by index if known
+
+### 3. Manage Monitors
+
+**When to use**: User wants to create, update, mute, or inspect monitors
+
+**Tool sequence**:
+1. `DATADOG_LIST_MONITORS` - List all monitors with filters [Required]
+2. `DATADOG_GET_MONITOR` - Get specific monitor details [Optional]
+3. `DATADOG_CREATE_MONITOR` - Create a new monitor [Optional]
+4. `DATADOG_UPDATE_MONITOR` - Update monitor configuration [Optional]
+5. `DATADOG_MUTE_MONITOR` - Silence a monitor temporarily [Optional]
+6. `DATADOG_UNMUTE_MONITOR` - Re-enable a muted monitor [Optional]
+
+**Key parameters**:
+- `monitor_id`: Numeric monitor ID
+- `name`: Monitor display name
+- `type`: Monitor type ('metric alert', 'service check', 'log alert', 'query alert', etc.)
+- `query`: Monitor query defining the alert condition
+- `message`: Notification message with @mentions
+- `tags`: Array of tag strings
+- `thresholds`: Alert threshold values (`critical`, `warning`, `ok`)
+
+**Pitfalls**:
+- Monitor `type` must match the query type; mismatches cause creation failures
+- `message` supports @mentions for notifications (e.g., `@slack-channel`, `@pagerduty`)
+- Thresholds vary by monitor type; metric monitors need `critical` at minimum
+- Muting a monitor suppresses notifications but the monitor still evaluates
+- Monitor IDs are numeric integers
+
+### 4. Manage Dashboards
+
+**When to use**: User wants to list, view, update, or delete dashboards
+
+**Tool sequence**:
+1. `DATADOG_LIST_DASHBOARDS` - List all dashboards [Required]
+2. `DATADOG_GET_DASHBOARD` - Get full dashboard definition [Optional]
+3. `DATADOG_UPDATE_DASHBOARD` - Update dashboard layout or widgets [Optional]
+4. `DATADOG_DELETE_DASHBOARD` - Remove a dashboard (irreversible) [Optional]
+
+**Key parameters**:
+- `dashboard_id`: Dashboard identifier string
+- `title`: Dashboard title
+- `layout_type`: 'ordered' (grid) or 'free' (freeform positioning)
+- `widgets`: Array of widget definition objects
+- `description`: Dashboard description
+
+**Pitfalls**:
+- Dashboard IDs are alphanumeric strings (e.g., 'abc-def-ghi'), not numeric
+- `layout_type` cannot be changed after creation; must recreate the dashboard
+- Widget definitions are complex nested objects; get existing dashboard first to understand structure
+- DELETE is permanent; there is no undo
+
+### 5. Create Events and Manage Downtimes
+
+**When to use**: User wants to post events or schedule maintenance downtimes
+
+**Tool sequence**:
+1. `DATADOG_LIST_EVENTS` - List existing events [Optional]
+2. `DATADOG_CREATE_EVENT` - Post a new event [Required]
+3. `DATADOG_CREATE_DOWNTIME` - Schedule a maintenance downtime [Optional]
+
+**Key parameters for events**:
+- `title`: Event title
+- `text`: Event body text (supports markdown)
+- `alert_type`: Event severity ('error', 'warning', 'info', 'success')
+- `tags`: Array of tag strings
+
+**Key parameters for downtimes**:
+- `scope`: Tag scope for the downtime (e.g., `host:web01`)
+- `start`: Start time (Unix epoch)
+- `end`: End time (Unix epoch; omit for indefinite)
+- `message`: Downtime description
+- `monitor_id`: Specific monitor to downtime (optional, omit for scope-based)
+
+**Pitfalls**:
+- Event `text` supports Datadog's markdown format including @mentions
+- Downtimes scope uses tag syntax: `host:web01`, `env:staging`
+- Omitting `end` creates an indefinite downtime; always set an end time for maintenance
+- Downtime `monitor_id` narrows to a single monitor; scope applies to all matching monitors
+
+### 6. Manage Hosts and Traces
+
+**When to use**: User wants to list infrastructure hosts or inspect distributed traces
+
+**Tool sequence**:
+1. `DATADOG_LIST_HOSTS` - List all reporting hosts [Required]
+2. `DATADOG_GET_TRACE_BY_ID` - Get a specific distributed trace [Optional]
+
+**Key parameters**:
+- `filter`: Host search filter string
+- `sort_field`: Sort hosts by field (e.g., 'name', 'apps', 'cpu')
+- `sort_dir`: Sort direction ('asc' or 'desc')
+- `trace_id`: Distributed trace ID for trace lookup
+
+**Pitfalls**:
+- Host list includes all hosts reporting to Datadog within the retention window
+- Trace IDs are long numeric strings; ensure exact match
+- Hosts that stop reporting are retained for a configured period before removal
+
+## Common Patterns
+
+### Monitor Query Syntax
+
+**Metric alerts**:
+```
+avg(last_5m):avg:system.cpu.user{env:prod} > 90
+```
+
+**Log alerts**:
+```
+logs("service:web status:error").index("main").rollup("count").last("5m") > 10
+```
+
+### Tag Filtering
+
+- Tags use `key:value` format: `host:web01`, `env:prod`, `service:api`
+- Multiple tags: `{host:web01,env:prod}` (AND logic)
+- Wildcard: `host:web*`
+
+### Pagination
+
+- Use `page` and `page_size` or offset-based pagination depending on endpoint
+- Check response for total count to determine if more pages exist
+- Continue until all results are retrieved
+
+## Known Pitfalls
+
+**Timestamps**:
+- Most endpoints use Unix epoch seconds (not milliseconds)
+- Some endpoints accept ISO 8601; check tool schema
+- Time ranges should be reasonable (not years of data)
+
+**Query Syntax**:
+- Metric queries: `aggregation:metric{tags}`
+- Log queries: `field:value` pairs
+- Monitor queries vary by type; check Datadog documentation
+
+**Rate Limits**:
+- Datadog API has per-endpoint rate limits
+- Implement backoff on 429 responses
+- Batch operations where possible
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Query metrics | DATADOG_QUERY_METRICS | query, from, to |
+| List metrics | DATADOG_LIST_METRICS | q |
+| Search logs | DATADOG_SEARCH_LOGS | query, from, to, limit |
+| List log indexes | DATADOG_LIST_LOG_INDEXES | (none) |
+| List monitors | DATADOG_LIST_MONITORS | tags |
+| Get monitor | DATADOG_GET_MONITOR | monitor_id |
+| Create monitor | DATADOG_CREATE_MONITOR | name, type, query, message |
+| Update monitor | DATADOG_UPDATE_MONITOR | monitor_id |
+| Mute monitor | DATADOG_MUTE_MONITOR | monitor_id |
+| Unmute monitor | DATADOG_UNMUTE_MONITOR | monitor_id |
+| List dashboards | DATADOG_LIST_DASHBOARDS | (none) |
+| Get dashboard | DATADOG_GET_DASHBOARD | dashboard_id |
+| Update dashboard | DATADOG_UPDATE_DASHBOARD | dashboard_id, title, widgets |
+| Delete dashboard | DATADOG_DELETE_DASHBOARD | dashboard_id |
+| List events | DATADOG_LIST_EVENTS | start, end |
+| Create event | DATADOG_CREATE_EVENT | title, text, alert_type |
+| 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/plugins/awesome-claude-skills/datagma-automation/SKILL.md b/plugins/awesome-claude-skills/datagma-automation/SKILL.md
new file mode 100644
index 0000000..34b313e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/datarobot-automation/SKILL.md b/plugins/awesome-claude-skills/datarobot-automation/SKILL.md
new file mode 100644
index 0000000..32267ed
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/deadline-funnel-automation/SKILL.md b/plugins/awesome-claude-skills/deadline-funnel-automation/SKILL.md
new file mode 100644
index 0000000..4066d92
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/deel-automation/SKILL.md b/plugins/awesome-claude-skills/deel-automation/SKILL.md
new file mode 100644
index 0000000..1d2b044
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/deepgram-automation/SKILL.md b/plugins/awesome-claude-skills/deepgram-automation/SKILL.md
new file mode 100644
index 0000000..cbf3fd6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/demio-automation/SKILL.md b/plugins/awesome-claude-skills/demio-automation/SKILL.md
new file mode 100644
index 0000000..21543c9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/desktime-automation/SKILL.md b/plugins/awesome-claude-skills/desktime-automation/SKILL.md
new file mode 100644
index 0000000..c4d2833
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/detrack-automation/SKILL.md b/plugins/awesome-claude-skills/detrack-automation/SKILL.md
new file mode 100644
index 0000000..1de64fd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dialmycalls-automation/SKILL.md b/plugins/awesome-claude-skills/dialmycalls-automation/SKILL.md
new file mode 100644
index 0000000..48845a4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dialpad-automation/SKILL.md b/plugins/awesome-claude-skills/dialpad-automation/SKILL.md
new file mode 100644
index 0000000..e9ad8f9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dictionary-api-automation/SKILL.md b/plugins/awesome-claude-skills/dictionary-api-automation/SKILL.md
new file mode 100644
index 0000000..d3bf09b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/diffbot-automation/SKILL.md b/plugins/awesome-claude-skills/diffbot-automation/SKILL.md
new file mode 100644
index 0000000..82b943b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/digicert-automation/SKILL.md b/plugins/awesome-claude-skills/digicert-automation/SKILL.md
new file mode 100644
index 0000000..b84161d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/digital-ocean-automation/SKILL.md b/plugins/awesome-claude-skills/digital-ocean-automation/SKILL.md
new file mode 100644
index 0000000..3279a76
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/discord-automation/SKILL.md b/plugins/awesome-claude-skills/discord-automation/SKILL.md
new file mode 100644
index 0000000..c6a6bbc
--- /dev/null
+++ b/plugins/awesome-claude-skills/discord-automation/SKILL.md
@@ -0,0 +1,192 @@
+---
+name: discord-automation
+description: "Automate Discord tasks via Rube MCP (Composio): messages, channels, roles, webhooks, reactions. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Discord Automation via Rube MCP
+
+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)
+- Active Discord connection via `RUBE_MANAGE_CONNECTIONS` with toolkits `discord` and `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` (bot operations) or `discord` (user operations)
+3. If connection is not ACTIVE, follow the returned auth link to complete Discord auth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Messages
+
+**When to use**: User wants to send messages to channels or DMs
+
+**Tool sequence**:
+1. `DISCORD_LIST_MY_GUILDS` - List guilds the bot belongs to [Prerequisite]
+2. `DISCORDBOT_LIST_GUILD_CHANNELS` - List channels in a guild [Prerequisite]
+3. `DISCORDBOT_CREATE_MESSAGE` - Send a message [Required]
+4. `DISCORDBOT_UPDATE_MESSAGE` - Edit a sent message [Optional]
+
+**Key parameters**:
+- `channel_id`: Channel snowflake ID
+- `content`: Message text (max 2000 characters)
+- `embeds`: Array of embed objects for rich content
+- `guild_id`: Guild ID for channel listing
+
+**Pitfalls**:
+- Bot must have SEND_MESSAGES permission in the channel
+- High-frequency sends can hit per-route rate limits; respect Retry-After headers
+- Only messages sent by the same bot can be edited
+
+### 2. Send Direct Messages
+
+**When to use**: User wants to DM a Discord user
+
+**Tool sequence**:
+1. `DISCORDBOT_CREATE_DM` - Create or get DM channel [Required]
+2. `DISCORDBOT_CREATE_MESSAGE` - Send message to DM channel [Required]
+
+**Key parameters**:
+- `recipient_id`: User snowflake ID for DM
+- `channel_id`: DM channel ID from CREATE_DM
+
+**Pitfalls**:
+- Cannot DM users who have DMs disabled or have blocked the bot
+- CREATE_DM returns existing channel if one already exists
+
+### 3. Manage Roles
+
+**When to use**: User wants to create, assign, or remove roles
+
+**Tool sequence**:
+1. `DISCORDBOT_CREATE_GUILD_ROLE` - Create a new role [Optional]
+2. `DISCORDBOT_ADD_GUILD_MEMBER_ROLE` - Assign role to member [Optional]
+3. `DISCORDBOT_DELETE_GUILD_ROLE` - Delete a role [Optional]
+4. `DISCORDBOT_GET_GUILD_MEMBER` - Get member details [Optional]
+5. `DISCORDBOT_UPDATE_GUILD_MEMBER` - Update member (roles, nick, etc.) [Optional]
+
+**Key parameters**:
+- `guild_id`: Guild snowflake ID
+- `user_id`: User snowflake ID
+- `role_id`: Role snowflake ID
+- `name`: Role name
+- `permissions`: Bitwise permission value
+- `color`: RGB color integer
+
+**Pitfalls**:
+- Role assignment requires MANAGE_ROLES permission
+- Target role must be lower in hierarchy than bot's highest role
+- DELETE permanently removes the role from all members
+
+### 4. Manage Webhooks
+
+**When to use**: User wants to create or use webhooks for external integrations
+
+**Tool sequence**:
+1. `DISCORDBOT_GET_GUILD_WEBHOOKS` / `DISCORDBOT_LIST_CHANNEL_WEBHOOKS` - List webhooks [Optional]
+2. `DISCORDBOT_CREATE_WEBHOOK` - Create a new webhook [Optional]
+3. `DISCORDBOT_EXECUTE_WEBHOOK` - Send message via webhook [Optional]
+4. `DISCORDBOT_UPDATE_WEBHOOK` - Update webhook settings [Optional]
+
+**Key parameters**:
+- `webhook_id`: Webhook ID
+- `webhook_token`: Webhook secret token
+- `channel_id`: Channel for webhook creation
+- `name`: Webhook name
+- `content`/`embeds`: Message content for execution
+
+**Pitfalls**:
+- Webhook tokens are secrets; handle securely
+- Webhooks can post with custom username and avatar per message
+- MANAGE_WEBHOOKS permission required for creation
+
+### 5. Manage Reactions
+
+**When to use**: User wants to view or manage message reactions
+
+**Tool sequence**:
+1. `DISCORDBOT_LIST_MESSAGE_REACTIONS_BY_EMOJI` - List users who reacted [Optional]
+2. `DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS` - Remove all reactions [Optional]
+3. `DISCORDBOT_DELETE_ALL_MESSAGE_REACTIONS_BY_EMOJI` - Remove specific emoji reactions [Optional]
+4. `DISCORDBOT_DELETE_USER_MESSAGE_REACTION` - Remove specific user's reaction [Optional]
+
+**Key parameters**:
+- `channel_id`: Channel ID
+- `message_id`: Message snowflake ID
+- `emoji_name`: URL-encoded emoji or `name:id` for custom emojis
+- `user_id`: User ID for specific reaction removal
+
+**Pitfalls**:
+- Unicode emojis must be URL-encoded (e.g., '%F0%9F%91%8D' for thumbs up)
+- Custom emojis use `name:id` format
+- DELETE_ALL requires MANAGE_MESSAGES permission
+
+## Common Patterns
+
+### Snowflake IDs
+
+Discord uses snowflake IDs (64-bit integers as strings) for all entities:
+- Guilds, channels, users, roles, messages, webhooks
+
+### Permission Bitfields
+
+Permissions are combined using bitwise OR:
+- SEND_MESSAGES = 0x800
+- MANAGE_ROLES = 0x10000000
+- MANAGE_MESSAGES = 0x2000
+- ADMINISTRATOR = 0x8
+
+### Pagination
+
+- Most list endpoints support `limit`, `before`, `after` parameters
+- Messages: max 100 per request
+- Reactions: max 100 per request, use `after` for pagination
+
+## Known Pitfalls
+
+**Bot vs User Tokens**:
+- `discordbot` toolkit uses bot tokens; `discord` uses user OAuth
+- Bot operations are preferred for automation
+
+**Rate Limits**:
+- Discord enforces per-route rate limits
+- Respect `Retry-After` headers on 429 responses
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List guilds | DISCORD_LIST_MY_GUILDS | (none) |
+| List channels | DISCORDBOT_LIST_GUILD_CHANNELS | guild_id |
+| Send message | DISCORDBOT_CREATE_MESSAGE | channel_id, content |
+| Edit message | DISCORDBOT_UPDATE_MESSAGE | channel_id, message_id |
+| Get messages | DISCORDBOT_LIST_MESSAGES | channel_id, limit |
+| Create DM | DISCORDBOT_CREATE_DM | recipient_id |
+| Create role | DISCORDBOT_CREATE_GUILD_ROLE | guild_id, name |
+| Assign role | DISCORDBOT_ADD_GUILD_MEMBER_ROLE | guild_id, user_id, role_id |
+| Delete role | DISCORDBOT_DELETE_GUILD_ROLE | guild_id, role_id |
+| Get member | DISCORDBOT_GET_GUILD_MEMBER | guild_id, user_id |
+| Update member | DISCORDBOT_UPDATE_GUILD_MEMBER | guild_id, user_id |
+| Get guild | DISCORDBOT_GET_GUILD | guild_id |
+| Create webhook | DISCORDBOT_CREATE_WEBHOOK | channel_id, name |
+| Execute webhook | DISCORDBOT_EXECUTE_WEBHOOK | webhook_id, webhook_token |
+| List webhooks | DISCORDBOT_GET_GUILD_WEBHOOKS | guild_id |
+| Get reactions | DISCORDBOT_LIST_MESSAGE_REACTIONS_BY_EMOJI | channel_id, message_id, emoji_name |
+| 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/plugins/awesome-claude-skills/discordbot-automation/SKILL.md b/plugins/awesome-claude-skills/discordbot-automation/SKILL.md
new file mode 100644
index 0000000..d8938a2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dnsfilter-automation/SKILL.md b/plugins/awesome-claude-skills/dnsfilter-automation/SKILL.md
new file mode 100644
index 0000000..022945d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dock-certs-automation/SKILL.md b/plugins/awesome-claude-skills/dock-certs-automation/SKILL.md
new file mode 100644
index 0000000..d8df22b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docker-hub-automation/SKILL.md b/plugins/awesome-claude-skills/docker-hub-automation/SKILL.md
new file mode 100644
index 0000000..92900fb
--- /dev/null
+++ b/plugins/awesome-claude-skills/docker-hub-automation/SKILL.md
@@ -0,0 +1,136 @@
+---
+name: Docker Hub Automation
+description: "Automate Docker Hub operations -- manage organizations, repositories, teams, members, and webhooks via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Docker Hub Automation
+
+Automate your Docker Hub workflows -- create and manage organizations, repositories, teams, add members, set up image push webhooks, and list container images.
+
+**Toolkit docs:** [composio.dev/toolkits/docker_hub](https://composio.dev/toolkits/docker_hub)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your Docker Hub account when prompted (JWT/token authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. List Organizations
+
+Use `DOCKER_HUB_LIST_ORGANIZATIONS` to discover which organizations the authenticated user belongs to.
+
+```
+Tool: DOCKER_HUB_LIST_ORGANIZATIONS
+Inputs:
+ - page: integer (1-indexed, default 1)
+ - page_size: integer (1-100, default 25)
+```
+
+### 2. Create an Organization
+
+Use `DOCKER_HUB_CREATE_ORGANIZATION` to programmatically create a new Docker Hub organization.
+
+```
+Tool: DOCKER_HUB_CREATE_ORGANIZATION
+Inputs:
+ - orgname: string (required) -- lowercase, letters/numbers/._- only, min 2 chars
+ - company: string (optional) -- company name associated with the org
+```
+
+**Note:** Requires JWT authentication obtained via `/v2/users/login` and may have restricted access.
+
+### 3. Get Organization Details and Repositories
+
+Use `DOCKER_HUB_GET_ORGANIZATION` to retrieve namespace info and its repositories. Works with any public namespace.
+
+```
+Tool: DOCKER_HUB_GET_ORGANIZATION
+Inputs:
+ - organization: string (required) -- e.g., "docker", "bitnami", "library"
+```
+
+### 4. Create a Repository
+
+Use `DOCKER_HUB_CREATE_REPOSITORY` to create public or private repositories under a namespace.
+
+```
+Tool: DOCKER_HUB_CREATE_REPOSITORY
+Inputs:
+ - namespace: string (required) -- Docker Hub username or org name
+ - name: string (required) -- lowercase; letters, numbers, ._- allowed
+ - description: string (optional) -- max 100 characters
+ - full_description: string (optional) -- Markdown README content
+ - is_private: boolean (default false) -- private repos require paid plan
+```
+
+### 5. List Repositories with Filtering
+
+Use `DOCKER_HUB_LIST_REPOSITORIES` to enumerate repos within a namespace with sorting and content-type filtering.
+
+```
+Tool: DOCKER_HUB_LIST_REPOSITORIES
+Inputs:
+ - namespace: string (required) -- e.g., "library", "myorg"
+ - ordering: "name" | "last_updated" | "pull_count" (prefix with - for descending)
+ - page: integer (default 1)
+ - page_size: integer (1-100, default 25)
+ - content_types: string (comma-separated, e.g., "image,artifact")
+```
+
+### 6. Manage Teams, Members, and Webhooks
+
+Use `DOCKER_HUB_LIST_TEAMS` to list teams within an org, `DOCKER_HUB_ADD_ORG_MEMBER` to invite users, and `DOCKER_HUB_CREATE_WEBHOOK` for push notifications.
+
+```
+Tool: DOCKER_HUB_LIST_TEAMS
+ - Lists all teams/groups within a Docker Hub organization
+
+Tool: DOCKER_HUB_ADD_ORG_MEMBER
+ - Invite a user to join an organization by Docker ID or email
+ - Requires owner or admin permissions
+
+Tool: DOCKER_HUB_CREATE_WEBHOOK
+ - Create a webhook on a repository for image push notifications
+ - Two-step process: create webhook, then add hook URL
+ - Requires admin permissions on the repository
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| JWT authentication | `DOCKER_HUB_CREATE_ORGANIZATION` requires JWT auth from `/v2/users/login` -- standard API tokens may not suffice. |
+| Private repo limits | Creating private repos (`is_private: true`) requires a paid Docker Hub plan. |
+| Org name constraints | Organization names must be lowercase, at least 2 characters, containing only letters, numbers, `.`, `_`, or `-`. |
+| Webhook two-step | `DOCKER_HUB_CREATE_WEBHOOK` is a two-step process: first create the webhook with a name, then add a hook URL to it. |
+| Pagination | All list endpoints use page-based pagination -- iterate pages until results are exhausted. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `DOCKER_HUB_LIST_ORGANIZATIONS` | List orgs the user belongs to |
+| `DOCKER_HUB_CREATE_ORGANIZATION` | Create a new Docker Hub organization |
+| `DOCKER_HUB_GET_ORGANIZATION` | Get org details and repository list |
+| `DOCKER_HUB_CREATE_REPOSITORY` | Create a repository under a namespace |
+| `DOCKER_HUB_LIST_REPOSITORIES` | List repos with filtering and sorting |
+| `DOCKER_HUB_LIST_TEAMS` | List teams/groups within an org |
+| `DOCKER_HUB_ADD_ORG_MEMBER` | Invite a user to an organization |
+| `DOCKER_HUB_CREATE_WEBHOOK` | Create push-notification webhook on a repo |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/docker_hub-automation/SKILL.md b/plugins/awesome-claude-skills/docker_hub-automation/SKILL.md
new file mode 100644
index 0000000..f68f903
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docmosis-automation/SKILL.md b/plugins/awesome-claude-skills/docmosis-automation/SKILL.md
new file mode 100644
index 0000000..c36e956
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docnify-automation/SKILL.md b/plugins/awesome-claude-skills/docnify-automation/SKILL.md
new file mode 100644
index 0000000..f2e37b3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docsbot-ai-automation/SKILL.md b/plugins/awesome-claude-skills/docsbot-ai-automation/SKILL.md
new file mode 100644
index 0000000..67ce8a7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docsumo-automation/SKILL.md b/plugins/awesome-claude-skills/docsumo-automation/SKILL.md
new file mode 100644
index 0000000..2ef4c5e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docugenerate-automation/SKILL.md b/plugins/awesome-claude-skills/docugenerate-automation/SKILL.md
new file mode 100644
index 0000000..064cc23
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/documenso-automation/SKILL.md b/plugins/awesome-claude-skills/documenso-automation/SKILL.md
new file mode 100644
index 0000000..72a6c63
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/documint-automation/SKILL.md b/plugins/awesome-claude-skills/documint-automation/SKILL.md
new file mode 100644
index 0000000..1002d65
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docupilot-automation/SKILL.md b/plugins/awesome-claude-skills/docupilot-automation/SKILL.md
new file mode 100644
index 0000000..9d11d78
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docupost-automation/SKILL.md b/plugins/awesome-claude-skills/docupost-automation/SKILL.md
new file mode 100644
index 0000000..8abca26
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docuseal-automation/SKILL.md b/plugins/awesome-claude-skills/docuseal-automation/SKILL.md
new file mode 100644
index 0000000..bb2a2da
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/docusign-automation/SKILL.md b/plugins/awesome-claude-skills/docusign-automation/SKILL.md
new file mode 100644
index 0000000..a6f6294
--- /dev/null
+++ b/plugins/awesome-claude-skills/docusign-automation/SKILL.md
@@ -0,0 +1,213 @@
+---
+name: docusign-automation
+description: "Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# DocuSign Automation via Rube MCP
+
+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)
+- Active DocuSign connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `docusign`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `docusign`
+3. If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Browse and Select Templates
+
+**When to use**: User wants to find available document templates for sending
+
+**Tool sequence**:
+1. `DOCUSIGN_LIST_ALL_TEMPLATES` - List all available templates [Required]
+2. `DOCUSIGN_GET_TEMPLATE` - Get detailed template information [Optional]
+
+**Key parameters**:
+- For listing: Optional search/filter parameters
+- For details: `templateId` (from list results)
+- Response includes template `templateId`, `name`, `description`, roles, and fields
+
+**Pitfalls**:
+- Template IDs are GUIDs (e.g., '12345678-abcd-1234-efgh-123456789012')
+- Templates define recipient roles with signing tabs; understand roles before creating envelopes
+- Large template libraries require pagination; check for continuation tokens
+- Template access depends on account permissions
+
+### 2. Create and Send Envelopes from Templates
+
+**When to use**: User wants to send documents for signature using a pre-built template
+
+**Tool sequence**:
+1. `DOCUSIGN_LIST_ALL_TEMPLATES` - Find the template to use [Prerequisite]
+2. `DOCUSIGN_GET_TEMPLATE` - Review template roles and fields [Optional]
+3. `DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE` - Create the envelope [Required]
+4. `DOCUSIGN_SEND_ENVELOPE` - Send the envelope for signing [Required]
+
+**Key parameters**:
+- For CREATE_ENVELOPE_FROM_TEMPLATE:
+ - `templateId`: Template to use
+ - `templateRoles`: Array of role assignments with `roleName`, `name`, `email`
+ - `status`: 'created' (draft) or 'sent' (send immediately)
+ - `emailSubject`: Custom subject line for the signing email
+ - `emailBlurb`: Custom message in the signing email
+- For SEND_ENVELOPE:
+ - `envelopeId`: Envelope ID from creation response
+
+**Pitfalls**:
+- `templateRoles` must match the role names defined in the template exactly (case-sensitive)
+- Setting `status` to 'sent' during creation sends immediately; use 'created' for drafts
+- If status is 'sent' at creation, no need to call SEND_ENVELOPE separately
+- Each role requires at minimum `roleName`, `name`, and `email`
+- `emailSubject` overrides the template's default email subject
+
+### 3. Monitor Envelope Status
+
+**When to use**: User wants to check the status of sent envelopes or track signing progress
+
+**Tool sequence**:
+1. `DOCUSIGN_GET_ENVELOPE` - Get envelope details and status [Required]
+
+**Key parameters**:
+- `envelopeId`: Envelope identifier (GUID)
+- Response includes `status`, `recipients`, `sentDateTime`, `completedDateTime`
+
+**Pitfalls**:
+- Envelope statuses: 'created', 'sent', 'delivered', 'signed', 'completed', 'declined', 'voided'
+- 'delivered' means the email was opened, not that the document was signed
+- 'completed' means all recipients have signed
+- Recipients array shows individual signing status per recipient
+- Envelope IDs are GUIDs; always resolve from creation or search results
+
+### 4. Add Templates to Existing Envelopes
+
+**When to use**: User wants to add additional documents or templates to an existing envelope
+
+**Tool sequence**:
+1. `DOCUSIGN_GET_ENVELOPE` - Verify envelope exists and is in draft state [Prerequisite]
+2. `DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE` - Add template to envelope [Required]
+
+**Key parameters**:
+- `envelopeId`: Target envelope ID
+- `documentId`: Document ID within the envelope
+- `templateId`: Template to add
+
+**Pitfalls**:
+- Envelope must be in 'created' (draft) status to add templates
+- Cannot add templates to already-sent envelopes
+- Document IDs are sequential within an envelope (starting from '1')
+- Adding a template merges its fields and roles into the existing envelope
+
+### 5. Manage Envelope Lifecycle
+
+**When to use**: User wants to send, void, or manage draft envelopes
+
+**Tool sequence**:
+1. `DOCUSIGN_GET_ENVELOPE` - Check current envelope status [Prerequisite]
+2. `DOCUSIGN_SEND_ENVELOPE` - Send a draft envelope [Optional]
+
+**Key parameters**:
+- `envelopeId`: Envelope to manage
+- For sending: envelope must be in 'created' status with all required recipients
+
+**Pitfalls**:
+- Only 'created' (draft) envelopes can be sent
+- Sent envelopes cannot be unsent; they can only be voided
+- Voiding an envelope notifies all recipients
+- All required recipients must have valid email addresses before sending
+
+## Common Patterns
+
+### ID Resolution
+
+**Template name -> Template ID**:
+```
+1. Call DOCUSIGN_LIST_ALL_TEMPLATES
+2. Find template by name in results
+3. Extract templateId (GUID format)
+```
+
+**Envelope tracking**:
+```
+1. Store envelopeId from CREATE_ENVELOPE_FROM_TEMPLATE response
+2. Call DOCUSIGN_GET_ENVELOPE periodically to check status
+3. Check recipient-level status for individual signing progress
+```
+
+### Template Role Mapping
+
+When creating an envelope from a template:
+```
+1. Call DOCUSIGN_GET_TEMPLATE to see defined roles
+2. Map each role to actual recipients:
+ {
+ "roleName": "Signer 1", // Must match template role name exactly
+ "name": "John Smith",
+ "email": "john@example.com"
+ }
+3. Include ALL required roles in templateRoles array
+```
+
+### Envelope Status Flow
+
+```
+created (draft) -> sent -> delivered -> signed -> completed
+ \-> declined
+ \-> voided (by sender)
+```
+
+## Known Pitfalls
+
+**Template Roles**:
+- Role names are case-sensitive; must match template definition exactly
+- All required roles must be assigned when creating an envelope
+- Missing role assignments cause envelope creation to fail
+
+**Envelope Status**:
+- 'delivered' means email opened, NOT document signed
+- 'completed' is the final successful state (all parties signed)
+- Status transitions are one-way; cannot revert to previous states
+
+**GUIDs**:
+- All DocuSign IDs (templates, envelopes) are GUID format
+- Always resolve names to GUIDs via list/search endpoints
+- Do not hardcode GUIDs; they are unique per account
+
+**Rate Limits**:
+- DocuSign API has per-account rate limits
+- Bulk envelope creation should be throttled
+- Polling envelope status should use reasonable intervals (30-60 seconds)
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Recipient information is nested within envelope response
+- Date fields use ISO 8601 format
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List templates | DOCUSIGN_LIST_ALL_TEMPLATES | (optional filters) |
+| Get template | DOCUSIGN_GET_TEMPLATE | templateId |
+| Create envelope | DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE | templateId, templateRoles, status |
+| 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/plugins/awesome-claude-skills/doppler-marketing-automation-automation/SKILL.md b/plugins/awesome-claude-skills/doppler-marketing-automation-automation/SKILL.md
new file mode 100644
index 0000000..a3f2ca2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/doppler-secretops-automation/SKILL.md b/plugins/awesome-claude-skills/doppler-secretops-automation/SKILL.md
new file mode 100644
index 0000000..47063bc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dotsimple-automation/SKILL.md b/plugins/awesome-claude-skills/dotsimple-automation/SKILL.md
new file mode 100644
index 0000000..1172d0e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dovetail-automation/SKILL.md b/plugins/awesome-claude-skills/dovetail-automation/SKILL.md
new file mode 100644
index 0000000..e3118f2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dpd2-automation/SKILL.md b/plugins/awesome-claude-skills/dpd2-automation/SKILL.md
new file mode 100644
index 0000000..99de4e8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/draftable-automation/SKILL.md b/plugins/awesome-claude-skills/draftable-automation/SKILL.md
new file mode 100644
index 0000000..3790c8e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dreamstudio-automation/SKILL.md b/plugins/awesome-claude-skills/dreamstudio-automation/SKILL.md
new file mode 100644
index 0000000..1420e17
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/drip-jobs-automation/SKILL.md b/plugins/awesome-claude-skills/drip-jobs-automation/SKILL.md
new file mode 100644
index 0000000..9b1af04
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dripcel-automation/SKILL.md b/plugins/awesome-claude-skills/dripcel-automation/SKILL.md
new file mode 100644
index 0000000..4942da7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dromo-automation/SKILL.md b/plugins/awesome-claude-skills/dromo-automation/SKILL.md
new file mode 100644
index 0000000..a1c5414
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dropbox-automation/SKILL.md b/plugins/awesome-claude-skills/dropbox-automation/SKILL.md
new file mode 100644
index 0000000..31a9410
--- /dev/null
+++ b/plugins/awesome-claude-skills/dropbox-automation/SKILL.md
@@ -0,0 +1,235 @@
+---
+name: dropbox-automation
+description: Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Dropbox Automation via Rube MCP
+
+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)
+- Active Dropbox connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dropbox`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add 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`
+3. If connection is not ACTIVE, follow the returned auth link to complete Dropbox OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search for Files and Folders
+
+**When to use**: User wants to find files or folders by name, content, or type
+
+**Tool sequence**:
+1. `DROPBOX_SEARCH_FILE_OR_FOLDER` - Search by query string with optional path scope and filters [Required]
+2. `DROPBOX_SEARCH_CONTINUE` - Paginate through additional results using cursor [Required if has_more]
+3. `DROPBOX_GET_METADATA` - Validate and get canonical path for a search result [Optional]
+4. `DROPBOX_READ_FILE` - Read file content to verify it is the intended document [Optional]
+
+**Key parameters**:
+- `query`: Search string (case-insensitive, 1+ non-whitespace characters)
+- `options.path`: Scope search to a folder (e.g., `"/Documents"`); empty string for root
+- `options.file_categories`: Filter by type (`"image"`, `"document"`, `"pdf"`, `"folder"`, etc.)
+- `options.file_extensions`: Filter by extension (e.g., `["jpg", "png"]`)
+- `options.filename_only`: Set `true` to match filenames only (not content)
+- `options.max_results`: Results per page (default 100, max 1000)
+
+**Pitfalls**:
+- Search returns `has_more: true` with a `cursor` when more results exist; MUST continue to avoid silently missing matches
+- Maximum 10,000 matches total across all pages of search + search_continue
+- `DROPBOX_GET_METADATA` returned `path_display` may differ in casing from user input; always use the returned canonical path
+- File content from `DROPBOX_READ_FILE` may be returned as base64-encoded `file_content_bytes`; decode before parsing
+
+### 2. Upload and Download Files
+
+**When to use**: User wants to upload files to Dropbox or download files from it
+
+**Tool sequence**:
+1. `DROPBOX_UPLOAD_FILE` - Upload a file to a specified path [Required for upload]
+2. `DROPBOX_READ_FILE` - Download/read a file from Dropbox [Required for download]
+3. `DROPBOX_DOWNLOAD_ZIP` - Download an entire folder as a zip file [Optional]
+4. `DROPBOX_SAVE_URL` - Save a file from a public URL directly to Dropbox [Optional]
+5. `DROPBOX_GET_SHARED_LINK_FILE` - Download a file from a shared link URL [Optional]
+6. `DROPBOX_EXPORT_FILE` - Export non-downloadable files like Dropbox Paper to markdown/HTML [Optional]
+
+**Key parameters**:
+- `path`: Dropbox path (must start with `/`, e.g., `"/Documents/report.pdf"`)
+- `mode`: `"add"` (default, fail on conflict) or `"overwrite"` for uploads
+- `autorename`: `true` to auto-rename on conflict instead of failing
+- `content`: FileUploadable object with `s3key`, `mimetype`, and `name` for uploads
+- `url`: Public URL for `DROPBOX_SAVE_URL`
+- `export_format`: `"markdown"`, `"html"`, or `"plain_text"` for Paper docs
+
+**Pitfalls**:
+- `DROPBOX_SAVE_URL` is asynchronous and may take up to 15 minutes for large files
+- `DROPBOX_DOWNLOAD_ZIP` folder must be under 20 GB with no single file over 4 GB and fewer than 10,000 entries
+- `DROPBOX_READ_FILE` content may be base64-encoded; check response format
+- Shared link downloads via `DROPBOX_GET_SHARED_LINK_FILE` may require `link_password` for protected links
+
+### 3. Share Files and Manage Links
+
+**When to use**: User wants to create sharing links or manage existing shared links
+
+**Tool sequence**:
+1. `DROPBOX_GET_METADATA` - Confirm file/folder exists and get canonical path [Prerequisite]
+2. `DROPBOX_LIST_SHARED_LINKS` - Check for existing shared links to avoid duplicates [Prerequisite]
+3. `DROPBOX_CREATE_SHARED_LINK` - Create a new shared link [Required]
+4. `DROPBOX_GET_SHARED_LINK_METADATA` - Resolve a shared link URL to metadata [Optional]
+5. `DROPBOX_LIST_SHARED_FOLDERS` - List all shared folders the user has access to [Optional]
+
+**Key parameters**:
+- `path`: File or folder path for link creation
+- `settings.audience`: `"public"`, `"team"`, or `"no_one"`
+- `settings.access`: `"viewer"` or `"editor"`
+- `settings.expires`: ISO 8601 expiration date (e.g., `"2026-12-31T23:59:59Z"`)
+- `settings.require_password` / `settings.link_password`: Password protection
+- `settings.allow_download`: Boolean for download permission
+- `direct_only`: For `LIST_SHARED_LINKS`, set `true` to only return direct links (not parent folder links)
+
+**Pitfalls**:
+- `DROPBOX_CREATE_SHARED_LINK` fails with 409 Conflict if a shared link already exists for the path; check with `DROPBOX_LIST_SHARED_LINKS` first
+- Always validate path with `DROPBOX_GET_METADATA` before creating links to avoid `path/not_found` errors
+- Reuse existing links from `DROPBOX_LIST_SHARED_LINKS` instead of creating duplicates
+- `requested_visibility` is deprecated; use `audience` for newer implementations
+
+### 4. Manage Folders (Create, Move, Delete)
+
+**When to use**: User wants to create, move, rename, or delete files and folders
+
+**Tool sequence**:
+1. `DROPBOX_CREATE_FOLDER` - Create a single folder [Required for create]
+2. `DROPBOX_CREATE_FOLDER_BATCH` - Create multiple folders at once [Optional]
+3. `DROPBOX_MOVE_FILE_OR_FOLDER` - Move or rename a single file/folder [Required for move]
+4. `DROPBOX_MOVE_BATCH` - Move multiple items at once [Optional]
+5. `DROPBOX_DELETE_FILE_OR_FOLDER` - Delete a single file or folder [Required for delete]
+6. `DROPBOX_DELETE_BATCH` - Delete multiple items at once [Optional]
+7. `DROPBOX_COPY_FILE_OR_FOLDER` - Copy a file or folder to a new location [Optional]
+8. `DROPBOX_CHECK_MOVE_BATCH` / `DROPBOX_CHECK_FOLDER_BATCH` - Poll async batch job status [Required for batch ops]
+
+**Key parameters**:
+- `path`: Target path (must start with `/`, case-sensitive)
+- `from_path` / `to_path`: Source and destination for move/copy operations
+- `autorename`: `true` to auto-rename on conflict
+- `entries`: Array of `{from_path, to_path}` for batch moves; array of paths for batch creates
+- `allow_shared_folder`: Set `true` to allow moving shared folders
+- `allow_ownership_transfer`: Set `true` if move changes ownership
+
+**Pitfalls**:
+- All paths are case-sensitive and must start with `/`
+- Paths must NOT end with `/` or whitespace
+- Batch operations may be asynchronous; poll with `DROPBOX_CHECK_MOVE_BATCH` or `DROPBOX_CHECK_FOLDER_BATCH`
+- `DROPBOX_FILES_MOVE_BATCH` (v1) has "all or nothing" behavior - if any entry fails, entire batch fails
+- `DROPBOX_MOVE_BATCH` (v2) is preferred over `DROPBOX_FILES_MOVE_BATCH` (v1)
+- Maximum 1000 entries per batch delete/move; 10,000 paths per batch folder create
+- Case-only renaming is not supported in batch move operations
+
+### 5. List Folder Contents
+
+**When to use**: User wants to browse or enumerate files in a Dropbox folder
+
+**Tool sequence**:
+1. `DROPBOX_LIST_FILES_IN_FOLDER` - List contents of a folder [Required]
+2. `DROPBOX_LIST_FOLDERS` - Alternative folder listing with deleted entries support [Optional]
+3. `DROPBOX_GET_METADATA` - Get details for a specific item [Optional]
+
+**Key parameters**:
+- `path`: Folder path (empty string `""` for root)
+- `recursive`: `true` to list all nested contents
+- `limit`: Max results per request (default/max 2000)
+- `include_deleted`: `true` to include deleted but recoverable items
+- `include_media_info`: `true` to get photo/video metadata
+
+**Pitfalls**:
+- Use empty string `""` for root folder, not `"/"`
+- Recursive listings can be very large; use `limit` to control page size
+- Results may paginate via cursor even with small limits
+- `DROPBOX_LIST_FILES_IN_FOLDER` returns 409 Conflict with `path/not_found` for incorrect paths
+
+## Common Patterns
+
+### ID Resolution
+- **Path-based**: Most Dropbox tools use path strings (e.g., `"/Documents/file.pdf"`)
+- **ID-based**: Some tools accept `id:...` format (e.g., `"id:4g0reWVRsAAAAAAAAAAAQ"`)
+- **Canonical path**: Always use `path_display` or `path_lower` from `DROPBOX_GET_METADATA` responses for subsequent calls
+- **Shared link URL**: Use `DROPBOX_GET_SHARED_LINK_METADATA` to resolve URLs to paths/IDs
+
+### Pagination
+Dropbox uses cursor-based pagination across most endpoints:
+- Search: Follow `has_more` + `cursor` with `DROPBOX_SEARCH_CONTINUE` (max 10,000 total matches)
+- Folder listing: Follow cursor from response until no more pages
+- Shared links: Follow `has_more` + `cursor` in `DROPBOX_LIST_SHARED_LINKS`
+- Batch job status: Poll with `DROPBOX_CHECK_MOVE_BATCH` / `DROPBOX_CHECK_FOLDER_BATCH`
+
+### Async Operations
+Several Dropbox operations run asynchronously:
+- `DROPBOX_SAVE_URL` - returns job ID; poll or set `wait: true` (up to 120s default)
+- `DROPBOX_MOVE_BATCH` / `DROPBOX_FILES_MOVE_BATCH` - may return job ID
+- `DROPBOX_CREATE_FOLDER_BATCH` - may return job ID
+- `DROPBOX_DELETE_BATCH` - returns job ID
+
+## Known Pitfalls
+
+### Path Formats
+- All paths must start with `/` (except empty string for root in some endpoints)
+- Paths must NOT end with `/` or contain trailing whitespace
+- Paths are case-sensitive for write operations
+- `path_display` from API may differ in casing from user input; always prefer API-returned paths
+
+### Rate Limits
+- Dropbox API has per-endpoint rate limits; batch operations help reduce call count
+- Search is limited to 10,000 total matches across all pagination
+- `DROPBOX_SAVE_URL` has a 15-minute timeout for large files
+
+### File Content
+- `DROPBOX_READ_FILE` may return content as base64-encoded `file_content_bytes`
+- Non-downloadable files (Dropbox Paper, Google Docs) require `DROPBOX_EXPORT_FILE` instead
+- Download URLs from shared links require proper authentication headers
+
+### Sharing
+- Creating a shared link when one already exists returns a 409 Conflict error
+- Always check `DROPBOX_LIST_SHARED_LINKS` before creating new links
+- Shared folder access may not appear in standard path listings; use `DROPBOX_LIST_SHARED_FOLDERS`
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search files | `DROPBOX_SEARCH_FILE_OR_FOLDER` | `query`, `options.path` |
+| Continue search | `DROPBOX_SEARCH_CONTINUE` | `cursor` |
+| List folder | `DROPBOX_LIST_FILES_IN_FOLDER` | `path`, `recursive`, `limit` |
+| List folders | `DROPBOX_LIST_FOLDERS` | `path`, `recursive` |
+| Get metadata | `DROPBOX_GET_METADATA` | `path` |
+| Read/download file | `DROPBOX_READ_FILE` | `path` |
+| Upload file | `DROPBOX_UPLOAD_FILE` | `path`, `content`, `mode` |
+| Save URL to Dropbox | `DROPBOX_SAVE_URL` | `path`, `url` |
+| Download folder zip | `DROPBOX_DOWNLOAD_ZIP` | `path` |
+| Export Paper doc | `DROPBOX_EXPORT_FILE` | `path`, `export_format` |
+| Download shared link | `DROPBOX_GET_SHARED_LINK_FILE` | `url` |
+| Create shared link | `DROPBOX_CREATE_SHARED_LINK` | `path`, `settings` |
+| List shared links | `DROPBOX_LIST_SHARED_LINKS` | `path`, `direct_only` |
+| Shared link metadata | `DROPBOX_GET_SHARED_LINK_METADATA` | `url` |
+| List shared folders | `DROPBOX_LIST_SHARED_FOLDERS` | `limit` |
+| Create folder | `DROPBOX_CREATE_FOLDER` | `path` |
+| Create folders batch | `DROPBOX_CREATE_FOLDER_BATCH` | `paths` |
+| Move file/folder | `DROPBOX_MOVE_FILE_OR_FOLDER` | `from_path`, `to_path` |
+| Move batch | `DROPBOX_MOVE_BATCH` | `entries` |
+| Delete file/folder | `DROPBOX_DELETE_FILE_OR_FOLDER` | `path` |
+| 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/plugins/awesome-claude-skills/dropbox-sign-automation/SKILL.md b/plugins/awesome-claude-skills/dropbox-sign-automation/SKILL.md
new file mode 100644
index 0000000..fcee2ca
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dropcontact-automation/SKILL.md b/plugins/awesome-claude-skills/dropcontact-automation/SKILL.md
new file mode 100644
index 0000000..7606b45
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dungeon-fighter-online-automation/SKILL.md b/plugins/awesome-claude-skills/dungeon-fighter-online-automation/SKILL.md
new file mode 100644
index 0000000..f107618
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/dynamics365-automation/SKILL.md b/plugins/awesome-claude-skills/dynamics365-automation/SKILL.md
new file mode 100644
index 0000000..ab43736
--- /dev/null
+++ b/plugins/awesome-claude-skills/dynamics365-automation/SKILL.md
@@ -0,0 +1,237 @@
+---
+name: Dynamics 365 Automation
+description: "Dynamics 365 Automation: manage CRM contacts, accounts, leads, opportunities, sales orders, invoices, and cases via the Dynamics CRM Web API"
+requires:
+ mcp: [rube]
+---
+
+# Dynamics 365 Automation
+
+Automate Microsoft Dynamics 365 CRM operations including creating and updating contacts, accounts, leads, opportunities, sales orders, invoices, and support cases.
+
+**Toolkit docs:** [composio.dev/toolkits/dynamics365](https://composio.dev/toolkits/dynamics365)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure an active connection exists for the `dynamics365` toolkit. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+---
+
+## Core Workflows
+
+### 1. Manage Leads
+
+Create, update, retrieve, and list lead records.
+
+**Tools:**
+- `DYNAMICS365_DYNAMICSCRM_CREATE_LEAD` -- Create a new lead
+- `DYNAMICS365_DYNAMICSCRM_UPDATE_LEAD` -- Update an existing lead
+- `DYNAMICS365_DYNAMICSCRM_GET_A_LEAD` -- Retrieve a lead by GUID
+- `DYNAMICS365_DYNAMICSCRM_GET_ALL_LEADS` -- List/filter all leads
+
+**Key Parameters for `DYNAMICS365_DYNAMICSCRM_CREATE_LEAD`:**
+- `firstname` -- First name of the lead
+- `lastname` -- Last name of the lead
+- `emailaddress1` -- Primary email address
+- `telephone1` -- Primary phone number
+- `companyname` -- Associated company name
+- `subject` -- Brief title/description
+
+**Key Parameters for `DYNAMICS365_DYNAMICSCRM_GET_ALL_LEADS`:**
+- `filter` -- OData filter, e.g., `"contains(fullname,'John')"`
+- `select` -- Fields to return, e.g., `"fullname,emailaddress1"`
+- `orderby` -- Sort expression, e.g., `"createdon desc"`
+- `top` -- Max number of results
+
+**Example:**
+```
+Tool: DYNAMICS365_DYNAMICSCRM_CREATE_LEAD
+Arguments:
+ firstname: "Jane"
+ lastname: "Smith"
+ emailaddress1: "jane.smith@example.com"
+ companyname: "Acme Corp"
+ subject: "Interested in Enterprise plan"
+```
+
+---
+
+### 2. Manage Accounts
+
+Create and organize account (company) records in the CRM.
+
+**Tool:** `DYNAMICS365_DYNAMICSCRM_CREATE_ACCOUNT`
+
+**Key Parameters:**
+- `name` -- Account/company name
+- `description` -- Description of the account
+- `revenue` -- Revenue amount (number)
+- `accountcategorycode` -- Category code (integer, default: 1)
+- `creditonhold` -- Whether account is on credit hold (boolean)
+
+**Example:**
+```
+Tool: DYNAMICS365_DYNAMICSCRM_CREATE_ACCOUNT
+Arguments:
+ name: "Contoso Ltd"
+ description: "Strategic partner for cloud services"
+ revenue: 5000000
+ creditonhold: false
+```
+
+---
+
+### 3. Manage Contacts
+
+Create detailed contact records with address and phone information.
+
+**Tool:** `DYNAMICS365_DYNAMICSCRM_CREATE_CONTACT`
+
+**Key Parameters:**
+- `firstname`, `lastname` -- Contact name
+- `emailaddress1` -- Primary email
+- `telephone1` -- Primary phone
+- `mobilephone` -- Mobile phone
+- `jobtitle` -- Job title
+- `address1_city`, `address1_stateorprovince`, `address1_postalcode`, `address1_country` -- Address fields
+
+**Example:**
+```
+Tool: DYNAMICS365_DYNAMICSCRM_CREATE_CONTACT
+Arguments:
+ firstname: "Bob"
+ lastname: "Johnson"
+ emailaddress1: "bob.johnson@example.com"
+ jobtitle: "VP of Engineering"
+ address1_city: "Seattle"
+ address1_stateorprovince: "WA"
+```
+
+---
+
+### 4. Manage Opportunities
+
+Create and update sales opportunities with estimated values and close dates.
+
+**Tools:**
+- `DYNAMICS365_DYNAMICSCRM_CREATE_OPPORTUNITY` -- Create a new opportunity
+- `DYNAMICS365_DYNAMICSCRM_UPDATE_OPPORTUNITY` -- Update an existing opportunity
+
+**Key Parameters for `DYNAMICS365_DYNAMICSCRM_CREATE_OPPORTUNITY`:**
+- `name` (required) -- Opportunity title
+- `description` -- Brief description
+- `estimatedvalue` -- Anticipated revenue (number)
+- `estimatedclosedate` -- Expected close date in `YYYY-MM-DD` format
+- `customer_account_id` -- GUID of the related account (no curly braces)
+- `customer_contact_id` -- GUID of the related contact (no curly braces)
+
+**Key Parameters for `DYNAMICS365_DYNAMICSCRM_UPDATE_OPPORTUNITY`:**
+- `opportunity_id` (required) -- GUID of the opportunity
+- `opportunityratingcode` -- 1 (Cold), 2 (Warm), 3 (Hot)
+- `salesstagecode` -- 1 (Qualify), 2 (Develop), 3 (Propose)
+
+**Example:**
+```
+Tool: DYNAMICS365_DYNAMICSCRM_CREATE_OPPORTUNITY
+Arguments:
+ name: "Enterprise Cloud Migration"
+ estimatedvalue: 250000
+ estimatedclosedate: "2026-06-30"
+ description: "Full cloud migration project for Contoso"
+```
+
+---
+
+### 5. Manage Sales Orders and Invoices
+
+Create and update sales orders; generate invoices for billing.
+
+**Tools:**
+- `DYNAMICS365_DYNAMICSCRM_CREATE_SALES_ORDER` -- Create a new sales order
+- `DYNAMICS365_DYNAMICSCRM_UPDATE_SALES_ORDER` -- Update an existing sales order
+- `DYNAMICS365_DYNAMICSCRM_CREATE_INVOICE` -- Create a new invoice
+
+**Key Parameters for `DYNAMICS365_DYNAMICSCRM_CREATE_SALES_ORDER`:**
+- `name` -- Sales order name
+- `description` -- Description
+- `account_id` -- Reference to account, format: `"/accounts(GUID)"`
+- `currency_id` -- Currency reference, format: `"/transactioncurrencies(GUID)"`
+- `price_level_id` -- Price list reference, format: `"/pricelevels(GUID)"`
+
+**Key Parameters for `DYNAMICS365_DYNAMICSCRM_UPDATE_SALES_ORDER`:**
+- `salesorder_id` (required) -- GUID of the sales order
+- `name` -- Updated name
+- `discountamount` -- Updated discount
+- `freightamount` -- Updated shipping cost
+
+**Key Parameters for `DYNAMICS365_DYNAMICSCRM_CREATE_INVOICE`:**
+- `name` -- Invoice name/number, e.g., `"Invoice #12345"`
+- `description` -- Invoice description
+- `account_id` -- Related account reference
+- `currency_id` -- Currency reference
+- `price_level_id` -- Price list reference
+
+---
+
+### 6. Create Support Cases
+
+Create incident/case records for customer support tracking.
+
+**Tool:** `DYNAMICS365_DYNAMICSCRM_CREATE_CASE`
+
+**Key Parameters:**
+- `title` -- Subject/title of the case
+- `description` -- Detailed description
+- `prioritycode` -- 1 (Low), 2 (Normal), 3 (High)
+- `caseorigincode` -- 1 (Phone), 2 (Email), 3 (Web)
+- `account_id` -- Related account, format: `"/accounts(GUID)"`
+- `contact_id` -- Related contact, format: `"/contacts(GUID)"`
+
+**Example:**
+```
+Tool: DYNAMICS365_DYNAMICSCRM_CREATE_CASE
+Arguments:
+ title: "Login issue reported by customer"
+ description: "Customer unable to access portal since Feb 10"
+ prioritycode: 3
+ caseorigincode: 2
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **GUID format** | All entity IDs are GUIDs (e.g., `"00000000-0000-0000-0000-000000000000"`). Do not include curly braces for opportunity/contact references. |
+| **Reference format** | Related entity references use the format `"/entityset(GUID)"` (e.g., `"/accounts(abc-123)"`). Missing the leading slash or parentheses causes errors. |
+| **OData filter syntax** | Use Dynamics 365 OData syntax for `filter` (e.g., `contains(fullname,'John')`). Incorrect syntax returns empty or error responses. |
+| **user_id default** | Most tools default `user_id` to `"me"` for the authenticated user. Override only when acting on behalf of another user. |
+| **Required fields** | `CREATE_OPPORTUNITY` requires `name`. Other create tools have no strict required fields but will create empty records without data. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `DYNAMICS365_DYNAMICSCRM_CREATE_LEAD` | Create a new lead record |
+| `DYNAMICS365_DYNAMICSCRM_UPDATE_LEAD` | Update an existing lead |
+| `DYNAMICS365_DYNAMICSCRM_GET_A_LEAD` | Retrieve a lead by GUID |
+| `DYNAMICS365_DYNAMICSCRM_GET_ALL_LEADS` | List/filter all leads |
+| `DYNAMICS365_DYNAMICSCRM_CREATE_ACCOUNT` | Create a new account |
+| `DYNAMICS365_DYNAMICSCRM_CREATE_CONTACT` | Create a new contact |
+| `DYNAMICS365_DYNAMICSCRM_CREATE_OPPORTUNITY` | Create a new opportunity |
+| `DYNAMICS365_DYNAMICSCRM_UPDATE_OPPORTUNITY` | Update an existing opportunity |
+| `DYNAMICS365_DYNAMICSCRM_CREATE_SALES_ORDER` | Create a new sales order |
+| `DYNAMICS365_DYNAMICSCRM_UPDATE_SALES_ORDER` | Update an existing sales order |
+| `DYNAMICS365_DYNAMICSCRM_CREATE_INVOICE` | Create a new invoice |
+| `DYNAMICS365_DYNAMICSCRM_CREATE_CASE` | Create a support case/incident |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/echtpost-automation/SKILL.md b/plugins/awesome-claude-skills/echtpost-automation/SKILL.md
new file mode 100644
index 0000000..750c1ea
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/elevenlabs-automation/SKILL.md b/plugins/awesome-claude-skills/elevenlabs-automation/SKILL.md
new file mode 100644
index 0000000..7b41f4d
--- /dev/null
+++ b/plugins/awesome-claude-skills/elevenlabs-automation/SKILL.md
@@ -0,0 +1,131 @@
+---
+name: ElevenLabs Automation
+description: "Automate ElevenLabs text-to-speech workflows -- generate speech from text, browse and inspect voices, check subscription limits, list models, stream audio, and retrieve history via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# ElevenLabs Automation
+
+Automate your ElevenLabs text-to-speech workflows -- convert text to natural speech, browse the voice library, inspect voice details, check subscription credits, select TTS models, stream audio for low-latency delivery, and retrieve previously generated audio from history.
+
+**Toolkit docs:** [composio.dev/toolkits/elevenlabs](https://composio.dev/toolkits/elevenlabs)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your ElevenLabs account when prompted (API key authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. Generate Speech from Text
+
+Use `ELEVENLABS_TEXT_TO_SPEECH` to convert text into a downloadable audio file.
+
+```
+Tool: ELEVENLABS_TEXT_TO_SPEECH
+Inputs:
+ - voice_id: string (required) -- obtain from ELEVENLABS_GET_VOICES
+ - text: string (required) -- max ~10,000 chars (most models), 30,000 (Flash/Turbo v2), 40,000 (v2.5)
+ - model_id: string (default "eleven_monolingual_v1") -- e.g., "eleven_multilingual_v2"
+ - output_format: string (default "mp3_44100_128") -- see formats below
+ - optimize_streaming_latency: integer (0-4; NOT supported with eleven_v3)
+ - seed: integer (optional, for reproducibility -- not guaranteed)
+ - pronunciation_dictionary_locators: array (optional, up to 3 dictionaries)
+```
+
+**Output formats:**
+- MP3: `mp3_22050_32`, `mp3_44100_32`, `mp3_44100_64`, `mp3_44100_96`, `mp3_44100_128`, `mp3_44100_192` (Creator+)
+- PCM: `pcm_16000`, `pcm_22050`, `pcm_24000`, `pcm_44100` (Pro+)
+- uLaw: `ulaw_8000` (for Twilio)
+
+**Important:** Output is a file object with a presigned download link at `data.file.s3url` (expires in ~1 hour). Download promptly.
+
+### 2. Browse Available Voices
+
+Use `ELEVENLABS_GET_VOICES` to list all voices with their attributes and settings.
+
+```
+Tool: ELEVENLABS_GET_VOICES
+Inputs: (none)
+```
+
+Returns an array at `data.voices[]` with `voice_id`, `name`, `labels` (gender, accent, use_case), and settings.
+
+### 3. Inspect a Specific Voice
+
+Use `ELEVENLABS_GET_VOICE` to get detailed metadata for a candidate voice before synthesis.
+
+```
+Tool: ELEVENLABS_GET_VOICE
+Inputs:
+ - voice_id: string (required) -- e.g., "21m00Tcm4TlvDq8ikWAM"
+ - with_settings: boolean (default false) -- include detailed voice settings
+```
+
+### 4. Check Subscription and Credits
+
+Use `ELEVENLABS_GET_USER_SUBSCRIPTION_INFO` to verify plan limits and remaining credits before bulk generation.
+
+```
+Tool: ELEVENLABS_GET_USER_SUBSCRIPTION_INFO
+Inputs: (none)
+```
+
+### 5. List Available TTS Models
+
+Use `ELEVENLABS_GET_MODELS` to discover compatible models and filter by `can_do_text_to_speech: true`.
+
+```
+Tool: ELEVENLABS_GET_MODELS
+Inputs: (none)
+```
+
+### 6. Stream Audio and Retrieve History
+
+Use `ELEVENLABS_TEXT_TO_SPEECH_STREAM` for low-latency streamed delivery, and `ELEVENLABS_GET_AUDIO_FROM_HISTORY_ITEM` to re-download previously generated audio.
+
+```
+Tool: ELEVENLABS_TEXT_TO_SPEECH_STREAM
+ - Same core inputs as TEXT_TO_SPEECH but returns a stream for low-latency playback
+
+Tool: ELEVENLABS_GET_AUDIO_FROM_HISTORY_ITEM
+ - history_item_id: string (required) -- ID from a previous generation
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| Text length limits | Most models cap at ~10,000-20,000 chars per request. Oversized input returns HTTP 400. Split long text into chunks (~5000 chars) and generate per chunk. |
+| Output is a presigned URL | `ELEVENLABS_TEXT_TO_SPEECH` returns `data.file.s3url` with a ~1 hour expiry (X-Amz-Expires=3600). Download the audio file promptly. |
+| Quota and credit errors | HTTP 401 with `quota_exceeded` or HTTP 402 `payment_required` means insufficient credits or tier restrictions. Check with `ELEVENLABS_GET_USER_SUBSCRIPTION_INFO` before bulk jobs. |
+| Voice permissions | HTTP 401 with `missing_permissions` means the API key lacks `voices_read` scope. Verify key permissions. |
+| Model compatibility | Not all models support TTS. Use `ELEVENLABS_GET_MODELS` and filter by `can_do_text_to_speech: true`. The `optimize_streaming_latency` parameter is NOT supported with `eleven_v3`. |
+| Large voice list truncation | `ELEVENLABS_GET_VOICES` may return a large list. Select from the full `data.voices[]` payload -- previews may appear truncated. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `ELEVENLABS_TEXT_TO_SPEECH` | Convert text to speech, returns downloadable audio file |
+| `ELEVENLABS_GET_VOICES` | List all available voices with attributes |
+| `ELEVENLABS_GET_VOICE` | Get detailed info for a specific voice |
+| `ELEVENLABS_GET_USER_SUBSCRIPTION_INFO` | Check subscription plan and remaining credits |
+| `ELEVENLABS_GET_MODELS` | List available TTS models and capabilities |
+| `ELEVENLABS_TEXT_TO_SPEECH_STREAM` | Stream audio for low-latency delivery |
+| `ELEVENLABS_GET_AUDIO_FROM_HISTORY_ITEM` | Re-download audio from generation history |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/elorus-automation/SKILL.md b/plugins/awesome-claude-skills/elorus-automation/SKILL.md
new file mode 100644
index 0000000..d3b7299
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/emailable-automation/SKILL.md b/plugins/awesome-claude-skills/emailable-automation/SKILL.md
new file mode 100644
index 0000000..98e4682
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/emaillistverify-automation/SKILL.md b/plugins/awesome-claude-skills/emaillistverify-automation/SKILL.md
new file mode 100644
index 0000000..017e523
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/emailoctopus-automation/SKILL.md b/plugins/awesome-claude-skills/emailoctopus-automation/SKILL.md
new file mode 100644
index 0000000..67bfb3e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/emelia-automation/SKILL.md b/plugins/awesome-claude-skills/emelia-automation/SKILL.md
new file mode 100644
index 0000000..f439ba2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/encodian-automation/SKILL.md b/plugins/awesome-claude-skills/encodian-automation/SKILL.md
new file mode 100644
index 0000000..3bab40b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/endorsal-automation/SKILL.md b/plugins/awesome-claude-skills/endorsal-automation/SKILL.md
new file mode 100644
index 0000000..197b9dc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/enginemailer-automation/SKILL.md b/plugins/awesome-claude-skills/enginemailer-automation/SKILL.md
new file mode 100644
index 0000000..28ac8a0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/enigma-automation/SKILL.md b/plugins/awesome-claude-skills/enigma-automation/SKILL.md
new file mode 100644
index 0000000..cda8171
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/entelligence-automation/SKILL.md b/plugins/awesome-claude-skills/entelligence-automation/SKILL.md
new file mode 100644
index 0000000..3e9be30
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/eodhd-apis-automation/SKILL.md b/plugins/awesome-claude-skills/eodhd-apis-automation/SKILL.md
new file mode 100644
index 0000000..55784e7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/epic-games-automation/SKILL.md b/plugins/awesome-claude-skills/epic-games-automation/SKILL.md
new file mode 100644
index 0000000..8c9fcdb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/esignatures-io-automation/SKILL.md b/plugins/awesome-claude-skills/esignatures-io-automation/SKILL.md
new file mode 100644
index 0000000..514a1ee
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/espocrm-automation/SKILL.md b/plugins/awesome-claude-skills/espocrm-automation/SKILL.md
new file mode 100644
index 0000000..4e65268
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/esputnik-automation/SKILL.md b/plugins/awesome-claude-skills/esputnik-automation/SKILL.md
new file mode 100644
index 0000000..7397442
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/etermin-automation/SKILL.md b/plugins/awesome-claude-skills/etermin-automation/SKILL.md
new file mode 100644
index 0000000..4547db1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/evenium-automation/SKILL.md b/plugins/awesome-claude-skills/evenium-automation/SKILL.md
new file mode 100644
index 0000000..b9dc686
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/eventbrite-automation/SKILL.md b/plugins/awesome-claude-skills/eventbrite-automation/SKILL.md
new file mode 100644
index 0000000..9bbf52c
--- /dev/null
+++ b/plugins/awesome-claude-skills/eventbrite-automation/SKILL.md
@@ -0,0 +1,148 @@
+---
+name: Eventbrite Automation
+description: "Automate Eventbrite event management, attendee tracking, organization discovery, and category browsing through natural language commands"
+requires:
+ mcp:
+ - rube
+---
+
+# Eventbrite Automation
+
+Automate Eventbrite event management workflows -- list organization events, track attendees, browse categories and formats, and manage organizations -- all through natural language.
+
+**Toolkit docs:** [composio.dev/toolkits/eventbrite](https://composio.dev/toolkits/eventbrite)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Connect your Eventbrite account when prompted (OAuth flow via Composio)
+3. Start issuing natural language commands for Eventbrite automation
+
+---
+
+## Core Workflows
+
+### 1. Discover Your Organizations
+
+Retrieve the organizations the authenticated user belongs to. This is a prerequisite for most other Eventbrite operations since `organization_id` is required.
+
+**Tool:** `EVENTBRITE_LIST_USER_ORGANIZATIONS`
+
+No parameters required. Returns organization IDs, names, and metadata.
+
+> Always call this first to obtain the `organization_id` needed by event and attendee endpoints.
+
+Example prompt:
+> "List my Eventbrite organizations"
+
+---
+
+### 2. List and Search Organization Events
+
+Browse events owned by a specific organization with filtering by status, time period, and pagination.
+
+**Tool:** `EVENTBRITE_LIST_ORGANIZATION_EVENTS`
+
+Key parameters:
+- `organization_id` -- the organization whose events to list (required; get from `EVENTBRITE_LIST_USER_ORGANIZATIONS`)
+- `status` -- filter by `live`, `draft`, `canceled`, `started`, `ended`, `completed`, or `all`
+- `time_filter` -- filter by `current_future` or `past`
+- `order_by` -- sort by `start_asc`, `start_desc`, `created_asc`, `created_desc`, `name_asc`, `name_desc`
+- `page_size` -- number of events per page
+- `continuation` -- pagination token from previous response
+- `expand` -- comma-separated fields to expand: `organizer`, `venue`, `ticket_classes`
+
+Example prompt:
+> "Show me all live events for my organization, sorted by start date"
+
+---
+
+### 3. Track Event Attendees
+
+Retrieve the attendee list for any event, with optional status filtering and pagination.
+
+**Tool:** `EVENTBRITE_LIST_EVENT_ATTENDEES`
+
+Key parameters:
+- `event_id` -- the event to retrieve attendees for (required)
+- `status` -- filter by `attending`, `not_attending`, or `cancelled`
+- `changed_since` -- ISO 8601 timestamp to get only recently changed attendees
+- `continuation` -- pagination token for subsequent pages
+
+Example prompt:
+> "Get all attending attendees for event 123456789 who changed since January 1st"
+
+---
+
+### 4. Browse Event Categories
+
+Retrieve available event categories for use when creating or filtering events.
+
+**Tool:** `EVENTBRITE_GET_EVENT_CATEGORIES`
+
+Key parameters:
+- `locale` -- BCP-47 locale for localized names (e.g., `en_US`, `es_ES`)
+
+Follow up with `EVENTBRITE_GET_EVENT_SUBCATEGORIES` to get subcategories within a selected category.
+
+Example prompt:
+> "List all Eventbrite event categories in English"
+
+---
+
+### 5. List Event Formats
+
+Retrieve all available event format types (conference, seminar, workshop, etc.).
+
+**Tool:** `EVENTBRITE_GET_EVENT_FORMATS`
+
+No parameters required. Returns format IDs and display names.
+
+Example prompt:
+> "What event formats are available on Eventbrite?"
+
+---
+
+### 6. Browse Event Subcategories
+
+Retrieve subcategories for more granular event classification.
+
+**Tool:** `EVENTBRITE_GET_EVENT_SUBCATEGORIES`
+
+Key parameters:
+- `locale` -- BCP-47 locale for localized names (e.g., `en_US`)
+
+Example prompt:
+> "List all Eventbrite event subcategories"
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| Organization ID required | Most event operations require `organization_id` -- always call `EVENTBRITE_LIST_USER_ORGANIZATIONS` first |
+| Pagination via continuation | Results use continuation-token pagination, not page numbers -- pass the `continuation` value from the previous response to get the next page |
+| Event ID discovery | You need to list events first via `EVENTBRITE_LIST_ORGANIZATION_EVENTS` to get `event_id` values for attendee queries |
+| Status values are specific | Event status values (`live`, `draft`, `canceled`, `started`, `ended`, `completed`) must match exactly |
+| Expand fields are comma-separated | The `expand` parameter takes a comma-separated string, not an array (e.g., `"organizer,venue"`) |
+| changed_since format | The `changed_since` parameter must be in ISO 8601 format (e.g., `2024-01-01T00:00:00Z`) |
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Key Params |
+|--------|-----------|------------|
+| List organizations | `EVENTBRITE_LIST_USER_ORGANIZATIONS` | (none) |
+| List events | `EVENTBRITE_LIST_ORGANIZATION_EVENTS` | `organization_id`, `status`, `time_filter` |
+| List attendees | `EVENTBRITE_LIST_EVENT_ATTENDEES` | `event_id`, `status`, `changed_since` |
+| Get categories | `EVENTBRITE_GET_EVENT_CATEGORIES` | `locale` |
+| Get subcategories | `EVENTBRITE_GET_EVENT_SUBCATEGORIES` | `locale` |
+| Get formats | `EVENTBRITE_GET_EVENT_FORMATS` | (none) |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/eventee-automation/SKILL.md b/plugins/awesome-claude-skills/eventee-automation/SKILL.md
new file mode 100644
index 0000000..4bc0517
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/eventzilla-automation/SKILL.md b/plugins/awesome-claude-skills/eventzilla-automation/SKILL.md
new file mode 100644
index 0000000..6f2600a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/everhour-automation/SKILL.md b/plugins/awesome-claude-skills/everhour-automation/SKILL.md
new file mode 100644
index 0000000..ef7bc5f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/eversign-automation/SKILL.md b/plugins/awesome-claude-skills/eversign-automation/SKILL.md
new file mode 100644
index 0000000..88b5a9f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/exa-automation/SKILL.md b/plugins/awesome-claude-skills/exa-automation/SKILL.md
new file mode 100644
index 0000000..886e92d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/excel-automation/SKILL.md b/plugins/awesome-claude-skills/excel-automation/SKILL.md
new file mode 100644
index 0000000..e18eb13
--- /dev/null
+++ b/plugins/awesome-claude-skills/excel-automation/SKILL.md
@@ -0,0 +1,203 @@
+---
+name: Excel Automation
+description: "Excel Automation: create workbooks, manage worksheets, read/write cell data, and format spreadsheets via Microsoft Excel and Google Sheets integration"
+requires:
+ mcp: [rube]
+---
+
+# Excel Automation
+
+Automate spreadsheet operations including creating workbooks, writing data, formatting cells, upserting rows, and managing worksheets. Works with Microsoft Excel (OneDrive) and Google Sheets.
+
+**Toolkit docs:** [composio.dev/toolkits/excel](https://composio.dev/toolkits/excel)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure an active connection exists for the `excel` (and optionally `googlesheets`) toolkit. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+---
+
+## Core Workflows
+
+### 1. Create a New Excel Workbook
+
+Use `EXCEL_CREATE_WORKBOOK` to generate a new `.xlsx` file and upload it to OneDrive.
+
+**Tool:** `EXCEL_CREATE_WORKBOOK`
+
+**Steps:**
+1. Call `EXCEL_CREATE_WORKBOOK` with worksheet names and data
+2. The tool creates a `.xlsx` file and uploads it to OneDrive
+3. Use the returned file path/URL for subsequent operations
+
+---
+
+### 2. Write Data to a Spreadsheet
+
+Use `GOOGLESHEETS_BATCH_UPDATE` to write values to a specific range or append rows.
+
+**Tool:** `GOOGLESHEETS_BATCH_UPDATE`
+
+**Key Parameters:**
+- `spreadsheet_id` (required) -- The spreadsheet ID from the URL (44-char alphanumeric string)
+- `sheet_name` (required) -- Tab name, e.g., `"Sheet1"`, `"Sales Data"`
+- `values` (required) -- 2D array of cell values, e.g., `[["Name","Amount"],["Alice",100]]`
+- `first_cell_location` -- Starting cell in A1 notation (e.g., `"A1"`, `"D3"`). Omit to append rows
+- `valueInputOption` -- `"USER_ENTERED"` (default, parses formulas) or `"RAW"` (stores as-is)
+
+**Example:**
+```
+Tool: GOOGLESHEETS_BATCH_UPDATE
+Arguments:
+ spreadsheet_id: "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms"
+ sheet_name: "Sheet1"
+ values: [["Item","Cost","Stocked"],["Wheel",20.50,true],["Screw",0.50,true]]
+ first_cell_location: "A1"
+```
+
+---
+
+### 3. Upsert Rows by Key Column
+
+Use `GOOGLESHEETS_UPSERT_ROWS` to update existing rows by matching a key column, or append new rows if no match is found. Ideal for CRM syncs, inventory updates, and deduplication.
+
+**Tool:** `GOOGLESHEETS_UPSERT_ROWS`
+
+**Key Parameters:**
+- `spreadsheetId` (required) -- The spreadsheet ID
+- `sheetName` (required) -- Tab name
+- `rows` (required) -- 2D array of data rows (min 1 row). If `headers` is omitted, the first row is treated as headers
+- `headers` -- Column names for the data, e.g., `["Email","Phone","Status"]`
+- `keyColumn` -- Column header to match on, e.g., `"Email"`, `"SKU"`, `"Lead ID"`
+- `strictMode` -- `true` (default) errors on mismatched columns; `false` truncates silently
+
+**Example:**
+```
+Tool: GOOGLESHEETS_UPSERT_ROWS
+Arguments:
+ spreadsheetId: "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms"
+ sheetName: "Contacts"
+ keyColumn: "Email"
+ headers: ["Email","Phone","Status"]
+ rows: [["john@example.com","555-0101","Active"],["jane@example.com","555-0102","Pending"]]
+```
+
+---
+
+### 4. Format Cells
+
+Use `GOOGLESHEETS_FORMAT_CELL` to apply bold, italic, font size, and background colors to ranges.
+
+**Tool:** `GOOGLESHEETS_FORMAT_CELL`
+
+**Key Parameters:**
+- `spreadsheet_id` (required) -- The spreadsheet ID
+- `range` -- Cell range in A1 notation, e.g., `"A1:D1"`, `"B2:B10"` (recommended over index-based)
+- `sheet_name` -- Worksheet name, e.g., `"Sheet1"`
+- `bold` -- `true`/`false`
+- `italic` -- `true`/`false`
+- `fontSize` -- Font size in points, e.g., `12`
+- `red`, `green`, `blue` -- Background color components (0.0--1.0 float scale, NOT 0--255)
+
+**Example (bold header row with blue background):**
+```
+Tool: GOOGLESHEETS_FORMAT_CELL
+Arguments:
+ spreadsheet_id: "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms"
+ range: "A1:D1"
+ sheet_name: "Sheet1"
+ bold: true
+ fontSize: 12
+ red: 0.2
+ green: 0.4
+ blue: 0.9
+```
+
+---
+
+### 5. Add New Worksheet Tabs
+
+Use `GOOGLESHEETS_ADD_SHEET` to create new tabs within an existing spreadsheet.
+
+**Tool:** `GOOGLESHEETS_ADD_SHEET`
+
+**Key Parameters:**
+- `spreadsheetId` (required) -- The spreadsheet ID
+- `title` -- Name for the new tab, e.g., `"Q4 Report"`
+- `forceUnique` -- `true` (default) auto-appends suffix if name exists
+
+**Example:**
+```
+Tool: GOOGLESHEETS_ADD_SHEET
+Arguments:
+ spreadsheetId: "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms"
+ title: "Q4 Report"
+ forceUnique: true
+```
+
+---
+
+### 6. Read Data and Verify Content
+
+Use `GOOGLESHEETS_BATCH_GET` to retrieve data from specified cell ranges for validation or further processing.
+
+**Tool:** `GOOGLESHEETS_BATCH_GET`
+
+**Steps:**
+1. Call `GOOGLESHEETS_BATCH_GET` with the spreadsheet ID and target ranges
+2. Validate headers and data alignment
+3. Use results to inform subsequent write or update operations
+
+**Supporting Tools:**
+- `GOOGLESHEETS_GET_SHEET_NAMES` -- List all tab names in a spreadsheet
+- `GOOGLESHEETS_GET_SPREADSHEET_INFO` -- Get metadata (sheet IDs, properties)
+- `GOOGLESHEETS_FIND_WORKSHEET_BY_TITLE` -- Check if a specific tab exists
+
+---
+
+## Recommended Execution Plan
+
+1. **Create or locate the spreadsheet** using `GOOGLESHEETS_CREATE_GOOGLE_SHEET1` or reuse an existing `spreadsheetId`
+2. **Confirm the destination tab** using `GOOGLESHEETS_GET_SHEET_NAMES` or `GOOGLESHEETS_FIND_WORKSHEET_BY_TITLE`; create it with `GOOGLESHEETS_ADD_SHEET` if missing
+3. **Read existing headers** (optional) using `GOOGLESHEETS_BATCH_GET` to align columns
+4. **Write or upsert data** using `GOOGLESHEETS_BATCH_UPDATE` or `GOOGLESHEETS_UPSERT_ROWS`
+5. **Apply formatting** (optional) using `GOOGLESHEETS_FORMAT_CELL`
+6. **Verify results** (optional) using `GOOGLESHEETS_BATCH_GET`
+7. **Fallback:** If Google Sheets creation is blocked (HTTP 403), use `EXCEL_CREATE_WORKBOOK` for local `.xlsx` output
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **HTTP 403 on sheet creation** | `GOOGLESHEETS_CREATE_GOOGLE_SHEET1` fails when Drive create scope is missing. Reuse an existing `spreadsheetId` or fall back to `EXCEL_CREATE_WORKBOOK`. |
+| **Cell limit and rate throttling** | Google Sheets has a ~5,000,000 cell limit per spreadsheet. Excessive write frequency triggers HTTP 429. Batch changes and chunk large writes (~500 rows/call). |
+| **Format range off-by-one** | `GOOGLESHEETS_FORMAT_CELL` uses 0-based, endIndex-exclusive ranges when using index mode. Background color uses 0--1 float RGB, NOT 0--255 integer RGB. |
+| **Sheet title uniqueness** | Sheet titles are not guaranteed unique across API responses. Prefer operating by numeric `sheetId` and verify the resolved tab before writing. |
+| **Upsert payload shape** | `GOOGLESHEETS_UPSERT_ROWS` requires headers + 2D rows array. Sending list-of-dicts or empty `rows` causes validation errors. Ensure at least 1 data row. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `EXCEL_CREATE_WORKBOOK` | Create a new `.xlsx` workbook and upload to OneDrive |
+| `GOOGLESHEETS_BATCH_UPDATE` | Write values to a range or append new rows |
+| `GOOGLESHEETS_UPSERT_ROWS` | Update existing rows by key or append new ones |
+| `GOOGLESHEETS_FORMAT_CELL` | Apply text/background formatting to cell ranges |
+| `GOOGLESHEETS_ADD_SHEET` | Add a new worksheet tab to a spreadsheet |
+| `GOOGLESHEETS_CREATE_GOOGLE_SHEET1` | Create a new Google Spreadsheet in Drive |
+| `GOOGLESHEETS_GET_SHEET_NAMES` | List all worksheet names in a spreadsheet |
+| `GOOGLESHEETS_GET_SPREADSHEET_INFO` | Retrieve spreadsheet metadata |
+| `GOOGLESHEETS_FIND_WORKSHEET_BY_TITLE` | Check if a worksheet exists by title |
+| `GOOGLESHEETS_BATCH_GET` | Read data from specified cell ranges |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/exist-automation/SKILL.md b/plugins/awesome-claude-skills/exist-automation/SKILL.md
new file mode 100644
index 0000000..7ef45ba
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/expofp-automation/SKILL.md b/plugins/awesome-claude-skills/expofp-automation/SKILL.md
new file mode 100644
index 0000000..5589928
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/extracta-ai-automation/SKILL.md b/plugins/awesome-claude-skills/extracta-ai-automation/SKILL.md
new file mode 100644
index 0000000..63f75c4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/facebook-automation/SKILL.md b/plugins/awesome-claude-skills/facebook-automation/SKILL.md
new file mode 100644
index 0000000..273a9c2
--- /dev/null
+++ b/plugins/awesome-claude-skills/facebook-automation/SKILL.md
@@ -0,0 +1,164 @@
+---
+name: Facebook Automation
+description: "Automate Facebook Page management including post creation, scheduling, video uploads, Messenger conversations, and audience engagement via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# Facebook Automation
+
+Automate Facebook Page operations -- create and schedule posts, upload videos, manage Messenger conversations, retrieve page insights, and handle scheduled content -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/facebook](https://composio.dev/toolkits/facebook)
+
+---
+
+## Setup
+
+1. Connect your Facebook account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `FACEBOOK_*` tools become available for execution
+4. **Note:** This toolkit supports Facebook Pages only, not personal Facebook accounts
+
+---
+
+## Core Workflows
+
+### 1. Discover Managed Pages
+List all Facebook Pages you manage to get page IDs and access tokens for subsequent operations.
+
+**Tool:** `FACEBOOK_LIST_MANAGED_PAGES`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `fields` | string | No | Comma-separated fields (default: `id,name,access_token,category,tasks,about,link,picture`) |
+| `limit` | integer | No | Max pages per request (default: 25) |
+| `user_id` | string | No | User ID (default: `me`) |
+
+**Always run this first** to cache `page_id` values. Avoid repeating discovery calls -- cache the results.
+
+---
+
+### 2. Create & Schedule Posts
+Publish or schedule text posts with optional links on a Facebook Page.
+
+**Tool:** `FACEBOOK_CREATE_POST`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `page_id` | string | Yes | Numeric Page ID from managed pages |
+| `message` | string | Yes | Text content of the post |
+| `published` | boolean | No | `true` to publish immediately, `false` for draft/scheduled (default: true) |
+| `scheduled_publish_time` | integer | No | Unix UTC timestamp; must be at least 10 minutes in the future |
+| `link` | string | No | URL to include in the post |
+| `targeting` | object | No | Audience targeting specifications |
+
+**When scheduling:** Set `published=false` and provide `scheduled_publish_time` as a Unix UTC timestamp.
+
+---
+
+### 3. Create & Schedule Video Posts
+Upload and schedule video content on a Facebook Page.
+
+**Tool:** `FACEBOOK_CREATE_VIDEO_POST`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `page_id` | string | Yes | Numeric Page ID |
+| `file_url` | string | Conditional | URL of the video file (provide `file_url` or `video`) |
+| `video` | object | Conditional | Local file upload with `name`, `mimetype`, `s3key` |
+| `title` | string | No | Video title |
+| `description` | string | No | Video description |
+| `published` | boolean | No | Publish immediately (default: true) |
+| `scheduled_publish_time` | integer | No | Unix timestamp for scheduled publishing |
+
+---
+
+### 4. Manage Scheduled Posts
+Review, reschedule, update, or publish scheduled content.
+
+**Tools:**
+
+- **`FACEBOOK_GET_SCHEDULED_POSTS`** -- List scheduled/unpublished posts for a page
+ - `page_id` (required), `fields`, `limit` (max 100)
+- **`FACEBOOK_RESCHEDULE_POST`** -- Change the scheduled publish time
+- **`FACEBOOK_UPDATE_POST`** -- Edit caption/text on an existing post
+- **`FACEBOOK_PUBLISH_SCHEDULED_POST`** -- Publish a scheduled post immediately
+
+---
+
+### 5. Read Page Messenger Conversations
+Retrieve inbox conversations and message threads between users and your Page.
+
+**Tool:** `FACEBOOK_GET_PAGE_CONVERSATIONS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `page_id` | string | Yes | The Facebook Page ID |
+| `fields` | string | No | Fields to return (default: `participants,updated_time,id`) |
+| `limit` | integer | No | Conversations to return, max 25 |
+
+Then retrieve full message threads:
+
+**Tool:** `FACEBOOK_GET_CONVERSATION_MESSAGES`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `page_id` | string | Yes | Page ID that owns the conversation |
+| `conversation_id` | string | Yes | Conversation ID in `t_` format (e.g., `t_3638640842939952`) |
+| `fields` | string | No | Default: `id,created_time,from,to,message` |
+| `limit` | integer | No | Messages to return, max 25 |
+
+---
+
+### 6. Send Messages & Mark as Seen
+Respond to users via Messenger and mark messages as read.
+
+**Tools:**
+
+- **`FACEBOOK_SEND_MESSAGE`** -- Send a text message from the Page to a user via Messenger
+- **`FACEBOOK_MARK_MESSAGE_SEEN`** -- Mark a user's message as seen by the Page
+
+**Warning:** Both tools cause user-visible side effects. Only call after explicit confirmation.
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **Scheduling too close to now** | `FACEBOOK_CREATE_POST` with `scheduled_publish_time` less than ~10 minutes in the future returns HTTP 400 -- enforce a larger buffer for bulk runs |
+| **Unix UTC timestamps required** | `scheduled_publish_time` must be Unix UTC -- timezone conversion mistakes cause off-by-hours scheduling or validation failures |
+| **Cursor-based pagination** | `FACEBOOK_GET_SCHEDULED_POSTS` and `FACEBOOK_GET_PAGE_CONVERSATIONS` return subsets -- follow paging cursors to get complete data |
+| **Large conversation payloads** | Requesting embedded messages in conversations creates huge payloads -- use `FACEBOOK_GET_CONVERSATION_MESSAGES` for full threads instead |
+| **Video processing delays** | Uploaded videos may remain in processing state -- only schedule via `FACEBOOK_CREATE_VIDEO_POST` after the upload is usable |
+| **Cache page IDs** | Repeating `FACEBOOK_LIST_MANAGED_PAGES` calls adds latency -- cache `page_id` per workspace/run |
+| **Pages only** | This toolkit does not support personal Facebook accounts -- only Facebook Pages |
+| **Write operations need confirmation** | `FACEBOOK_SEND_MESSAGE` and `FACEBOOK_MARK_MESSAGE_SEEN` cause user-visible side effects -- only call after explicit user confirmation |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `FACEBOOK_LIST_MANAGED_PAGES` | List Pages you manage with access tokens |
+| `FACEBOOK_GET_PAGE_DETAILS` | Get detailed info about a specific Page |
+| `FACEBOOK_CREATE_POST` | Create or schedule a text/link post |
+| `FACEBOOK_CREATE_VIDEO_POST` | Create or schedule a video post |
+| `FACEBOOK_GET_SCHEDULED_POSTS` | List scheduled/unpublished posts |
+| `FACEBOOK_RESCHEDULE_POST` | Change scheduled publish time |
+| `FACEBOOK_UPDATE_POST` | Edit an existing post |
+| `FACEBOOK_PUBLISH_SCHEDULED_POST` | Publish a scheduled post immediately |
+| `FACEBOOK_UPLOAD_VIDEO` | Upload a video file to a Page |
+| `FACEBOOK_GET_PAGE_CONVERSATIONS` | List Messenger inbox conversations |
+| `FACEBOOK_GET_CONVERSATION_MESSAGES` | Retrieve messages from a conversation |
+| `FACEBOOK_SEND_MESSAGE` | Send a Messenger message from the Page |
+| `FACEBOOK_MARK_MESSAGE_SEEN` | Mark a message as seen |
+| `FACEBOOK_GET_PAGE_POSTS` | Retrieve posts from a Page feed |
+| `FACEBOOK_GET_USER_PAGES` | List Pages with tasks and tokens |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/faceup-automation/SKILL.md b/plugins/awesome-claude-skills/faceup-automation/SKILL.md
new file mode 100644
index 0000000..5302a19
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/factorial-automation/SKILL.md b/plugins/awesome-claude-skills/factorial-automation/SKILL.md
new file mode 100644
index 0000000..306c812
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/feathery-automation/SKILL.md b/plugins/awesome-claude-skills/feathery-automation/SKILL.md
new file mode 100644
index 0000000..67055f6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/felt-automation/SKILL.md b/plugins/awesome-claude-skills/felt-automation/SKILL.md
new file mode 100644
index 0000000..a269c81
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fibery-automation/SKILL.md b/plugins/awesome-claude-skills/fibery-automation/SKILL.md
new file mode 100644
index 0000000..90fa97c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fidel-api-automation/SKILL.md b/plugins/awesome-claude-skills/fidel-api-automation/SKILL.md
new file mode 100644
index 0000000..2a79618
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/figma-automation/SKILL.md b/plugins/awesome-claude-skills/figma-automation/SKILL.md
new file mode 100644
index 0000000..86bab70
--- /dev/null
+++ b/plugins/awesome-claude-skills/figma-automation/SKILL.md
@@ -0,0 +1,186 @@
+---
+name: figma-automation
+description: "Automate Figma tasks via Rube MCP (Composio): files, components, design tokens, comments, exports. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Figma Automation via Rube MCP
+
+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)
+- Active Figma connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `figma`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `figma`
+3. If connection is not ACTIVE, follow the returned auth link to complete Figma auth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Get File Data and Components
+
+**When to use**: User wants to inspect Figma design files or extract component information
+
+**Tool sequence**:
+1. `FIGMA_DISCOVER_FIGMA_RESOURCES` - Extract IDs from Figma URLs [Prerequisite]
+2. `FIGMA_GET_FILE_JSON` - Get file data (simplified by default) [Required]
+3. `FIGMA_GET_FILE_NODES` - Get specific node data [Optional]
+4. `FIGMA_GET_FILE_COMPONENTS` - List published components [Optional]
+5. `FIGMA_GET_FILE_COMPONENT_SETS` - List component sets [Optional]
+
+**Key parameters**:
+- `file_key`: File key from URL (e.g., 'abc123XYZ' from figma.com/design/abc123XYZ/...)
+- `ids`: Comma-separated node IDs (NOT an array)
+- `depth`: Tree traversal depth (2 for pages and top-level children)
+- `simplify`: True for AI-friendly format (70%+ size reduction)
+
+**Pitfalls**:
+- Only supports Design files; FigJam boards and Slides return 400 errors
+- `ids` must be a comma-separated string, not an array
+- Node IDs may be dash-formatted (1-541) in URLs but need colon format (1:541) for API
+- Broad ids/depth can trigger oversized payloads (413); narrow scope or reduce depth
+- Response data may be in `data_preview` instead of `data`
+
+### 2. Export and Render Images
+
+**When to use**: User wants to export design assets as images
+
+**Tool sequence**:
+1. `FIGMA_GET_FILE_JSON` - Find node IDs to export [Prerequisite]
+2. `FIGMA_RENDER_IMAGES_OF_FILE_NODES` - Render nodes as images [Required]
+3. `FIGMA_DOWNLOAD_FIGMA_IMAGES` - Download rendered images [Optional]
+4. `FIGMA_GET_IMAGE_FILLS` - Get image fill URLs [Optional]
+
+**Key parameters**:
+- `file_key`: File key
+- `ids`: Comma-separated node IDs to render
+- `format`: 'png', 'svg', 'jpg', or 'pdf'
+- `scale`: Scale factor (0.01-4.0) for PNG/JPG
+- `images`: Array of {node_id, file_name, format} for downloads
+
+**Pitfalls**:
+- Images return as node_id-to-URL map; some IDs may be null (failed renders)
+- URLs are temporary (valid ~30 days)
+- Images capped at 32 megapixels; larger requests auto-scaled down
+
+### 3. Extract Design Tokens
+
+**When to use**: User wants to extract design tokens for development
+
+**Tool sequence**:
+1. `FIGMA_EXTRACT_DESIGN_TOKENS` - Extract colors, typography, spacing [Required]
+2. `FIGMA_DESIGN_TOKENS_TO_TAILWIND` - Convert to Tailwind config [Optional]
+
+**Key parameters**:
+- `file_key`: File key
+- `include_local_styles`: Include local styles (default true)
+- `include_variables`: Include Figma variables
+- `tokens`: Full tokens object from extraction (for Tailwind conversion)
+
+**Pitfalls**:
+- Tailwind conversion requires the full tokens object including total_tokens and sources
+- Do not strip fields from the extraction response before passing to conversion
+
+### 4. Manage Comments and Versions
+
+**When to use**: User wants to view or add comments, or inspect version history
+
+**Tool sequence**:
+1. `FIGMA_GET_COMMENTS_IN_A_FILE` - List all file comments [Optional]
+2. `FIGMA_ADD_A_COMMENT_TO_A_FILE` - Add a comment [Optional]
+3. `FIGMA_GET_REACTIONS_FOR_A_COMMENT` - Get comment reactions [Optional]
+4. `FIGMA_GET_VERSIONS_OF_A_FILE` - Get version history [Optional]
+
+**Key parameters**:
+- `file_key`: File key
+- `as_md`: Return comments in Markdown format
+- `message`: Comment text
+- `comment_id`: Comment ID for reactions
+
+**Pitfalls**:
+- Comments can be positioned on specific nodes using client_meta
+- Reply comments cannot be nested (only one level of replies)
+
+### 5. Browse Projects and Teams
+
+**When to use**: User wants to list team projects or files
+
+**Tool sequence**:
+1. `FIGMA_GET_PROJECTS_IN_A_TEAM` - List team projects [Optional]
+2. `FIGMA_GET_FILES_IN_A_PROJECT` - List project files [Optional]
+3. `FIGMA_GET_TEAM_STYLES` - List team published styles [Optional]
+
+**Key parameters**:
+- `team_id`: Team ID from URL (figma.com/files/team/TEAM_ID/...)
+- `project_id`: Project ID
+
+**Pitfalls**:
+- Team ID cannot be obtained programmatically; extract from Figma URL
+- Only published styles/components are returned by team endpoints
+
+## Common Patterns
+
+### URL Parsing
+
+Extract IDs from Figma URLs:
+```
+1. Call FIGMA_DISCOVER_FIGMA_RESOURCES with figma_url
+2. Extract file_key, node_id, team_id from response
+3. Convert dash-format node IDs (1-541) to colon format (1:541)
+```
+
+### Node Traversal
+
+```
+1. Call FIGMA_GET_FILE_JSON with depth=2 for overview
+2. Identify target nodes from the response
+3. Call again with specific ids and higher depth for details
+```
+
+## Known Pitfalls
+
+**File Type Support**:
+- GET_FILE_JSON only supports Design files (figma.com/design/ or figma.com/file/)
+- FigJam boards (figma.com/board/) and Slides (figma.com/slides/) are NOT supported
+
+**Node ID Formats**:
+- URLs use dash format: `node-id=1-541`
+- API uses colon format: `1:541`
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Parse URL | FIGMA_DISCOVER_FIGMA_RESOURCES | figma_url |
+| Get file JSON | FIGMA_GET_FILE_JSON | file_key, ids, depth |
+| Get nodes | FIGMA_GET_FILE_NODES | file_key, ids |
+| Render images | FIGMA_RENDER_IMAGES_OF_FILE_NODES | file_key, ids, format |
+| Download images | FIGMA_DOWNLOAD_FIGMA_IMAGES | file_key, images |
+| Get component | FIGMA_GET_COMPONENT | file_key, node_id |
+| File components | FIGMA_GET_FILE_COMPONENTS | file_key |
+| Component sets | FIGMA_GET_FILE_COMPONENT_SETS | file_key |
+| Design tokens | FIGMA_EXTRACT_DESIGN_TOKENS | file_key |
+| Tokens to Tailwind | FIGMA_DESIGN_TOKENS_TO_TAILWIND | tokens |
+| File comments | FIGMA_GET_COMMENTS_IN_A_FILE | file_key |
+| Add comment | FIGMA_ADD_A_COMMENT_TO_A_FILE | file_key, message |
+| File versions | FIGMA_GET_VERSIONS_OF_A_FILE | file_key |
+| Team projects | FIGMA_GET_PROJECTS_IN_A_TEAM | team_id |
+| Project files | FIGMA_GET_FILES_IN_A_PROJECT | project_id |
+| 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/plugins/awesome-claude-skills/files-com-automation/SKILL.md b/plugins/awesome-claude-skills/files-com-automation/SKILL.md
new file mode 100644
index 0000000..3bd46b6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fillout-forms-automation/SKILL.md b/plugins/awesome-claude-skills/fillout-forms-automation/SKILL.md
new file mode 100644
index 0000000..17c9ae5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fillout_forms-automation/SKILL.md b/plugins/awesome-claude-skills/fillout_forms-automation/SKILL.md
new file mode 100644
index 0000000..64fd957
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/finage-automation/SKILL.md b/plugins/awesome-claude-skills/finage-automation/SKILL.md
new file mode 100644
index 0000000..24badea
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/findymail-automation/SKILL.md b/plugins/awesome-claude-skills/findymail-automation/SKILL.md
new file mode 100644
index 0000000..3562abd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/finerworks-automation/SKILL.md b/plugins/awesome-claude-skills/finerworks-automation/SKILL.md
new file mode 100644
index 0000000..eb4db42
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fingertip-automation/SKILL.md b/plugins/awesome-claude-skills/fingertip-automation/SKILL.md
new file mode 100644
index 0000000..bdf84cd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/finmei-automation/SKILL.md b/plugins/awesome-claude-skills/finmei-automation/SKILL.md
new file mode 100644
index 0000000..992382a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fireberry-automation/SKILL.md b/plugins/awesome-claude-skills/fireberry-automation/SKILL.md
new file mode 100644
index 0000000..0165bb0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/firecrawl-automation/SKILL.md b/plugins/awesome-claude-skills/firecrawl-automation/SKILL.md
new file mode 100644
index 0000000..064c460
--- /dev/null
+++ b/plugins/awesome-claude-skills/firecrawl-automation/SKILL.md
@@ -0,0 +1,177 @@
+---
+name: Firecrawl Automation
+description: "Automate web crawling and data extraction with Firecrawl -- scrape pages, crawl sites, extract structured data, batch scrape URLs, and map website structures through the Composio Firecrawl integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Firecrawl Automation
+
+Run **Firecrawl** web crawling and extraction directly from Claude Code. Scrape individual pages, crawl entire sites, extract structured data with AI, batch process URL lists, and map website structures without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/firecrawl](https://composio.dev/toolkits/firecrawl)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Firecrawl account when prompted. The agent will provide an authentication link.
+3. Be mindful of credit consumption -- scope your crawls tightly and test on small URL sets before scaling.
+
+---
+
+## Core Workflows
+
+### 1. Scrape a Single Page
+
+Fetch content from a URL in multiple formats with optional browser actions for dynamic pages.
+
+**Tool:** `FIRECRAWL_SCRAPE`
+
+Key parameters:
+- `url` (required) -- fully qualified URL to scrape
+- `formats` -- output formats: `markdown` (default), `html`, `rawHtml`, `links`, `screenshot`, `json`
+- `onlyMainContent` (default true) -- extract main content only, excluding nav/footer/ads
+- `waitFor` -- milliseconds to wait for JS rendering (default 0)
+- `timeout` -- max wait in ms (default 30000)
+- `actions` -- browser actions before scraping (click, write, wait, press, scroll)
+- `includeTags` / `excludeTags` -- filter by HTML tags
+- `jsonOptions` -- for structured extraction with `schema` and/or `prompt`
+
+Example prompt: *"Scrape the main content from https://example.com/pricing as markdown"*
+
+---
+
+### 2. Crawl an Entire Site
+
+Discover and scrape multiple pages from a website with configurable depth, path filters, and concurrency.
+
+**Tool:** `FIRECRAWL_CRAWL_V2`
+
+Key parameters:
+- `url` (required) -- starting URL for the crawl
+- `limit` (default 10) -- max pages to crawl
+- `maxDiscoveryDepth` -- depth limit from the root page
+- `includePaths` / `excludePaths` -- regex patterns for URL paths
+- `allowSubdomains` -- include subdomains (default false)
+- `crawlEntireDomain` -- follow sibling/parent links, not just children (default false)
+- `sitemap` -- `include` (default), `skip`, or `only`
+- `prompt` -- natural language to auto-configure crawler settings
+- `scrapeOptions_formats` -- output format for each page
+- `scrapeOptions_onlyMainContent` -- main content extraction per page
+
+Example prompt: *"Crawl the docs section of firecrawl.dev, max 50 pages, only paths matching docs"*
+
+---
+
+### 3. Extract Structured Data
+
+Extract structured JSON data from web pages using AI with a natural language prompt or JSON schema.
+
+**Tool:** `FIRECRAWL_EXTRACT`
+
+Key parameters:
+- `urls` (required) -- array of URLs to extract from (max 10 in beta). Supports wildcards like `https://example.com/blog/*`
+- `prompt` -- natural language description of what to extract
+- `schema` -- JSON Schema defining the desired output structure
+- `enable_web_search` -- allow crawling links outside initial domains (default false)
+
+At least one of `prompt` or `schema` must be provided.
+
+Check extraction status with `FIRECRAWL_EXTRACT_GET` using the returned job `id`.
+
+Example prompt: *"Extract company name, pricing tiers, and feature lists from https://example.com/pricing"*
+
+---
+
+### 4. Batch Scrape Multiple URLs
+
+Scrape many URLs concurrently with shared configuration for efficient bulk data collection.
+
+**Tool:** `FIRECRAWL_BATCH_SCRAPE`
+
+Key parameters:
+- `urls` (required) -- array of URLs to scrape
+- `formats` -- output format for all pages (default `markdown`)
+- `onlyMainContent` (default true) -- main content extraction
+- `maxConcurrency` -- parallel scrape limit
+- `ignoreInvalidURLs` (default true) -- skip bad URLs instead of failing the batch
+- `location` -- geolocation settings with `country` code
+- `actions` -- browser actions applied to each page
+- `blockAds` (default true) -- block advertisements
+
+Example prompt: *"Batch scrape these 20 product page URLs as markdown with ad blocking"*
+
+---
+
+### 5. Map Website Structure
+
+Discover all URLs on a website from a starting URL, useful for planning crawls or auditing site structure.
+
+**Tool:** `FIRECRAWL_MAP_MULTIPLE_URLS_BASED_ON_OPTIONS`
+
+Key parameters:
+- `url` (required) -- starting URL (must be `https://` or `http://`)
+- `search` -- guide URL discovery toward specific page types
+- `limit` (default 5000, max 100000) -- max URLs to return
+- `includeSubdomains` (default true) -- include subdomains
+- `ignoreQueryParameters` (default true) -- dedupe URLs differing only by query params
+- `sitemap` -- `include`, `skip`, or `only`
+
+Example prompt: *"Map all URLs on docs.example.com, focusing on API reference pages"*
+
+---
+
+### 6. Monitor and Manage Crawl Jobs
+
+Track crawl progress, retrieve results, and cancel runaway jobs.
+
+**Tools:** `FIRECRAWL_CRAWL_GET`, `FIRECRAWL_GET_THE_STATUS_OF_A_CRAWL_JOB`, `FIRECRAWL_CANCEL_A_CRAWL_JOB`
+
+- `FIRECRAWL_CRAWL_GET` -- get status, progress, credits used, and crawled page data
+- `FIRECRAWL_CANCEL_A_CRAWL_JOB` -- stop an active or queued crawl
+
+Both require the crawl job `id` (UUID) returned when the crawl was initiated.
+
+Example prompt: *"Check the status of crawl job 019b0806-b7a1-7652-94c1-e865b5d2e89a"*
+
+---
+
+## Known Pitfalls
+
+- **Rate limiting:** Firecrawl can trigger "Rate limit exceeded" errors (429). Prefer `FIRECRAWL_BATCH_SCRAPE` over many individual `FIRECRAWL_SCRAPE` calls, and implement backoff on 429/5xx responses.
+- **Credit consumption:** `FIRECRAWL_EXTRACT` can fail with "Insufficient credits." Scope tightly and avoid broad homepage URLs that yield sparse fields. Test on small URL sets first.
+- **Nested error responses:** Per-page failures may be nested in `response.data.code` (e.g., `SCRAPE_DNS_RESOLUTION_ERROR`) even when the outer API call succeeds. Always validate inner status/error fields.
+- **JS-heavy pages:** Non-rendered fetches may miss key content. Use `waitFor` (e.g., 1000-5000ms) for dynamic pages, or configure `scrapeOptions_actions` to interact with the page before scraping.
+- **Extraction schema precision:** Vague or shifting schemas/prompts produce noisy, inconsistent output. Freeze your schema and test on a small sample before scaling to many URLs.
+- **Crawl jobs are async:** `FIRECRAWL_CRAWL_V2` returns immediately with a job ID. Use `FIRECRAWL_CRAWL_GET` to poll for results. Cancel stuck crawls with `FIRECRAWL_CANCEL_A_CRAWL_JOB` to avoid wasting credits.
+- **Extract job polling:** `FIRECRAWL_EXTRACT` is also async for larger jobs. Retrieve final output with `FIRECRAWL_EXTRACT_GET`.
+- **URL batching for extract:** Keep extract URL batches small (~10 URLs) to avoid 429 rate limit errors.
+- **Deeply nested responses:** Results are often nested under `data.data` or deeper. Inspect the returned shape rather than assuming flat keys.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `FIRECRAWL_SCRAPE` | Scrape a single URL with format/action options |
+| `FIRECRAWL_CRAWL_V2` | Crawl a website with depth/path control |
+| `FIRECRAWL_EXTRACT` | Extract structured data with AI prompt/schema |
+| `FIRECRAWL_BATCH_SCRAPE` | Batch scrape multiple URLs concurrently |
+| `FIRECRAWL_MAP_MULTIPLE_URLS_BASED_ON_OPTIONS` | Discover/map all URLs on a site |
+| `FIRECRAWL_CRAWL_GET` | Get crawl job status and results |
+| `FIRECRAWL_GET_THE_STATUS_OF_A_CRAWL_JOB` | Check crawl job progress |
+| `FIRECRAWL_CANCEL_A_CRAWL_JOB` | Cancel an active crawl job |
+| `FIRECRAWL_EXTRACT_GET` | Get extraction job status and results |
+| `FIRECRAWL_CRAWL_PARAMS_PREVIEW` | Preview crawl parameters before starting |
+| `FIRECRAWL_SEARCH` | Web search + scrape top results |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/fireflies-automation/SKILL.md b/plugins/awesome-claude-skills/fireflies-automation/SKILL.md
new file mode 100644
index 0000000..7e01f74
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/firmao-automation/SKILL.md b/plugins/awesome-claude-skills/firmao-automation/SKILL.md
new file mode 100644
index 0000000..b09c687
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fitbit-automation/SKILL.md b/plugins/awesome-claude-skills/fitbit-automation/SKILL.md
new file mode 100644
index 0000000..ece8d16
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fixer-automation/SKILL.md b/plugins/awesome-claude-skills/fixer-automation/SKILL.md
new file mode 100644
index 0000000..adc2c88
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fixer-io-automation/SKILL.md b/plugins/awesome-claude-skills/fixer-io-automation/SKILL.md
new file mode 100644
index 0000000..f91f21f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/flexisign-automation/SKILL.md b/plugins/awesome-claude-skills/flexisign-automation/SKILL.md
new file mode 100644
index 0000000..5513714
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/flowiseai-automation/SKILL.md b/plugins/awesome-claude-skills/flowiseai-automation/SKILL.md
new file mode 100644
index 0000000..94992d0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/flutterwave-automation/SKILL.md b/plugins/awesome-claude-skills/flutterwave-automation/SKILL.md
new file mode 100644
index 0000000..aff1120
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fluxguard-automation/SKILL.md b/plugins/awesome-claude-skills/fluxguard-automation/SKILL.md
new file mode 100644
index 0000000..57100c9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/folk-automation/SKILL.md b/plugins/awesome-claude-skills/folk-automation/SKILL.md
new file mode 100644
index 0000000..2bbd26d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fomo-automation/SKILL.md b/plugins/awesome-claude-skills/fomo-automation/SKILL.md
new file mode 100644
index 0000000..4ac4034
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/forcemanager-automation/SKILL.md b/plugins/awesome-claude-skills/forcemanager-automation/SKILL.md
new file mode 100644
index 0000000..00a70bc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/formbricks-automation/SKILL.md b/plugins/awesome-claude-skills/formbricks-automation/SKILL.md
new file mode 100644
index 0000000..6546332
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/formcarry-automation/SKILL.md b/plugins/awesome-claude-skills/formcarry-automation/SKILL.md
new file mode 100644
index 0000000..e2a4de7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/formdesk-automation/SKILL.md b/plugins/awesome-claude-skills/formdesk-automation/SKILL.md
new file mode 100644
index 0000000..d4e7c04
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/formsite-automation/SKILL.md b/plugins/awesome-claude-skills/formsite-automation/SKILL.md
new file mode 100644
index 0000000..8959dd1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/foursquare-automation/SKILL.md b/plugins/awesome-claude-skills/foursquare-automation/SKILL.md
new file mode 100644
index 0000000..9388753
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fraudlabs-pro-automation/SKILL.md b/plugins/awesome-claude-skills/fraudlabs-pro-automation/SKILL.md
new file mode 100644
index 0000000..0fb89ac
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/freshbooks-automation/SKILL.md b/plugins/awesome-claude-skills/freshbooks-automation/SKILL.md
new file mode 100644
index 0000000..822d211
--- /dev/null
+++ b/plugins/awesome-claude-skills/freshbooks-automation/SKILL.md
@@ -0,0 +1,140 @@
+---
+name: FreshBooks Automation
+description: "FreshBooks Automation: manage businesses, projects, time tracking, and billing in FreshBooks cloud accounting"
+requires:
+ mcp: [rube]
+---
+
+# FreshBooks Automation
+
+Automate FreshBooks operations including listing businesses, managing projects, tracking time, and monitoring budgets for small and medium-sized business accounting.
+
+**Toolkit docs:** [composio.dev/toolkits/freshbooks](https://composio.dev/toolkits/freshbooks)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure an active connection exists for the `freshbooks` toolkit. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+---
+
+## Core Workflows
+
+### 1. List Businesses
+
+Retrieve all businesses associated with the authenticated user. The `business_id` from this response is required for most other FreshBooks API calls.
+
+**Tool:** `FRESHBOOKS_LIST_BUSINESSES`
+
+**Parameters:** None required.
+
+**Example:**
+```
+Tool: FRESHBOOKS_LIST_BUSINESSES
+Arguments: {}
+```
+
+**Output:** Returns business membership information including all businesses the user has access to, along with their role in each business.
+
+> **Important:** Always call this first to obtain a valid `business_id` before performing project-specific operations.
+
+---
+
+### 2. List and Filter Projects
+
+Retrieve all projects for a business with comprehensive filtering and sorting options.
+
+**Tool:** `FRESHBOOKS_LIST_PROJECTS`
+
+**Key Parameters:**
+- `business_id` (required) -- Business ID obtained from `FRESHBOOKS_LIST_BUSINESSES`
+- `active` -- Filter by active status: `true` (active only), `false` (inactive only), omit for all
+- `complete` -- Filter by completion: `true` (completed), `false` (incomplete), omit for all
+- `sort_by` -- Sort order: `"created_at"`, `"due_date"`, or `"title"`
+- `updated_since` -- UTC datetime in RFC3339 format, e.g., `"2026-01-01T00:00:00Z"`
+- `include_logged_duration` -- `true` to include total logged time (in seconds) per project
+- `skip_group` -- `true` to omit team member/invitation data (reduces response size)
+
+**Example:**
+```
+Tool: FRESHBOOKS_LIST_PROJECTS
+Arguments:
+ business_id: 123456
+ active: true
+ complete: false
+ sort_by: "due_date"
+ include_logged_duration: true
+```
+
+**Use Cases:**
+- Get all projects for time tracking or invoicing
+- Find projects by client, status, or date range
+- Monitor project completion and budget tracking
+- Retrieve team assignments and project groups
+
+---
+
+### 3. Monitor Active Projects
+
+Track project progress and budgets by filtering for active, incomplete projects.
+
+**Steps:**
+1. Call `FRESHBOOKS_LIST_BUSINESSES` to get `business_id`
+2. Call `FRESHBOOKS_LIST_PROJECTS` with `active: true`, `complete: false`, `include_logged_duration: true`
+3. Analyze logged duration vs. budget for each project
+
+---
+
+### 4. Review Recently Updated Projects
+
+Check for recent project activity using the `updated_since` filter.
+
+**Steps:**
+1. Call `FRESHBOOKS_LIST_BUSINESSES` to get `business_id`
+2. Call `FRESHBOOKS_LIST_PROJECTS` with `updated_since` set to your cutoff datetime
+3. Review returned projects for recent changes
+
+**Example:**
+```
+Tool: FRESHBOOKS_LIST_PROJECTS
+Arguments:
+ business_id: 123456
+ updated_since: "2026-02-01T00:00:00Z"
+ sort_by: "created_at"
+```
+
+---
+
+## Recommended Execution Plan
+
+1. **Get the business ID** by calling `FRESHBOOKS_LIST_BUSINESSES`
+2. **List projects** using `FRESHBOOKS_LIST_PROJECTS` with the obtained `business_id`
+3. **Filter as needed** using `active`, `complete`, `updated_since`, and `sort_by` parameters
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **business_id required** | Most FreshBooks operations require a `business_id`. Always call `FRESHBOOKS_LIST_BUSINESSES` first to obtain it. |
+| **Date format** | The `updated_since` parameter must be in RFC3339 format: `"2026-01-01T00:00:00Z"`. Other formats will fail. |
+| **Paginated results** | Project list responses are paginated. Check for additional pages in the response. |
+| **Empty results** | Returns an empty list if no projects exist or match the applied filters. This is not an error. |
+| **Logged duration units** | When `include_logged_duration` is true, the duration is returned in seconds. Convert to hours (divide by 3600) for display. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `FRESHBOOKS_LIST_BUSINESSES` | List all businesses for the authenticated user |
+| `FRESHBOOKS_LIST_PROJECTS` | List projects with filtering and sorting for a business |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/freshdesk-automation/SKILL.md b/plugins/awesome-claude-skills/freshdesk-automation/SKILL.md
new file mode 100644
index 0000000..fd11b62
--- /dev/null
+++ b/plugins/awesome-claude-skills/freshdesk-automation/SKILL.md
@@ -0,0 +1,224 @@
+---
+name: freshdesk-automation
+description: Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Freshdesk Automation via Rube MCP
+
+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)
+- Active Freshdesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshdesk`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `freshdesk`
+3. If connection is not ACTIVE, follow the returned auth link to complete Freshdesk authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Tickets
+
+**When to use**: User wants to create a new support ticket, update an existing ticket, or view ticket details.
+
+**Tool sequence**:
+1. `FRESHDESK_SEARCH_CONTACTS` - Find requester by email to get requester_id [Optional]
+2. `FRESHDESK_LIST_TICKET_FIELDS` - Check available custom fields and statuses [Optional]
+3. `FRESHDESK_CREATE_TICKET` - Create a new ticket with subject, description, requester info [Required]
+4. `FRESHDESK_UPDATE_TICKET` - Modify ticket status, priority, assignee, or other fields [Optional]
+5. `FRESHDESK_VIEW_TICKET` - Retrieve full ticket details by ID [Optional]
+
+**Key parameters for FRESHDESK_CREATE_TICKET**:
+- `subject`: Ticket subject (required)
+- `description`: HTML content of the ticket (required)
+- `email`: Requester email (at least one requester identifier required)
+- `requester_id`: User ID of requester (alternative to email)
+- `status`: 2=Open, 3=Pending, 4=Resolved, 5=Closed (default 2)
+- `priority`: 1=Low, 2=Medium, 3=High, 4=Urgent (default 1)
+- `source`: 1=Email, 2=Portal, 3=Phone, 7=Chat (default 2)
+- `responder_id`: Agent ID to assign the ticket to
+- `group_id`: Group to assign the ticket to
+- `tags`: Array of tag strings
+- `custom_fields`: Object with `cf_` keys
+
+**Pitfalls**:
+- At least one requester identifier is required: `requester_id`, `email`, `phone`, `facebook_id`, `twitter_id`, or `unique_external_id`
+- If `phone` is provided without `email`, then `name` becomes mandatory
+- `description` supports HTML formatting
+- `attachments` field expects multipart/form-data format, not file paths or URLs
+- Custom field keys must be prefixed with `cf_` (e.g., `cf_reference_number`)
+- Status and priority are integers, not strings
+
+### 2. Search and Filter Tickets
+
+**When to use**: User wants to find tickets by status, priority, date range, agent, or custom fields.
+
+**Tool sequence**:
+1. `FRESHDESK_GET_TICKETS` - List tickets with simple filters (status, priority, agent) [Required]
+2. `FRESHDESK_GET_SEARCH` - Advanced ticket search with query syntax [Required]
+3. `FRESHDESK_VIEW_TICKET` - Get full details for specific tickets from results [Optional]
+4. `FRESHDESK_LIST_TICKET_FIELDS` - Check available fields for search queries [Optional]
+
+**Key parameters for FRESHDESK_GET_TICKETS**:
+- `status`: Filter by status integer (2=Open, 3=Pending, 4=Resolved, 5=Closed)
+- `priority`: Filter by priority integer (1-4)
+- `agent_id`: Filter by assigned agent
+- `requester_id`: Filter by requester
+- `email`: Filter by requester email
+- `created_since`: ISO 8601 timestamp
+- `page` / `per_page`: Pagination (default 30 per page)
+- `sort_by` / `sort_order`: Sort field and direction
+
+**Key parameters for FRESHDESK_GET_SEARCH**:
+- `query`: Query string like `"status:2 AND priority:3"` or `"(created_at:>'2024-01-01' AND tag:'urgent')"`
+- `page`: Page number (1-10, max 300 total results)
+
+**Pitfalls**:
+- `FRESHDESK_GET_SEARCH` query must be enclosed in double quotes
+- Query string limited to 512 characters
+- Maximum 10 pages (300 results) from search endpoints
+- Date fields in queries use UTC format YYYY-MM-DD
+- Use `null` keyword to find tickets with empty fields (e.g., `"agent_id:null"`)
+- `FRESHDESK_LIST_ALL_TICKETS` takes no parameters and returns all tickets (use GET_TICKETS for filtering)
+
+### 3. Reply to and Add Notes on Tickets
+
+**When to use**: User wants to send a reply to a customer, add internal notes, or view conversation history.
+
+**Tool sequence**:
+1. `FRESHDESK_VIEW_TICKET` - Verify ticket exists and check current state [Prerequisite]
+2. `FRESHDESK_REPLY_TO_TICKET` - Send a public reply to the requester [Required]
+3. `FRESHDESK_ADD_NOTE_TO_TICKET` - Add a private or public note [Required]
+4. `FRESHDESK_LIST_ALL_TICKET_CONVERSATIONS` - View all messages and notes on a ticket [Optional]
+5. `FRESHDESK_UPDATE_CONVERSATIONS` - Edit an existing note [Optional]
+
+**Key parameters for FRESHDESK_REPLY_TO_TICKET**:
+- `ticket_id`: Ticket ID (integer, required)
+- `body`: Reply content, supports HTML (required)
+- `cc_emails` / `bcc_emails`: Additional recipients (max 50 total across to/cc/bcc)
+- `from_email`: Override sender email if multiple support emails configured
+- `user_id`: Agent ID to reply on behalf of
+
+**Key parameters for FRESHDESK_ADD_NOTE_TO_TICKET**:
+- `ticket_id`: Ticket ID (integer, required)
+- `body`: Note content, supports HTML (required)
+- `private`: true for agent-only visibility, false for public (default true)
+- `notify_emails`: Only accepts agent email addresses, not external contacts
+
+**Pitfalls**:
+- There are two reply tools: `FRESHDESK_REPLY_TO_TICKET` (more features) and `FRESHDESK_REPLY_TICKET` (simpler); both work
+- `FRESHDESK_ADD_NOTE_TO_TICKET` defaults to private (agent-only); set `private: false` for public notes
+- `notify_emails` in notes only accepts agent emails, not customer emails
+- Only notes can be edited via `FRESHDESK_UPDATE_CONVERSATIONS`; incoming replies cannot be edited
+
+### 4. Manage Contacts and Companies
+
+**When to use**: User wants to create, search, or manage customer contacts and company records.
+
+**Tool sequence**:
+1. `FRESHDESK_SEARCH_CONTACTS` - Search contacts by email, phone, or company [Required]
+2. `FRESHDESK_GET_CONTACTS` - List contacts with filters [Optional]
+3. `FRESHDESK_IMPORT_CONTACT` - Bulk import contacts from CSV [Optional]
+4. `FRESHDESK_SEARCH_COMPANIES` - Search companies by custom fields [Required]
+5. `FRESHDESK_GET_COMPANIES` - List all companies [Optional]
+6. `FRESHDESK_CREATE_COMPANIES` - Create a new company [Optional]
+7. `FRESHDESK_UPDATE_COMPANIES` - Update company details [Optional]
+8. `FRESHDESK_LIST_COMPANY_FIELDS` - Check available company fields [Optional]
+
+**Key parameters for FRESHDESK_SEARCH_CONTACTS**:
+- `query`: Search string like `"email:'user@example.com'"` (required)
+- `page`: Pagination (1-10, max 30 per page)
+
+**Key parameters for FRESHDESK_CREATE_COMPANIES**:
+- `name`: Company name (required)
+- `domains`: Array of domain strings for auto-association with contacts
+- `health_score`: "Happy", "Doing okay", or "At risk"
+- `account_tier`: "Basic", "Premium", or "Enterprise"
+- `industry`: Standard industry classification
+
+**Pitfalls**:
+- `FRESHDESK_SEARCH_CONTACTS` requires exact matches; partial/regex searches are not supported
+- `FRESHDESK_SEARCH_COMPANIES` cannot search by standard `name` field; use custom fields or `created_at`
+- Company custom fields do NOT use the `cf_` prefix (unlike ticket custom fields)
+- `domains` on companies enables automatic contact-to-company association by email domain
+- Contact search queries require string values in single quotes inside double-quoted query
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display values to IDs before operations:
+- **Requester email -> requester_id**: `FRESHDESK_SEARCH_CONTACTS` with `"email:'user@example.com'"`
+- **Company name -> company_id**: `FRESHDESK_GET_COMPANIES` and match by name (search by name not supported)
+- **Agent name -> agent_id**: Not directly available; use agent_id from ticket responses or admin configuration
+
+### Pagination
+Freshdesk uses page-based pagination:
+- `FRESHDESK_GET_TICKETS`: `page` (starting at 1) and `per_page` (max 100)
+- `FRESHDESK_GET_SEARCH`: `page` (1-10, 30 results per page, max 300 total)
+- `FRESHDESK_SEARCH_CONTACTS`: `page` (1-10, 30 per page)
+- `FRESHDESK_LIST_ALL_TICKET_CONVERSATIONS`: `page` and `per_page` (max 100)
+
+## Known Pitfalls
+
+### ID Formats
+- Ticket IDs, contact IDs, company IDs, agent IDs, and group IDs are all integers
+- There are no string-based IDs in Freshdesk
+
+### Rate Limits
+- Freshdesk enforces per-account API rate limits based on plan tier
+- Bulk operations should be paced to avoid 429 responses
+- Search endpoints are limited to 300 total results (10 pages of 30)
+
+### Parameter Quirks
+- Status values: 2=Open, 3=Pending, 4=Resolved, 5=Closed (integers, not strings)
+- Priority values: 1=Low, 2=Medium, 3=High, 4=Urgent (integers, not strings)
+- Source values: 1=Email, 2=Portal, 3=Phone, 7=Chat, 9=Feedback Widget, 10=Outbound Email
+- Ticket custom fields use `cf_` prefix; company custom fields do NOT
+- `description` in tickets supports HTML formatting
+- Search query strings must be in double quotes with string values in single quotes
+- `FRESHDESK_LIST_ALL_TICKETS` returns all tickets with no filter parameters
+
+### Response Structure
+- Ticket details include nested objects for requester, assignee, and conversation data
+- Search results are paginated with a maximum of 300 results across 10 pages
+- Conversation lists include both replies and notes in chronological order
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create ticket | `FRESHDESK_CREATE_TICKET` | `subject`, `description`, `email`, `priority` |
+| Update ticket | `FRESHDESK_UPDATE_TICKET` | `ticket_id`, `status`, `priority` |
+| View ticket | `FRESHDESK_VIEW_TICKET` | `ticket_id` |
+| List tickets | `FRESHDESK_GET_TICKETS` | `status`, `priority`, `page`, `per_page` |
+| List all tickets | `FRESHDESK_LIST_ALL_TICKETS` | (none) |
+| Search tickets | `FRESHDESK_GET_SEARCH` | `query`, `page` |
+| Reply to ticket | `FRESHDESK_REPLY_TO_TICKET` | `ticket_id`, `body`, `cc_emails` |
+| Reply (simple) | `FRESHDESK_REPLY_TICKET` | `ticket_id`, `body` |
+| Add note | `FRESHDESK_ADD_NOTE_TO_TICKET` | `ticket_id`, `body`, `private` |
+| List conversations | `FRESHDESK_LIST_ALL_TICKET_CONVERSATIONS` | `ticket_id`, `page` |
+| Update note | `FRESHDESK_UPDATE_CONVERSATIONS` | `conversation_id`, `body` |
+| Search contacts | `FRESHDESK_SEARCH_CONTACTS` | `query`, `page` |
+| List contacts | `FRESHDESK_GET_CONTACTS` | `email`, `company_id`, `page` |
+| Import contacts | `FRESHDESK_IMPORT_CONTACT` | `file`, `name_column_index`, `email_column_index` |
+| Create company | `FRESHDESK_CREATE_COMPANIES` | `name`, `domains`, `industry` |
+| Update company | `FRESHDESK_UPDATE_COMPANIES` | `company_id`, `name`, `domains` |
+| Search companies | `FRESHDESK_SEARCH_COMPANIES` | `query`, `page` |
+| 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/plugins/awesome-claude-skills/freshservice-automation/SKILL.md b/plugins/awesome-claude-skills/freshservice-automation/SKILL.md
new file mode 100644
index 0000000..4060de8
--- /dev/null
+++ b/plugins/awesome-claude-skills/freshservice-automation/SKILL.md
@@ -0,0 +1,218 @@
+---
+name: freshservice-automation
+description: "Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Freshservice Automation via Rube MCP
+
+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)
+- Active Freshservice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`
+3. If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Search Tickets
+
+**When to use**: User wants to find, list, or search for tickets
+
+**Tool sequence**:
+1. `FRESHSERVICE_LIST_TICKETS` - List tickets with optional filtering and pagination [Required]
+2. `FRESHSERVICE_GET_TICKET` - Get detailed information for a specific ticket [Optional]
+
+**Key parameters for listing**:
+- `filter`: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')
+- `updated_since`: ISO 8601 timestamp to get tickets updated after this time
+- `order_by`: Sort field ('created_at', 'updated_at', 'status', 'priority')
+- `order_type`: Sort direction ('asc' or 'desc')
+- `page`: Page number (1-indexed)
+- `per_page`: Results per page (1-100, default 30)
+- `include`: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')
+
+**Key parameters for get**:
+- `ticket_id`: Unique ticket ID or display_id
+- `include`: Additional fields to include
+
+**Pitfalls**:
+- By default, only tickets created within the past 30 days are returned
+- Use `updated_since` to retrieve older tickets
+- Each `include` value consumes additional API credits
+- `page` is 1-indexed; minimum value is 1
+- `per_page` max is 100; default is 30
+- Ticket IDs can be the internal ID or the display_id shown in the UI
+
+### 2. Create a Ticket
+
+**When to use**: User wants to log a new incident or request
+
+**Tool sequence**:
+1. `FRESHSERVICE_CREATE_TICKET` - Create a new ticket [Required]
+
+**Key parameters**:
+- `subject`: Ticket subject line (required)
+- `description`: HTML description of the ticket (required)
+- `status`: Ticket status - 2 (Open), 3 (Pending), 4 (Resolved), 5 (Closed) (required)
+- `priority`: Ticket priority - 1 (Low), 2 (Medium), 3 (High), 4 (Urgent) (required)
+- `email`: Requester's email address (provide either email or requester_id)
+- `requester_id`: User ID of the requester
+- `type`: Ticket type ('Incident' or 'Service Request')
+- `source`: Channel - 1 (Email), 2 (Portal), 3 (Phone), 4 (Chat), 5 (Twitter), 6 (Facebook)
+- `impact`: Impact level - 1 (Low), 2 (Medium), 3 (High)
+- `urgency`: Urgency level - 1 (Low), 2 (Medium), 3 (High), 4 (Critical)
+
+**Pitfalls**:
+- `subject`, `description`, `status`, and `priority` are all required
+- Either `email` or `requester_id` must be provided to identify the requester
+- Status and priority use numeric codes, not string names
+- Description supports HTML formatting
+- If email does not match an existing contact, a new contact is created
+
+### 3. Bulk Update Tickets
+
+**When to use**: User wants to update multiple tickets at once
+
+**Tool sequence**:
+1. `FRESHSERVICE_LIST_TICKETS` - Find tickets to update [Prerequisite]
+2. `FRESHSERVICE_BULK_UPDATE_TICKETS` - Update multiple tickets [Required]
+
+**Key parameters**:
+- `ids`: Array of ticket IDs to update (required)
+- `update_fields`: Dictionary of fields to update (required)
+ - Allowed keys: 'subject', 'description', 'status', 'priority', 'responder_id', 'group_id', 'type', 'tags', 'custom_fields'
+
+**Pitfalls**:
+- Bulk update performs sequential updates internally; large batches may take time
+- All specified tickets receive the same field updates
+- If one ticket update fails, others may still succeed; check response for individual results
+- Cannot selectively update different fields per ticket in a single call
+- Custom fields must use their internal field names, not display names
+
+### 4. Create Ticket via Outbound Email
+
+**When to use**: User wants to create a ticket by sending an outbound email notification
+
+**Tool sequence**:
+1. `FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL` - Create ticket with email notification [Required]
+
+**Key parameters**:
+- `email`: Requester's email address (required)
+- `subject`: Email subject / ticket subject (required)
+- `description`: HTML email body content
+- `status`: Ticket status (2=Open, 3=Pending, 4=Resolved, 5=Closed)
+- `priority`: Ticket priority (1=Low, 2=Medium, 3=High, 4=Urgent)
+- `cc_emails`: Array of CC email addresses
+- `email_config_id`: Email configuration ID for the sender address
+- `name`: Requester name
+
+**Pitfalls**:
+- This creates a standard ticket via the /api/v2/tickets endpoint while sending an email
+- If the email does not match an existing contact, a new contact is created with the provided name
+- `email_config_id` determines which email address the notification appears to come from
+
+### 5. Create Service Requests
+
+**When to use**: User wants to submit a service catalog request
+
+**Tool sequence**:
+1. `FRESHSERVICE_CREATE_SERVICE_REQUEST` - Create a service request for a catalog item [Required]
+
+**Key parameters**:
+- `item_display_id`: Display ID of the catalog item (required)
+- `email`: Requester's email address
+- `quantity`: Number of items to request (default: 1)
+- `custom_fields`: Custom field values for the service item form
+- `parent_ticket_id`: Display ID of a parent ticket (for child requests)
+
+**Pitfalls**:
+- `item_display_id` can be found in Admin > Service Catalog > item URL (e.g., /service_catalog/items/1)
+- Custom fields keys must match the service item form field names
+- Quantity defaults to 1 if not specified
+- Service requests follow the approval workflow defined for the catalog item
+
+## Common Patterns
+
+### Status Code Reference
+
+| Code | Status |
+|------|--------|
+| 2 | Open |
+| 3 | Pending |
+| 4 | Resolved |
+| 5 | Closed |
+
+### Priority Code Reference
+
+| Code | Priority |
+|------|----------|
+| 1 | Low |
+| 2 | Medium |
+| 3 | High |
+| 4 | Urgent |
+
+### Pagination
+
+- Use `page` (1-indexed) and `per_page` (max 100) parameters
+- Increment `page` by 1 each request
+- Continue until returned results count < `per_page`
+- Default page size is 30
+
+### Finding Tickets by Date Range
+
+```
+1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'
+2. Optionally add order_by='updated_at' and order_type='desc'
+3. Paginate through results
+```
+
+## Known Pitfalls
+
+**Numeric Codes**:
+- Status and priority use numeric values, not strings
+- Source channel uses numeric codes (1-6)
+- Impact and urgency use numeric codes (1-3 or 1-4)
+
+**Date Filtering**:
+- Default returns only tickets from the last 30 days
+- Use `updated_since` parameter for older tickets
+- Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')
+
+**Rate Limits**:
+- Freshservice API has per-account rate limits
+- Each `include` option consumes additional API credits
+- Implement backoff on 429 responses
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Ticket IDs are numeric integers
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List tickets | FRESHSERVICE_LIST_TICKETS | filter, updated_since, page, per_page |
+| Get ticket | FRESHSERVICE_GET_TICKET | ticket_id, include |
+| Create ticket | FRESHSERVICE_CREATE_TICKET | subject, description, status, priority, email |
+| 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/plugins/awesome-claude-skills/front-automation/SKILL.md b/plugins/awesome-claude-skills/front-automation/SKILL.md
new file mode 100644
index 0000000..22884ac
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/fullenrich-automation/SKILL.md b/plugins/awesome-claude-skills/fullenrich-automation/SKILL.md
new file mode 100644
index 0000000..aa6a7e9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gagelist-automation/SKILL.md b/plugins/awesome-claude-skills/gagelist-automation/SKILL.md
new file mode 100644
index 0000000..772734e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gamma-automation/SKILL.md b/plugins/awesome-claude-skills/gamma-automation/SKILL.md
new file mode 100644
index 0000000..9f01a3a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gan-ai-automation/SKILL.md b/plugins/awesome-claude-skills/gan-ai-automation/SKILL.md
new file mode 100644
index 0000000..fc3fc04
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gatherup-automation/SKILL.md b/plugins/awesome-claude-skills/gatherup-automation/SKILL.md
new file mode 100644
index 0000000..4b85a7e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gemini-automation/SKILL.md b/plugins/awesome-claude-skills/gemini-automation/SKILL.md
new file mode 100644
index 0000000..ff827db
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gender-api-automation/SKILL.md b/plugins/awesome-claude-skills/gender-api-automation/SKILL.md
new file mode 100644
index 0000000..aec80f3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/genderapi-io-automation/SKILL.md b/plugins/awesome-claude-skills/genderapi-io-automation/SKILL.md
new file mode 100644
index 0000000..f515d35
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/genderize-automation/SKILL.md b/plugins/awesome-claude-skills/genderize-automation/SKILL.md
new file mode 100644
index 0000000..20e9322
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/geoapify-automation/SKILL.md b/plugins/awesome-claude-skills/geoapify-automation/SKILL.md
new file mode 100644
index 0000000..487a6a4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/geocodio-automation/SKILL.md b/plugins/awesome-claude-skills/geocodio-automation/SKILL.md
new file mode 100644
index 0000000..2b405f7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/geokeo-automation/SKILL.md b/plugins/awesome-claude-skills/geokeo-automation/SKILL.md
new file mode 100644
index 0000000..f47bf18
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/getform-automation/SKILL.md b/plugins/awesome-claude-skills/getform-automation/SKILL.md
new file mode 100644
index 0000000..7dc9223
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gift-up-automation/SKILL.md b/plugins/awesome-claude-skills/gift-up-automation/SKILL.md
new file mode 100644
index 0000000..f95b2cf
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gigasheet-automation/SKILL.md b/plugins/awesome-claude-skills/gigasheet-automation/SKILL.md
new file mode 100644
index 0000000..30d89c2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/giphy-automation/SKILL.md b/plugins/awesome-claude-skills/giphy-automation/SKILL.md
new file mode 100644
index 0000000..57197ff
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gist-automation/SKILL.md b/plugins/awesome-claude-skills/gist-automation/SKILL.md
new file mode 100644
index 0000000..1445e20
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/github-automation/SKILL.md b/plugins/awesome-claude-skills/github-automation/SKILL.md
new file mode 100644
index 0000000..778ffeb
--- /dev/null
+++ b/plugins/awesome-claude-skills/github-automation/SKILL.md
@@ -0,0 +1,232 @@
+---
+name: github-automation
+description: Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
+requires:
+ mcp: [rube]
+---
+
+# GitHub Automation via Rube MCP
+
+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)
+- Active GitHub connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `github`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `github`
+3. If connection is not ACTIVE, follow the returned auth link to complete GitHub OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Issues
+
+**When to use**: User wants to create, list, or manage GitHub issues
+
+**Tool sequence**:
+1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - Find target repo if unknown [Prerequisite]
+2. `GITHUB_LIST_REPOSITORY_ISSUES` - List existing issues (includes PRs) [Required]
+3. `GITHUB_CREATE_AN_ISSUE` - Create a new issue [Required]
+4. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Add comments to an issue [Optional]
+5. `GITHUB_SEARCH_ISSUES_AND_PULL_REQUESTS` - Search across repos by keyword [Optional]
+
+**Key parameters**:
+- `owner`: Repository owner (username or org), case-insensitive
+- `repo`: Repository name without .git extension
+- `title`: Issue title (required for creation)
+- `body`: Issue description (supports Markdown)
+- `labels`: Array of label names
+- `assignees`: Array of GitHub usernames
+- `state`: 'open', 'closed', or 'all' for filtering
+
+**Pitfalls**:
+- `GITHUB_LIST_REPOSITORY_ISSUES` returns both issues AND pull requests; check `pull_request` field to distinguish
+- Only users with push access can set assignees, labels, and milestones; they are silently dropped otherwise
+- Pagination: `per_page` max 100; iterate pages until empty
+
+### 2. Manage Pull Requests
+
+**When to use**: User wants to create, review, or merge pull requests
+
+**Tool sequence**:
+1. `GITHUB_FIND_PULL_REQUESTS` - Search and filter PRs [Required]
+2. `GITHUB_GET_A_PULL_REQUEST` - Get detailed PR info including mergeable status [Required]
+3. `GITHUB_LIST_PULL_REQUESTS_FILES` - Review changed files [Optional]
+4. `GITHUB_CREATE_A_PULL_REQUEST` - Create a new PR [Required]
+5. `GITHUB_CREATE_AN_ISSUE_COMMENT` - Post review comments [Optional]
+6. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Verify CI status before merge [Optional]
+7. `GITHUB_MERGE_A_PULL_REQUEST` - Merge after explicit user approval [Required]
+
+**Key parameters**:
+- `head`: Source branch with changes (must exist; for cross-repo: 'username:branch')
+- `base`: Target branch to merge into (e.g., 'main')
+- `title`: PR title (required unless `issue` number provided)
+- `merge_method`: 'merge', 'squash', or 'rebase'
+- `state`: 'open', 'closed', or 'all'
+
+**Pitfalls**:
+- `GITHUB_CREATE_A_PULL_REQUEST` fails with 422 if base/head are invalid, identical, or already merged
+- `GITHUB_MERGE_A_PULL_REQUEST` can be rejected if PR is draft, closed, or branch protection applies
+- Always verify mergeable status with `GITHUB_GET_A_PULL_REQUEST` immediately before merging
+- Require explicit user confirmation before calling MERGE
+
+### 3. Manage Repositories and Branches
+
+**When to use**: User wants to create repos, manage branches, or update repo settings
+
+**Tool sequence**:
+1. `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` - List user's repos [Required]
+2. `GITHUB_GET_A_REPOSITORY` - Get detailed repo info [Optional]
+3. `GITHUB_CREATE_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER` - Create personal repo [Required]
+4. `GITHUB_CREATE_AN_ORGANIZATION_REPOSITORY` - Create org repo [Alternative]
+5. `GITHUB_LIST_BRANCHES` - List branches [Required]
+6. `GITHUB_CREATE_A_REFERENCE` - Create new branch from SHA [Required]
+7. `GITHUB_UPDATE_A_REPOSITORY` - Update repo settings [Optional]
+
+**Key parameters**:
+- `name`: Repository name
+- `private`: Boolean for visibility
+- `ref`: Full reference path (e.g., 'refs/heads/new-branch')
+- `sha`: Commit SHA to point the new reference to
+- `default_branch`: Default branch name
+
+**Pitfalls**:
+- `GITHUB_CREATE_A_REFERENCE` only creates NEW references; use `GITHUB_UPDATE_A_REFERENCE` for existing ones
+- `ref` must start with 'refs/' and contain at least two slashes
+- `GITHUB_LIST_BRANCHES` paginates via `page`/`per_page`; iterate until empty page
+- `GITHUB_DELETE_A_REPOSITORY` is permanent and irreversible; requires admin privileges
+
+### 4. Search Code and Commits
+
+**When to use**: User wants to find code, files, or commits across repositories
+
+**Tool sequence**:
+1. `GITHUB_SEARCH_CODE` - Search file contents and paths [Required]
+2. `GITHUB_SEARCH_CODE_ALL_PAGES` - Multi-page code search [Alternative]
+3. `GITHUB_SEARCH_COMMITS_BY_AUTHOR` - Search commits by author/date/org [Required]
+4. `GITHUB_LIST_COMMITS` - List commits for a specific repo [Alternative]
+5. `GITHUB_GET_A_COMMIT` - Get detailed commit info [Optional]
+6. `GITHUB_GET_REPOSITORY_CONTENT` - Get file content [Optional]
+
+**Key parameters**:
+- `q`: Search query with qualifiers (`language:python`, `repo:owner/repo`, `extension:js`)
+- `owner`/`repo`: For repo-specific commit listing
+- `author`: Filter by commit author
+- `since`/`until`: ISO 8601 date range for commits
+
+**Pitfalls**:
+- Code search only indexes files under 384KB on default branch
+- Maximum 1000 results returned from code search
+- `GITHUB_SEARCH_COMMITS_BY_AUTHOR` requires keywords in addition to qualifiers; qualifier-only queries are not allowed
+- `GITHUB_LIST_COMMITS` returns 409 on empty repos
+
+### 5. Manage CI/CD and Deployments
+
+**When to use**: User wants to view workflows, check CI status, or manage deployments
+
+**Tool sequence**:
+1. `GITHUB_LIST_REPOSITORY_WORKFLOWS` - List GitHub Actions workflows [Required]
+2. `GITHUB_GET_A_WORKFLOW` - Get workflow details by ID or filename [Optional]
+3. `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` - Manually trigger a workflow [Required]
+4. `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` - Check CI status for a commit/branch [Required]
+5. `GITHUB_LIST_DEPLOYMENTS` - List deployments [Optional]
+6. `GITHUB_GET_A_DEPLOYMENT_STATUS` - Get deployment status [Optional]
+
+**Key parameters**:
+- `workflow_id`: Numeric ID or filename (e.g., 'ci.yml')
+- `ref`: Git reference (branch/tag) for workflow dispatch
+- `inputs`: JSON string of workflow inputs matching `on.workflow_dispatch.inputs`
+- `environment`: Filter deployments by environment name
+
+**Pitfalls**:
+- `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` requires the workflow to have `workflow_dispatch` trigger configured
+- Full path `.github/workflows/main.yml` is auto-stripped to just `main.yml`
+- Inputs max 10 key-value pairs; must match workflow's `on.workflow_dispatch.inputs` definitions
+
+### 6. Manage Users and Permissions
+
+**When to use**: User wants to check collaborators, permissions, or branch protection
+
+**Tool sequence**:
+1. `GITHUB_LIST_REPOSITORY_COLLABORATORS` - List repo collaborators [Required]
+2. `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` - Check specific user's access [Optional]
+3. `GITHUB_GET_BRANCH_PROTECTION` - Inspect branch protection rules [Required]
+4. `GITHUB_UPDATE_BRANCH_PROTECTION` - Update protection settings [Optional]
+5. `GITHUB_ADD_A_REPOSITORY_COLLABORATOR` - Add/update collaborator [Optional]
+
+**Key parameters**:
+- `affiliation`: 'outside', 'direct', or 'all' for collaborator filtering
+- `permission`: Filter by 'pull', 'triage', 'push', 'maintain', 'admin'
+- `branch`: Branch name for protection rules
+- `enforce_admins`: Whether protection applies to admins
+
+**Pitfalls**:
+- `GITHUB_GET_BRANCH_PROTECTION` returns 404 for unprotected branches; treat as no protection rules
+- Determine push ability from `permissions.push` or `role_name`, not display labels
+- `GITHUB_LIST_REPOSITORY_COLLABORATORS` paginates; iterate all pages
+- `GITHUB_GET_REPOSITORY_PERMISSIONS_FOR_A_USER` may be inconclusive for non-collaborators
+
+## Common Patterns
+
+### ID Resolution
+- **Repo name -> owner/repo**: `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER`
+- **PR number -> PR details**: `GITHUB_FIND_PULL_REQUESTS` then `GITHUB_GET_A_PULL_REQUEST`
+- **Branch name -> SHA**: `GITHUB_GET_A_BRANCH`
+- **Workflow name -> ID**: `GITHUB_LIST_REPOSITORY_WORKFLOWS`
+
+### Pagination
+All list endpoints use page-based pagination:
+- `page`: Page number (starts at 1)
+- `per_page`: Results per page (max 100)
+- Iterate until response returns fewer results than `per_page`
+
+### Safety
+- Always verify PR mergeable status before merge
+- Require explicit user confirmation for destructive operations (merge, delete)
+- Check CI status with `GITHUB_LIST_CHECK_RUNS_FOR_A_REF` before merging
+
+## Known Pitfalls
+
+- **Issues vs PRs**: `GITHUB_LIST_REPOSITORY_ISSUES` returns both; check `pull_request` field
+- **Pagination limits**: `per_page` max 100; always iterate pages until empty
+- **Branch creation**: `GITHUB_CREATE_A_REFERENCE` fails with 422 if reference already exists
+- **Merge guards**: Merge can fail due to branch protection, failing checks, or draft status
+- **Code search limits**: Only files <384KB on default branch; max 1000 results
+- **Commit search**: Requires search text keywords alongside qualifiers
+- **Destructive actions**: Repo deletion is irreversible; merge cannot be undone
+- **Silent permission drops**: Labels, assignees, milestones silently dropped without push access
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List repos | `GITHUB_LIST_REPOSITORIES_FOR_THE_AUTHENTICATED_USER` | `type`, `sort`, `per_page` |
+| Get repo | `GITHUB_GET_A_REPOSITORY` | `owner`, `repo` |
+| Create issue | `GITHUB_CREATE_AN_ISSUE` | `owner`, `repo`, `title`, `body` |
+| List issues | `GITHUB_LIST_REPOSITORY_ISSUES` | `owner`, `repo`, `state` |
+| Find PRs | `GITHUB_FIND_PULL_REQUESTS` | `repo`, `state`, `author` |
+| Create PR | `GITHUB_CREATE_A_PULL_REQUEST` | `owner`, `repo`, `head`, `base`, `title` |
+| Merge PR | `GITHUB_MERGE_A_PULL_REQUEST` | `owner`, `repo`, `pull_number`, `merge_method` |
+| List branches | `GITHUB_LIST_BRANCHES` | `owner`, `repo` |
+| Create branch | `GITHUB_CREATE_A_REFERENCE` | `owner`, `repo`, `ref`, `sha` |
+| Search code | `GITHUB_SEARCH_CODE` | `q` |
+| List commits | `GITHUB_LIST_COMMITS` | `owner`, `repo`, `author`, `since` |
+| Search commits | `GITHUB_SEARCH_COMMITS_BY_AUTHOR` | `q` |
+| List workflows | `GITHUB_LIST_REPOSITORY_WORKFLOWS` | `owner`, `repo` |
+| Trigger workflow | `GITHUB_CREATE_A_WORKFLOW_DISPATCH_EVENT` | `owner`, `repo`, `workflow_id`, `ref` |
+| 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/plugins/awesome-claude-skills/gitlab-automation/SKILL.md b/plugins/awesome-claude-skills/gitlab-automation/SKILL.md
new file mode 100644
index 0000000..c44ea96
--- /dev/null
+++ b/plugins/awesome-claude-skills/gitlab-automation/SKILL.md
@@ -0,0 +1,259 @@
+---
+name: gitlab-automation
+description: Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# GitLab Automation via Rube MCP
+
+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)
+- Active GitLab connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gitlab`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gitlab`
+3. If connection is not ACTIVE, follow the returned auth link to complete GitLab OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Issues
+
+**When to use**: User wants to create, update, list, or search issues in a GitLab project
+
+**Tool sequence**:
+1. `GITLAB_GET_PROJECTS` - Find the target project and get its ID [Prerequisite]
+2. `GITLAB_LIST_PROJECT_ISSUES` - List and filter issues for a project [Required]
+3. `GITLAB_CREATE_PROJECT_ISSUE` - Create a new issue [Required for create]
+4. `GITLAB_UPDATE_PROJECT_ISSUE` - Update an existing issue (title, labels, state, assignees) [Required for update]
+5. `GITLAB_LIST_PROJECT_USERS` - Find user IDs for assignment [Optional]
+
+**Key parameters**:
+- `id`: Project ID (integer) or URL-encoded path (e.g., `"my-group/my-project"`)
+- `title`: Issue title (required for creation)
+- `description`: Issue body text (max 1,048,576 characters)
+- `labels`: Comma-separated label names (e.g., `"bug,critical"`)
+- `add_labels` / `remove_labels`: Add or remove labels without replacing all
+- `state`: Filter by `"all"`, `"opened"`, or `"closed"`
+- `state_event`: `"close"` or `"reopen"` to change issue state
+- `assignee_ids`: Array of user IDs; use `[0]` to unassign all
+- `issue_iid`: Internal issue ID within the project (required for updates)
+- `milestone`: Filter by milestone title
+- `search`: Search in title and description
+- `scope`: `"created_by_me"`, `"assigned_to_me"`, or `"all"`
+- `page` / `per_page`: Pagination (default per_page: 20)
+
+**Pitfalls**:
+- `id` accepts either integer project ID or URL-encoded path; wrong IDs yield 4xx errors
+- `issue_iid` is the project-internal ID (shown as #42), different from the global issue ID
+- Labels in `labels` field replace ALL existing labels; use `add_labels`/`remove_labels` for incremental changes
+- Setting `assignee_ids` to empty array does NOT unassign; use `[0]` instead
+- `updated_at` field requires administrator or project/group owner rights
+
+### 2. Manage Merge Requests
+
+**When to use**: User wants to list, filter, or review merge requests in a project
+
+**Tool sequence**:
+1. `GITLAB_GET_PROJECT` - Get project details and verify access [Prerequisite]
+2. `GITLAB_GET_PROJECT_MERGE_REQUESTS` - List and filter merge requests [Required]
+3. `GITLAB_GET_REPOSITORY_BRANCHES` - Verify source/target branches [Optional]
+4. `GITLAB_LIST_ALL_PROJECT_MEMBERS` - Find reviewers/assignees [Optional]
+
+**Key parameters**:
+- `id`: Project ID or URL-encoded path
+- `state`: `"opened"`, `"closed"`, `"locked"`, `"merged"`, or `"all"`
+- `scope`: `"created_by_me"` (default), `"assigned_to_me"`, or `"all"`
+- `source_branch` / `target_branch`: Filter by branch names
+- `author_id` / `author_username`: Filter by MR author
+- `assignee_id`: Filter by assignee (use `None` for unassigned, `Any` for assigned)
+- `reviewer_id` / `reviewer_username`: Filter by reviewer
+- `labels`: Comma-separated label filter
+- `search`: Search in title and description
+- `wip`: `"yes"` for draft MRs, `"no"` for non-draft
+- `order_by`: `"created_at"` (default), `"title"`, `"merged_at"`, `"updated_at"`
+- `view`: `"simple"` for minimal fields
+- `iids[]`: Filter by specific MR internal IDs
+
+**Pitfalls**:
+- Default `scope` is `"created_by_me"` which limits results; use `"all"` for complete listings
+- `author_id` and `author_username` are mutually exclusive
+- `reviewer_id` and `reviewer_username` are mutually exclusive
+- `approved` filter requires the `mr_approved_filter` feature flag (disabled by default)
+- Large MR histories can be noisy; use filters and moderate `per_page` values
+
+### 3. Manage Projects and Repositories
+
+**When to use**: User wants to list projects, create new projects, or manage branches
+
+**Tool sequence**:
+1. `GITLAB_GET_PROJECTS` - List all accessible projects with filters [Required]
+2. `GITLAB_GET_PROJECT` - Get detailed info for a specific project [Optional]
+3. `GITLAB_LIST_USER_PROJECTS` - List projects owned by a specific user [Optional]
+4. `GITLAB_CREATE_PROJECT` - Create a new project [Required for create]
+5. `GITLAB_GET_REPOSITORY_BRANCHES` - List branches in a project [Required for branch ops]
+6. `GITLAB_CREATE_REPOSITORY_BRANCH` - Create a new branch [Optional]
+7. `GITLAB_GET_REPOSITORY_BRANCH` - Get details of a specific branch [Optional]
+8. `GITLAB_LIST_REPOSITORY_COMMITS` - View commit history [Optional]
+9. `GITLAB_GET_PROJECT_LANGUAGES` - Get language breakdown [Optional]
+
+**Key parameters**:
+- `name` / `path`: Project name and URL-friendly path (both required for creation)
+- `visibility`: `"private"`, `"internal"`, or `"public"`
+- `namespace_id`: Group or user ID for project placement
+- `search`: Case-insensitive substring search for projects
+- `membership`: `true` to limit to projects user is a member of
+- `owned`: `true` to limit to user-owned projects
+- `project_id`: Project ID for branch operations
+- `branch_name`: Name for new branch
+- `ref`: Source branch or commit SHA for new branch creation
+- `order_by`: `"id"`, `"name"`, `"path"`, `"created_at"`, `"updated_at"`, `"star_count"`, `"last_activity_at"`
+
+**Pitfalls**:
+- `GITLAB_GET_PROJECTS` pagination is required for complete coverage; stopping at first page misses projects
+- Some responses place items under `data.details`; parse the actual returned list structure
+- Most follow-up calls depend on correct `project_id`; verify with `GITLAB_GET_PROJECT` first
+- Invalid `branch_name`/`ref`/`sha` causes client errors; verify branch existence via `GITLAB_GET_REPOSITORY_BRANCHES` first
+- Both `name` and `path` are required for `GITLAB_CREATE_PROJECT`
+
+### 4. Monitor CI/CD Pipelines
+
+**When to use**: User wants to check pipeline status, list jobs, or monitor CI/CD runs
+
+**Tool sequence**:
+1. `GITLAB_GET_PROJECT` - Verify project access [Prerequisite]
+2. `GITLAB_LIST_PROJECT_PIPELINES` - List pipelines with filters [Required]
+3. `GITLAB_GET_SINGLE_PIPELINE` - Get detailed info for a specific pipeline [Optional]
+4. `GITLAB_LIST_PIPELINE_JOBS` - List jobs within a pipeline [Optional]
+
+**Key parameters**:
+- `id`: Project ID or URL-encoded path
+- `status`: Filter by `"created"`, `"waiting_for_resource"`, `"preparing"`, `"pending"`, `"running"`, `"success"`, `"failed"`, `"canceled"`, `"skipped"`, `"manual"`, `"scheduled"`
+- `scope`: `"running"`, `"pending"`, `"finished"`, `"branches"`, `"tags"`
+- `ref`: Branch or tag name
+- `sha`: Specific commit SHA
+- `source`: Pipeline source (use `"parent_pipeline"` for child pipelines)
+- `order_by`: `"id"` (default), `"status"`, `"ref"`, `"updated_at"`, `"user_id"`
+- `created_after` / `created_before`: ISO 8601 date filters
+- `pipeline_id`: Specific pipeline ID for job listing
+- `include_retried`: `true` to include retried jobs (default `false`)
+
+**Pitfalls**:
+- Large pipeline histories can be noisy; use `status`, `ref`, and date filters to narrow results
+- Use moderate `per_page` values to keep output manageable
+- Pipeline job `scope` accepts single status string or array of statuses
+- `yaml_errors: true` returns only pipelines with invalid configurations
+
+### 5. Manage Users and Members
+
+**When to use**: User wants to find users, list project members, or check user status
+
+**Tool sequence**:
+1. `GITLAB_GET_USERS` - Search and list GitLab users [Required]
+2. `GITLAB_GET_USER` - Get details for a specific user by ID [Optional]
+3. `GITLAB_GET_USERS_ID_STATUS` - Get user status message and availability [Optional]
+4. `GITLAB_LIST_ALL_PROJECT_MEMBERS` - List all project members (direct + inherited) [Required for member listing]
+5. `GITLAB_LIST_PROJECT_USERS` - List project users with search filter [Optional]
+
+**Key parameters**:
+- `search`: Search by name, username, or public email
+- `username`: Get specific user by username
+- `active` / `blocked`: Filter by user state
+- `id`: Project ID for member listing
+- `query`: Filter members by name, email, or username
+- `state`: Filter members by `"awaiting"` or `"active"` (Premium/Ultimate)
+- `user_ids`: Filter by specific user IDs
+
+**Pitfalls**:
+- Many user filters (admins, auditors, extern_uid, two_factor) are admin-only
+- `GITLAB_LIST_ALL_PROJECT_MEMBERS` includes direct, inherited, and invited members
+- User search is case-insensitive but may not match partial email domains
+- Premium/Ultimate features (state filter, seat info) are not available on free plans
+
+## Common Patterns
+
+### ID Resolution
+GitLab uses two identifier formats for projects:
+- **Numeric ID**: Integer project ID (e.g., `123`)
+- **URL-encoded path**: Namespace/project format (e.g., `"my-group%2Fmy-project"` or `"my-group/my-project"`)
+- **Issue IID vs ID**: `issue_iid` is the project-internal number (#42); the global `id` is different
+- **User ID**: Numeric; resolve via `GITLAB_GET_USERS` with `search` or `username`
+
+### Pagination
+GitLab uses offset-based pagination:
+- Set `page` (starting at 1) and `per_page` (1-100, default 20)
+- Continue incrementing `page` until response returns fewer items than `per_page` or is empty
+- Total count may be available in response headers (`X-Total`, `X-Total-Pages`)
+- Always paginate to completion for accurate results
+
+### URL-Encoded Paths
+When using project paths as identifiers:
+- Forward slashes must be URL-encoded: `my-group/my-project` becomes `my-group%2Fmy-project`
+- Some tools accept unencoded paths; check schema for each tool
+- Prefer numeric IDs when available for reliability
+
+## Known Pitfalls
+
+### ID Formats
+- Project `id` field accepts both integer and string (URL-encoded path)
+- Issue `issue_iid` is project-scoped; do not confuse with global issue ID
+- Pipeline IDs are project-scoped integers
+- User IDs are global integers across the GitLab instance
+
+### Rate Limits
+- GitLab has per-user rate limits (typically 300-2000 requests/minute depending on plan)
+- Large pipeline/issue histories should use date and status filters to reduce result sets
+- Paginate responsibly with moderate `per_page` values
+
+### Parameter Quirks
+- `labels` field replaces ALL labels; use `add_labels`/`remove_labels` for incremental changes
+- `assignee_ids: [0]` unassigns all; empty array does nothing
+- `scope` defaults vary: `"created_by_me"` for MRs, `"all"` for issues
+- `author_id` and `author_username` are mutually exclusive in MR filters
+- Date parameters use ISO 8601 format: `"2024-01-15T10:30:00Z"`
+
+### Plan Restrictions
+- Some features require Premium/Ultimate: `epic_id`, `weight`, `iteration_id`, `approved_by_ids`, member `state` filter
+- Admin-only features: user management filters, `updated_at` override, custom attributes
+- The `mr_approved_filter` feature flag is disabled by default
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List projects | `GITLAB_GET_PROJECTS` | `search`, `membership`, `visibility` |
+| Get project details | `GITLAB_GET_PROJECT` | `id` |
+| User's projects | `GITLAB_LIST_USER_PROJECTS` | `id`, `search`, `owned` |
+| Create project | `GITLAB_CREATE_PROJECT` | `name`, `path`, `visibility` |
+| List issues | `GITLAB_LIST_PROJECT_ISSUES` | `id`, `state`, `labels`, `search` |
+| Create issue | `GITLAB_CREATE_PROJECT_ISSUE` | `id`, `title`, `description`, `labels` |
+| Update issue | `GITLAB_UPDATE_PROJECT_ISSUE` | `id`, `issue_iid`, `state_event` |
+| List merge requests | `GITLAB_GET_PROJECT_MERGE_REQUESTS` | `id`, `state`, `scope`, `labels` |
+| List branches | `GITLAB_GET_REPOSITORY_BRANCHES` | `project_id`, `search` |
+| Get branch | `GITLAB_GET_REPOSITORY_BRANCH` | `project_id`, `branch_name` |
+| Create branch | `GITLAB_CREATE_REPOSITORY_BRANCH` | `project_id`, `branch_name`, `ref` |
+| List commits | `GITLAB_LIST_REPOSITORY_COMMITS` | project ID, branch ref |
+| Project languages | `GITLAB_GET_PROJECT_LANGUAGES` | project ID |
+| List pipelines | `GITLAB_LIST_PROJECT_PIPELINES` | `id`, `status`, `ref` |
+| Get pipeline | `GITLAB_GET_SINGLE_PIPELINE` | `project_id`, `pipeline_id` |
+| List pipeline jobs | `GITLAB_LIST_PIPELINE_JOBS` | `id`, `pipeline_id`, `scope` |
+| Search users | `GITLAB_GET_USERS` | `search`, `username`, `active` |
+| Get user | `GITLAB_GET_USER` | user ID |
+| 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/plugins/awesome-claude-skills/givebutter-automation/SKILL.md b/plugins/awesome-claude-skills/givebutter-automation/SKILL.md
new file mode 100644
index 0000000..2753eea
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gladia-automation/SKILL.md b/plugins/awesome-claude-skills/gladia-automation/SKILL.md
new file mode 100644
index 0000000..7e6a259
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gleap-automation/SKILL.md b/plugins/awesome-claude-skills/gleap-automation/SKILL.md
new file mode 100644
index 0000000..d5647b8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/globalping-automation/SKILL.md b/plugins/awesome-claude-skills/globalping-automation/SKILL.md
new file mode 100644
index 0000000..237fa29
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gmail-automation/SKILL.md b/plugins/awesome-claude-skills/gmail-automation/SKILL.md
new file mode 100644
index 0000000..074b1e1
--- /dev/null
+++ b/plugins/awesome-claude-skills/gmail-automation/SKILL.md
@@ -0,0 +1,274 @@
+---
+name: gmail-automation
+description: "Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Gmail Automation via Rube MCP
+
+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)
+- Active Gmail connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gmail`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gmail`
+3. If connection is not ACTIVE, follow the returned auth link to complete Google OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send an Email
+
+**When to use**: User wants to compose and send a new email
+
+**Tool sequence**:
+1. `GMAIL_SEARCH_PEOPLE` - Resolve contact name to email address [Optional]
+2. `GMAIL_SEND_EMAIL` - Send the email [Required]
+
+**Key parameters**:
+- `recipient_email`: Email address or 'me' for self
+- `subject`: Email subject line
+- `body`: Email content (plain text or HTML)
+- `is_html`: Must be `true` if body contains HTML markup
+- `cc`/`bcc`: Arrays of email addresses
+- `attachment`: Object with `{s3key, mimetype, name}` from prior download
+
+**Pitfalls**:
+- At least one of `recipient_email`, `cc`, or `bcc` required
+- At least one of `subject` or `body` required
+- Attachment `mimetype` MUST contain '/' (e.g., 'application/pdf', not 'pdf')
+- Total message size limit ~25MB after base64 encoding
+- Use `from_email` only for verified aliases in Gmail 'Send mail as' settings
+
+### 2. Reply to a Thread
+
+**When to use**: User wants to reply to an existing email conversation
+
+**Tool sequence**:
+1. `GMAIL_FETCH_EMAILS` - Find the email/thread to reply to [Prerequisite]
+2. `GMAIL_REPLY_TO_THREAD` - Send reply within the thread [Required]
+
+**Key parameters**:
+- `thread_id`: Hex string from FETCH_EMAILS (e.g., '169eefc8138e68ca')
+- `message_body`: Reply content
+- `recipient_email`: Reply recipient
+- `is_html`: Set `true` for HTML content
+
+**Pitfalls**:
+- `thread_id` must be hex string; prefixes like 'msg-f:' are auto-stripped
+- Legacy Gmail web UI IDs (e.g., 'FMfcgz...') are NOT supported
+- Subject is inherited from original thread; setting it creates a new thread instead
+- Do NOT include subject parameter to stay within thread
+
+### 3. Search and Filter Emails
+
+**When to use**: User wants to find specific emails by sender, subject, date, label, etc.
+
+**Tool sequence**:
+1. `GMAIL_FETCH_EMAILS` - Search with Gmail query syntax [Required]
+2. `GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID` - Get full message details for selected results [Optional]
+
+**Key parameters**:
+- `query`: Gmail search syntax (from:, to:, subject:, is:unread, has:attachment, after:YYYY/MM/DD, before:YYYY/MM/DD)
+- `max_results`: 1-500 messages per page
+- `label_ids`: System IDs like 'INBOX', 'UNREAD'
+- `include_payload`: Set `true` to get full message content
+- `ids_only`: Set `true` for just message IDs
+- `page_token`: For pagination (from `nextPageToken`)
+
+**Pitfalls**:
+- Returns max ~500 per page; follow `nextPageToken` via `page_token` until absent
+- `resultSizeEstimate` is approximate, not exact count
+- Use 'is:' for states (is:unread, is:snoozed, is:starred)
+- Use 'label:' ONLY for user-created labels
+- Common mistake: 'label:snoozed' is WRONG — use 'is:snoozed'
+- `include_payload=true` on broad searches creates huge responses; default to metadata
+- Custom labels require label ID (e.g., 'Label_123'), NOT label name
+
+### 4. Manage Labels
+
+**When to use**: User wants to create, modify, or organize labels
+
+**Tool sequence**:
+1. `GMAIL_LIST_LABELS` - List all labels to find IDs and detect conflicts [Required]
+2. `GMAIL_CREATE_LABEL` - Create a new label [Optional]
+3. `GMAIL_PATCH_LABEL` - Rename or change label colors/visibility [Optional]
+4. `GMAIL_DELETE_LABEL` - Delete a user-created label (irreversible) [Optional]
+
+**Key parameters**:
+- `label_name`: Max 225 chars, no commas, '/' for nesting (e.g., 'Work/Projects')
+- `background_color`/`text_color`: Hex values from Gmail's predefined palette
+- `id`: Label ID for PATCH/DELETE operations
+
+**Pitfalls**:
+- 400/409 error if name is blank, duplicate, or reserved (INBOX, SPAM, CATEGORY_*)
+- Color specs must use Gmail's predefined palette of 102 hex values
+- DELETE is permanent and removes label from all messages
+- Cannot delete system labels (INBOX, SENT, DRAFT, etc.)
+
+### 5. Apply/Remove Labels on Messages
+
+**When to use**: User wants to label, archive, or mark emails as read/unread
+
+**Tool sequence**:
+1. `GMAIL_LIST_LABELS` - Get label IDs for custom labels [Prerequisite]
+2. `GMAIL_FETCH_EMAILS` - Find target messages [Prerequisite]
+3. `GMAIL_BATCH_MODIFY_MESSAGES` - Bulk add/remove labels (up to 1000 messages) [Required]
+4. `GMAIL_ADD_LABEL_TO_EMAIL` - Single-message label changes [Fallback]
+
+**Key parameters**:
+- `messageIds`: Array of message IDs (max 1000)
+- `addLabelIds`: Array of label IDs to add
+- `removeLabelIds`: Array of label IDs to remove
+- `message_id`: 15-16 char hex string for single operations
+
+**Pitfalls**:
+- Max 1000 messageIds per BATCH call; chunk larger sets
+- Use 'CATEGORY_UPDATES' not 'UPDATES'; full prefix required for category labels
+- SENT, DRAFT, CHAT are immutable — cannot be added/removed
+- To mark as read: REMOVE 'UNREAD'. To archive: REMOVE 'INBOX'
+- `message_id` must be 15-16 char hex, NOT UUIDs or web UI IDs
+
+### 6. Handle Drafts and Attachments
+
+**When to use**: User wants to create, edit, or send email drafts, possibly with attachments
+
+**Tool sequence**:
+1. `GMAIL_CREATE_EMAIL_DRAFT` - Create a new draft [Required]
+2. `GMAIL_UPDATE_DRAFT` - Edit draft content [Optional]
+3. `GMAIL_LIST_DRAFTS` - List existing drafts [Optional]
+4. `GMAIL_SEND_DRAFT` - Send a draft (requires explicit user approval) [Optional]
+5. `GMAIL_GET_ATTACHMENT` - Download attachment from existing message [Optional]
+
+**Key parameters**:
+- `recipient_email`: Draft recipient
+- `subject`: Draft subject (omit for reply drafts to stay in thread)
+- `body`: Draft content
+- `is_html`: Set `true` for HTML content
+- `attachment`: Object with `{s3key, mimetype, name}`
+- `thread_id`: For reply drafts (leave subject empty to stay in thread)
+
+**Pitfalls**:
+- Response includes `data.id` (draft_id) AND `data.message.id`; use `data.id` for draft operations
+- Setting subject on a thread reply draft creates a NEW thread instead
+- Attachment capped at ~25MB; base64 overhead can push near-limit files over
+- UPDATE_DRAFT replaces entire content, not patches; include all fields you want to keep
+- HTTP 429 on bulk draft creation; use exponential backoff
+
+## Common Patterns
+
+### ID Resolution
+
+**Label name → Label ID**:
+```
+1. Call GMAIL_LIST_LABELS
+2. Find label by name in response
+3. Extract id field (e.g., 'Label_123')
+```
+
+**Contact name → Email**:
+```
+1. Call GMAIL_SEARCH_PEOPLE with query=contact_name
+2. Extract emailAddresses from response
+```
+
+**Thread ID from search**:
+```
+1. Call GMAIL_FETCH_EMAILS or GMAIL_LIST_THREADS
+2. Extract threadId (15-16 char hex string)
+```
+
+### Pagination
+
+- Set `max_results` up to 500 per page
+- Check response for `nextPageToken`
+- Pass token as `page_token` in next request
+- Continue until `nextPageToken` is absent or empty string
+- `resultSizeEstimate` is approximate, not exact
+
+### Gmail Query Syntax
+
+**Operators**:
+- `from:sender@example.com` - Emails from sender
+- `to:recipient@example.com` - Emails to recipient
+- `subject:"exact phrase"` - Subject contains exact phrase
+- `is:unread` - Unread messages
+- `is:starred` - Starred messages
+- `is:snoozed` - Snoozed messages
+- `has:attachment` - Has attachments
+- `after:2024/01/01` - After date (YYYY/MM/DD)
+- `before:2024/12/31` - Before date
+- `label:custom_label` - User-created label (use label ID)
+- `in:sent` - In sent folder
+- `category:primary` - Primary category
+
+**Combinators**:
+- `AND` - Both conditions (default)
+- `OR` - Either condition
+- `NOT` - Exclude condition
+- `()` - Group conditions
+
+**Examples**:
+- `from:boss@company.com is:unread` - Unread emails from boss
+- `subject:invoice has:attachment after:2024/01/01` - Invoices with attachments this year
+- `(from:alice OR from:bob) is:starred` - Starred emails from Alice or Bob
+
+## Known Pitfalls
+
+**ID Formats**:
+- Custom label operations require label IDs (e.g., 'Label_123'), not display names
+- Always call LIST_LABELS first to resolve names to IDs
+- Message IDs are 15-16 char hex strings
+- Do NOT use UUIDs, web UI IDs, or 'thread-f:' prefixes
+
+**Query Syntax**:
+- Use 'is:' for states (unread, snoozed, starred)
+- Use 'label:' ONLY for user-created labels
+- System labels use 'is:' or 'in:' (e.g., 'is:sent', 'in:inbox')
+
+**Rate Limits**:
+- BATCH_MODIFY_MESSAGES max 1000 messages per call
+- Heavy use triggers 403/429 rate limits
+- Implement exponential backoff for bulk operations
+
+**Response Parsing**:
+- Response data may be nested under `data_preview` or `data.messages`
+- Parse defensively with fallbacks
+- Timestamp `messageTimestamp` uses RFC3339 with 'Z' suffix
+- Normalize to '+00:00' for parsing if needed
+
+**Attachments**:
+- Attachment `s3key` from prior download may expire
+- Use promptly after retrieval
+- Mimetype must include '/' separator
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Send email | GMAIL_SEND_EMAIL | recipient_email, subject, body, is_html |
+| Reply to thread | GMAIL_REPLY_TO_THREAD | thread_id, message_body, recipient_email |
+| Search emails | GMAIL_FETCH_EMAILS | query, max_results, label_ids, page_token |
+| Get message details | GMAIL_FETCH_MESSAGE_BY_MESSAGE_ID | message_id |
+| List labels | GMAIL_LIST_LABELS | (none) |
+| Create label | GMAIL_CREATE_LABEL | label_name, background_color, text_color |
+| Modify labels bulk | GMAIL_BATCH_MODIFY_MESSAGES | messageIds, addLabelIds, removeLabelIds |
+| Create draft | GMAIL_CREATE_EMAIL_DRAFT | recipient_email, subject, body, thread_id |
+| 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) |
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/go-to-webinar-automation/SKILL.md b/plugins/awesome-claude-skills/go-to-webinar-automation/SKILL.md
new file mode 100644
index 0000000..57bcd6f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/godial-automation/SKILL.md b/plugins/awesome-claude-skills/godial-automation/SKILL.md
new file mode 100644
index 0000000..23c98ee
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/gong-automation/SKILL.md b/plugins/awesome-claude-skills/gong-automation/SKILL.md
new file mode 100644
index 0000000..9dcd8b5
--- /dev/null
+++ b/plugins/awesome-claude-skills/gong-automation/SKILL.md
@@ -0,0 +1,172 @@
+---
+name: Gong Automation
+description: "Automate Gong conversation intelligence -- retrieve call recordings, transcripts, detailed analytics, speaker stats, and workspace data -- using natural language through the Composio MCP integration."
+category: conversation-intelligence
+requires:
+ mcp:
+ - rube
+---
+
+# Gong Automation
+
+Unlock insights from your sales calls -- retrieve transcripts, analyze call data by date range, access detailed conversation analytics with topics and trackers, and manage workspaces -- all through natural language commands.
+
+**Toolkit docs:** [composio.dev/toolkits/gong](https://composio.dev/toolkits/gong)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Gong account when prompted (OAuth / Bearer token authentication).
+3. Start issuing natural language commands to analyze your call data.
+
+---
+
+## Core Workflows
+
+### 1. Retrieve Call Transcripts by Date Range
+Get transcripts for all calls within a specified time period, with optional filtering by specific call IDs or workspace.
+
+**Tool:** `GONG_RETRIEVE_TRANSCRIPTS_OF_CALLS_V2_CALLS_TRANSCRIPT`
+
+**Example prompt:**
+> "Get Gong transcripts for all calls from February 1-10, 2025"
+
+**Key parameters:**
+- `filter__fromDateTime` -- ISO-8601 start date (e.g., `2025-02-01T00:00:00Z`)
+- `filter__toDateTime` -- ISO-8601 end date (e.g., `2025-02-10T23:59:59Z`)
+- `filter__callIds` -- Optional array of specific call IDs to filter
+- `filter__workspaceId` -- Optional workspace ID filter
+- `cursor` -- Pagination cursor from previous response
+
+**Required scope:** `api:calls:read:transcript`
+
+---
+
+### 2. Get Transcript for Specific Calls
+Retrieve transcripts with speaker information, timestamps, and topic categorization using a filter object.
+
+**Tool:** `GONG_GET_CALL_TRANSCRIPT`
+
+**Example prompt:**
+> "Get the Gong transcript for call ID 555785916001072125"
+
+**Key parameters (filter required):**
+- `filter.callIds` -- Array of specific call IDs (e.g., `["555785916001072125"]`)
+- `filter.fromDateTime` -- ISO-8601 start date
+- `filter.toDateTime` -- ISO-8601 end date
+- `filter.workspaceId` -- Optional workspace filter
+- `cursor` -- Pagination cursor
+
+---
+
+### 3. List Calls by Date Range
+Retrieve basic call metadata (participants, duration, timing) for calls within a date range.
+
+**Tool:** `GONG_RETRIEVE_CALL_DATA_BY_DATE_RANGE_V2_CALLS`
+
+**Example prompt:**
+> "List all Gong calls from last week"
+
+**Key parameters (both required):**
+- `fromDateTime` -- ISO-8601 start date (e.g., `2025-02-03T00:00:00Z`)
+- `toDateTime` -- ISO-8601 end date (e.g., `2025-02-10T00:00:00Z`)
+- `workspaceId` -- Optional workspace filter
+- `cursor` -- Pagination cursor
+
+**Required scope:** `api:calls:read:basic`
+
+---
+
+### 4. Get Detailed Call Analytics
+Retrieve extensive call details including highlights, key points, topics, trackers, speaker stats, questions, and media URLs.
+
+**Tool:** `GONG_RETRIEVE_FILTERED_CALL_DETAILS`
+
+**Example prompt:**
+> "Get detailed analytics for Gong calls this week including topics, key points, and speaker stats"
+
+**Key parameters:**
+- `filter__fromDateTime` / `filter__toDateTime` -- Date range filter
+- `filter__callIds` -- Specific call IDs
+- `filter__primaryUserIds` -- Filter by call host user IDs
+- Content selectors (all boolean):
+ - `contentSelector__exposedFields__content__keyPoints` -- Key points of the call
+ - `contentSelector__exposedFields__content__topics` -- Topic durations
+ - `contentSelector__exposedFields__content__highlights` -- Call highlights
+ - `contentSelector__exposedFields__content__outline` -- Call outline
+ - `contentSelector__exposedFields__content__brief` -- Spotlight call brief
+ - `contentSelector__exposedFields__content__callOutcome` -- Call outcome
+ - `contentSelector__exposedFields__content__trackers` -- Smart/keyword trackers
+ - `contentSelector__exposedFields__content__trackerOccurrences` -- Tracker timing and speaker (requires trackers=true)
+ - `contentSelector__exposedFields__interaction__speakers` -- Time each participant spoke
+ - `contentSelector__exposedFields__interaction__questions` -- Question counts
+ - `contentSelector__exposedFields__interaction__personInteractionStats` -- Host statistics
+ - `contentSelector__exposedFields__media` -- Audio/video URLs (valid 8 hours)
+ - `contentSelector__exposedFields__parties` -- Party information
+ - `contentSelector__exposedFields__collaboration__publicComments` -- Public comments
+- `contentSelector__context` -- "Basic", "Extended", or "None" for CRM/external system links
+
+**Required scope:** `api:calls:read:extensive` (plus `api:calls:read:media-url` for media)
+
+---
+
+### 5. Get a Specific Call by ID
+Retrieve basic data for a single call using its unique Gong ID.
+
+**Tool:** `GONG_RETRIEVE_DATA_FOR_A_SPECIFIC_CALL_V2_CALLS_ID`
+
+**Example prompt:**
+> "Get details for Gong call 1223781272986876929"
+
+**Key parameters (required):**
+- `id` -- Gong's unique numeric identifier for the call (up to 20 digits)
+
+**Required scope:** `api:calls:read:basic`
+
+---
+
+### 6. List Company Workspaces
+Retrieve all workspaces in your Gong organization to get workspace IDs for filtering.
+
+**Tool:** `GONG_LIST_ALL_COMPANY_WORKSPACES_V2_WORKSPACES`
+
+**Example prompt:**
+> "List all Gong workspaces in my company"
+
+**Key parameters:** None required.
+
+**Required scope:** `api:workspaces:read`
+
+---
+
+## Known Pitfalls
+
+- **ISO-8601 date format is mandatory**: All date parameters must use ISO-8601 format with timezone: `2025-02-01T00:00:00Z` or `2025-02-01T02:30:00-07:00`. Plain dates will fail.
+- **Date range is exclusive on toDateTime**: The `toDateTime` parameter returns calls started UP TO BUT EXCLUDING the specified time. To include calls on a specific day, set `toDateTime` to the next day.
+- **Pagination is required for large result sets**: All list endpoints return paginated results. Use the `cursor` value from the previous response to fetch the next page. Continue until no cursor is returned.
+- **Scope requirements vary by endpoint**: Different endpoints require different API scopes. Transcript access needs `api:calls:read:transcript`, basic call data needs `api:calls:read:basic`, and detailed analytics need `api:calls:read:extensive`.
+- **Media URLs expire after 8 hours**: Audio and video URLs returned by the detailed call endpoint are temporary and expire after 8 hours.
+- **Tracker occurrence data availability**: Tracker occurrence data (timing and speaker ID) is only available for calls recorded since January 1, 2023. Contact Gong support for backfill.
+- **Web-conference vs. regular calls**: For web-conference calls recorded by Gong, the date represents the scheduled time. For other calls, it represents the actual start time.
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Required Params |
+|---|---|---|
+| Get transcripts by date | `GONG_RETRIEVE_TRANSCRIPTS_OF_CALLS_V2_CALLS_TRANSCRIPT` | None (date range recommended) |
+| Get call transcript | `GONG_GET_CALL_TRANSCRIPT` | `filter` object |
+| List calls by date | `GONG_RETRIEVE_CALL_DATA_BY_DATE_RANGE_V2_CALLS` | `fromDateTime`, `toDateTime` |
+| Get detailed call analytics | `GONG_RETRIEVE_FILTERED_CALL_DETAILS` | None (date range or call IDs recommended) |
+| Get specific call | `GONG_RETRIEVE_DATA_FOR_A_SPECIFIC_CALL_V2_CALLS_ID` | `id` |
+| List workspaces | `GONG_LIST_ALL_COMPANY_WORKSPACES_V2_WORKSPACES` | None |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/goodbits-automation/SKILL.md b/plugins/awesome-claude-skills/goodbits-automation/SKILL.md
new file mode 100644
index 0000000..52366ad
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/goody-automation/SKILL.md b/plugins/awesome-claude-skills/goody-automation/SKILL.md
new file mode 100644
index 0000000..9b9504b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/google-address-validation-automation/SKILL.md b/plugins/awesome-claude-skills/google-address-validation-automation/SKILL.md
new file mode 100644
index 0000000..e08c8d7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/google-admin-automation/SKILL.md b/plugins/awesome-claude-skills/google-admin-automation/SKILL.md
new file mode 100644
index 0000000..c7e3cdc
--- /dev/null
+++ b/plugins/awesome-claude-skills/google-admin-automation/SKILL.md
@@ -0,0 +1,146 @@
+---
+name: google-admin-automation
+description: "Automate Google Workspace Admin tasks via Rube MCP (Composio): manage users, groups, memberships, suspend accounts, create users, add aliases. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Workspace Admin Automation via Rube MCP
+
+Manage Google Workspace users, groups, memberships, and organizational settings programmatically using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/google_admin](https://composio.dev/toolkits/google_admin)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin`
+- Google Workspace admin privileges for the authenticated account
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add 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
+
+## Core Workflows
+
+### 1. List All Users
+Use `GOOGLE_ADMIN_LIST_USERS` to retrieve Google Workspace users with optional filtering and pagination.
+```
+Tool: GOOGLE_ADMIN_LIST_USERS
+Parameters:
+ - customer: Customer ID or "my_customer" (default)
+ - domain: Domain to list users from
+ - query: Filter string (e.g., "orgName=Engineering", "isSuspended=false")
+ - max_results: Maximum results (1-500, default 100)
+ - order_by: Sort by "email", "givenName", or "familyName"
+ - sort_order: "ASCENDING" or "DESCENDING"
+ - page_token: Pagination token
+```
+
+### 2. Create a New User
+Use `GOOGLE_ADMIN_CREATE_USER` to provision a new Google Workspace account.
+```
+Tool: GOOGLE_ADMIN_CREATE_USER
+Parameters:
+ - primary_email (required): User's email (e.g., "john.doe@company.com")
+ - given_name (required): First name
+ - family_name (required): Last name
+ - password (required): Password meeting domain requirements
+ - org_unit_path: Organizational unit (default: "/")
+ - change_password_at_next_login: Force password change (default: true)
+ - recovery_email: Recovery email address
+ - recovery_phone: Recovery phone number
+ - suspended: Whether account starts suspended (default: false)
+```
+
+### 3. List and Manage Groups
+Use `GOOGLE_ADMIN_LIST_GROUPS` to list groups, and `GOOGLE_ADMIN_CREATE_GROUP` to create new ones.
+```
+Tool: GOOGLE_ADMIN_LIST_GROUPS
+Parameters:
+ - customer: "my_customer" (default)
+ - domain: Filter by domain
+ - query: Filter (e.g., "name=Engineering*")
+ - max_results: Max results (1-200)
+ - order_by: Sort by "email"
+ - page_token: Pagination token
+
+Tool: GOOGLE_ADMIN_CREATE_GROUP
+Parameters:
+ - email (required): Group email address (e.g., "engineering@company.com")
+ - name (required): Display name (e.g., "Engineering Team")
+ - description: Group purpose description
+```
+
+### 4. Add Users to Groups
+Use `GOOGLE_ADMIN_ADD_USER_TO_GROUP` to manage group membership.
+```
+Tool: GOOGLE_ADMIN_ADD_USER_TO_GROUP
+Parameters:
+ - group_key (required): Group email or ID
+ - user_key (required): User email or ID to add
+ - role: "MEMBER" (default), "MANAGER", or "OWNER"
+```
+
+### 5. Suspend or Unsuspend Users
+Use `GOOGLE_ADMIN_SUSPEND_USER` to toggle user account suspension.
+```
+Tool: GOOGLE_ADMIN_SUSPEND_USER
+Parameters:
+ - user_key (required): User's email or unique ID
+ - suspended: true to suspend, false to unsuspend (default: true)
+ - suspension_reason: Reason for suspension (optional)
+```
+
+### 6. Get User or Group Details
+Use `GOOGLE_ADMIN_GET_USER` or `GOOGLE_ADMIN_GET_GROUP` to retrieve detailed information.
+```
+Tool: GOOGLE_ADMIN_GET_USER
+Parameters:
+ - user_key (required): User's email or unique ID
+
+Tool: GOOGLE_ADMIN_GET_GROUP
+Parameters:
+ - group_key (required): Group's email or unique ID
+```
+
+## Common Patterns
+
+- **Onboarding workflow**: Use `GOOGLE_ADMIN_CREATE_USER` to provision the account, then `GOOGLE_ADMIN_ADD_USER_TO_GROUP` to add them to relevant groups.
+- **Offboarding workflow**: Use `GOOGLE_ADMIN_SUSPEND_USER` to disable access, or `GOOGLE_ADMIN_DELETE_USER` for permanent removal.
+- **Audit group membership**: Use `GOOGLE_ADMIN_LIST_GROUPS` to find groups, then `GOOGLE_ADMIN_LIST_GROUP_MEMBERS` to review members.
+- **Bulk user management**: List users with `GOOGLE_ADMIN_LIST_USERS` and filter queries, then iterate for updates.
+- **Add email aliases**: Use `GOOGLE_ADMIN_ADD_USER_ALIAS` to add alternative email addresses for a user.
+- **Look up user details**: Use `GOOGLE_ADMIN_GET_USER` to retrieve full profile information before making changes.
+
+## Known Pitfalls
+
+- **Admin privileges required**: All tools require the authenticated user to have Google Workspace administrator privileges. Non-admin accounts will receive permission errors.
+- **Delete is permanent**: `GOOGLE_ADMIN_DELETE_USER` permanently removes a user account. This action cannot be undone.
+- **user_key accepts email or ID**: The `user_key` parameter accepts both the user's primary email address and their unique numeric user ID.
+- **Group membership replaces**: When adding to groups, the `role` parameter controls the member's role. There is no "update role" -- remove and re-add to change roles.
+- **Customer ID**: Use `"my_customer"` as the `customer` parameter for the authenticated user's organization. Specific customer IDs look like `C01abc123`.
+- **Pagination**: Both user and group list endpoints may return paginated results. Always check for `page_token` in responses for complete results.
+- **Password requirements**: `GOOGLE_ADMIN_CREATE_USER` requires a password that meets the domain's password policy. Weak passwords will be rejected.
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| List users | `GOOGLE_ADMIN_LIST_USERS` | `customer`, `domain`, `query`, `max_results` |
+| Get user details | `GOOGLE_ADMIN_GET_USER` | `user_key` |
+| Create user | `GOOGLE_ADMIN_CREATE_USER` | `primary_email`, `given_name`, `family_name`, `password` |
+| Delete user | `GOOGLE_ADMIN_DELETE_USER` | `user_key` |
+| Suspend user | `GOOGLE_ADMIN_SUSPEND_USER` | `user_key`, `suspended` |
+| Add user alias | `GOOGLE_ADMIN_ADD_USER_ALIAS` | (see full schema via RUBE_SEARCH_TOOLS) |
+| List groups | `GOOGLE_ADMIN_LIST_GROUPS` | `customer`, `domain`, `query` |
+| Get group details | `GOOGLE_ADMIN_GET_GROUP` | `group_key` |
+| Create group | `GOOGLE_ADMIN_CREATE_GROUP` | `email`, `name`, `description` |
+| Add to group | `GOOGLE_ADMIN_ADD_USER_TO_GROUP` | `group_key`, `user_key`, `role` |
+| List group members | `GOOGLE_ADMIN_LIST_GROUP_MEMBERS` | (see full schema via RUBE_SEARCH_TOOLS) |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/google-analytics-automation/SKILL.md b/plugins/awesome-claude-skills/google-analytics-automation/SKILL.md
new file mode 100644
index 0000000..2f55abe
--- /dev/null
+++ b/plugins/awesome-claude-skills/google-analytics-automation/SKILL.md
@@ -0,0 +1,232 @@
+---
+name: google-analytics-automation
+description: "Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Analytics Automation via Rube MCP
+
+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)
+- Active Google Analytics connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_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 `google_analytics`
+3. If connection is not ACTIVE, follow the returned auth link to complete Google OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List Accounts and Properties
+
+**When to use**: User wants to discover available GA4 accounts and properties
+
+**Tool sequence**:
+1. `GOOGLE_ANALYTICS_LIST_ACCOUNTS` - List all accessible GA4 accounts [Required]
+2. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - List properties under an account [Required]
+
+**Key parameters**:
+- `pageSize`: Number of results per page
+- `pageToken`: Pagination token from previous response
+- `filter`: Filter expression for properties (e.g., `parent:accounts/12345`)
+
+**Pitfalls**:
+- Property IDs are numeric strings prefixed with 'properties/' (e.g., 'properties/123456')
+- Account IDs are prefixed with 'accounts/' (e.g., 'accounts/12345')
+- Always list accounts first, then properties under each account
+- Pagination required for organizations with many properties
+
+### 2. Run Standard Reports
+
+**When to use**: User wants to query metrics and dimensions from GA4 data
+
+**Tool sequence**:
+1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]
+2. `GOOGLE_ANALYTICS_GET_METADATA` - Discover available dimensions and metrics [Optional]
+3. `GOOGLE_ANALYTICS_CHECK_COMPATIBILITY` - Verify dimension/metric compatibility [Optional]
+4. `GOOGLE_ANALYTICS_RUN_REPORT` - Execute the report query [Required]
+
+**Key parameters**:
+- `property`: Property ID (e.g., 'properties/123456')
+- `dateRanges`: Array of date range objects with `startDate` and `endDate`
+- `dimensions`: Array of dimension objects with `name` field
+- `metrics`: Array of metric objects with `name` field
+- `dimensionFilter` / `metricFilter`: Filter expressions
+- `orderBys`: Sort order configuration
+- `limit`: Maximum rows to return
+- `offset`: Row offset for pagination
+
+**Pitfalls**:
+- Date format is 'YYYY-MM-DD' or relative values like 'today', 'yesterday', '7daysAgo', '30daysAgo'
+- Not all dimensions and metrics are compatible; use CHECK_COMPATIBILITY first
+- Use GET_METADATA to discover valid dimension and metric names
+- Maximum 9 dimensions per report request
+- Row limit defaults vary; set explicitly for large datasets
+- `offset` is for result pagination, not date pagination
+
+### 3. Run Batch Reports
+
+**When to use**: User needs multiple different reports from the same property in one call
+
+**Tool sequence**:
+1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]
+2. `GOOGLE_ANALYTICS_BATCH_RUN_REPORTS` - Execute multiple reports at once [Required]
+
+**Key parameters**:
+- `property`: Property ID (required)
+- `requests`: Array of individual report request objects (same structure as RUN_REPORT)
+
+**Pitfalls**:
+- Maximum 5 report requests per batch call
+- All reports in a batch must target the same property
+- Each individual report has the same dimension/metric limits as RUN_REPORT
+- Batch errors may affect all reports; check individual report responses
+
+### 4. Run Pivot Reports
+
+**When to use**: User wants cross-tabulated data (rows vs columns) like pivot tables
+
+**Tool sequence**:
+1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]
+2. `GOOGLE_ANALYTICS_RUN_PIVOT_REPORT` - Execute pivot report [Required]
+
+**Key parameters**:
+- `property`: Property ID (required)
+- `dateRanges`: Date range objects
+- `dimensions`: All dimensions used in any pivot
+- `metrics`: Metrics to aggregate
+- `pivots`: Array of pivot definitions with `fieldNames`, `limit`, and `orderBys`
+
+**Pitfalls**:
+- Dimensions used in pivots must also be listed in top-level `dimensions`
+- Pivot `fieldNames` reference dimension names from the top-level list
+- Complex pivots with many dimensions can produce very large result sets
+- Each pivot has its own independent `limit` and `orderBys`
+
+### 5. Run Funnel Reports
+
+**When to use**: User wants to analyze conversion funnels and drop-off rates
+
+**Tool sequence**:
+1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]
+2. `GOOGLE_ANALYTICS_RUN_FUNNEL_REPORT` - Execute funnel analysis [Required]
+
+**Key parameters**:
+- `property`: Property ID (required)
+- `dateRanges`: Date range objects
+- `funnel`: Funnel definition with `steps` array
+- `funnelBreakdown`: Optional dimension to break down funnel by
+
+**Pitfalls**:
+- Funnel steps are ordered; each step defines a condition users must meet
+- Steps use filter expressions similar to dimension/metric filters
+- Open funnels allow entry at any step; closed funnels require sequential progression
+- Funnel reports may take longer to process than standard reports
+
+### 6. Manage Key Events
+
+**When to use**: User wants to view or manage conversion events (key events) in GA4
+
+**Tool sequence**:
+1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]
+2. `GOOGLE_ANALYTICS_LIST_KEY_EVENTS` - List all key events for the property [Required]
+
+**Key parameters**:
+- `parent`: Property resource name (e.g., 'properties/123456')
+- `pageSize`: Number of results per page
+- `pageToken`: Pagination token
+
+**Pitfalls**:
+- Key events were previously called "conversions" in GA4
+- Property must have key events configured to return results
+- Key event names correspond to GA4 event names
+
+## Common Patterns
+
+### ID Resolution
+
+**Account name -> Account ID**:
+```
+1. Call GOOGLE_ANALYTICS_LIST_ACCOUNTS
+2. Find account by displayName
+3. Extract name field (e.g., 'accounts/12345')
+```
+
+**Property name -> Property ID**:
+```
+1. Call GOOGLE_ANALYTICS_LIST_PROPERTIES with filter
+2. Find property by displayName
+3. Extract name field (e.g., 'properties/123456')
+```
+
+### Dimension/Metric Discovery
+
+```
+1. Call GOOGLE_ANALYTICS_GET_METADATA with property ID
+2. Browse available dimensions and metrics
+3. Call GOOGLE_ANALYTICS_CHECK_COMPATIBILITY to verify combinations
+4. Use verified dimensions/metrics in RUN_REPORT
+```
+
+### Pagination
+
+- Reports: Use `offset` and `limit` for row pagination
+- Accounts/Properties: Use `pageToken` from response
+- Continue until `pageToken` is absent or `rowCount` reached
+
+### Common Dimensions and Metrics
+
+**Dimensions**: `date`, `city`, `country`, `deviceCategory`, `sessionSource`, `sessionMedium`, `pagePath`, `pageTitle`, `eventName`
+
+**Metrics**: `activeUsers`, `sessions`, `screenPageViews`, `eventCount`, `conversions`, `totalRevenue`, `bounceRate`, `averageSessionDuration`
+
+## Known Pitfalls
+
+**Property IDs**:
+- Always use full resource name format: 'properties/123456'
+- Numeric ID alone will cause errors
+- Resolve property names to IDs via LIST_PROPERTIES
+
+**Date Ranges**:
+- Format: 'YYYY-MM-DD' or relative ('today', 'yesterday', '7daysAgo', '30daysAgo')
+- Data processing delay means today's data may be incomplete
+- Maximum date range varies by property configuration
+
+**Compatibility**:
+- Not all dimensions work with all metrics
+- Always verify with CHECK_COMPATIBILITY before complex reports
+- Custom dimensions/metrics have specific naming patterns
+
+**Response Parsing**:
+- Report data is nested in `rows` array with `dimensionValues` and `metricValues`
+- Values are returned as strings; parse numbers explicitly
+- Empty reports return no `rows` key (not an empty array)
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List accounts | GOOGLE_ANALYTICS_LIST_ACCOUNTS | pageSize, pageToken |
+| List properties | GOOGLE_ANALYTICS_LIST_PROPERTIES | filter, pageSize |
+| Get metadata | GOOGLE_ANALYTICS_GET_METADATA | property |
+| Check compatibility | GOOGLE_ANALYTICS_CHECK_COMPATIBILITY | property, dimensions, metrics |
+| Run report | GOOGLE_ANALYTICS_RUN_REPORT | property, dateRanges, dimensions, metrics |
+| Batch reports | GOOGLE_ANALYTICS_BATCH_RUN_REPORTS | property, requests |
+| 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/plugins/awesome-claude-skills/google-calendar-automation/SKILL.md b/plugins/awesome-claude-skills/google-calendar-automation/SKILL.md
new file mode 100644
index 0000000..2561d9b
--- /dev/null
+++ b/plugins/awesome-claude-skills/google-calendar-automation/SKILL.md
@@ -0,0 +1,181 @@
+---
+name: google-calendar-automation
+description: Automate Google Calendar events, scheduling, availability checks, and attendee management via Rube MCP (Composio). Create events, find free slots, manage attendees, and list calendars programmatically.
+requires:
+ mcp: [rube]
+---
+
+# Google Calendar Automation via Rube MCP
+
+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)
+- 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 Google OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Events
+
+**When to use**: User wants to create, update, or delete calendar events
+
+**Tool sequence**:
+1. `GOOGLECALENDAR_LIST_CALENDARS` - Identify target calendar ID [Prerequisite]
+2. `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` - Get current time with proper timezone [Optional]
+3. `GOOGLECALENDAR_FIND_FREE_SLOTS` - Check availability before booking [Optional]
+4. `GOOGLECALENDAR_CREATE_EVENT` - Create the event [Required]
+5. `GOOGLECALENDAR_PATCH_EVENT` - Update specific fields of an existing event [Alternative]
+6. `GOOGLECALENDAR_UPDATE_EVENT` - Full replacement update of an event [Alternative]
+7. `GOOGLECALENDAR_DELETE_EVENT` - Delete an event [Optional]
+
+**Key parameters**:
+- `calendar_id`: Use 'primary' for main calendar, or specific calendar ID
+- `start_datetime`: ISO 8601 format 'YYYY-MM-DDTHH:MM:SS' (NOT natural language)
+- `timezone`: IANA timezone name (e.g., 'America/New_York', NOT 'EST' or 'PST')
+- `event_duration_hour`: Hours (0+)
+- `event_duration_minutes`: Minutes (0-59 only; NEVER use 60+)
+- `summary`: Event title
+- `attendees`: Array of email addresses (NOT names)
+- `location`: Free-form text for event location
+
+**Pitfalls**:
+- `start_datetime` must be ISO 8601; natural language like 'tomorrow' is rejected
+- `event_duration_minutes` max is 59; use `event_duration_hour=1` instead of `event_duration_minutes=60`
+- `timezone` must be IANA identifier; abbreviations like 'EST', 'PST' are NOT valid
+- `attendees` only accepts email addresses, not names; resolve names first
+- Google Meet link creation defaults to true; may fail on personal Gmail accounts (graceful fallback)
+- Organizer is auto-added as attendee unless `exclude_organizer=true`
+
+### 2. List and Search Events
+
+**When to use**: User wants to find or browse events on their calendar
+
+**Tool sequence**:
+1. `GOOGLECALENDAR_LIST_CALENDARS` - Get available calendars [Prerequisite]
+2. `GOOGLECALENDAR_FIND_EVENT` - Search by title/keyword with time bounds [Required]
+3. `GOOGLECALENDAR_EVENTS_LIST` - List events in a time range [Alternative]
+4. `GOOGLECALENDAR_EVENTS_INSTANCES` - List instances of a recurring event [Optional]
+
+**Key parameters**:
+- `query` / `q`: Free-text search (matches summary, description, location, attendees)
+- `timeMin`: Lower bound (RFC3339 with timezone offset, e.g., '2024-01-01T00:00:00-08:00')
+- `timeMax`: Upper bound (RFC3339 with timezone offset)
+- `singleEvents`: true to expand recurring events into instances
+- `orderBy`: 'startTime' (requires singleEvents=true) or 'updated'
+- `maxResults`: Results per page (max 2500)
+
+**Pitfalls**:
+- **Timezone warning**: UTC timestamps (ending in 'Z') don't align with local dates; use local timezone offsets instead
+- Example: '2026-01-19T00:00:00Z' covers 2026-01-18 4pm to 2026-01-19 4pm in PST
+- Omitting `timeMin`/`timeMax` scans the full calendar and can be slow
+- `pageToken` in response means more results; paginate until absent
+- `orderBy='startTime'` requires `singleEvents=true`
+
+### 3. Manage Attendees and Invitations
+
+**When to use**: User wants to add, remove, or update event attendees
+
+**Tool sequence**:
+1. `GOOGLECALENDAR_FIND_EVENT` or `GOOGLECALENDAR_EVENTS_LIST` - Find the event [Prerequisite]
+2. `GOOGLECALENDAR_PATCH_EVENT` - Add attendees (replaces entire attendees list) [Required]
+3. `GOOGLECALENDAR_REMOVE_ATTENDEE` - Remove a specific attendee by email [Required]
+
+**Key parameters**:
+- `event_id`: Unique event identifier (opaque string, NOT the event title)
+- `attendees`: Full list of attendee emails (PATCH replaces entire list)
+- `attendee_email`: Email to remove
+- `send_updates`: 'all', 'externalOnly', or 'none'
+
+**Pitfalls**:
+- `event_id` is a technical identifier, NOT the event title; always search first to get the ID
+- `PATCH_EVENT` attendees field replaces the entire list; include existing attendees to avoid removing them
+- Attendee names cannot be resolved; always use email addresses
+- Use `GMAIL_SEARCH_PEOPLE` to resolve names to emails before managing attendees
+
+### 4. Check Availability and Free/Busy Status
+
+**When to use**: User wants to find available time slots or check busy periods
+
+**Tool sequence**:
+1. `GOOGLECALENDAR_LIST_CALENDARS` - Identify calendars to check [Prerequisite]
+2. `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` - Get current time with timezone [Optional]
+3. `GOOGLECALENDAR_FIND_FREE_SLOTS` - Find free intervals across calendars [Required]
+4. `GOOGLECALENDAR_FREE_BUSY_QUERY` - Get raw busy periods for computing gaps [Fallback]
+5. `GOOGLECALENDAR_CREATE_EVENT` - Book a confirmed slot [Required]
+
+**Key parameters**:
+- `items`: List of calendar IDs to check (e.g., ['primary'])
+- `time_min`/`time_max`: Query interval (defaults to current day if omitted)
+- `timezone`: IANA timezone for interpreting naive timestamps
+- `calendarExpansionMax`: Max calendars (1-50)
+- `groupExpansionMax`: Max members per group (1-100)
+
+**Pitfalls**:
+- Maximum span ~90 days per Google Calendar freeBusy API limit
+- Very long ranges or inaccessible calendars yield empty/invalid results
+- Only calendars with at least freeBusyReader access are visible
+- Free slots responses may normalize to UTC ('Z'); check offsets
+- `GOOGLECALENDAR_FREE_BUSY_QUERY` requires RFC3339 timestamps with timezone
+
+## Common Patterns
+
+### ID Resolution
+- **Calendar name -> calendar_id**: `GOOGLECALENDAR_LIST_CALENDARS` to enumerate all calendars
+- **Event title -> event_id**: `GOOGLECALENDAR_FIND_EVENT` or `GOOGLECALENDAR_EVENTS_LIST`
+- **Attendee name -> email**: `GMAIL_SEARCH_PEOPLE`
+
+### Timezone Handling
+- Always use IANA timezone identifiers (e.g., 'America/Los_Angeles')
+- Use `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` to get current time in user's timezone
+- When querying events for a local date, use timestamps with local offset, NOT UTC
+- Example: '2026-01-19T00:00:00-08:00' for PST, NOT '2026-01-19T00:00:00Z'
+
+### Pagination
+- `GOOGLECALENDAR_EVENTS_LIST` returns `nextPageToken`; iterate until absent
+- `GOOGLECALENDAR_LIST_CALENDARS` also paginates; use `page_token`
+
+## Known Pitfalls
+
+- **Natural language dates**: NOT supported; all dates must be ISO 8601 or RFC3339
+- **Timezone mismatch**: UTC timestamps don't align with local dates for filtering
+- **Duration limits**: `event_duration_minutes` max 59; use hours for longer durations
+- **IANA timezones only**: 'EST', 'PST', etc. are NOT valid; use 'America/New_York'
+- **Event IDs are opaque**: Always search to get event_id; never guess or construct
+- **Attendees as emails**: Names cannot be used; resolve with GMAIL_SEARCH_PEOPLE
+- **PATCH replaces attendees**: Include all desired attendees in the array, not just new ones
+- **Conference limitations**: Google Meet may fail on personal accounts (graceful fallback)
+- **Rate limits**: High-volume searches can trigger 403/429; throttle between calls
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List calendars | `GOOGLECALENDAR_LIST_CALENDARS` | `max_results` |
+| Create event | `GOOGLECALENDAR_CREATE_EVENT` | `start_datetime`, `timezone`, `summary` |
+| Update event | `GOOGLECALENDAR_PATCH_EVENT` | `calendar_id`, `event_id`, fields to update |
+| Delete event | `GOOGLECALENDAR_DELETE_EVENT` | `calendar_id`, `event_id` |
+| Search events | `GOOGLECALENDAR_FIND_EVENT` | `query`, `timeMin`, `timeMax` |
+| List events | `GOOGLECALENDAR_EVENTS_LIST` | `calendarId`, `timeMin`, `timeMax` |
+| Recurring instances | `GOOGLECALENDAR_EVENTS_INSTANCES` | `calendarId`, `eventId` |
+| Find free slots | `GOOGLECALENDAR_FIND_FREE_SLOTS` | `items`, `time_min`, `time_max`, `timezone` |
+| Free/busy query | `GOOGLECALENDAR_FREE_BUSY_QUERY` | `timeMin`, `timeMax`, `items` |
+| 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/plugins/awesome-claude-skills/google-classroom-automation/SKILL.md b/plugins/awesome-claude-skills/google-classroom-automation/SKILL.md
new file mode 100644
index 0000000..60d152d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/google-cloud-vision-automation/SKILL.md b/plugins/awesome-claude-skills/google-cloud-vision-automation/SKILL.md
new file mode 100644
index 0000000..74046c6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/google-drive-automation/SKILL.md b/plugins/awesome-claude-skills/google-drive-automation/SKILL.md
new file mode 100644
index 0000000..64ac888
--- /dev/null
+++ b/plugins/awesome-claude-skills/google-drive-automation/SKILL.md
@@ -0,0 +1,198 @@
+---
+name: google-drive-automation
+description: Automate Google Drive file operations (upload, download, search, share, organize) via Rube MCP (Composio). Upload/download files, manage folders, share with permissions, and search across drives programmatically.
+requires:
+ mcp: [rube]
+---
+
+# Google Drive Automation via Rube MCP
+
+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)
+- 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 Google OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Upload and Download Files
+
+**When to use**: User wants to upload files to or download files from Google Drive
+
+**Tool sequence**:
+1. `GOOGLEDRIVE_FIND_FILE` - Locate target folder for upload [Prerequisite]
+2. `GOOGLEDRIVE_UPLOAD_FILE` - Upload a file (max 5MB) [Required]
+3. `GOOGLEDRIVE_RESUMABLE_UPLOAD` - Upload large files [Fallback]
+4. `GOOGLEDRIVE_DOWNLOAD_FILE` - Download a file by ID [Required]
+5. `GOOGLEDRIVE_DOWNLOAD_FILE_OPERATION` - Track long-running downloads [Fallback]
+6. `GOOGLEDRIVE_GET_FILE_METADATA` - Verify file after upload/download [Optional]
+
+**Key parameters**:
+- `file_to_upload`: Object with `name`, `mimetype`, and `s3key` (file must be in internal storage)
+- `folder_to_upload_to`: Target folder ID (optional; uploads to root if omitted)
+- `file_id`: ID of file to download
+- `mime_type`: Export format for Google Workspace files only (omit for native files)
+
+**Pitfalls**:
+- `GOOGLEDRIVE_UPLOAD_FILE` requires `file_to_upload.s3key`; files must already be in internal storage
+- For non-Google formats (Excel, PDF), do NOT set `mime_type`; it causes errors for native files
+- Download responses provide a temporary URL at `data.downloaded_file_content.s3url`, not inline bytes
+- Use `GOOGLEDRIVE_RESUMABLE_UPLOAD` for files >5MB or when basic uploads fail
+
+### 2. Search and List Files
+
+**When to use**: User wants to find specific files or browse Drive contents
+
+**Tool sequence**:
+1. `GOOGLEDRIVE_FIND_FILE` - Search by name, content, type, date, or folder [Required]
+2. `GOOGLEDRIVE_LIST_FILES` - Browse files with folder scoping [Alternative]
+3. `GOOGLEDRIVE_LIST_SHARED_DRIVES` - Enumerate shared drives [Optional]
+4. `GOOGLEDRIVE_GET_FILE_METADATA` - Get detailed file info [Optional]
+5. `GOOGLEDRIVE_GET_ABOUT` - Check storage quota and supported formats [Optional]
+
+**Key parameters**:
+- `q`: Drive query string (e.g., "name contains 'report'", "mimeType = 'application/pdf'")
+- `corpora`: Search scope ('user', 'domain', 'drive', 'allDrives')
+- `fields`: Response fields to include (e.g., 'files(id,name,mimeType)')
+- `orderBy`: Sort key ('modifiedTime desc', 'name', 'quotaBytesUsed desc')
+- `pageSize`: Results per page (max 1000)
+- `pageToken`: Pagination cursor from `nextPageToken`
+- `folder_id`: Scope search to a specific folder
+
+**Pitfalls**:
+- 403 PERMISSION_DENIED if OAuth scopes insufficient for shared drives
+- Pagination required; files are in `response.data.files`; follow `nextPageToken` until exhausted
+- `corpora="domain"` may trigger 400; try `"allDrives"` with `includeItemsFromAllDrives=true`
+- Query complexity limits: >5-10 OR clauses may error "The query is too complex"
+- Wildcards (*) NOT supported in `name`; use `contains` for partial matching
+- 'My Drive' is NOT searchable by name; use `folder_id='root'` for root folder
+- User email searches: use `'user@example.com' in owners` (NOT `owner:user@example.com`)
+
+### 3. Share Files and Manage Permissions
+
+**When to use**: User wants to share files or manage access permissions
+
+**Tool sequence**:
+1. `GOOGLEDRIVE_FIND_FILE` - Locate the file to share [Prerequisite]
+2. `GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE` - Set sharing permission [Required]
+3. `GOOGLEDRIVE_LIST_PERMISSIONS` - View current permissions [Optional]
+4. `GOOGLEDRIVE_GET_PERMISSION` - Inspect a specific permission [Optional]
+5. `GOOGLEDRIVE_UPDATE_PERMISSION` - Modify existing permission [Optional]
+6. `GOOGLEDRIVE_DELETE_PERMISSION` - Revoke access [Optional]
+
+**Key parameters**:
+- `file_id`: ID of file to share
+- `type`: 'user', 'group', 'domain', or 'anyone'
+- `role`: 'owner', 'organizer', 'fileOrganizer', 'writer', 'commenter', 'reader'
+- `email_address`: Required for type='user' or 'group'
+- `domain`: Required for type='domain'
+- `transfer_ownership`: Required when role='owner'
+
+**Pitfalls**:
+- Invalid type/email combinations trigger 4xx errors
+- Using `type='anyone'` or powerful roles is risky; get explicit user confirmation
+- Org policies may block certain sharing types, causing 403
+- Permission changes may take time to propagate
+- Use `GMAIL_SEARCH_PEOPLE` to resolve contact names to emails before sharing
+
+### 4. Create and Organize Folders
+
+**When to use**: User wants to create folder structures or move files between folders
+
+**Tool sequence**:
+1. `GOOGLEDRIVE_FIND_FILE` - Check if folder already exists [Prerequisite]
+2. `GOOGLEDRIVE_CREATE_FOLDER` - Create a new folder [Required]
+3. `GOOGLEDRIVE_GET_FILE_METADATA` - Verify created folder [Optional]
+4. `GOOGLEDRIVE_MOVE_FILE` - Move files between folders [Optional]
+5. `GOOGLEDRIVE_UPDATE_FILE_PUT` - Update file metadata/parents [Alternative]
+
+**Key parameters**:
+- `name`: Folder name
+- `parent_id`: Parent folder ID (NOT name); omit for root
+- `file_id`: File to move
+- `add_parents`: Destination folder ID for move
+- `remove_parents`: Source folder ID to remove from
+
+**Pitfalls**:
+- `GOOGLEDRIVE_CREATE_FOLDER` requires `parent_id` as an ID, not a folder name
+- Using `parent_id="root"` creates at top level; for nested paths, chain folder IDs
+- `GOOGLEDRIVE_FIND_FILE` returns ~100 items/page; follow `nextPageToken` for large drives
+- Move operations can leave items with multiple parents; use `remove_parents` for true moves
+- Always verify parent folder exists before creating children
+
+## Common Patterns
+
+### ID Resolution
+- **File/folder name -> ID**: `GOOGLEDRIVE_FIND_FILE` with `q` parameter
+- **Root folder**: Use `folder_id='root'` or `'root' in parents`
+- **Shared drive -> driveId**: `GOOGLEDRIVE_LIST_SHARED_DRIVES`
+- **Contact name -> email**: `GMAIL_SEARCH_PEOPLE` (for sharing)
+
+### Query Syntax
+Google Drive uses a specific query language:
+- Name search: `"name contains 'report'"` or `"name = 'exact.pdf'"`
+- Type filter: `"mimeType = 'application/pdf'"` or `"mimeType = 'application/vnd.google-apps.folder'"`
+- Folder scoping: `"'FOLDER_ID' in parents"`
+- Date filter: `"modifiedTime > '2024-01-01T00:00:00'"`
+- Combine with `and`/`or`/`not`: `"name contains 'report' and trashed = false"`
+- Boolean filters: `"sharedWithMe = true"`, `"starred = true"`, `"trashed = false"`
+
+### Pagination
+- Follow `nextPageToken` until absent for complete results
+- Set `pageSize` explicitly (default 100, max 1000)
+- De-duplicate results if running multiple searches
+
+### Export Formats
+For Google Workspace files, set `mime_type` to export:
+- **Docs**: `application/pdf`, `text/plain`, `text/html`, `application/vnd.openxmlformats-officedocument.wordprocessingml.document`
+- **Sheets**: `text/csv`, `application/vnd.openxmlformats-officedocument.spreadsheetml.sheet`
+- **Slides**: `application/pdf`, `application/vnd.openxmlformats-officedocument.presentationml.presentation`
+
+## Known Pitfalls
+
+- **Internal storage required**: Upload requires files in internal S3 storage (s3key)
+- **Export vs download**: Set `mime_type` ONLY for Google Workspace files; omit for native files
+- **Temporary URLs**: Downloaded content via `s3url` is temporary; fetch promptly
+- **Query complexity**: >5-10 OR clauses may error; split complex searches into multiple queries
+- **Shared drive scoping**: Missing drive permissions yield empty results; verify access first
+- **No wildcards**: Use `contains` operator instead of `*` for partial name matching
+- **Folder creation chains**: Always pass folder IDs (not names) as `parent_id`
+- **Multiple parents**: Move operations may leave items with multiple parents; use `remove_parents`
+- **Rate limits**: Heavy searches/exports can trigger 403/429; implement backoff
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search files | `GOOGLEDRIVE_FIND_FILE` | `q`, `corpora`, `pageSize` |
+| List files | `GOOGLEDRIVE_LIST_FILES` | `folderId`, `q`, `orderBy` |
+| Upload file | `GOOGLEDRIVE_UPLOAD_FILE` | `file_to_upload`, `folder_to_upload_to` |
+| Resumable upload | `GOOGLEDRIVE_RESUMABLE_UPLOAD` | file data |
+| Download file | `GOOGLEDRIVE_DOWNLOAD_FILE` | `file_id`, `mime_type` (Workspace only) |
+| File metadata | `GOOGLEDRIVE_GET_FILE_METADATA` | `fileId`, `fields` |
+| Create folder | `GOOGLEDRIVE_CREATE_FOLDER` | `name`, `parent_id` |
+| Move file | `GOOGLEDRIVE_MOVE_FILE` | `file_id`, `add_parents`, `remove_parents` |
+| Share file | `GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE` | `file_id`, `role`, `type`, `email_address` |
+| List permissions | `GOOGLEDRIVE_LIST_PERMISSIONS` | `fileId` |
+| Update permission | `GOOGLEDRIVE_UPDATE_PERMISSION` | file_id, permission_id |
+| Delete permission | `GOOGLEDRIVE_DELETE_PERMISSION` | file_id, permission_id |
+| 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/plugins/awesome-claude-skills/google-maps-automation/SKILL.md b/plugins/awesome-claude-skills/google-maps-automation/SKILL.md
new file mode 100644
index 0000000..800ce20
--- /dev/null
+++ b/plugins/awesome-claude-skills/google-maps-automation/SKILL.md
@@ -0,0 +1,138 @@
+---
+name: google-maps-automation
+description: "Automate Google Maps tasks via Rube MCP (Composio): geocode addresses, search places, get directions, compute route matrices, reverse geocode, autocomplete, get place details. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Maps Automation via Rube MCP
+
+Geocode addresses, search places, get directions, compute distance matrices, and retrieve place details using Google Maps via Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/google_maps](https://composio.dev/toolkits/google_maps)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active 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
+
+## Core Workflows
+
+### 1. Geocode an Address
+Use `GOOGLE_MAPS_GEOCODING_API` to convert a street address into geographic coordinates (latitude/longitude).
+```
+Tool: GOOGLE_MAPS_GEOCODING_API
+Parameters:
+ - address: Street address or plus code to geocode
+ - latlng: Lat/lng for reverse geocoding (e.g., "40.714224,-73.961452")
+ - place_id: Place ID for place geocoding
+ - language: Language for results
+ - region: Region bias (ccTLD code)
+ - bounds: Bounding box for viewport bias
+ - components: Component filter (e.g., "postal_code:94043|country:US")
+```
+
+### 2. Search for Places
+Use `GOOGLE_MAPS_TEXT_SEARCH` to find places using a free-text query.
+```
+Tool: GOOGLE_MAPS_TEXT_SEARCH
+Parameters:
+ - textQuery (required): Search text (e.g., "restaurants in London")
+ - fieldMask: Fields to return (e.g., "displayName,formattedAddress,rating")
+ - maxResultCount: Max results (1-20, default 10)
+```
+
+### 3. Get Directions Between Two Locations
+Use `GOOGLE_MAPS_GET_ROUTE` to calculate routes with distance and duration.
+```
+Tool: GOOGLE_MAPS_GET_ROUTE
+Parameters:
+ - origin_address (required): Starting point (address or "lat,lng")
+ - destination_address (required): End point (address or "lat,lng")
+ - travelMode: DRIVE, BICYCLE, WALK, TWO_WHEELER, or TRANSIT
+ - routingPreference: TRAFFIC_UNAWARE, TRAFFIC_AWARE, TRAFFIC_AWARE_OPTIMAL
+ - computeAlternativeRoutes: Return alternative routes (boolean)
+ - units: METRIC or IMPERIAL
+ - languageCode: BCP-47 language code
+ - routeModifiers_avoidTolls / avoidHighways / avoidFerries: Route preferences
+```
+
+### 4. Compute Distance Matrix
+Use `GOOGLE_MAPS_COMPUTE_ROUTE_MATRIX` to calculate distances and durations between multiple origins and destinations.
+```
+Tool: GOOGLE_MAPS_COMPUTE_ROUTE_MATRIX
+Parameters:
+ - origins (required): Array of origin locations (address strings or lat/lng objects)
+ - destinations (required): Array of destination locations
+ - travelMode: DRIVE, BICYCLE, WALK, TWO_WHEELER, or TRANSIT
+ - routingPreference: TRAFFIC_UNAWARE, TRAFFIC_AWARE, TRAFFIC_AWARE_OPTIMAL
+ - fieldMask: Response fields to include
+ - units: METRIC or IMPERIAL
+```
+
+### 5. Get Place Details
+Use `GOOGLE_MAPS_GET_PLACE_DETAILS` to retrieve comprehensive information about a specific place.
+```
+Tool: GOOGLE_MAPS_GET_PLACE_DETAILS
+Description: Retrieves comprehensive details for a place using its resource
+ name (places/{place_id} format). Returns hours, contacts, reviews, etc.
+Note: Call RUBE_SEARCH_TOOLS to get the full schema for this tool.
+```
+
+### 6. Search Nearby Places
+Use `GOOGLE_MAPS_NEARBY_SEARCH` to find places within a circular area around a point.
+```
+Tool: GOOGLE_MAPS_NEARBY_SEARCH
+Parameters:
+ - latitude (required): Center latitude (-90 to 90)
+ - longitude (required): Center longitude (-180 to 180)
+ - radius (required): Search radius in meters (max 50000)
+ - includedTypes: Place types to include (e.g., ["restaurant", "cafe"])
+ - excludedTypes: Place types to exclude
+ - fieldMask: Fields to return
+ - maxResultCount: Max results (1-20)
+```
+
+## Common Patterns
+
+- **Geocode then route**: Use `GOOGLE_MAPS_GEOCODING_API` to convert addresses to coordinates, then `GOOGLE_MAPS_GET_ROUTE` for directions between them.
+- **Search then detail**: Use `GOOGLE_MAPS_TEXT_SEARCH` to find places, then `GOOGLE_MAPS_GET_PLACE_DETAILS` for richer metadata (hours, contacts, reviews).
+- **Autocomplete UX**: Use `GOOGLE_MAPS_AUTOCOMPLETE` for type-ahead search suggestions as users type addresses or place names.
+- **Reverse geocode**: Use `GOOGLE_MAPS_GEOCODE_LOCATION` to convert coordinates back to a human-readable address.
+- **Batch distance calculation**: Use `GOOGLE_MAPS_COMPUTE_ROUTE_MATRIX` for many-to-many distance calculations instead of calling `GOOGLE_MAPS_GET_ROUTE` repeatedly.
+- **Embed maps**: Use `GOOGLE_MAPS_MAPS_EMBED_API` to generate embeddable map URLs for places, directions, or search results.
+
+## Known Pitfalls
+
+- **Route matrix results structure**: `GOOGLE_MAPS_COMPUTE_ROUTE_MATRIX` returns results under `data.elements` with `originIndex` and `destinationIndex` plus `distanceMeters` and `duration` -- not a `routes[]` structure.
+- **Duration format**: `GOOGLE_MAPS_GET_ROUTE` returns durations as strings like `"937s"` inside `data.response_data.routes`. You must parse these before numeric comparisons.
+- **Place IDs for chaining**: Use place identifiers returned from `GOOGLE_MAPS_TEXT_SEARCH` when calling `GOOGLE_MAPS_GET_PLACE_DETAILS` for richer fields.
+- **Reverse geocoding input**: `GOOGLE_MAPS_GEOCODE_LOCATION` is coordinate-driven. Ensure you pass lat/lng (not an address string) to avoid mismatched lookups.
+- **Routing preference restrictions**: `routingPreference` cannot be set when `travelMode` is WALK, BICYCLE, or TRANSIT -- it must be omitted for these modes.
+- **Nearby search type validity**: `"food"` is NOT a valid type for `GOOGLE_MAPS_NEARBY_SEARCH` (it is Table B). Use specific types like `restaurant`, `cafe`, `bakery`, `fast_food_restaurant` instead.
+- **Embed API uses API keys only**: `GOOGLE_MAPS_MAPS_EMBED_API` requires an API key and does not support OAuth2.
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| Geocode address | `GOOGLE_MAPS_GEOCODING_API` | `address` or `latlng` or `place_id` |
+| Reverse geocode | `GOOGLE_MAPS_GEOCODE_LOCATION` | (see full schema via RUBE_SEARCH_TOOLS) |
+| Text search | `GOOGLE_MAPS_TEXT_SEARCH` | `textQuery`, `fieldMask`, `maxResultCount` |
+| Nearby search | `GOOGLE_MAPS_NEARBY_SEARCH` | `latitude`, `longitude`, `radius`, `includedTypes` |
+| Get directions | `GOOGLE_MAPS_GET_ROUTE` | `origin_address`, `destination_address`, `travelMode` |
+| Distance matrix | `GOOGLE_MAPS_COMPUTE_ROUTE_MATRIX` | `origins`, `destinations`, `travelMode` |
+| Place details | `GOOGLE_MAPS_GET_PLACE_DETAILS` | (see full schema via RUBE_SEARCH_TOOLS) |
+| Autocomplete | `GOOGLE_MAPS_AUTOCOMPLETE` | `input`, `includedRegionCodes`, `locationBias` |
+| Place photo | `GOOGLE_MAPS_PLACE_PHOTO` | (see full schema via RUBE_SEARCH_TOOLS) |
+| Embed map | `GOOGLE_MAPS_MAPS_EMBED_API` | `mode`, plus mode-specific params |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/google-search-console-automation/SKILL.md b/plugins/awesome-claude-skills/google-search-console-automation/SKILL.md
new file mode 100644
index 0000000..27e251f
--- /dev/null
+++ b/plugins/awesome-claude-skills/google-search-console-automation/SKILL.md
@@ -0,0 +1,123 @@
+---
+name: google-search-console-automation
+description: "Automate Google Search Console tasks via Rube MCP (Composio): query search analytics, list sites, inspect URLs, submit sitemaps, monitor search performance. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Search Console Automation via Rube MCP
+
+Query search analytics, inspect URLs, manage sitemaps, and monitor search performance using Google Search Console via Rube MCP (Composio).
+
+**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 connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_search_console`
+- Verified site ownership or appropriate permissions in 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
+
+## Core Workflows
+
+### 1. List All Verified Sites
+Use `GOOGLE_SEARCH_CONSOLE_LIST_SITES` to retrieve all sites the authenticated user owns or has access to.
+```
+Tool: GOOGLE_SEARCH_CONSOLE_LIST_SITES
+Parameters: (none required)
+Returns: List of site entries with siteUrl and permissionLevel
+```
+
+### 2. Query Search Analytics
+Use `GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY` to get search performance data including clicks, impressions, CTR, and position.
+```
+Tool: GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY
+Parameters:
+ - site_url (required): Site URL (e.g., "https://www.example.com/" or "sc-domain:example.com")
+ - start_date (required): Start date in YYYY-MM-DD format
+ - end_date (required): End date in YYYY-MM-DD format
+ - dimensions: Group by ["query", "page", "country", "device", "date", "searchAppearance"]
+ - search_type: "web" (default), "image", "video", "news", "discover", "googleNews"
+ - dimension_filter_groups: Filters for dimensions (operator: equals, notEquals, contains, notContains, includingRegex, excludingRegex)
+ - row_limit: Max rows (1-25000, default 1000)
+ - start_row: Pagination offset (default 0)
+ - aggregation_type: "auto", "byPage", "byProperty", "byNewsShowcasePanel"
+ - data_state: "final" (default), "all", "hourly_all"
+```
+
+### 3. Inspect a URL
+Use `GOOGLE_SEARCH_CONSOLE_INSPECT_URL` to check the indexing status and issues for a specific URL.
+```
+Tool: GOOGLE_SEARCH_CONSOLE_INSPECT_URL
+Parameters:
+ - inspection_url (required): Full URL to inspect (e.g., "https://www.example.com/page")
+ - site_url (required): Property URL (e.g., "https://www.example.com/")
+ - language_code: BCP-47 language (default: "en-US")
+```
+
+### 4. List Sitemaps
+Use `GOOGLE_SEARCH_CONSOLE_LIST_SITEMAPS` to retrieve all sitemaps submitted for a site.
+```
+Tool: GOOGLE_SEARCH_CONSOLE_LIST_SITEMAPS
+Parameters:
+ - site_url (required): Site URL (e.g., "https://www.example.com/")
+ - sitemap_index: Specific sitemap index URL to list sitemaps from
+```
+
+### 5. Submit a Sitemap
+Use `GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP` to register or resubmit a sitemap for indexing.
+```
+Tool: GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP
+Parameters:
+ - site_url (required): Site URL or domain property (e.g., "sc-domain:example.com")
+ - feedpath (required): Full sitemap URL (e.g., "https://www.example.com/sitemap.xml")
+```
+
+### 6. Get Sitemap Details
+Use `GOOGLE_SEARCH_CONSOLE_GET_SITEMAP` to retrieve information about a specific submitted sitemap.
+```
+Tool: GOOGLE_SEARCH_CONSOLE_GET_SITEMAP
+Parameters:
+ - site_url (required): Site URL
+ - feedpath (required): Sitemap URL to retrieve details for
+```
+
+## Common Patterns
+
+- **Performance monitoring**: Use `GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY` with `dimensions: ["date"]` over a date range to track daily search performance trends.
+- **Top queries report**: Use `GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY` with `dimensions: ["query"]` to find the most clicked search terms.
+- **Page-level analysis**: Use `dimensions: ["page"]` to identify top-performing pages, then `dimensions: ["query", "page"]` to see which queries drive traffic to each page.
+- **Indexing audit**: Use `GOOGLE_SEARCH_CONSOLE_INSPECT_URL` to check the indexing status of important pages.
+- **Sitemap management**: Use `GOOGLE_SEARCH_CONSOLE_LIST_SITEMAPS` to verify submitted sitemaps, then `GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP` to submit new or updated ones.
+- **Country/device breakdown**: Use `dimensions: ["country", "device"]` to understand geographic and device-type distribution of search traffic.
+- **Filter for specific queries**: Use `dimension_filter_groups` with `contains` or `includingRegex` operators to focus on specific keyword groups.
+
+## Known Pitfalls
+
+- **Site URL format matters**: URL-prefix properties use the full URL with protocol and trailing slash (e.g., `https://www.example.com/`). Domain properties use the `sc-domain:` prefix (e.g., `sc-domain:example.com`). Using the wrong format will return empty results or errors.
+- **Date range limits**: Data is typically available with a 2-3 day delay. `data_state: "all"` includes fresher data that may still change. `hourly_all` only works for dates within the last 3 days.
+- **Row limit pagination**: The API returns top results sorted by clicks (or by date when grouping by date). For complete data, paginate using `start_row` with the `row_limit`.
+- **Max 25,000 rows per request**: Even with pagination, each request returns at most 25,000 rows. For very large datasets, narrow your date range or add dimension filters.
+- **Inspection URL must match site**: The `inspection_url` must be a page under the `site_url` property. Cross-property inspections will fail.
+- **Sitemap must be accessible**: `GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP` requires the sitemap file to be publicly accessible at the specified URL and properly formatted as XML.
+- **Results sorted by clicks**: By default, analytics results are sorted by click count descending, except when grouping by `date` (which sorts by date ascending).
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| List sites | `GOOGLE_SEARCH_CONSOLE_LIST_SITES` | (none) |
+| Search analytics | `GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY` | `site_url`, `start_date`, `end_date`, `dimensions` |
+| Inspect URL | `GOOGLE_SEARCH_CONSOLE_INSPECT_URL` | `inspection_url`, `site_url` |
+| List sitemaps | `GOOGLE_SEARCH_CONSOLE_LIST_SITEMAPS` | `site_url` |
+| Submit sitemap | `GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP` | `site_url`, `feedpath` |
+| Get sitemap info | `GOOGLE_SEARCH_CONSOLE_GET_SITEMAP` | `site_url`, `feedpath` |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/google_admin-automation/SKILL.md b/plugins/awesome-claude-skills/google_admin-automation/SKILL.md
new file mode 100644
index 0000000..4e0cf23
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/google_classroom-automation/SKILL.md b/plugins/awesome-claude-skills/google_classroom-automation/SKILL.md
new file mode 100644
index 0000000..0c42f54
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/google_maps-automation/SKILL.md b/plugins/awesome-claude-skills/google_maps-automation/SKILL.md
new file mode 100644
index 0000000..a2f4d51
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/google_search_console-automation/SKILL.md b/plugins/awesome-claude-skills/google_search_console-automation/SKILL.md
new file mode 100644
index 0000000..d383af6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/googleads-automation/SKILL.md b/plugins/awesome-claude-skills/googleads-automation/SKILL.md
new file mode 100644
index 0000000..059ed03
--- /dev/null
+++ b/plugins/awesome-claude-skills/googleads-automation/SKILL.md
@@ -0,0 +1,124 @@
+---
+name: googleads-automation
+description: "Automate Google Ads analytics tasks via Rube MCP (Composio): list Google Ads links, run GA4 reports, check compatibility, list properties and accounts. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Ads Automation via Rube MCP
+
+Access Google Ads data through Google Analytics integration, run performance reports, list linked Ads accounts, and analyze campaign metrics using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/googleads](https://composio.dev/toolkits/googleads)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_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 `google_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
+
+> **Note**: Google Ads data is accessed through the Google Analytics toolkit integration. The tools below use GA4 properties linked to Google Ads accounts.
+
+## Core Workflows
+
+### 1. List Google Ads Links for a Property
+Use `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_GOOGLE_ADS` to retrieve all Google Ads account links configured for a GA4 property.
+```
+Tool: GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_GOOGLE_ADS
+Parameters:
+ - parent (required): Property resource name (format: "properties/{propertyId}")
+ - pageSize: Max results (1-200, default 50)
+ - pageToken: Pagination token
+```
+
+### 2. Run a GA4 Performance Report
+Use `GOOGLE_ANALYTICS_RUN_REPORT` to run customized reports with dimensions, metrics, date ranges, and filters.
+```
+Tool: GOOGLE_ANALYTICS_RUN_REPORT
+Parameters:
+ - property (required): Property resource (format: "properties/{property_id}")
+ - dimensions: Array of dimension objects (e.g., [{"name": "sessionCampaignName"}, {"name": "date"}])
+ - metrics: Array of metric objects (e.g., [{"name": "sessions"}, {"name": "totalRevenue"}])
+ - dateRanges: Array with startDate and endDate (e.g., [{"startDate": "2025-01-01", "endDate": "2025-01-31"}])
+ - dimensionFilter: Filter by dimension values
+ - metricFilter: Filter by metric values (applied after aggregation)
+ - orderBys: Sort results
+ - limit: Max rows to return (1-250000)
+```
+
+### 3. Check Dimension/Metric Compatibility
+Use `GOOGLE_ANALYTICS_CHECK_COMPATIBILITY` to validate dimension and metric combinations before running a report.
+```
+Tool: GOOGLE_ANALYTICS_CHECK_COMPATIBILITY
+Description: Validates compatibility of chosen dimensions or metrics
+ before running a report.
+Note: Call RUBE_SEARCH_TOOLS to get the full schema for this tool.
+```
+
+### 4. List GA4 Accounts
+Use `GOOGLE_ANALYTICS_LIST_ACCOUNTS` to enumerate all accessible Google Analytics accounts.
+```
+Tool: GOOGLE_ANALYTICS_LIST_ACCOUNTS
+Parameters:
+ - pageSize: Max accounts to return
+ - pageToken: Pagination token
+ - showDeleted: Include soft-deleted accounts
+```
+
+### 5. List GA4 Properties Under an Account
+Use `GOOGLE_ANALYTICS_LIST_PROPERTIES` to list properties for a specific GA4 account.
+```
+Tool: GOOGLE_ANALYTICS_LIST_PROPERTIES
+Parameters:
+ - account (required): Account resource name (format: "accounts/{account_id}")
+ - pageSize: Max properties (1-200)
+ - pageToken: Pagination token
+ - showDeleted: Include trashed properties
+```
+
+### 6. Get Available Dimensions and Metrics
+Use `GOOGLE_ANALYTICS_GET_METADATA` to discover all available fields for building reports.
+```
+Tool: GOOGLE_ANALYTICS_GET_METADATA
+Description: Gets metadata for dimensions, metrics, and comparisons
+ for a GA4 property.
+Note: Call RUBE_SEARCH_TOOLS to get the full schema for this tool.
+```
+
+## Common Patterns
+
+- **Discover then report**: Use `GOOGLE_ANALYTICS_LIST_ACCOUNTS` to find account IDs, then `GOOGLE_ANALYTICS_LIST_PROPERTIES` to find property IDs, then `GOOGLE_ANALYTICS_RUN_REPORT` to pull data.
+- **Validate before querying**: Use `GOOGLE_ANALYTICS_CHECK_COMPATIBILITY` to validate dimension/metric combinations before running reports to avoid 400 errors.
+- **Campaign performance**: Run reports with dimensions like `sessionCampaignName`, `sessionSource`, `sessionMedium` and metrics like `sessions`, `activeUsers`, `totalRevenue`.
+- **Ads link discovery**: Use `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_GOOGLE_ADS` to find which Google Ads accounts are linked to each GA4 property.
+- **Field discovery**: Use `GOOGLE_ANALYTICS_GET_METADATA` to list all available dimensions and metrics before constructing complex reports.
+
+## Known Pitfalls
+
+- **Dimension/metric compatibility**: The GA4 API has strict compatibility rules. Not all dimensions can be combined with all metrics. Demographic dimensions (e.g., `userAgeBracket`, `userGender`) are often incompatible with session-scoped dimensions/filters (e.g., `sessionCampaignName`, `sessionSource`).
+- **`dateRange` is NOT a dimension**: Do not include `dateRange` in the dimensions array. Use `date`, `dateHour`, `year`, `month`, or `week` instead.
+- **`exits` is NOT valid**: Neither `exits` as a dimension nor as a metric is valid in GA4.
+- **Property ID format**: Must be `properties/{numeric_id}` (e.g., `properties/123456789`). Do not use Google Account IDs (long OAuth IDs).
+- **Account ID format**: Must be `accounts/{numeric_id}` where the numeric ID is 6-10 digits.
+- **Filter separation**: Use `dimensionFilter` only for dimension fields and `metricFilter` only for metric fields. Mixing them will cause errors.
+- **Max 9 dimensions and 10 metrics** per report request.
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| List Ads links | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_GOOGLE_ADS` | `parent` |
+| Run report | `GOOGLE_ANALYTICS_RUN_REPORT` | `property`, `dimensions`, `metrics`, `dateRanges` |
+| Check compatibility | `GOOGLE_ANALYTICS_CHECK_COMPATIBILITY` | (see full schema via RUBE_SEARCH_TOOLS) |
+| List accounts | `GOOGLE_ANALYTICS_LIST_ACCOUNTS` | `pageSize` |
+| List properties | `GOOGLE_ANALYTICS_LIST_PROPERTIES` | `account`, `pageSize` |
+| Get metadata | `GOOGLE_ANALYTICS_GET_METADATA` | (see full schema via RUBE_SEARCH_TOOLS) |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/googlebigquery-automation/SKILL.md b/plugins/awesome-claude-skills/googlebigquery-automation/SKILL.md
new file mode 100644
index 0000000..2ed0cc4
--- /dev/null
+++ b/plugins/awesome-claude-skills/googlebigquery-automation/SKILL.md
@@ -0,0 +1,128 @@
+---
+name: googlebigquery-automation
+description: "Automate Google BigQuery tasks via Rube MCP (Composio): run SQL queries, explore datasets and metadata, execute MBQL queries via Metabase integration. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google BigQuery Automation via Rube MCP
+
+Run SQL queries, explore database schemas, and analyze datasets through the Metabase integration using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/googlebigquery](https://composio.dev/toolkits/googlebigquery)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `metabase`
+- A Metabase instance connected to your BigQuery data source
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `metabase`
+3. If connection is not ACTIVE, follow the returned auth link to complete setup
+4. Confirm connection status shows ACTIVE before running any workflows
+
+> **Note**: BigQuery data is accessed through Metabase, a business intelligence tool that connects to BigQuery as a data source. The tools below execute queries and retrieve metadata through Metabase's API.
+
+## Core Workflows
+
+### 1. Run a Native SQL Query
+Use `METABASE_POST_API_DATASET` with type `native` to execute raw SQL queries against your BigQuery database.
+```
+Tool: METABASE_POST_API_DATASET
+Parameters:
+ - database (required): Metabase database ID (integer)
+ - type (required): "native" for SQL queries
+ - native (required): Object with "query" string
+ - query: Raw SQL string (e.g., "SELECT * FROM users LIMIT 10")
+ - template_tags: Parameterized query variables (optional)
+ - constraints: { "max-results": 1000 } (optional)
+```
+
+### 2. Run a Structured MBQL Query
+Use `METABASE_POST_API_DATASET` with type `query` for Metabase Query Language queries with built-in aggregation and filtering.
+```
+Tool: METABASE_POST_API_DATASET
+Parameters:
+ - database (required): Metabase database ID
+ - type (required): "query" for MBQL
+ - query (required): Object with:
+ - source-table: Table ID (integer)
+ - aggregation: e.g., [["count"]] or [["sum", ["field", 5, null]]]
+ - breakout: Group-by fields
+ - filter: Filter conditions
+ - limit: Max rows
+ - order-by: Sort fields
+```
+
+### 3. Get Query Metadata
+Use `METABASE_POST_API_DATASET_QUERY_METADATA` to retrieve metadata about databases, tables, and fields available for querying.
+```
+Tool: METABASE_POST_API_DATASET_QUERY_METADATA
+Parameters:
+ - database (required): Metabase database ID
+ - type (required): "query" or "native"
+ - query (required): Query object (e.g., {"source-table": 1})
+```
+
+### 4. Convert Query to Native SQL
+Use `METABASE_POST_API_DATASET_NATIVE` to convert an MBQL query into its native SQL representation.
+```
+Tool: METABASE_POST_API_DATASET_NATIVE
+Parameters:
+ - database (required): Metabase database ID
+ - type (required): "native"
+ - native (required): Object with "query" and optional "template_tags"
+ - parameters: Query parameter values (optional)
+```
+
+### 5. List Available Databases
+Use `METABASE_GET_API_DATABASE` to discover all database connections configured in Metabase.
+```
+Tool: METABASE_GET_API_DATABASE
+Description: Retrieves a list of all Database instances configured in Metabase.
+Note: Call RUBE_SEARCH_TOOLS to get the full schema for this tool.
+```
+
+### 6. Get Database Schema Metadata
+Use `METABASE_GET_API_DATABASE_ID_METADATA` to retrieve complete table and field information for a specific database.
+```
+Tool: METABASE_GET_API_DATABASE_ID_METADATA
+Description: Retrieves complete metadata for a specific database including
+ all tables and fields.
+Note: Call RUBE_SEARCH_TOOLS to get the full schema for this tool.
+```
+
+## Common Patterns
+
+- **Discover then query**: Use `METABASE_GET_API_DATABASE` to find database IDs, then `METABASE_GET_API_DATABASE_ID_METADATA` to explore tables and fields, then `METABASE_POST_API_DATASET` to run queries.
+- **SQL-first approach**: Use `METABASE_POST_API_DATASET` with `type: "native"` and write standard SQL queries for maximum flexibility.
+- **Parameterized queries**: Use `template_tags` in native queries for safe parameterization (e.g., `SELECT * FROM users WHERE id = {{user_id}}`).
+- **Schema exploration**: Use `METABASE_POST_API_DATASET_QUERY_METADATA` to understand table structures before building complex queries.
+- **Get parameter values**: Use `METABASE_POST_API_DATASET_PARAMETER_VALUES` to retrieve possible values for filter dropdowns.
+
+## Known Pitfalls
+
+- The `database` parameter is a Metabase-internal **integer ID**, not the BigQuery project or dataset name. Use `METABASE_GET_API_DATABASE` to find valid database IDs first.
+- `source-table` in MBQL queries is also a Metabase-internal integer, not the BigQuery table name. Discover table IDs via metadata tools.
+- Native SQL queries use BigQuery SQL dialect (Standard SQL). Ensure your syntax is BigQuery-compatible.
+- `max-results` in constraints defaults can limit returned rows. Set explicitly for large result sets.
+- Responses from `METABASE_POST_API_DATASET` contain results nested under `data` -- parse carefully as the structure may be deeply nested.
+- Metabase field IDs used in MBQL `aggregation`, `breakout`, and `filter` arrays must be integers obtained from metadata responses.
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| Run SQL query | `METABASE_POST_API_DATASET` | `database`, `type: "native"`, `native.query` |
+| Run MBQL query | `METABASE_POST_API_DATASET` | `database`, `type: "query"`, `query` |
+| Get query metadata | `METABASE_POST_API_DATASET_QUERY_METADATA` | `database`, `type`, `query` |
+| Convert to SQL | `METABASE_POST_API_DATASET_NATIVE` | `database`, `type`, `native` |
+| Get parameter values | `METABASE_POST_API_DATASET_PARAMETER_VALUES` | `parameter`, `field_ids` |
+| List databases | `METABASE_GET_API_DATABASE` | (see full schema via RUBE_SEARCH_TOOLS) |
+| Get database metadata | `METABASE_GET_API_DATABASE_ID_METADATA` | (see full schema via RUBE_SEARCH_TOOLS) |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/googlecalendar-automation/SKILL.md b/plugins/awesome-claude-skills/googlecalendar-automation/SKILL.md
new file mode 100644
index 0000000..f12a0fb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/googledocs-automation/SKILL.md b/plugins/awesome-claude-skills/googledocs-automation/SKILL.md
new file mode 100644
index 0000000..4059be9
--- /dev/null
+++ b/plugins/awesome-claude-skills/googledocs-automation/SKILL.md
@@ -0,0 +1,124 @@
+---
+name: googledocs-automation
+description: "Automate Google Docs tasks via Rube MCP (Composio): create, edit, search, export, copy, and update documents. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Docs Automation via Rube MCP
+
+Create, edit, search, export, and manage Google Docs documents programmatically using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/googledocs](https://composio.dev/toolkits/googledocs)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active 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
+
+## Core Workflows
+
+### 1. Create a New Document
+Use `GOOGLEDOCS_CREATE_DOCUMENT` to create a new Google Doc with a title and initial text content.
+```
+Tool: GOOGLEDOCS_CREATE_DOCUMENT
+Parameters:
+ - title (required): Document filename/title
+ - text (required): Initial text content to insert into the document
+```
+
+### 2. Search for Documents
+Use `GOOGLEDOCS_SEARCH_DOCUMENTS` to find Google Docs by name, content, date, or sharing status.
+```
+Tool: GOOGLEDOCS_SEARCH_DOCUMENTS
+Parameters:
+ - query: Search query string
+ - max_results: Limit number of results
+ - modified_after / created_after: Filter by date
+ - shared_with_me: Filter shared documents
+ - starred_only: Filter starred documents
+ - include_shared_drives: Search shared drives
+ - order_by: Sort results
+ - page_token: Pagination token
+```
+
+### 3. Update Document Content with Markdown
+Use `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` to replace the entire content of a document with Markdown-formatted text.
+```
+Tool: GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN
+Parameters:
+ - id (required): Document ID
+ - markdown (required): Markdown content to replace entire document body
+```
+
+### 4. Find and Replace Text
+Use `GOOGLEDOCS_REPLACE_ALL_TEXT` to replace all occurrences of a string in a document.
+```
+Tool: GOOGLEDOCS_REPLACE_ALL_TEXT
+Parameters:
+ - document_id (required): Target document ID
+ - find_text (required): Text to search for
+ - replace_text (required): Replacement text
+ - match_case: Case-sensitive matching (boolean)
+ - search_by_regex: Use regex for find_text
+ - tab_ids: Specific tabs to search
+```
+
+### 5. Export Document as PDF
+Use `GOOGLEDOCS_EXPORT_DOCUMENT_AS_PDF` to export a Google Doc to PDF format.
+```
+Tool: GOOGLEDOCS_EXPORT_DOCUMENT_AS_PDF
+Parameters:
+ - file_id (required): Document file ID
+ - filename: Output PDF filename
+```
+
+### 6. Copy a Document
+Use `GOOGLEDOCS_COPY_DOCUMENT` to duplicate an existing Google Doc.
+```
+Tool: GOOGLEDOCS_COPY_DOCUMENT
+Parameters:
+ - document_id (required): Source document ID to copy
+ - title: Title for the new copy
+ - include_shared_drives: Search shared drives for the source
+```
+
+## Common Patterns
+
+- **Search then edit**: Use `GOOGLEDOCS_SEARCH_DOCUMENTS` to find a document by name, then use the returned document ID with `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` or `GOOGLEDOCS_REPLACE_ALL_TEXT` to modify it.
+- **Create from template**: Use `GOOGLEDOCS_COPY_DOCUMENT` to duplicate a template, then `GOOGLEDOCS_REPLACE_ALL_TEXT` to fill in placeholder text.
+- **Retrieve then update**: Use `GOOGLEDOCS_GET_DOCUMENT_BY_ID` to read current content, then apply edits with `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT`.
+- **Batch text insertion**: Use `GOOGLEDOCS_INSERT_TEXT_ACTION` to insert text at specific positions (by index) or append to the end of a document.
+- **Share documents**: Combine with `GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE` (googledrive toolkit) to share documents after creation.
+
+## Known Pitfalls
+
+- `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` replaces the **entire** document content -- it does not append. Use it for full rewrites only.
+- `GOOGLEDOCS_INSERT_TEXT_ACTION` requires a precise `insertion_index` (character position). Set `append_to_end: true` to safely add text at the end.
+- `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT` requires constructing an `editDocs` request body with raw Google Docs API batch update requests -- consult the API documentation for the correct structure.
+- Document IDs and file IDs are the same value for Google Docs, but parameter names differ across tools (`id`, `document_id`, `file_id`).
+- `GOOGLEDOCS_SEARCH_DOCUMENTS` uses Google Drive search syntax for the `query` parameter (e.g., `name contains 'report'`).
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| Create document | `GOOGLEDOCS_CREATE_DOCUMENT` | `title`, `text` |
+| Search documents | `GOOGLEDOCS_SEARCH_DOCUMENTS` | `query`, `max_results`, `modified_after` |
+| Get document by ID | `GOOGLEDOCS_GET_DOCUMENT_BY_ID` | `id` |
+| Update with Markdown | `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` | `id`, `markdown` |
+| Programmatic edits | `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT` | `document_id`, `editDocs` |
+| Insert text | `GOOGLEDOCS_INSERT_TEXT_ACTION` | `document_id`, `text_to_insert`, `insertion_index` |
+| Find and replace | `GOOGLEDOCS_REPLACE_ALL_TEXT` | `document_id`, `find_text`, `replace_text` |
+| Export as PDF | `GOOGLEDOCS_EXPORT_DOCUMENT_AS_PDF` | `file_id`, `filename` |
+| Copy document | `GOOGLEDOCS_COPY_DOCUMENT` | `document_id`, `title` |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/googledrive-automation/SKILL.md b/plugins/awesome-claude-skills/googledrive-automation/SKILL.md
new file mode 100644
index 0000000..88df43c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/googlemeet-automation/SKILL.md b/plugins/awesome-claude-skills/googlemeet-automation/SKILL.md
new file mode 100644
index 0000000..cb9a27d
--- /dev/null
+++ b/plugins/awesome-claude-skills/googlemeet-automation/SKILL.md
@@ -0,0 +1,108 @@
+---
+name: googlemeet-automation
+description: "Automate Google Meet tasks via Rube MCP (Composio): create Meet spaces, schedule video conferences via Calendar events, manage meeting access. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Meet Automation via Rube MCP
+
+Create Google Meet video conferences, schedule meetings with Meet links, and manage meeting spaces using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/googlemeet](https://composio.dev/toolkits/googlemeet)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlemeet`
+- For scheduling meetings with attendees, also connect the `googlecalendar` toolkit
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add 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. Optionally also connect `googlecalendar` for scheduling meetings with calendar events
+4. If connection is not ACTIVE, follow the returned auth link to complete setup
+5. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create a Standalone Meet Space
+Use `GOOGLEMEET_CREATE_MEET` to create a new Google Meet meeting space with optional access configuration.
+```
+Tool: GOOGLEMEET_CREATE_MEET
+Description: Creates a new Google Meet space, optionally configuring
+ its access type and entry points.
+Note: Call RUBE_SEARCH_TOOLS to get the full schema for this tool.
+```
+
+### 2. Schedule a Meeting with Google Meet Link
+Use `GOOGLECALENDAR_CREATE_EVENT` to create a calendar event that automatically generates a Google Meet link (enabled by default).
+```
+Tool: GOOGLECALENDAR_CREATE_EVENT
+Parameters:
+ - start_datetime (required): ISO 8601 format (e.g., "2025-01-16T13:00:00")
+ - summary: Meeting title
+ - attendees: List of email addresses
+ - timezone: IANA timezone (e.g., "America/New_York")
+ - event_duration_hour: Duration hours (default: 0)
+ - event_duration_minutes: Duration minutes (default: 30, max: 59)
+ - create_meeting_room: true (default) -- generates Meet link
+ - description: Meeting agenda/notes
+ - location: Physical or virtual location
+```
+
+### 3. Find Available Time Slots
+Use `GOOGLECALENDAR_FIND_FREE_SLOTS` before scheduling to find when participants are available.
+```
+Tool: GOOGLECALENDAR_FIND_FREE_SLOTS
+Parameters:
+ - items: List of calendar IDs to check (e.g., ["primary", "user@example.com"])
+ - time_min: Start of time window (ISO format)
+ - time_max: End of time window (ISO format)
+ - timezone: IANA timezone
+```
+
+### 4. Update an Existing Meeting
+Use `GOOGLECALENDAR_PATCH_EVENT` to modify meeting details, reschedule, or update attendees.
+```
+Tool: GOOGLECALENDAR_PATCH_EVENT
+Parameters:
+ - calendar_id (required): Calendar ID (use "primary")
+ - event_id (required): Event ID (from search/list)
+ - summary: Updated title
+ - start_time / end_time: Rescheduled times
+ - attendees: Updated attendee list (replaces existing)
+ - send_updates: Notification preference ("all", "externalOnly", "none")
+```
+
+## Common Patterns
+
+- **Quick meeting link**: Use `GOOGLEMEET_CREATE_MEET` for an instant meeting space without a calendar event.
+- **Scheduled meeting with attendees**: Use `GOOGLECALENDAR_CREATE_EVENT` with `create_meeting_room: true` (default) to create a calendar event with an embedded Meet link. Workspace accounts get a Meet link automatically.
+- **Check availability first**: Use `GOOGLECALENDAR_FIND_FREE_SLOTS` to find open time slots before scheduling with `GOOGLECALENDAR_CREATE_EVENT`.
+- **Resolve names to emails**: Use `GMAIL_SEARCH_PEOPLE` (gmail toolkit) to look up email addresses from names before adding attendees.
+- **Get current time**: Use `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` with a timezone to get the current date/time for scheduling relative to "now".
+
+## Known Pitfalls
+
+- **Attendees must be email addresses**: `GOOGLECALENDAR_CREATE_EVENT` only accepts email addresses for attendees, not names. Use `GMAIL_SEARCH_PEOPLE` to resolve names to emails first.
+- **Personal Gmail vs Workspace**: The `create_meeting_room` feature works best with Google Workspace accounts. Personal Gmail accounts will gracefully fallback to creating an event without a Meet link.
+- **start_datetime format**: Must be exact ISO 8601 (e.g., `2025-01-16T13:00:00`). Natural language like "tomorrow at 3pm" is NOT supported.
+- **Duration limits**: `event_duration_minutes` max is 59. For 1+ hour meetings, use `event_duration_hour` combined with `event_duration_minutes`.
+- **Timezone is critical**: Always provide `timezone` as a valid IANA identifier (e.g., `America/New_York`). Abbreviations like "EST" or "PST" are NOT valid.
+- **Event IDs are opaque**: To update or delete events, you must first retrieve the event ID using a search or list tool.
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| Create Meet space | `GOOGLEMEET_CREATE_MEET` | (see full schema via RUBE_SEARCH_TOOLS) |
+| Schedule meeting | `GOOGLECALENDAR_CREATE_EVENT` | `start_datetime`, `summary`, `attendees`, `timezone` |
+| Find free slots | `GOOGLECALENDAR_FIND_FREE_SLOTS` | `items`, `time_min`, `time_max`, `timezone` |
+| Update meeting | `GOOGLECALENDAR_PATCH_EVENT` | `calendar_id`, `event_id`, `summary`, `start_time` |
+| Get current time | `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` | `timezone` |
+| Look up contacts | `GMAIL_SEARCH_PEOPLE` | `query` |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/googlephotos-automation/SKILL.md b/plugins/awesome-claude-skills/googlephotos-automation/SKILL.md
new file mode 100644
index 0000000..d726a98
--- /dev/null
+++ b/plugins/awesome-claude-skills/googlephotos-automation/SKILL.md
@@ -0,0 +1,124 @@
+---
+name: googlephotos-automation
+description: "Automate Google Photos tasks via Rube MCP (Composio): upload media, manage albums, search photos, batch add items, create and update albums. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Photos Automation via Rube MCP
+
+Upload photos, manage albums, search media items, and batch-organize content in Google Photos using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/googlephotos](https://composio.dev/toolkits/googlephotos)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active 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
+
+## Core Workflows
+
+### 1. List Albums
+Use `GOOGLEPHOTOS_LIST_ALBUMS` to retrieve all albums visible in the user's Albums tab.
+```
+Tool: GOOGLEPHOTOS_LIST_ALBUMS
+Parameters:
+ - pageSize: Number of albums per page
+ - pageToken: Pagination token
+ - excludeNonAppCreatedData: Only show albums created by this app
+```
+
+### 2. Create a New Album
+Use `GOOGLEPHOTOS_CREATE_ALBUM` to create a new album in Google Photos.
+```
+Tool: GOOGLEPHOTOS_CREATE_ALBUM
+Parameters:
+ - title (required): Album title
+```
+
+### 3. Upload Media
+Use `GOOGLEPHOTOS_UPLOAD_MEDIA` to upload an image or video file to Google Photos.
+```
+Tool: GOOGLEPHOTOS_UPLOAD_MEDIA
+Parameters:
+ - file_to_upload: Local file path to upload
+ - url: URL of file to upload (alternative to file_to_upload)
+ - file_name: Name for the uploaded file
+ - description: Description/caption for the media item
+```
+
+### 4. Batch Upload and Create Media Items
+Use `GOOGLEPHOTOS_BATCH_CREATE_MEDIA_ITEMS` to upload multiple files and create media items in one operation.
+```
+Tool: GOOGLEPHOTOS_BATCH_CREATE_MEDIA_ITEMS
+Parameters:
+ - files: Local file paths to upload
+ - urls: URLs of files to upload
+ - media_files: Mixed input (files and URLs)
+ - albumId: Album to add items to
+ - albumPosition: Position within the album
+```
+
+### 5. Search Media Items
+Use `GOOGLEPHOTOS_SEARCH_MEDIA_ITEMS` to search the user's photo library with filters.
+```
+Tool: GOOGLEPHOTOS_SEARCH_MEDIA_ITEMS
+Parameters:
+ - albumId: Filter by album
+ - filters: Search filters (date ranges, content categories, media types)
+ - orderBy: Sort order
+ - pageSize: Results per page
+ - pageToken: Pagination token
+```
+
+### 6. Add Items to an Album
+Use `GOOGLEPHOTOS_BATCH_ADD_MEDIA_ITEMS` to add existing media items to an album.
+```
+Tool: GOOGLEPHOTOS_BATCH_ADD_MEDIA_ITEMS
+Parameters:
+ - albumId (required): Target album ID
+ - mediaItemIds (required): Array of media item IDs to add
+```
+
+## Common Patterns
+
+- **Create album then upload**: Use `GOOGLEPHOTOS_CREATE_ALBUM` to create an album, then `GOOGLEPHOTOS_BATCH_CREATE_MEDIA_ITEMS` with the album ID to upload and organize photos in one step.
+- **List then organize**: Use `GOOGLEPHOTOS_SEARCH_MEDIA_ITEMS` or `GOOGLEPHOTOS_LIST_MEDIA_ITEMS` to find media item IDs, then `GOOGLEPHOTOS_BATCH_ADD_MEDIA_ITEMS` to add them to albums.
+- **Update album metadata**: Use `GOOGLEPHOTOS_UPDATE_ALBUM` to change an album's title or cover photo.
+- **Get album details**: Use `GOOGLEPHOTOS_GET_ALBUM` with an album ID to retrieve full album information.
+- **Add enrichments**: Use `GOOGLEPHOTOS_ADD_ENRICHMENT` to add text overlays, locations, or map enrichments to album positions.
+- **Upload from URLs**: Use the `url` parameter in `GOOGLEPHOTOS_UPLOAD_MEDIA` or `urls` in `GOOGLEPHOTOS_BATCH_CREATE_MEDIA_ITEMS` to upload images directly from web URLs.
+
+## Known Pitfalls
+
+- `GOOGLEPHOTOS_LIST_MEDIA_ITEMS` is **deprecated** -- prefer `GOOGLEPHOTOS_SEARCH_MEDIA_ITEMS` for listing and filtering media.
+- `GOOGLEPHOTOS_UPLOAD_MEDIA` supports images up to **200MB** and videos up to a larger limit. Exceeding these will fail.
+- Album IDs must be obtained from `GOOGLEPHOTOS_LIST_ALBUMS` or `GOOGLEPHOTOS_CREATE_ALBUM` responses -- they are opaque strings.
+- `GOOGLEPHOTOS_BATCH_ADD_MEDIA_ITEMS` can only add items to albums **created by the app** or albums the user owns.
+- The `filters` parameter in `GOOGLEPHOTOS_SEARCH_MEDIA_ITEMS` uses a specific Google Photos API filter structure -- consult the schema for date range and content category formats.
+- Media items created via the API may not immediately appear in the Google Photos web UI due to processing delays.
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| List albums | `GOOGLEPHOTOS_LIST_ALBUMS` | `pageSize`, `pageToken` |
+| Create album | `GOOGLEPHOTOS_CREATE_ALBUM` | `title` |
+| Get album | `GOOGLEPHOTOS_GET_ALBUM` | `albumId` |
+| Update album | `GOOGLEPHOTOS_UPDATE_ALBUM` | `albumId`, `title`, `coverPhotoMediaItemId` |
+| Upload media | `GOOGLEPHOTOS_UPLOAD_MEDIA` | `file_to_upload` or `url`, `description` |
+| Batch upload | `GOOGLEPHOTOS_BATCH_CREATE_MEDIA_ITEMS` | `files` or `urls`, `albumId` |
+| Search media | `GOOGLEPHOTOS_SEARCH_MEDIA_ITEMS` | `albumId`, `filters`, `pageSize` |
+| List media items | `GOOGLEPHOTOS_LIST_MEDIA_ITEMS` | `pageSize`, `pageToken` |
+| Add items to album | `GOOGLEPHOTOS_BATCH_ADD_MEDIA_ITEMS` | `albumId`, `mediaItemIds` |
+| Add enrichment | `GOOGLEPHOTOS_ADD_ENRICHMENT` | `albumId`, `newEnrichmentItem`, `albumPosition` |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/googlesheets-automation/SKILL.md b/plugins/awesome-claude-skills/googlesheets-automation/SKILL.md
new file mode 100644
index 0000000..0d83b3a
--- /dev/null
+++ b/plugins/awesome-claude-skills/googlesheets-automation/SKILL.md
@@ -0,0 +1,202 @@
+---
+name: googlesheets-automation
+description: Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.
+requires:
+ mcp: [rube]
+---
+
+# Google Sheets Automation via Rube MCP
+
+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)
+- Active Google Sheets connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googlesheets`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlesheets`
+3. If connection is not ACTIVE, follow the returned auth link to complete Google OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Read and Write Data
+
+**When to use**: User wants to read data from or write data to a Google Sheet
+
+**Tool sequence**:
+1. `GOOGLESHEETS_SEARCH_SPREADSHEETS` - Find spreadsheet by name if ID unknown [Prerequisite]
+2. `GOOGLESHEETS_GET_SHEET_NAMES` - Enumerate tab names to target the right sheet [Prerequisite]
+3. `GOOGLESHEETS_BATCH_GET` - Read data from one or more ranges [Required]
+4. `GOOGLESHEETS_BATCH_UPDATE` - Write data to a range or append rows [Required]
+5. `GOOGLESHEETS_VALUES_UPDATE` - Update a single specific range [Alternative]
+6. `GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND` - Append rows to end of table [Alternative]
+
+**Key parameters**:
+- `spreadsheet_id`: Alphanumeric ID from the spreadsheet URL (between '/d/' and '/edit')
+- `ranges`: A1 notation array (e.g., 'Sheet1!A1:Z1000'); always use bounded ranges
+- `sheet_name`: Tab name (case-insensitive matching supported)
+- `values`: 2D array where each inner array is a row
+- `first_cell_location`: Starting cell in A1 notation (omit to append)
+- `valueInputOption`: 'USER_ENTERED' (parsed) or 'RAW' (literal)
+
+**Pitfalls**:
+- Mis-cased or non-existent tab names error "Sheet 'X' not found"
+- Empty ranges may omit `valueRanges[i].values`; treat missing as empty array
+- `GOOGLESHEETS_BATCH_UPDATE` values must be a 2D array (list of lists), even for a single row
+- Unbounded ranges like 'A:Z' on sheets with >10,000 rows may cause timeouts; always bound with row limits
+- Append follows the detected `tableRange`; use returned `updatedRange` to verify placement
+
+### 2. Create and Manage Spreadsheets
+
+**When to use**: User wants to create a new spreadsheet or manage tabs within one
+
+**Tool sequence**:
+1. `GOOGLESHEETS_CREATE_GOOGLE_SHEET1` - Create a new spreadsheet [Required]
+2. `GOOGLESHEETS_ADD_SHEET` - Add a new tab/worksheet [Required]
+3. `GOOGLESHEETS_UPDATE_SHEET_PROPERTIES` - Rename, hide, reorder, or color tabs [Optional]
+4. `GOOGLESHEETS_GET_SPREADSHEET_INFO` - Get full spreadsheet metadata [Optional]
+5. `GOOGLESHEETS_FIND_WORKSHEET_BY_TITLE` - Check if a specific tab exists [Optional]
+
+**Key parameters**:
+- `title`: Spreadsheet or sheet tab name
+- `spreadsheetId`: Target spreadsheet ID
+- `forceUnique`: Auto-append suffix if tab name exists (default true)
+- `properties.gridProperties`: Set row/column counts, frozen rows
+
+**Pitfalls**:
+- Sheet names must be unique within a spreadsheet
+- Default sheet names are locale-dependent ('Sheet1' in English, 'Hoja 1' in Spanish)
+- Don't use `index` when creating multiple sheets in parallel (causes 'index too high' errors)
+- `GOOGLESHEETS_GET_SPREADSHEET_INFO` can return 403 if account lacks access
+
+### 3. Search and Filter Rows
+
+**When to use**: User wants to find specific rows or apply filters to sheet data
+
+**Tool sequence**:
+1. `GOOGLESHEETS_LOOKUP_SPREADSHEET_ROW` - Find first row matching exact cell value [Required]
+2. `GOOGLESHEETS_SET_BASIC_FILTER` - Apply filter/sort to a range [Alternative]
+3. `GOOGLESHEETS_CLEAR_BASIC_FILTER` - Remove existing filter [Optional]
+4. `GOOGLESHEETS_BATCH_GET` - Read filtered results [Optional]
+
+**Key parameters**:
+- `query`: Exact text value to match (matches entire cell content)
+- `range`: A1 notation range to search within
+- `case_sensitive`: Boolean for case-sensitive matching (default false)
+- `filter.range`: Grid range with sheet_id for basic filter
+- `filter.criteria`: Column-based filter conditions
+- `filter.sortSpecs`: Sort specifications
+
+**Pitfalls**:
+- `GOOGLESHEETS_LOOKUP_SPREADSHEET_ROW` matches entire cell content, not substrings
+- Sheet names with spaces must be single-quoted in ranges (e.g., "'My Sheet'!A:Z")
+- Bare sheet names without ranges are not supported for lookup; always specify a range
+
+### 4. Upsert Rows by Key
+
+**When to use**: User wants to update existing rows or insert new ones based on a unique key column
+
+**Tool sequence**:
+1. `GOOGLESHEETS_UPSERT_ROWS` - Update matching rows or append new ones [Required]
+
+**Key parameters**:
+- `spreadsheetId`: Target spreadsheet ID
+- `sheetName`: Tab name
+- `keyColumn`: Column header name used as unique identifier (e.g., 'Email', 'SKU')
+- `headers`: List of column names for the data
+- `rows`: 2D array of data rows
+- `strictMode`: Error on mismatched column counts (default true)
+
+**Pitfalls**:
+- `keyColumn` must be an actual header name, NOT a column letter (e.g., 'Email' not 'A')
+- If `headers` is NOT provided, first row of `rows` is treated as headers
+- With `strictMode=true`, rows with more values than headers cause an error
+- Auto-adds missing columns to the sheet
+
+### 5. Format Cells
+
+**When to use**: User wants to apply formatting (bold, colors, font size) to cells
+
+**Tool sequence**:
+1. `GOOGLESHEETS_GET_SPREADSHEET_INFO` - Get numeric sheetId for target tab [Prerequisite]
+2. `GOOGLESHEETS_FORMAT_CELL` - Apply formatting to a range [Required]
+3. `GOOGLESHEETS_UPDATE_SHEET_PROPERTIES` - Change frozen rows, column widths [Optional]
+
+**Key parameters**:
+- `spreadsheet_id`: Spreadsheet ID
+- `worksheet_id`: Numeric sheetId (NOT tab name); get from GET_SPREADSHEET_INFO
+- `range`: A1 notation (e.g., 'A1:F1') - preferred over index fields
+- `bold`, `italic`, `underline`, `strikethrough`: Boolean formatting options
+- `red`, `green`, `blue`: Background color as 0.0-1.0 floats (NOT 0-255 ints)
+- `fontSize`: Font size in points
+
+**Pitfalls**:
+- Requires numeric `worksheet_id`, not tab title; get from spreadsheet metadata
+- Color channels are 0-1 floats (e.g., 1.0 for full red), NOT 0-255 integers
+- Responses may return empty reply objects ([{}]); verify formatting via readback
+- Format one range per call; batch formatting requires separate calls
+
+## Common Patterns
+
+### ID Resolution
+- **Spreadsheet name -> ID**: `GOOGLESHEETS_SEARCH_SPREADSHEETS` with `query`
+- **Tab name -> sheetId**: `GOOGLESHEETS_GET_SPREADSHEET_INFO`, extract from sheets metadata
+- **Tab existence check**: `GOOGLESHEETS_FIND_WORKSHEET_BY_TITLE`
+
+### Rate Limits
+Google Sheets enforces strict rate limits:
+- Max 60 reads/minute and 60 writes/minute
+- Exceeding limits causes errors; batch operations where possible
+- Use `GOOGLESHEETS_BATCH_GET` and `GOOGLESHEETS_BATCH_UPDATE` for efficiency
+
+### Data Patterns
+- Always read before writing to understand existing layout
+- Use `GOOGLESHEETS_UPSERT_ROWS` for CRM syncs, inventory updates, and dedup scenarios
+- Append mode (omit `first_cell_location`) is safest for adding new records
+- Use `GOOGLESHEETS_CLEAR_VALUES` to clear content while preserving formatting
+
+## Known Pitfalls
+
+- **Tab names**: Locale-dependent defaults; 'Sheet1' may not exist in non-English accounts
+- **Range notation**: Sheet names with spaces need single quotes in A1 notation
+- **Unbounded ranges**: Can timeout on large sheets; always specify row bounds (e.g., 'A1:Z10000')
+- **2D arrays**: All value parameters must be list-of-lists, even for single rows
+- **Color values**: Floats 0.0-1.0, not integers 0-255
+- **Formatting IDs**: `FORMAT_CELL` needs numeric sheetId, not tab title
+- **Rate limits**: 60 reads/min and 60 writes/min; batch to stay within limits
+- **Delete dimension**: `GOOGLESHEETS_DELETE_DIMENSION` is irreversible; double-check bounds
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search spreadsheets | `GOOGLESHEETS_SEARCH_SPREADSHEETS` | `query`, `search_type` |
+| Create spreadsheet | `GOOGLESHEETS_CREATE_GOOGLE_SHEET1` | `title` |
+| List tabs | `GOOGLESHEETS_GET_SHEET_NAMES` | `spreadsheet_id` |
+| Add tab | `GOOGLESHEETS_ADD_SHEET` | `spreadsheetId`, `title` |
+| Read data | `GOOGLESHEETS_BATCH_GET` | `spreadsheet_id`, `ranges` |
+| Read single range | `GOOGLESHEETS_VALUES_GET` | `spreadsheet_id`, `range` |
+| Write data | `GOOGLESHEETS_BATCH_UPDATE` | `spreadsheet_id`, `sheet_name`, `values` |
+| Update range | `GOOGLESHEETS_VALUES_UPDATE` | `spreadsheet_id`, `range`, `values` |
+| Append rows | `GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND` | `spreadsheetId`, `range`, `values` |
+| Upsert rows | `GOOGLESHEETS_UPSERT_ROWS` | `spreadsheetId`, `sheetName`, `keyColumn`, `rows` |
+| Lookup row | `GOOGLESHEETS_LOOKUP_SPREADSHEET_ROW` | `spreadsheet_id`, `query` |
+| Format cells | `GOOGLESHEETS_FORMAT_CELL` | `spreadsheet_id`, `worksheet_id`, `range` |
+| Set filter | `GOOGLESHEETS_SET_BASIC_FILTER` | `spreadsheetId`, `filter` |
+| Clear values | `GOOGLESHEETS_CLEAR_VALUES` | `spreadsheet_id`, range |
+| 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/plugins/awesome-claude-skills/googleslides-automation/SKILL.md b/plugins/awesome-claude-skills/googleslides-automation/SKILL.md
new file mode 100644
index 0000000..1d7edb2
--- /dev/null
+++ b/plugins/awesome-claude-skills/googleslides-automation/SKILL.md
@@ -0,0 +1,116 @@
+---
+name: googleslides-automation
+description: "Automate Google Slides tasks via Rube MCP (Composio): create presentations, add slides from Markdown, batch update, copy from templates, get thumbnails. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Slides Automation via Rube MCP
+
+Create, edit, and manage Google Slides presentations programmatically using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/googleslides](https://composio.dev/toolkits/googleslides)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active 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
+
+## Core Workflows
+
+### 1. Create a Blank Presentation
+Use `GOOGLESLIDES_PRESENTATIONS_CREATE` to initialize a new blank presentation.
+```
+Tool: GOOGLESLIDES_PRESENTATIONS_CREATE
+Parameters:
+ - title (required): Title for the new presentation
+ - presentationId (optional): Specific ID to assign (usually auto-generated)
+```
+
+### 2. Create Slides from Markdown
+Use `GOOGLESLIDES_CREATE_SLIDES_MARKDOWN` to generate a full presentation from Markdown text. Content is automatically split into slides.
+```
+Tool: GOOGLESLIDES_CREATE_SLIDES_MARKDOWN
+Parameters:
+ - title (required): Presentation title
+ - markdown_text (required): Markdown content (auto-split into slides)
+```
+
+### 3. Batch Update a Presentation
+Use `GOOGLESLIDES_PRESENTATIONS_BATCH_UPDATE` to apply updates to an existing presentation using Markdown or raw API requests.
+```
+Tool: GOOGLESLIDES_PRESENTATIONS_BATCH_UPDATE
+Parameters:
+ - presentationId (required): Target presentation ID
+ - markdown_text: Markdown content to update slides
+ - requests: Raw Google Slides API batch update requests
+ - writeControl: Write control settings
+```
+
+### 4. Copy from Template
+Use `GOOGLESLIDES_PRESENTATIONS_COPY_FROM_TEMPLATE` to duplicate an existing presentation as a template.
+```
+Tool: GOOGLESLIDES_PRESENTATIONS_COPY_FROM_TEMPLATE
+Parameters:
+ - template_presentation_id (required): Source template presentation ID
+ - new_title (required): Title for the new copy
+ - parent_folder_id (optional): Google Drive folder for the copy
+```
+
+### 5. Get Presentation Details
+Use `GOOGLESLIDES_PRESENTATIONS_GET` to retrieve the current state of a presentation including all slides and elements.
+```
+Tool: GOOGLESLIDES_PRESENTATIONS_GET
+Parameters:
+ - presentationId (required): Presentation ID to retrieve
+ - fields (optional): Specific fields to return
+```
+
+### 6. Generate Slide Thumbnails
+Use `GOOGLESLIDES_PRESENTATIONS_PAGES_GET_THUMBNAIL` to generate a thumbnail image URL for a specific slide.
+```
+Tool: GOOGLESLIDES_PRESENTATIONS_PAGES_GET_THUMBNAIL
+Parameters:
+ - presentationId (required): Presentation ID
+ - pageObjectId (required): Page/slide object ID
+ - thumbnailProperties.mimeType: Image format (e.g., PNG)
+ - thumbnailProperties.thumbnailSize: Thumbnail size
+```
+
+## Common Patterns
+
+- **Markdown-first workflow**: Use `GOOGLESLIDES_CREATE_SLIDES_MARKDOWN` to quickly generate presentations from structured text. The tool auto-splits content into separate slides.
+- **Template-based generation**: Use `GOOGLESLIDES_PRESENTATIONS_COPY_FROM_TEMPLATE` to copy a styled template, then `GOOGLESLIDES_PRESENTATIONS_BATCH_UPDATE` to fill in content.
+- **Retrieve then modify**: Use `GOOGLESLIDES_PRESENTATIONS_GET` to inspect slide structure and object IDs, then `GOOGLESLIDES_PRESENTATIONS_BATCH_UPDATE` to make targeted changes.
+- **Export thumbnails**: Use `GOOGLESLIDES_PRESENTATIONS_PAGES_GET` to list page object IDs, then `GOOGLESLIDES_PRESENTATIONS_PAGES_GET_THUMBNAIL` to generate preview images.
+- **Share presentations**: Combine with `GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE` (googledrive toolkit) to share after creation.
+
+## Known Pitfalls
+
+- `GOOGLESLIDES_CREATE_SLIDES_MARKDOWN` creates a brand-new presentation each time -- it cannot append to an existing one.
+- `GOOGLESLIDES_PRESENTATIONS_BATCH_UPDATE` with raw `requests` requires knowledge of the Google Slides API request format. Prefer `markdown_text` for simpler updates.
+- Page object IDs must be obtained from `GOOGLESLIDES_PRESENTATIONS_GET` before using thumbnail or page-get tools.
+- The `presentationId` is the long alphanumeric string from the Google Slides URL (between `/d/` and `/edit`).
+- Copying from a template requires the authenticated user to have at least read access to the template presentation.
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| Create blank presentation | `GOOGLESLIDES_PRESENTATIONS_CREATE` | `title` |
+| Create from Markdown | `GOOGLESLIDES_CREATE_SLIDES_MARKDOWN` | `title`, `markdown_text` |
+| Batch update slides | `GOOGLESLIDES_PRESENTATIONS_BATCH_UPDATE` | `presentationId`, `markdown_text` or `requests` |
+| Copy from template | `GOOGLESLIDES_PRESENTATIONS_COPY_FROM_TEMPLATE` | `template_presentation_id`, `new_title` |
+| Get presentation | `GOOGLESLIDES_PRESENTATIONS_GET` | `presentationId` |
+| Get page details | `GOOGLESLIDES_PRESENTATIONS_PAGES_GET` | `presentationId`, `pageObjectId` |
+| Get slide thumbnail | `GOOGLESLIDES_PRESENTATIONS_PAGES_GET_THUMBNAIL` | `presentationId`, `pageObjectId` |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/googlesuper-automation/SKILL.md b/plugins/awesome-claude-skills/googlesuper-automation/SKILL.md
new file mode 100644
index 0000000..ca30f8c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/googletasks-automation/SKILL.md b/plugins/awesome-claude-skills/googletasks-automation/SKILL.md
new file mode 100644
index 0000000..e998505
--- /dev/null
+++ b/plugins/awesome-claude-skills/googletasks-automation/SKILL.md
@@ -0,0 +1,136 @@
+---
+name: googletasks-automation
+description: "Automate Google Tasks via Rube MCP (Composio): create, list, update, delete, move, and bulk-insert tasks and task lists. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Google Tasks Automation via Rube MCP
+
+Create, manage, organize, and bulk-operate on Google Tasks and task lists using Rube MCP (Composio).
+
+**Toolkit docs**: [composio.dev/toolkits/googletasks](https://composio.dev/toolkits/googletasks)
+
+## Prerequisites
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active 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
+
+## Core Workflows
+
+### 1. List All Task Lists
+Use `GOOGLETASKS_LIST_TASK_LISTS` to fetch all available task lists for the authenticated user.
+```
+Tool: GOOGLETASKS_LIST_TASK_LISTS
+Parameters:
+ - maxResults: Maximum task lists to return
+ - pageToken: Pagination token for next page
+```
+
+### 2. Create a New Task
+Use `GOOGLETASKS_INSERT_TASK` to add a new task to a specific task list.
+```
+Tool: GOOGLETASKS_INSERT_TASK
+Parameters:
+ - tasklist_id (required): ID of the target task list
+ - title (required): Task title
+ - notes: Task description/notes
+ - due: Due date in RFC3339 format (e.g., "2025-01-20T00:00:00.000Z")
+ - status: "needsAction" or "completed"
+ - task_parent: Parent task ID (to create subtask)
+ - task_previous: Previous task ID (for ordering)
+```
+
+### 3. List All Tasks Across Lists
+Use `GOOGLETASKS_LIST_ALL_TASKS` to fetch tasks across all task lists with optional filters.
+```
+Tool: GOOGLETASKS_LIST_ALL_TASKS
+Parameters:
+ - max_tasks_total: Maximum total tasks to return
+ - showCompleted: Include completed tasks
+ - showDeleted: Include deleted tasks
+ - showHidden: Include hidden tasks
+ - dueMin / dueMax: Filter by due date range
+ - completedMin / completedMax: Filter by completion date
+ - updatedMin: Filter by last update time
+ - showAssigned: Include assigned tasks
+```
+
+### 4. Update an Existing Task
+Use `GOOGLETASKS_UPDATE_TASK` to modify a task's title, notes, due date, or status.
+```
+Tool: GOOGLETASKS_UPDATE_TASK
+Parameters:
+ - tasklist_id (required): Task list ID
+ - task_id (required): Task ID to update
+ - title: New title
+ - notes: Updated notes
+ - due: New due date (RFC3339)
+ - status: "needsAction" or "completed"
+```
+
+### 5. Bulk Insert Tasks
+Use `GOOGLETASKS_BULK_INSERT_TASKS` to create multiple tasks at once in a single operation.
+```
+Tool: GOOGLETASKS_BULK_INSERT_TASKS
+Parameters:
+ - tasklist_id (required): Target task list ID
+ - tasks (required): Array of task objects (each with title, notes, due, status)
+ - batch_size: Number of tasks per batch request
+```
+
+### 6. Delete or Clear Tasks
+Use `GOOGLETASKS_DELETE_TASK` to remove a specific task, or `GOOGLETASKS_CLEAR_TASKS` to permanently remove all completed tasks from a list.
+```
+Tool: GOOGLETASKS_DELETE_TASK
+Parameters:
+ - tasklist_id (required): Task list ID
+ - task_id (required): Task ID to delete
+
+Tool: GOOGLETASKS_CLEAR_TASKS
+Parameters:
+ - tasklist (required): Task list ID to clear completed tasks from
+```
+
+## Common Patterns
+
+- **Get task list ID first**: Always start with `GOOGLETASKS_LIST_TASK_LISTS` to discover available task lists and their IDs before creating or listing tasks.
+- **List then update**: Use `GOOGLETASKS_LIST_ALL_TASKS` or `GOOGLETASKS_LIST_TASKS` to find task IDs, then use `GOOGLETASKS_UPDATE_TASK` to modify them.
+- **Mark complete**: Update a task with `status: "completed"` using `GOOGLETASKS_UPDATE_TASK`.
+- **Create subtasks**: Use `GOOGLETASKS_INSERT_TASK` with the `task_parent` parameter set to the parent task's ID.
+- **Reorder tasks**: Use `GOOGLETASKS_MOVE_TASK` to change a task's position within its list or reparent it.
+- **Batch creation**: Use `GOOGLETASKS_BULK_INSERT_TASKS` for creating many tasks at once (e.g., importing from another system).
+
+## Known Pitfalls
+
+- Both `tasklist_id` and `task_id` are **required** for `GOOGLETASKS_UPDATE_TASK`, `GOOGLETASKS_DELETE_TASK`, and `GOOGLETASKS_GET_TASK`. You cannot operate on a task without knowing which list it belongs to.
+- All date/time strings must be in **RFC3339 format** (e.g., `2025-01-20T00:00:00.000Z`). Other formats will be rejected.
+- `GOOGLETASKS_CLEAR_TASKS` permanently deletes all **completed** tasks from a list. This action is irreversible.
+- `GOOGLETASKS_LIST_ALL_TASKS` fetches across all lists but results may be paginated -- check for pagination tokens.
+- Task list IDs are not the same as task list names. Always resolve names to IDs using `GOOGLETASKS_LIST_TASK_LISTS`.
+- The default task list is typically named "My Tasks" but its ID is an opaque string, not "default" or "primary".
+
+## Quick Reference
+| Action | Tool | Key Parameters |
+|--------|------|----------------|
+| List task lists | `GOOGLETASKS_LIST_TASK_LISTS` | `maxResults`, `pageToken` |
+| List all tasks | `GOOGLETASKS_LIST_ALL_TASKS` | `max_tasks_total`, `showCompleted`, `dueMin` |
+| List tasks in a list | `GOOGLETASKS_LIST_TASKS` | `tasklist_id`, `maxResults`, `showCompleted` |
+| Get single task | `GOOGLETASKS_GET_TASK` | `tasklist_id`, `task_id` |
+| Create task | `GOOGLETASKS_INSERT_TASK` | `tasklist_id`, `title`, `notes`, `due` |
+| Bulk create tasks | `GOOGLETASKS_BULK_INSERT_TASKS` | `tasklist_id`, `tasks` |
+| Update task | `GOOGLETASKS_UPDATE_TASK` | `tasklist_id`, `task_id`, `title`, `status` |
+| Delete task | `GOOGLETASKS_DELETE_TASK` | `tasklist_id`, `task_id` |
+| Move/reorder task | `GOOGLETASKS_MOVE_TASK` | `tasklist_id`, `task_id` |
+| Clear completed | `GOOGLETASKS_CLEAR_TASKS` | `tasklist` |
+
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/gorgias-automation/SKILL.md b/plugins/awesome-claude-skills/gorgias-automation/SKILL.md
new file mode 100644
index 0000000..7d50aac
--- /dev/null
+++ b/plugins/awesome-claude-skills/gorgias-automation/SKILL.md
@@ -0,0 +1,145 @@
+---
+name: Gorgias Automation
+description: "Automate e-commerce customer support workflows in Gorgias -- manage tickets, customers, tags, and teams through natural language commands."
+requires:
+ mcp:
+ - rube
+---
+
+# Gorgias Automation
+
+Automate your Gorgias helpdesk operations directly from Claude Code. Create, update, and triage support tickets, manage customers, and organize your support team -- all without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/gorgias](https://composio.dev/toolkits/gorgias)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your Claude Code config with URL: `https://rube.app/mcp`
+2. When prompted, authenticate your Gorgias account through the connection link provided
+3. Start automating your support workflows with natural language
+
+---
+
+## Core Workflows
+
+### 1. List and Filter Tickets
+
+Retrieve tickets with filtering by status, channel, assignee, date range, and more.
+
+**Tool:** `GORGIAS_LIST_TICKETS`
+
+```
+List all open tickets from the email channel created in the last 7 days
+```
+
+Key parameters:
+- `status` -- filter by ticket status (e.g., "open", "closed")
+- `channel` -- filter by channel (e.g., "email", "chat")
+- `assignee_user_id` / `assignee_team_id` -- filter by assigned agent or team
+- `created_from` / `created_to` -- ISO date range filters
+- `limit` (max 100) / `offset` -- pagination controls
+- `order_by` / `order_dir` -- sorting options
+
+### 2. Create and Update Tickets
+
+Create new tickets or update existing ones with assignment, priority, and status changes.
+
+**Tools:** `GORGIAS_CREATE_TICKET`, `GORGIAS_UPDATE_TICKET`, `GORGIAS_GET_TICKET`
+
+```
+Create a high-priority ticket for customer 12345 about a missing order with subject "Order #9876 not delivered"
+```
+
+- `GORGIAS_CREATE_TICKET` requires `customer_id`; accepts `subject`, `status`, `priority`, `channel`, `messages`, `tags`
+- `GORGIAS_UPDATE_TICKET` requires `ticket_id`; all other fields are optional partial updates
+- `GORGIAS_GET_TICKET` retrieves full ticket details by `ticket_id`
+
+### 3. Manage Ticket Tags
+
+Add tags to tickets for categorization, routing, and reporting.
+
+**Tools:** `GORGIAS_ADD_TICKET_TAGS`, `GORGIAS_LIST_TICKET_TAGS`
+
+```
+Add tags 101 and 202 to ticket 5678, then show me all tags on that ticket
+```
+
+- `GORGIAS_ADD_TICKET_TAGS` requires `ticket_id` and `tag_ids` (array of integers)
+- `GORGIAS_LIST_TICKET_TAGS` requires `ticket_id` to retrieve current tags
+
+### 4. Customer Management
+
+Create new customers or merge duplicate customer records.
+
+**Tools:** `GORGIAS_CREATE_CUSTOMER`, `GORGIAS_MERGE_CUSTOMERS`, `GORGIAS_LIST_CUSTOMERS`
+
+```
+Create a new customer named "Jane Doe" with email jane@example.com and phone channel
+```
+
+- `GORGIAS_CREATE_CUSTOMER` requires `name`; accepts `email`, `channels` (array with `type` and `value`), `external_id`, `address`, `data`
+- `GORGIAS_MERGE_CUSTOMERS` requires `source_customer_id` and `target_customer_id` -- source is merged into target
+- `GORGIAS_LIST_CUSTOMERS` retrieves customers with filtering options
+
+### 5. Team and Account Operations
+
+List teams, retrieve account info, and inspect ticket custom fields.
+
+**Tools:** `GORGIAS_LIST_TEAMS`, `GORGIAS_GET_TEAM`, `GORGIAS_GET_ACCOUNT`, `GORGIAS_LIST_TICKET_FIELD_VALUES`
+
+```
+Show me all support teams in our Gorgias account
+```
+
+- `GORGIAS_GET_ACCOUNT` returns account-level metrics and configuration
+- `GORGIAS_LIST_TEAMS` / `GORGIAS_GET_TEAM` manage team lookup
+- `GORGIAS_LIST_TICKET_FIELD_VALUES` returns custom field values for a given ticket
+
+### 6. Activity and Event Tracking
+
+Monitor ticket activity and customer event history.
+
+**Tools:** `GORGIAS_LIST_EVENTS`
+
+```
+List recent events to see what activity has happened across our support queue
+```
+
+- `GORGIAS_LIST_EVENTS` provides an activity timeline with filtering options
+
+---
+
+## Known Pitfalls
+
+- **Pagination required:** `GORGIAS_LIST_TICKETS` uses `limit`/`offset` pagination. Failing to loop through pages will miss older tickets and produce incomplete data.
+- **Filter specificity:** Missing or overly broad filters on `GORGIAS_LIST_TICKETS` can overload the export or omit the desired reporting window. Always set `created_from`/`created_to` for time-bound queries.
+- **Custom fields are separate:** Key business KPIs may only exist in custom fields. You must query `GORGIAS_LIST_TICKET_FIELD_VALUES` explicitly to include them.
+- **Rate limits:** High-volume exports across `GORGIAS_LIST_TICKETS` and related endpoints can hit Gorgias rate limits. Add backoff and resume from the last offset.
+- **Auth errors:** 401/403 responses on any Gorgias tool indicate token or permission issues. Do not treat partial data as a complete dataset.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `GORGIAS_LIST_TICKETS` | List tickets with filters (status, channel, date, assignee) |
+| `GORGIAS_GET_TICKET` | Retrieve a specific ticket by ID |
+| `GORGIAS_CREATE_TICKET` | Create a new ticket (requires `customer_id`) |
+| `GORGIAS_UPDATE_TICKET` | Update ticket fields (requires `ticket_id`) |
+| `GORGIAS_ADD_TICKET_TAGS` | Add tags to a ticket |
+| `GORGIAS_LIST_TICKET_TAGS` | List all tags on a ticket |
+| `GORGIAS_LIST_TICKET_FIELD_VALUES` | List custom field values for a ticket |
+| `GORGIAS_CREATE_CUSTOMER` | Create a new customer (requires `name`) |
+| `GORGIAS_MERGE_CUSTOMERS` | Merge two customer records |
+| `GORGIAS_LIST_CUSTOMERS` | List customers with filters |
+| `GORGIAS_LIST_TEAMS` | List all teams |
+| `GORGIAS_GET_TEAM` | Retrieve a specific team |
+| `GORGIAS_GET_ACCOUNT` | Retrieve account information |
+| `GORGIAS_LIST_EVENTS` | List activity events with filters |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/gosquared-automation/SKILL.md b/plugins/awesome-claude-skills/gosquared-automation/SKILL.md
new file mode 100644
index 0000000..dfac20e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/grafbase-automation/SKILL.md b/plugins/awesome-claude-skills/grafbase-automation/SKILL.md
new file mode 100644
index 0000000..732c776
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/graphhopper-automation/SKILL.md b/plugins/awesome-claude-skills/graphhopper-automation/SKILL.md
new file mode 100644
index 0000000..ed5dd90
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/griptape-automation/SKILL.md b/plugins/awesome-claude-skills/griptape-automation/SKILL.md
new file mode 100644
index 0000000..a6f06dd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/grist-automation/SKILL.md b/plugins/awesome-claude-skills/grist-automation/SKILL.md
new file mode 100644
index 0000000..e0b712e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/groqcloud-automation/SKILL.md b/plugins/awesome-claude-skills/groqcloud-automation/SKILL.md
new file mode 100644
index 0000000..3336033
--- /dev/null
+++ b/plugins/awesome-claude-skills/groqcloud-automation/SKILL.md
@@ -0,0 +1,117 @@
+---
+name: GroqCloud Automation
+description: "Automate AI inference, chat completions, audio translation, and TTS voice management through GroqCloud's high-performance API via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# GroqCloud Automation
+
+Automate AI inference workflows using GroqCloud's ultra-fast API -- chat completions, model discovery, audio translation, and TTS voice selection -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/groqcloud](https://composio.dev/toolkits/groqcloud)
+
+---
+
+## Setup
+
+1. Connect your GroqCloud account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `GROQCLOUD_*` tools become available for execution
+
+---
+
+## Core Workflows
+
+### 1. Discover Available Models
+List all models available on GroqCloud to find valid model IDs before running inference.
+
+**Tool:** `GROQCLOUD_LIST_MODELS`
+
+```
+No parameters required -- returns all available models with metadata.
+```
+
+Use this as a prerequisite before any chat completion call to ensure you reference a valid, non-deprecated model ID.
+
+---
+
+### 2. Run Chat Completions
+Generate AI responses for conversational prompts using a specified GroqCloud model.
+
+**Tool:** `GROQCLOUD_GROQ_CREATE_CHAT_COMPLETION`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `model` | string | Yes | Model ID from `GROQCLOUD_LIST_MODELS` |
+| `messages` | array | Yes | Ordered list of `{role, content}` objects (`system`, `user`, `assistant`) |
+| `temperature` | number | No | Sampling temperature 0-2 (default: 1) |
+| `max_completion_tokens` | integer | No | Max tokens to generate |
+| `top_p` | number | No | Nucleus sampling 0-1 (default: 1) |
+| `stop` | string/array | No | Up to 4 stop sequences |
+| `stream` | boolean | No | Enable SSE streaming (default: false) |
+
+---
+
+### 3. Inspect Model Details
+Retrieve detailed metadata for a specific model including context window and capabilities.
+
+**Tool:** `GROQCLOUD_GROQ_RETRIEVE_MODEL`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `model` | string | Yes | Model identifier (e.g., `groq-1-large`) |
+
+---
+
+### 4. Translate Audio to English
+Translate non-English audio files into English text using Whisper models.
+
+**Tool:** `GROQCLOUD_GROQ_CREATE_AUDIO_TRANSLATION`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `file_path` | string | Yes | Local path, HTTP(S) URL, or base64 data URL for audio |
+| `model` | string | No | Model ID (default: `whisper-large-v3`). Note: `whisper-large-v3-turbo` may not support translations |
+| `response_format` | string | No | `json`, `verbose_json`, or `text` (default: `json`) |
+| `temperature` | number | No | Sampling temperature 0-1 (default: 0) |
+
+---
+
+### 5. List TTS Voices
+Enumerate available text-to-speech voices for Groq PlayAI models to drive voice selection UX.
+
+**Tool:** `GROQCLOUD_LIST_VOICES`
+
+```
+Returns the set of supported TTS voices. Note: this is a static list maintained manually.
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **Nested model list** | `GROQCLOUD_LIST_MODELS` response may be nested at `response['data']['data']` -- do not assume a flat top-level array |
+| **Hard-coded model IDs break** | Always fetch model IDs dynamically via `GROQCLOUD_LIST_MODELS`; hard-coded names can break when models are deprecated or renamed |
+| **Audio format validation** | `GROQCLOUD_GROQ_CREATE_AUDIO_TRANSLATION` rejects invalid or unsupported audio formats silently -- validate inputs before calling |
+| **Model metadata drifts** | Data from `GROQCLOUD_GROQ_RETRIEVE_MODEL` (context window, features) can change as models update -- do not treat it as static |
+| **TTS voice changes** | Voice sets from `GROQCLOUD_LIST_VOICES` may shrink or rename over time -- handle missing voices gracefully |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `GROQCLOUD_LIST_MODELS` | List all available models and metadata |
+| `GROQCLOUD_GROQ_CREATE_CHAT_COMPLETION` | Generate chat-based AI completions |
+| `GROQCLOUD_GROQ_RETRIEVE_MODEL` | Get detailed info for a specific model |
+| `GROQCLOUD_GROQ_CREATE_AUDIO_TRANSLATION` | Translate non-English audio to English text |
+| `GROQCLOUD_LIST_VOICES` | Retrieve available TTS voices for PlayAI |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/gumroad-automation/SKILL.md b/plugins/awesome-claude-skills/gumroad-automation/SKILL.md
new file mode 100644
index 0000000..f093aed
--- /dev/null
+++ b/plugins/awesome-claude-skills/gumroad-automation/SKILL.md
@@ -0,0 +1,123 @@
+---
+name: Gumroad Automation
+description: "Automate Gumroad product management, sales tracking, license verification, and webhook subscriptions using natural language through the Composio MCP integration."
+category: e-commerce
+requires:
+ mcp:
+ - rube
+---
+
+# Gumroad Automation
+
+Automate your Gumroad storefront -- list products, track sales, verify licenses, and manage real-time webhooks -- all through natural language commands.
+
+**Toolkit docs:** [composio.dev/toolkits/gumroad](https://composio.dev/toolkits/gumroad)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Gumroad account when prompted (API key authentication).
+3. Start issuing natural language commands to manage your Gumroad store.
+
+---
+
+## Core Workflows
+
+### 1. List All Products
+Retrieve every product in your authenticated Gumroad account to get product IDs for downstream operations.
+
+**Tool:** `GUMROAD_LIST_PRODUCTS`
+
+**Example prompt:**
+> "List all my Gumroad products"
+
+**Parameters:** None required -- returns all products for the authenticated account.
+
+---
+
+### 2. Track Sales with Filters
+Retrieve successful sales with optional filtering by email, date range, product, or pagination.
+
+**Tool:** `GUMROAD_GET_SALES`
+
+**Example prompt:**
+> "Show me all Gumroad sales from January 2025 for product prod_ABC123"
+
+**Key parameters:**
+- `after` -- ISO8601 date/time to filter sales after (e.g., `2025-01-01T00:00:00Z`)
+- `before` -- ISO8601 date/time to filter sales before
+- `email` -- Filter by customer email address
+- `product_id` -- Filter by specific product ID
+- `page` -- Page number for paginated results (minimum 1)
+
+---
+
+### 3. Verify License Keys
+Check if a license key is valid against a specific product, inspect usage count, or verify membership entitlement.
+
+**Tool:** `GUMROAD_VERIFY_LICENSE`
+
+**Example prompt:**
+> "Verify license key ABCD-EFGH-IJKL-MNOP for product prod_ABC123"
+
+**Key parameters (all required):**
+- `product_id` -- The product ID to verify against (required for products created on/after Jan 9, 2023)
+- `license_key` -- The license key string (e.g., `ABCD-EFGH-IJKL-MNOP`)
+- `increment_uses_count` -- Whether to increment usage count (defaults to true)
+
+---
+
+### 4. Subscribe to Webhook Events
+Set up real-time event notifications by subscribing your endpoint URL to specific Gumroad resource events.
+
+**Tool:** `GUMROAD_SUBSCRIBE_TO_RESOURCE`
+
+**Example prompt:**
+> "Subscribe my webhook https://example.com/hook to Gumroad sale events"
+
+**Key parameters (all required):**
+- `resource_name` -- One of: `sale`, `refund`, `dispute`, `dispute_won`, `cancellation`, `subscription_updated`, `subscription_ended`, `subscription_restarted`
+- `post_url` -- Your endpoint URL that receives HTTP POST notifications
+
+---
+
+### 5. List Active Webhook Subscriptions
+Review existing webhook subscriptions for a given resource type before adding new ones to avoid duplicates.
+
+**Tool:** `GUMROAD_GET_RESOURCE_SUBSCRIPTIONS`
+
+**Example prompt:**
+> "Show all my active Gumroad webhook subscriptions for sale events"
+
+**Key parameters (required):**
+- `resource_name` -- One of the eight supported event types (e.g., `sale`, `refund`)
+
+---
+
+## Known Pitfalls
+
+- **Product ID required for license verification**: Products created on or after January 9, 2023 require the `product_id` parameter. Older products may work without it but providing it is recommended.
+- **Pagination on sales**: Sales results are paginated. Always check if more pages exist by incrementing the `page` parameter.
+- **Webhook deduplication**: Before subscribing to a resource, use `GUMROAD_GET_RESOURCE_SUBSCRIPTIONS` to check for existing subscriptions and avoid duplicate webhooks.
+- **ISO8601 date format**: Date filters on sales must use ISO8601 format (e.g., `2025-01-01T00:00:00Z`), not plain dates.
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Required Params |
+|---|---|---|
+| List products | `GUMROAD_LIST_PRODUCTS` | None |
+| Get sales | `GUMROAD_GET_SALES` | None (all optional filters) |
+| Verify license | `GUMROAD_VERIFY_LICENSE` | `product_id`, `license_key` |
+| Subscribe to events | `GUMROAD_SUBSCRIBE_TO_RESOURCE` | `resource_name`, `post_url` |
+| List webhook subs | `GUMROAD_GET_RESOURCE_SUBSCRIPTIONS` | `resource_name` |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/habitica-automation/SKILL.md b/plugins/awesome-claude-skills/habitica-automation/SKILL.md
new file mode 100644
index 0000000..b91822f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hackernews-automation/SKILL.md b/plugins/awesome-claude-skills/hackernews-automation/SKILL.md
new file mode 100644
index 0000000..8776036
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/happy-scribe-automation/SKILL.md b/plugins/awesome-claude-skills/happy-scribe-automation/SKILL.md
new file mode 100644
index 0000000..3756efc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/harvest-automation/SKILL.md b/plugins/awesome-claude-skills/harvest-automation/SKILL.md
new file mode 100644
index 0000000..bef2807
--- /dev/null
+++ b/plugins/awesome-claude-skills/harvest-automation/SKILL.md
@@ -0,0 +1,153 @@
+---
+name: Harvest Automation
+description: "Automate time tracking, project management, and invoicing workflows in Harvest -- log hours, manage projects, clients, and tasks through natural language commands."
+requires:
+ mcp:
+ - rube
+---
+
+# Harvest Automation
+
+Automate your Harvest time tracking operations directly from Claude Code. Log time entries, manage projects and clients, create tasks, and pull reporting data -- all without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/harvest](https://composio.dev/toolkits/harvest)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your Claude Code config with URL: `https://rube.app/mcp`
+2. When prompted, authenticate your Harvest account through the connection link provided
+3. Start automating your time tracking workflows with natural language
+
+---
+
+## Core Workflows
+
+### 1. Log and Manage Time Entries
+
+Create, list, update, and retrieve time entries for accurate billing and reporting.
+
+**Tools:** `HARVEST_CREATE_TIME_ENTRY`, `HARVEST_LIST_TIME_ENTRIES`, `HARVEST_GET_TIME_ENTRY`, `HARVEST_UPDATE_TIME_ENTRY`
+
+```
+Log 3.5 hours of development work on project 12345, task 67890 for today
+```
+
+Key parameters for `HARVEST_CREATE_TIME_ENTRY`:
+- `project_id` (required) -- the project to log against
+- `task_id` (required) -- the task must be assigned to the project
+- `spent_date` (required) -- date in YYYY-MM-DD format
+- `hours` -- total hours (for duration-based accounts)
+- `started_time` / `ended_time` -- for timestamp-based accounts
+- `notes` -- description of work performed
+
+Key parameters for `HARVEST_LIST_TIME_ENTRIES`:
+- `from_date` / `to` -- date range filters (YYYY-MM-DD)
+- `project_id`, `client_id`, `task_id`, `user_id` -- entity filters
+- `is_billed` / `is_running` -- status filters
+- `page` / `per_page` (max 2000) -- pagination
+
+### 2. Manage Projects
+
+Create new projects and list existing ones with client and billing configuration.
+
+**Tools:** `HARVEST_CREATE_PROJECT`, `HARVEST_LIST_PROJECTS`, `HARVEST_GET_PROJECT`
+
+```
+Create a billable project called "Website Redesign" for client 456 with Tasks billing and project budget
+```
+
+Key parameters for `HARVEST_CREATE_PROJECT`:
+- `name`, `client_id`, `is_billable`, `bill_by`, `budget_by` (all required)
+- `bill_by` options: `"Project"`, `"Tasks"`, `"People"`, `"none"`
+- `budget_by` options: `"project"`, `"project_cost"`, `"task"`, `"task_fees"`, `"person"`, `"none"`
+- Optional: `budget`, `hourly_rate`, `starts_on`, `ends_on`, `is_fixed_fee`
+
+### 3. Manage Clients
+
+Create and list clients that projects are organized under.
+
+**Tools:** `HARVEST_CREATE_CLIENT`, `HARVEST_LIST_CLIENTS`
+
+```
+List all active clients in our Harvest account
+```
+
+- `HARVEST_CREATE_CLIENT` requires `name`; accepts `address`, `currency`, `is_active`
+- `HARVEST_LIST_CLIENTS` supports `is_active` filter and pagination (`per_page` max 2000)
+
+### 4. Manage Tasks
+
+Create and list reusable task types for time tracking.
+
+**Tools:** `HARVEST_CREATE_TASK`, `HARVEST_LIST_TASKS`
+
+```
+Create a new billable task called "Code Review" with a default rate of $150/hr
+```
+
+- `HARVEST_CREATE_TASK` requires `name`; accepts `billable_by_default`, `default_hourly_rate`, `is_active`, `is_default`
+- `HARVEST_LIST_TASKS` supports `is_active`, `is_default` filters and pagination (`per_page` max 100)
+- Task names must be unique across all tasks (active and archived)
+
+### 5. Time Entry Reporting
+
+Pull time entries with date ranges and filters for billing summaries and utilization reports.
+
+**Tools:** `HARVEST_LIST_TIME_ENTRIES`, `HARVEST_GET_TIME_ENTRY`
+
+```
+Show me all unbilled time entries for project 789 from January 2026
+```
+
+- Use `from_date` and `to` for date windowing
+- Filter with `is_billed: false` for unbilled entries
+- Combine `project_id`, `user_id`, `client_id` for cross-dimensional reporting
+- Paginate with `page` and `per_page` to gather complete datasets
+
+### 6. Update and Correct Time Entries
+
+Modify existing time entries to fix hours, reassign projects, or update notes.
+
+**Tools:** `HARVEST_UPDATE_TIME_ENTRY`
+
+```
+Update time entry 123456 to change the hours to 4.0 and add the note "Completed API integration"
+```
+
+- Requires `time_entry_id`
+- Supports partial updates -- only include fields you want to change
+- Can update `hours`, `notes`, `project_id`, `task_id`, `spent_date`, `started_time`, `ended_time`
+
+---
+
+## Known Pitfalls
+
+- **Task assignment matters:** When creating time entries, the `task_id` must correspond to a task that is actually assigned to the specified `project_id`. Use project task assignments endpoint to verify, not just `HARVEST_LIST_TASKS` (which returns global tasks).
+- **Duration vs. timestamp tracking:** Harvest accounts are configured for either duration-based or timestamp-based tracking. `hours` is ignored on timestamp accounts; `started_time`/`ended_time` are ignored on duration accounts.
+- **Pagination limits vary:** `HARVEST_LIST_TIME_ENTRIES` and `HARVEST_LIST_CLIENTS` support up to 2000 per page, but `HARVEST_LIST_PROJECTS` and `HARVEST_LIST_TASKS` cap at 100 per page.
+- **Date format consistency:** All date parameters must use `YYYY-MM-DD` format. ISO 8601 with timezone is used for `updated_since` filters.
+- **Required fields for projects:** `HARVEST_CREATE_PROJECT` requires five fields: `name`, `client_id`, `is_billable`, `bill_by`, and `budget_by`. Missing any will cause a validation error.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `HARVEST_LIST_TIME_ENTRIES` | List time entries with date, project, client, user filters |
+| `HARVEST_CREATE_TIME_ENTRY` | Log a new time entry (requires `project_id`, `task_id`, `spent_date`) |
+| `HARVEST_GET_TIME_ENTRY` | Retrieve a specific time entry by ID |
+| `HARVEST_UPDATE_TIME_ENTRY` | Update an existing time entry (requires `time_entry_id`) |
+| `HARVEST_LIST_PROJECTS` | List projects with optional client filter |
+| `HARVEST_CREATE_PROJECT` | Create a new project with billing config |
+| `HARVEST_GET_PROJECT` | Retrieve a specific project by ID |
+| `HARVEST_LIST_CLIENTS` | List clients with active/inactive filter |
+| `HARVEST_CREATE_CLIENT` | Create a new client (requires `name`) |
+| `HARVEST_LIST_TASKS` | List reusable task types |
+| `HARVEST_CREATE_TASK` | Create a new task type (requires `name`) |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/hashnode-automation/SKILL.md b/plugins/awesome-claude-skills/hashnode-automation/SKILL.md
new file mode 100644
index 0000000..31d47bf
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/helcim-automation/SKILL.md b/plugins/awesome-claude-skills/helcim-automation/SKILL.md
new file mode 100644
index 0000000..fc926df
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/helloleads-automation/SKILL.md b/plugins/awesome-claude-skills/helloleads-automation/SKILL.md
new file mode 100644
index 0000000..795f523
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/helpdesk-automation/SKILL.md b/plugins/awesome-claude-skills/helpdesk-automation/SKILL.md
new file mode 100644
index 0000000..0ded03d
--- /dev/null
+++ b/plugins/awesome-claude-skills/helpdesk-automation/SKILL.md
@@ -0,0 +1,171 @@
+---
+name: helpdesk-automation
+description: "Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# HelpDesk Automation via Rube MCP
+
+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)
+- Active HelpDesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `helpdesk`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `helpdesk`
+3. If connection is not ACTIVE, follow the returned auth link to complete HelpDesk authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Browse Tickets
+
+**When to use**: User wants to retrieve, browse, or paginate through support tickets
+
+**Tool sequence**:
+1. `HELPDESK_LIST_TICKETS` - List tickets with sorting and pagination [Required]
+
+**Key parameters**:
+- `silo`: Ticket folder - 'tickets', 'archive', 'trash', or 'spam' (default: 'tickets')
+- `sortBy`: Sort field - 'createdAt', 'updatedAt', or 'lastMessageAt' (default: 'createdAt')
+- `order`: Sort direction - 'asc' or 'desc' (default: 'desc')
+- `pageSize`: Results per page, 1-100 (default: 20)
+- `next.value`: Timestamp cursor for forward pagination
+- `next.ID`: ID cursor for forward pagination
+- `prev.value`: Timestamp cursor for backward pagination
+- `prev.ID`: ID cursor for backward pagination
+
+**Pitfalls**:
+- Pagination uses cursor-based approach with timestamp + ID pairs
+- Forward pagination requires both `next.value` and `next.ID` from previous response
+- Backward pagination requires both `prev.value` and `prev.ID`
+- `silo` determines which folder to list from; default is active tickets
+- `pageSize` max is 100; default is 20
+- Archived and trashed tickets are in separate silos
+
+### 2. Manage Ticket Views
+
+**When to use**: User wants to see saved agent views for organizing tickets
+
+**Tool sequence**:
+1. `HELPDESK_LIST_VIEWS` - List all agent views [Required]
+
+**Key parameters**: (none required)
+
+**Pitfalls**:
+- Views are predefined saved filters configured by agents in the HelpDesk UI
+- View definitions include filter criteria that can be used to understand ticket organization
+- Views cannot be created or modified via API; they are managed in the HelpDesk UI
+
+### 3. Use Canned Responses
+
+**When to use**: User wants to list available canned (template) responses for tickets
+
+**Tool sequence**:
+1. `HELPDESK_LIST_CANNED_RESPONSES` - Retrieve all predefined reply templates [Required]
+
+**Key parameters**: (none required)
+
+**Pitfalls**:
+- Canned responses are predefined templates for common replies
+- They may include placeholder variables that need to be filled in
+- Canned responses are managed through the HelpDesk UI
+- Response content may include HTML formatting
+
+### 4. Inspect Custom Fields
+
+**When to use**: User wants to view custom field definitions for the account
+
+**Tool sequence**:
+1. `HELPDESK_LIST_CUSTOM_FIELDS` - List all custom field definitions [Required]
+
+**Key parameters**: (none required)
+
+**Pitfalls**:
+- Custom fields extend the default ticket schema with organization-specific data
+- Field definitions include field type, name, and validation rules
+- Custom fields are configured in the HelpDesk admin panel
+- Field values appear on tickets when the field has been populated
+
+## Common Patterns
+
+### Ticket Browsing Pattern
+
+```
+1. Call HELPDESK_LIST_TICKETS with desired silo and sortBy
+2. Process the returned page of tickets
+3. Extract next.value and next.ID from the response
+4. Call HELPDESK_LIST_TICKETS with those cursor values for next page
+5. Continue until no more cursor values are returned
+```
+
+### Ticket Folder Navigation
+
+```
+Active tickets: silo='tickets'
+Archived: silo='archive'
+Trashed: silo='trash'
+Spam: silo='spam'
+```
+
+### Cursor-Based Pagination
+
+```
+Forward pagination:
+ - Use next.value (timestamp) and next.ID from response
+ - Pass as next.value and next.ID parameters in next call
+
+Backward pagination:
+ - Use prev.value (timestamp) and prev.ID from response
+ - Pass as prev.value and prev.ID parameters in next call
+```
+
+## Known Pitfalls
+
+**Cursor Pagination**:
+- Both timestamp and ID are required for cursor navigation
+- Cursor values are timestamps in ISO 8601 date-time format
+- Mixing forward and backward cursors in the same request is undefined behavior
+
+**Silo Filtering**:
+- Tickets are physically separated into silos (folders)
+- Moving tickets between silos is done in the HelpDesk UI
+- Each silo query is independent; there is no cross-silo search
+
+**Read-Only Operations**:
+- Current Composio toolkit provides list/read operations
+- Ticket creation, update, and reply operations may require additional tools
+- Check RUBE_SEARCH_TOOLS for any newly available tools
+
+**Rate Limits**:
+- HelpDesk API has per-account rate limits
+- Implement backoff on 429 responses
+- Keep page sizes reasonable to avoid timeouts
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Ticket IDs are strings
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List tickets | HELPDESK_LIST_TICKETS | silo, sortBy, order, pageSize |
+| 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/plugins/awesome-claude-skills/helpwise-automation/SKILL.md b/plugins/awesome-claude-skills/helpwise-automation/SKILL.md
new file mode 100644
index 0000000..495d737
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/here-automation/SKILL.md b/plugins/awesome-claude-skills/here-automation/SKILL.md
new file mode 100644
index 0000000..7cf32fc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/heygen-automation/SKILL.md b/plugins/awesome-claude-skills/heygen-automation/SKILL.md
new file mode 100644
index 0000000..0838c01
--- /dev/null
+++ b/plugins/awesome-claude-skills/heygen-automation/SKILL.md
@@ -0,0 +1,121 @@
+---
+name: HeyGen Automation
+description: "Automate AI video generation, avatar browsing, template-based video creation, and video status tracking through HeyGen's platform via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# HeyGen Automation
+
+Automate AI-powered video creation workflows -- browse avatars and templates, generate personalized videos from templates, track processing status, and retrieve shareable URLs -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/heygen](https://composio.dev/toolkits/heygen)
+
+---
+
+## Setup
+
+1. Connect your HeyGen account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `HEYGEN_*` tools become available for execution
+
+---
+
+## Core Workflows
+
+### 1. Browse Available Templates
+Retrieve pre-designed avatar templates from the HeyGen library for video creation.
+
+**Tool:** `HEYGEN_V2_TEMPLATES`
+
+```
+No parameters required -- returns template IDs, names, preview images, and customization options.
+```
+
+Use this to discover templates before generating videos. Each template has a unique ID needed for generation.
+
+---
+
+### 2. Inspect Template Details & Variables
+Retrieve the full structure of a template including all variables, scene mappings, and customization options.
+
+**Tool:** `HEYGEN_RETRIEVE_TEMPLATE_DETAILS_V3`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `template_id` | string | Yes | Template ID from `HEYGEN_V2_TEMPLATES` or the HeyGen dashboard |
+
+This is a **required prerequisite** before generating videos -- it tells you exactly which variables must be populated.
+
+---
+
+### 3. Browse Available Avatars
+List all realistic avatars available for video creation, useful for mapping characters to scenes.
+
+**Tool:** `HEYGEN_V2_AVATARS`
+
+```
+No parameters required -- returns avatar identifiers, names, and preview images.
+The list may be paginated; additional calls might be needed for the full set.
+```
+
+---
+
+### 4. Generate Video from Template
+Create a customized video by populating a template with your variables and content.
+
+**Tool:** `HEYGEN_V2_TEMPLATE_GENERATE`
+
+Provide a video title and all template variables discovered via `HEYGEN_RETRIEVE_TEMPLATE_DETAILS_V3`. Every required variable must be supplied with exact names and types.
+
+---
+
+### 5. Check Video Processing Status
+Poll the processing status and retrieve metadata for a video being generated.
+
+**Tool:** `HEYGEN_RETRIEVE_VIDEO_STATUS_DETAILS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `video_id` | string | Yes | Video ID returned from the generation API |
+
+Returned URLs expire after 7 days but can be regenerated by calling this endpoint again.
+
+---
+
+### 6. Get Shareable Video URL
+Generate a public, shareable link that allows anyone to view the video without authentication.
+
+**Tool:** `HEYGEN_RETRIEVE_SHARABLE_VIDEO_URL`
+
+Provide the `video_id` to receive a public URL for distribution.
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **All template variables required** | `HEYGEN_V2_TEMPLATE_GENERATE` demands every variable from `HEYGEN_RETRIEVE_TEMPLATE_DETAILS_V3` with exact names and types -- missing or misnamed fields break scenes or fail generation |
+| **Always inspect templates first** | Never skip `HEYGEN_RETRIEVE_TEMPLATE_DETAILS_V3` before generation -- multi-scene templates have complex variable structures |
+| **Video URLs expire** | URLs from `HEYGEN_RETRIEVE_VIDEO_STATUS_DETAILS` expire after 7 days; regenerate by calling the endpoint again |
+| **Paginated avatar lists** | `HEYGEN_V2_AVATARS` may return paginated results -- additional calls may be needed for the full library |
+| **Processing time varies** | Video generation is asynchronous; poll `HEYGEN_RETRIEVE_VIDEO_STATUS_DETAILS` until status is complete before using output URLs |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `HEYGEN_V2_TEMPLATES` | List available video templates |
+| `HEYGEN_RETRIEVE_TEMPLATE_DETAILS_V3` | Get template variables and scene structure |
+| `HEYGEN_V2_AVATARS` | Browse available AI avatars |
+| `HEYGEN_V2_TEMPLATE_GENERATE` | Generate video from a template |
+| `HEYGEN_RETRIEVE_VIDEO_STATUS_DETAILS` | Check video processing status and get URLs |
+| `HEYGEN_RETRIEVE_SHARABLE_VIDEO_URL` | Get a public shareable video link |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/heyreach-automation/SKILL.md b/plugins/awesome-claude-skills/heyreach-automation/SKILL.md
new file mode 100644
index 0000000..99b5274
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/heyzine-automation/SKILL.md b/plugins/awesome-claude-skills/heyzine-automation/SKILL.md
new file mode 100644
index 0000000..a5b57a5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/highergov-automation/SKILL.md b/plugins/awesome-claude-skills/highergov-automation/SKILL.md
new file mode 100644
index 0000000..a717590
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/highlevel-automation/SKILL.md b/plugins/awesome-claude-skills/highlevel-automation/SKILL.md
new file mode 100644
index 0000000..5a63f70
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/honeybadger-automation/SKILL.md b/plugins/awesome-claude-skills/honeybadger-automation/SKILL.md
new file mode 100644
index 0000000..6e210c1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/honeyhive-automation/SKILL.md b/plugins/awesome-claude-skills/honeyhive-automation/SKILL.md
new file mode 100644
index 0000000..59dc5e3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hookdeck-automation/SKILL.md b/plugins/awesome-claude-skills/hookdeck-automation/SKILL.md
new file mode 100644
index 0000000..b4c1e5e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hotspotsystem-automation/SKILL.md b/plugins/awesome-claude-skills/hotspotsystem-automation/SKILL.md
new file mode 100644
index 0000000..e292193
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/html-to-image-automation/SKILL.md b/plugins/awesome-claude-skills/html-to-image-automation/SKILL.md
new file mode 100644
index 0000000..8110b68
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hubspot-automation/SKILL.md b/plugins/awesome-claude-skills/hubspot-automation/SKILL.md
new file mode 100644
index 0000000..247f165
--- /dev/null
+++ b/plugins/awesome-claude-skills/hubspot-automation/SKILL.md
@@ -0,0 +1,182 @@
+---
+name: hubspot-automation
+description: Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.
+requires:
+ mcp: [rube]
+---
+
+# HubSpot CRM Automation via Rube MCP
+
+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)
+- Active HubSpot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`
+3. If connection is not ACTIVE, follow the returned auth link to complete HubSpot OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Contacts
+
+**When to use**: User wants to create new contacts or update existing ones in HubSpot CRM
+
+**Tool sequence**:
+1. `HUBSPOT_GET_ACCOUNT_INFO` - Verify connection and permissions (Prerequisite)
+2. `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` - Search for existing contacts to avoid duplicates (Prerequisite)
+3. `HUBSPOT_READ_A_CRM_PROPERTY_BY_NAME` - Check property metadata for constrained values (Optional)
+4. `HUBSPOT_CREATE_CONTACT` - Create a single contact (Required)
+5. `HUBSPOT_CREATE_CONTACTS` - Batch create contacts up to 100 (Alternative)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_CONTACT`: `properties` object with `email`, `firstname`, `lastname`, `phone`, `company`
+- `HUBSPOT_CREATE_CONTACTS`: `inputs` array of `{properties}` objects, max 100 per batch
+- `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA`: `filterGroups` array with `{filters: [{propertyName, operator, value}]}`, `properties` array of fields to return
+
+**Pitfalls**:
+- Max 100 records per batch; chunk larger imports
+- 400 'Property values were not valid' if using incorrect property names or enum values
+- Always search before creating to avoid duplicates
+- Auth errors from GET_ACCOUNT_INFO mean all subsequent calls will fail
+
+### 2. Manage Companies
+
+**When to use**: User wants to create, search, or update company records
+
+**Tool sequence**:
+1. `HUBSPOT_SEARCH_COMPANIES` - Search existing companies (Prerequisite)
+2. `HUBSPOT_CREATE_COMPANIES` - Batch create companies, max 100 (Required)
+3. `HUBSPOT_UPDATE_COMPANIES` - Batch update existing companies (Alternative)
+4. `HUBSPOT_GET_COMPANY` - Get single company details (Optional)
+5. `HUBSPOT_BATCH_READ_COMPANIES_BY_PROPERTIES` - Bulk read companies by property values (Optional)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_COMPANIES`: `inputs` array of `{properties}` objects, max 100
+- `HUBSPOT_SEARCH_COMPANIES`: `filterGroups`, `properties`, `sorts`, `limit`, `after` (pagination cursor)
+
+**Pitfalls**:
+- Max 100 per batch; chunk larger sets
+- Store returned IDs immediately for downstream operations
+- Property values must match exact internal names, not display labels
+
+### 3. Manage Deals and Pipeline
+
+**When to use**: User wants to search deals, view pipeline stages, or track deal progress
+
+**Tool sequence**:
+1. `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` - Map pipeline and stage IDs/names (Prerequisite)
+2. `HUBSPOT_SEARCH_DEALS` - Search deals with filters (Required)
+3. `HUBSPOT_RETRIEVE_PIPELINE_STAGES` - Get stage details for one pipeline (Optional)
+4. `HUBSPOT_RETRIEVE_OWNERS` - Get owner/rep details (Optional)
+5. `HUBSPOT_GET_DEAL` - Get single deal details (Optional)
+6. `HUBSPOT_LIST_DEALS` - List all deals without filters (Fallback)
+
+**Key parameters**:
+- `HUBSPOT_SEARCH_DEALS`: `filterGroups` with filters on `pipeline`, `dealstage`, `createdate`, `closedate`, `hubspot_owner_id`; `properties`, `sorts`, `limit`, `after`
+- `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`: `objectType` set to `'deals'`
+
+**Pitfalls**:
+- Results nested under `response.data.results`; properties are often strings (amounts, dates)
+- Stage IDs may be readable strings or opaque numeric IDs; use `label` field for display
+- Filters must use internal property names (`pipeline`, `dealstage`, `createdate`), not display names
+- Paginate via `paging.next.after` until absent
+
+### 4. Search and Filter Tickets
+
+**When to use**: User wants to find support tickets by status, date, or criteria
+
+**Tool sequence**:
+1. `HUBSPOT_SEARCH_TICKETS` - Search with filterGroups (Required)
+2. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - Discover available property names (Fallback)
+3. `HUBSPOT_GET_TICKET` - Get single ticket details (Optional)
+4. `HUBSPOT_GET_TICKETS` - Bulk fetch tickets by IDs (Optional)
+
+**Key parameters**:
+- `HUBSPOT_SEARCH_TICKETS`: `filterGroups`, `properties` (only listed fields are returned), `sorts`, `limit`, `after`
+
+**Pitfalls**:
+- Incorrect `propertyName`/`operator` returns zero results without errors
+- Date filtering may require epoch-ms bounds; mixing formats causes mismatches
+- Only fields in the `properties` array are returned; missing ones break downstream logic
+- Use READ_ALL_PROPERTIES to discover exact internal property names
+
+### 5. Create and Manage Custom Properties
+
+**When to use**: User wants to add custom fields to CRM objects
+
+**Tool sequence**:
+1. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - List existing properties (Prerequisite)
+2. `HUBSPOT_READ_PROPERTY_GROUPS_FOR_OBJECT_TYPE` - List property groups (Optional)
+3. `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` - Create a single property (Required)
+4. `HUBSPOT_CREATE_BATCH_OF_PROPERTIES` - Batch create properties (Alternative)
+5. `HUBSPOT_UPDATE_SPECIFIC_CRM_PROPERTY` - Update existing property definition (Optional)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE`: `objectType`, `name`, `label`, `type` (string/number/date/enumeration), `fieldType`, `groupName`, `options` (for enumerations)
+
+**Pitfalls**:
+- Property names are immutable after creation; choose carefully
+- Enumeration options must be pre-defined with `value` and `label`
+- Group must exist before assigning properties to it
+
+## Common Patterns
+
+### ID Resolution
+- **Property display name → internal name**: Use `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE`
+- **Pipeline name → pipeline ID**: Use `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`
+- **Stage name → stage ID**: Extract from pipeline stages response
+- **Owner name → owner ID**: Use `HUBSPOT_RETRIEVE_OWNERS`
+
+### Pagination
+- Search endpoints use cursor-based pagination
+- Follow `paging.next.after` until absent
+- Typical limit: 100 records per page
+- Pass `after` value from previous response to get next page
+
+### Batch Operations
+- Most create/update endpoints support batching with max 100 records per call
+- For larger datasets, chunk into groups of 100
+- Store returned IDs from each batch before proceeding
+- Use batch endpoints (`CREATE_CONTACTS`, `CREATE_COMPANIES`, `UPDATE_COMPANIES`) instead of single-record endpoints for efficiency
+
+## Known Pitfalls
+
+- **Property names**: All search/filter endpoints use internal property names, NOT display labels. Always call `READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` to discover correct names
+- **Batch limits**: Max 100 records per batch operation. Larger sets must be chunked
+- **Response structure**: Search results are nested under `response.data.results` with properties as string values
+- **Date formats**: Date properties may be epoch-ms or ISO strings depending on endpoint. Parse defensively
+- **Immutable names**: Property names cannot be changed after creation. Plan naming conventions carefully
+- **Cursor pagination**: Use `paging.next.after` cursor, not page numbers. Continue until `after` is absent
+- **Duplicate prevention**: Always search before creating contacts/companies to avoid duplicates
+- **Auth verification**: Run `HUBSPOT_GET_ACCOUNT_INFO` first; auth failures cascade to all subsequent calls
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create contact | `HUBSPOT_CREATE_CONTACT` | `properties: {email, firstname, lastname}` |
+| Batch create contacts | `HUBSPOT_CREATE_CONTACTS` | `inputs: [{properties}]` (max 100) |
+| Search contacts | `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` | `filterGroups, properties, limit, after` |
+| Create companies | `HUBSPOT_CREATE_COMPANIES` | `inputs: [{properties}]` (max 100) |
+| Search companies | `HUBSPOT_SEARCH_COMPANIES` | `filterGroups, properties, after` |
+| Search deals | `HUBSPOT_SEARCH_DEALS` | `filterGroups, properties, after` |
+| Get pipelines | `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` | `objectType: 'deals'` |
+| Search tickets | `HUBSPOT_SEARCH_TICKETS` | `filterGroups, properties, after` |
+| 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 |
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/humanitix-automation/SKILL.md b/plugins/awesome-claude-skills/humanitix-automation/SKILL.md
new file mode 100644
index 0000000..d2803c2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/humanloop-automation/SKILL.md b/plugins/awesome-claude-skills/humanloop-automation/SKILL.md
new file mode 100644
index 0000000..2ba6388
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hunter-automation/SKILL.md b/plugins/awesome-claude-skills/hunter-automation/SKILL.md
new file mode 100644
index 0000000..44cd295
--- /dev/null
+++ b/plugins/awesome-claude-skills/hunter-automation/SKILL.md
@@ -0,0 +1,152 @@
+---
+name: Hunter Automation
+description: "Automate Hunter.io email intelligence -- search domains for email addresses, find specific contacts, verify email deliverability, manage leads, and monitor account usage -- using natural language through the Composio MCP integration."
+category: email-intelligence
+requires:
+ mcp:
+ - rube
+---
+
+# Hunter Automation
+
+Power your outreach with Hunter.io -- discover email addresses by domain, find specific people's emails, verify deliverability, save leads, and track your API usage -- all through natural language commands.
+
+**Toolkit docs:** [composio.dev/toolkits/hunter](https://composio.dev/toolkits/hunter)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Hunter.io account when prompted (API key authentication).
+3. Start issuing natural language commands to find and verify emails.
+
+---
+
+## Core Workflows
+
+### 1. Search Domain for Email Addresses
+Discover all publicly available email addresses for a given domain or company, with filtering by department, seniority, and type.
+
+**Tool:** `HUNTER_DOMAIN_SEARCH`
+
+**Example prompt:**
+> "Find all executive email addresses at stripe.com using Hunter"
+
+**Key parameters:**
+- `domain` -- Domain to search (e.g., "stripe.com"). Required if `company` not provided.
+- `company` -- Company name to search (e.g., "Stripe"). Required if `domain` not provided.
+- `type` -- Filter by "personal" or "generic" emails
+- `seniority` -- Filter by levels: "junior", "senior", "executive" (array)
+- `department` -- Filter by departments: "executive", "it", "finance", "sales", etc. (array)
+- `required_field` -- Require specific fields: "full_name", "position", "phone_number" (array)
+- `limit` -- Max results per request (1-100, default 10; free/basic plans limited to 10)
+- `offset` -- Skip results for pagination (default 0)
+
+---
+
+### 2. Find a Specific Person's Email
+Infer the most likely email address for a person given their name and domain or company.
+
+**Tool:** `HUNTER_EMAIL_FINDER`
+
+**Example prompt:**
+> "Find the email for Alexis Ohanian at reddit.com using Hunter"
+
+**Key parameters:**
+- `domain` -- Target domain (e.g., "reddit.com"). Takes precedence over `company`.
+- `company` -- Company name (e.g., "Reddit"). Used if domain not provided.
+- Name (one of these combinations required):
+ - `first_name` + `last_name` (e.g., "Alexis" + "Ohanian")
+ - `full_name` (e.g., "Alexis Ohanian")
+- `max_duration` -- Max request duration in seconds (3-20, default 10). Longer durations yield more accurate results.
+
+---
+
+### 3. Verify Email Deliverability
+Check whether an email address is valid, deliverable, and safe to send to.
+
+**Tool:** `HUNTER_EMAIL_VERIFIER`
+
+**Example prompt:**
+> "Verify if john.doe@example.com is a valid email address"
+
+**Key parameters:**
+- `email` (required) -- The email address to verify (e.g., "john.doe@example.com")
+
+**Response includes:** verification status, deliverability score, MX record validation, and risk assessment.
+
+---
+
+### 4. Get Email Volume Estimates
+Check how many email addresses Hunter has for a domain or company -- this call is free and does not consume API credits.
+
+**Tool:** `HUNTER_EMAIL_COUNT`
+
+**Example prompt:**
+> "How many email addresses does Hunter have for stripe.com?"
+
+**Key parameters:**
+- `domain` -- Domain to query (e.g., "stripe.com"). Required if `company` not provided.
+- `company` -- Company name (min 3 characters). Required if `domain` not provided.
+- `type` -- Filter count by "personal" or "generic" emails
+
+**Returns:** Total count with breakdowns by type, department, and seniority level.
+
+---
+
+### 5. Save and Manage Leads
+Create or update leads by email in a single upsert call -- no need to check existence first.
+
+**Tool:** `HUNTER_UPSERT_LEAD`
+
+**Example prompt:**
+> "Save john@stripe.com as a lead in Hunter with name John Doe, position CTO"
+
+**Key parameters:**
+- `email` -- Lead's email address (primary identifier for upsert)
+- Name, position, company, and other lead metadata
+
+---
+
+### 6. Check Account Usage and Limits
+Review your Hunter account plan details, remaining searches, and verification quotas before running bulk operations.
+
+**Tool:** `HUNTER_ACCOUNT_INFORMATION`
+
+**Example prompt:**
+> "How many Hunter API searches do I have left this month?"
+
+**Key parameters:** None required.
+
+---
+
+## Known Pitfalls
+
+- **HTTP 401 means invalid credentials**: `authentication_failed` errors indicate an invalid or expired API key. Fix before attempting bulk operations.
+- **Email counts are estimates**: `HUNTER_EMAIL_COUNT` returns approximate numbers for sizing and prioritization, not guaranteed retrievable email counts.
+- **Domain search uses offset pagination**: `HUNTER_DOMAIN_SEARCH` paginates via `limit`/`offset`. Do not assume the first page is complete -- continue fetching until results are empty or you hit a cap.
+- **Empty results are not errors**: `HUNTER_DOMAIN_SEARCH` can return `emails: []` with no error. Treat as "no data found" and continue, rather than retrying as a failure.
+- **Verification status nuances**: `accept_all` or `risky` statuses from `HUNTER_EMAIL_VERIFIER` indicate uncertainty. Exclude these from strict deliverability workflows or handle them separately.
+- **Free/basic plan limits**: Free and basic plans limit `HUNTER_DOMAIN_SEARCH` to 10 results per request. Higher limits require a paid plan.
+- **Domain format matters**: Use bare domains like "stripe.com" -- do not include protocol ("https://") or "www." prefix.
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Required Params |
+|---|---|---|
+| Search domain emails | `HUNTER_DOMAIN_SEARCH` | `domain` or `company` |
+| Find person's email | `HUNTER_EMAIL_FINDER` | Name + (`domain` or `company`) |
+| Verify email | `HUNTER_EMAIL_VERIFIER` | `email` |
+| Get email count | `HUNTER_EMAIL_COUNT` | `domain` or `company` |
+| Save/update lead | `HUNTER_UPSERT_LEAD` | `email` |
+| Check account | `HUNTER_ACCOUNT_INFORMATION` | None |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/hypeauditor-automation/SKILL.md b/plugins/awesome-claude-skills/hypeauditor-automation/SKILL.md
new file mode 100644
index 0000000..6437e5d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hyperbrowser-automation/SKILL.md b/plugins/awesome-claude-skills/hyperbrowser-automation/SKILL.md
new file mode 100644
index 0000000..660aa07
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hyperise-automation/SKILL.md b/plugins/awesome-claude-skills/hyperise-automation/SKILL.md
new file mode 100644
index 0000000..1dc6e5c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/hystruct-automation/SKILL.md b/plugins/awesome-claude-skills/hystruct-automation/SKILL.md
new file mode 100644
index 0000000..d318a8c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/icims-talent-cloud-automation/SKILL.md b/plugins/awesome-claude-skills/icims-talent-cloud-automation/SKILL.md
new file mode 100644
index 0000000..58b4659
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/icypeas-automation/SKILL.md b/plugins/awesome-claude-skills/icypeas-automation/SKILL.md
new file mode 100644
index 0000000..1f2eff7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/idea-scale-automation/SKILL.md b/plugins/awesome-claude-skills/idea-scale-automation/SKILL.md
new file mode 100644
index 0000000..6bd7ca0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/identitycheck-automation/SKILL.md b/plugins/awesome-claude-skills/identitycheck-automation/SKILL.md
new file mode 100644
index 0000000..ddf1d21
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ignisign-automation/SKILL.md b/plugins/awesome-claude-skills/ignisign-automation/SKILL.md
new file mode 100644
index 0000000..47592dd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/imagekit-io-automation/SKILL.md b/plugins/awesome-claude-skills/imagekit-io-automation/SKILL.md
new file mode 100644
index 0000000..1f860dd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/imgbb-automation/SKILL.md b/plugins/awesome-claude-skills/imgbb-automation/SKILL.md
new file mode 100644
index 0000000..9ac19f7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/imgix-automation/SKILL.md b/plugins/awesome-claude-skills/imgix-automation/SKILL.md
new file mode 100644
index 0000000..8f8a375
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/influxdb-cloud-automation/SKILL.md b/plugins/awesome-claude-skills/influxdb-cloud-automation/SKILL.md
new file mode 100644
index 0000000..dc9e9ed
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/insighto-ai-automation/SKILL.md b/plugins/awesome-claude-skills/insighto-ai-automation/SKILL.md
new file mode 100644
index 0000000..442c63e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/instacart-automation/SKILL.md b/plugins/awesome-claude-skills/instacart-automation/SKILL.md
new file mode 100644
index 0000000..52c9a8e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/instagram-automation/SKILL.md b/plugins/awesome-claude-skills/instagram-automation/SKILL.md
new file mode 100644
index 0000000..91522f6
--- /dev/null
+++ b/plugins/awesome-claude-skills/instagram-automation/SKILL.md
@@ -0,0 +1,197 @@
+---
+name: instagram-automation
+description: "Automate Instagram tasks via Rube MCP (Composio): create posts, carousels, manage media, get insights, and publishing limits. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Instagram Automation via Rube MCP
+
+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)
+- Active Instagram connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `instagram`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+- Instagram Business or Creator account required (personal accounts not supported)
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `instagram`
+3. If connection is not ACTIVE, follow the returned auth link to complete Instagram/Facebook OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create a Single Image/Video Post
+
+**When to use**: User wants to publish a single photo or video to Instagram
+
+**Tool sequence**:
+1. `INSTAGRAM_GET_USER_INFO` - Get Instagram user ID [Prerequisite]
+2. `INSTAGRAM_CREATE_MEDIA_CONTAINER` - Create a media container with the image/video URL [Required]
+3. `INSTAGRAM_GET_POST_STATUS` - Check if the media container is ready [Optional]
+4. `INSTAGRAM_CREATE_POST` or `INSTAGRAM_POST_IG_USER_MEDIA_PUBLISH` - Publish the container [Required]
+
+**Key parameters**:
+- `image_url`: Public URL of the image to post
+- `video_url`: Public URL of the video to post
+- `caption`: Post caption text
+- `ig_user_id`: Instagram Business account user ID
+
+**Pitfalls**:
+- Media URLs must be publicly accessible; private/authenticated URLs will fail
+- Video containers may take time to process; poll GET_POST_STATUS before publishing
+- Caption supports hashtags and mentions but has a 2200 character limit
+- Publishing a container that is not yet finished processing returns an error
+
+### 2. Create a Carousel Post
+
+**When to use**: User wants to publish multiple images/videos in a single carousel post
+
+**Tool sequence**:
+1. `INSTAGRAM_CREATE_MEDIA_CONTAINER` - Create individual containers for each media item [Required, repeat per item]
+2. `INSTAGRAM_CREATE_CAROUSEL_CONTAINER` - Create the carousel container referencing all media containers [Required]
+3. `INSTAGRAM_GET_POST_STATUS` - Check carousel container readiness [Optional]
+4. `INSTAGRAM_POST_IG_USER_MEDIA_PUBLISH` - Publish the carousel [Required]
+
+**Key parameters**:
+- `children`: Array of media container IDs for the carousel
+- `caption`: Carousel post caption
+- `ig_user_id`: Instagram Business account user ID
+
+**Pitfalls**:
+- Carousels require 2-10 media items; fewer or more will fail
+- Each child container must be created individually before the carousel container
+- All child containers must be fully processed before creating the carousel
+- Mixed media (images + videos) is supported in carousels
+
+### 3. Get Media and Insights
+
+**When to use**: User wants to view their posts or analyze post performance
+
+**Tool sequence**:
+1. `INSTAGRAM_GET_IG_USER_MEDIA` or `INSTAGRAM_GET_USER_MEDIA` - List user's media [Required]
+2. `INSTAGRAM_GET_IG_MEDIA` - Get details for a specific post [Optional]
+3. `INSTAGRAM_GET_POST_INSIGHTS` or `INSTAGRAM_GET_IG_MEDIA_INSIGHTS` - Get metrics for a post [Optional]
+4. `INSTAGRAM_GET_USER_INSIGHTS` - Get account-level insights [Optional]
+
+**Key parameters**:
+- `ig_user_id`: Instagram Business account user ID
+- `media_id`: ID of the specific media post
+- `metric`: Metrics to retrieve (e.g., impressions, reach, engagement)
+- `period`: Time period for insights (e.g., day, week, lifetime)
+
+**Pitfalls**:
+- Insights are only available for Business/Creator accounts
+- Some metrics require minimum follower counts
+- Insight data may have a delay of up to 48 hours
+- The `period` parameter must match the metric type
+
+### 4. Check Publishing Limits
+
+**When to use**: User wants to verify they can publish before attempting a post
+
+**Tool sequence**:
+1. `INSTAGRAM_GET_IG_USER_CONTENT_PUBLISHING_LIMIT` - Check remaining publishing quota [Required]
+
+**Key parameters**:
+- `ig_user_id`: Instagram Business account user ID
+
+**Pitfalls**:
+- Instagram enforces a 25 posts per 24-hour rolling window limit
+- Publishing limit resets on a rolling basis, not at midnight
+- Check limits before bulk posting operations to avoid failures
+
+### 5. Get Media Comments and Children
+
+**When to use**: User wants to view comments on a post or children of a carousel
+
+**Tool sequence**:
+1. `INSTAGRAM_GET_IG_MEDIA_COMMENTS` - List comments on a media post [Required]
+2. `INSTAGRAM_GET_IG_MEDIA_CHILDREN` - List children of a carousel post [Optional]
+
+**Key parameters**:
+- `media_id`: ID of the media post
+- `ig_media_id`: Alternative media ID parameter
+
+**Pitfalls**:
+- Comments may be paginated; follow pagination cursors for complete results
+- Carousel children are returned as individual media objects
+- Comment moderation settings on the account affect what is returned
+
+## Common Patterns
+
+### ID Resolution
+
+**Instagram User ID**:
+```
+1. Call INSTAGRAM_GET_USER_INFO
+2. Extract ig_user_id from response
+3. Use in all subsequent API calls
+```
+
+**Media Container Status Check**:
+```
+1. Call INSTAGRAM_CREATE_MEDIA_CONTAINER
+2. Extract container_id from response
+3. Poll INSTAGRAM_GET_POST_STATUS with container_id
+4. Wait until status is 'FINISHED' before publishing
+```
+
+### Two-Phase Publishing
+
+- Phase 1: Create media container(s) with content URLs
+- Phase 2: Publish the container after it finishes processing
+- Always check container status between phases for video content
+- For carousels, all children must complete Phase 1 before creating the carousel container
+
+## Known Pitfalls
+
+**Media URLs**:
+- All image/video URLs must be publicly accessible HTTPS URLs
+- URLs behind authentication, CDN restrictions, or that require cookies will fail
+- Temporary URLs (pre-signed S3, etc.) may expire before processing completes
+
+**Rate Limits**:
+- 25 posts per 24-hour rolling window
+- API rate limits apply separately from publishing limits
+- Implement exponential backoff for 429 responses
+
+**Account Requirements**:
+- Only Business or Creator Instagram accounts are supported
+- Personal accounts cannot use the Instagram Graph API
+- The account must be connected to a Facebook Page
+
+**Response Parsing**:
+- Media IDs are numeric strings
+- Insights data may be nested under different response keys
+- Pagination uses cursor-based tokens
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Get user info | INSTAGRAM_GET_USER_INFO | (none) |
+| Create media container | INSTAGRAM_CREATE_MEDIA_CONTAINER | image_url/video_url, caption |
+| Create carousel | INSTAGRAM_CREATE_CAROUSEL_CONTAINER | children, caption |
+| Publish post | INSTAGRAM_CREATE_POST | ig_user_id, creation_id |
+| Publish media | INSTAGRAM_POST_IG_USER_MEDIA_PUBLISH | ig_user_id, creation_id |
+| Check post status | INSTAGRAM_GET_POST_STATUS | ig_container_id |
+| List user media | INSTAGRAM_GET_IG_USER_MEDIA | ig_user_id |
+| Get media details | INSTAGRAM_GET_IG_MEDIA | ig_media_id |
+| Get post insights | INSTAGRAM_GET_POST_INSIGHTS | media_id, metric |
+| Get user insights | INSTAGRAM_GET_USER_INSIGHTS | ig_user_id, metric, period |
+| 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/plugins/awesome-claude-skills/instantly-automation/SKILL.md b/plugins/awesome-claude-skills/instantly-automation/SKILL.md
new file mode 100644
index 0000000..6df7c47
--- /dev/null
+++ b/plugins/awesome-claude-skills/instantly-automation/SKILL.md
@@ -0,0 +1,171 @@
+---
+name: Instantly Automation
+description: "Automate Instantly cold email outreach -- manage campaigns, sending accounts, lead lists, bulk lead imports, and campaign analytics -- using natural language through the Composio MCP integration."
+category: email-outreach
+requires:
+ mcp:
+ - rube
+---
+
+# Instantly Automation
+
+Automate your cold email outreach with Instantly -- create and manage campaigns with multi-step sequences, configure sending schedules, import leads in bulk, manage sending accounts, and track campaign performance -- all through natural language commands.
+
+**Toolkit docs:** [composio.dev/toolkits/instantly](https://composio.dev/toolkits/instantly)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Instantly account when prompted (API key authentication).
+3. Start issuing natural language commands to manage your outreach campaigns.
+
+---
+
+## Core Workflows
+
+### 1. List Sending Accounts
+Retrieve all email accounts configured in your Instantly workspace, with filtering by status and provider.
+
+**Tool:** `INSTANTLY_LIST_ACCOUNTS`
+
+**Example prompt:**
+> "Show all active sending accounts in my Instantly workspace"
+
+**Key parameters:**
+- `status` -- Filter by status: `1` (Active), `2` (Paused), `-1` (Connection Error), `-2` (Soft Bounce Error), `-3` (Sending Error)
+- `provider_code` -- Filter by provider: `1` (Custom IMAP/SMTP), `2` (Google), `3` (Microsoft), `4` (AWS)
+- `search` -- Search by email substring or domain
+- `limit` -- Max items (1-100)
+- `starting_after` -- Pagination cursor from previous response
+- `tag_ids` -- Comma-separated tag UUIDs
+
+---
+
+### 2. Create a Campaign
+Launch a new outreach campaign with scheduling, email sequences, A/B testing variants, and sending configuration.
+
+**Tool:** `INSTANTLY_CREATE_CAMPAIGN`
+
+**Example prompt:**
+> "Create an Instantly campaign called 'Q1 Outreach' that sends Monday-Friday 9am-5pm Central time with a 3-step email sequence"
+
+**Key parameters:**
+- `name` (required) -- Campaign name
+- `campaign_schedule` (required) -- Schedule configuration:
+ - `schedules` (required) -- Array of schedule objects, each with:
+ - `name` -- Schedule name
+ - `timing` -- `{from: "09:00", to: "17:00"}` (HH:mm format)
+ - `days` -- Map of day index strings "0" (Sun) to "6" (Sat) to booleans
+ - `timezone` -- Supported values include "America/Chicago", "America/Detroit", "America/Boise", "America/Anchorage"
+ - `start_date` / `end_date` -- ISO 8601 dates
+- `email_list` -- Array of sending account email addresses (must be pre-configured accounts; use `INSTANTLY_LIST_ACCOUNTS` to discover valid addresses)
+- `sequences` -- Array (only first element used) containing:
+ - `steps` -- Array of step objects with:
+ - `type` -- Must be "email"
+ - `delay` -- Days before NEXT email (integer, min 0)
+ - `variants` -- Array of `{subject, body}` objects for A/B testing
+- `daily_limit` -- Daily sending cap
+- `email_gap` -- Minutes between emails
+- `stop_on_reply` -- Stop campaign when lead replies (boolean)
+- `stop_on_auto_reply` -- Stop on auto-replies (boolean)
+- `open_tracking` / `link_tracking` -- Enable tracking (booleans)
+
+**Timezone notes:**
+- Verified working: "America/Chicago" (Central), "America/Detroit" (Eastern), "America/Boise" (Mountain)
+- Auto-mapped: "America/New_York" maps to "America/Detroit", "America/Denver" maps to "America/Boise"
+- NOT supported: "America/Los_Angeles", "US/Pacific" -- use "America/Anchorage" or "America/Dawson" as alternatives
+
+---
+
+### 3. Update Campaign Settings
+Modify an existing campaign's schedule, sending limits, sequences, or tracking settings.
+
+**Tool:** `INSTANTLY_UPDATE_CAMPAIGN`
+
+**Example prompt:**
+> "Update my Instantly campaign to increase the daily limit to 100 and enable open tracking"
+
+**Key parameters:**
+- `id` (required) -- Campaign UUID
+- Any combination of: `name`, `campaign_schedule`, `email_list`, `sequences`, `daily_limit`, `email_gap`, `stop_on_reply`, `open_tracking`, `link_tracking`, etc.
+- Set any parameter to `null` to unset it
+
+---
+
+### 4. Manage Lead Lists and Bulk Import
+Create dedicated lead lists and import prospects in bulk for campaign targeting.
+
+**Tools:** `INSTANTLY_CREATE_LEAD_LIST`, `INSTANTLY_ADD_LEADS_BULK`
+
+**Example prompt:**
+> "Create a lead list called 'Q1 Prospects' and add 50 leads to my Instantly campaign"
+
+**Key parameters for creating lead lists:**
+- List name and configuration
+
+**Key parameters for bulk lead import:**
+- Campaign or list ID to import into
+- Array of lead objects with email and metadata
+- Duplicate handling options
+- Lead verification settings
+
+---
+
+### 5. Review Campaign Details
+Retrieve full campaign configuration to verify settings, inspect sequences, or prepare for updates.
+
+**Tool:** `INSTANTLY_GET_CAMPAIGN`
+
+**Example prompt:**
+> "Show me the full details of my Instantly campaign"
+
+**Key parameters:**
+- `id` (required) -- Campaign UUID
+
+---
+
+### 6. List All Campaigns
+Enumerate all campaigns in your workspace with optional filters and pagination.
+
+**Tool:** `INSTANTLY_LIST_CAMPAIGNS`
+
+**Example prompt:**
+> "List all my Instantly campaigns"
+
+**Key parameters:**
+- Optional filters and pagination parameters
+
+---
+
+## Known Pitfalls
+
+- **Timezone support is limited**: The Instantly API accepts a restricted set of timezone strings. Pacific Time ("America/Los_Angeles") is NOT supported. Use "America/Anchorage" (UTC-9/UTC-8) or "America/Dawson" (UTC-7 year-round) as alternatives.
+- **Invalid schedule payloads cause 400 errors**: A malformed `campaign_schedule` (missing `days`, `from`, `to`, or `schedules`) triggers HTTP 400. Repeated 400s indicate payload issues, not transient failures.
+- **Sequences must be complete**: Each sequence step requires a valid `type` ("email"), `delay`, and at least one variant with both `subject` and `body`. Incomplete variants block campaign creation.
+- **Only first sequence element is used**: The API only processes `sequences[0]`. Additional sequences are ignored.
+- **email_list must reference existing accounts**: The `email_list` field requires email addresses of pre-configured sending accounts in your Instantly workspace, not arbitrary recipient addresses. Always use `INSTANTLY_LIST_ACCOUNTS` to discover valid sending addresses.
+- **401 scope errors on campaign creation**: Campaign creation can fail with "Invalid scope. Required: campaigns:create". Update your API key permissions before retrying writes.
+- **Read-back fields may differ**: Field names in `INSTANTLY_GET_CAMPAIGN` responses may differ from create payloads (e.g., `timing.from_` vs `timing.from`). Parse defensively.
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Required Params |
+|---|---|---|
+| List sending accounts | `INSTANTLY_LIST_ACCOUNTS` | None (optional filters) |
+| Create campaign | `INSTANTLY_CREATE_CAMPAIGN` | `name`, `campaign_schedule` |
+| Update campaign | `INSTANTLY_UPDATE_CAMPAIGN` | `id` |
+| Get campaign details | `INSTANTLY_GET_CAMPAIGN` | `id` |
+| List campaigns | `INSTANTLY_LIST_CAMPAIGNS` | None (optional filters) |
+| Create lead list | `INSTANTLY_CREATE_LEAD_LIST` | List name |
+| Bulk import leads | `INSTANTLY_ADD_LEADS_BULK` | Campaign/list ID, leads |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/intelliprint-automation/SKILL.md b/plugins/awesome-claude-skills/intelliprint-automation/SKILL.md
new file mode 100644
index 0000000..6ec88fb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/intercom-automation/SKILL.md b/plugins/awesome-claude-skills/intercom-automation/SKILL.md
new file mode 100644
index 0000000..97edb8a
--- /dev/null
+++ b/plugins/awesome-claude-skills/intercom-automation/SKILL.md
@@ -0,0 +1,253 @@
+---
+name: intercom-automation
+description: "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Intercom Automation via Rube MCP
+
+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)
+- Active Intercom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`
+3. If connection is not ACTIVE, follow the returned auth link to complete Intercom OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Conversations
+
+**When to use**: User wants to create, list, search, or manage support conversations
+
+**Tool sequence**:
+1. `INTERCOM_LIST_ALL_ADMINS` - Get admin IDs for assignment [Prerequisite]
+2. `INTERCOM_LIST_CONVERSATIONS` - List all conversations [Optional]
+3. `INTERCOM_SEARCH_CONVERSATIONS` - Search with filters [Optional]
+4. `INTERCOM_GET_CONVERSATION` - Get conversation details [Optional]
+5. `INTERCOM_CREATE_CONVERSATION` - Create a new conversation [Optional]
+
+**Key parameters**:
+- `from`: Object with `type` ('user'/'lead') and `id` for conversation creator
+- `body`: Message body (HTML supported)
+- `id`: Conversation ID for retrieval
+- `query`: Search query object with `field`, `operator`, `value`
+
+**Pitfalls**:
+- CREATE_CONVERSATION requires a contact (user/lead) as the `from` field, not an admin
+- Conversation bodies support HTML; plain text is auto-wrapped in `` tags
+- Search query uses structured filter objects, not free-text search
+- Conversation IDs are numeric strings
+
+### 2. Reply and Manage Conversation State
+
+**When to use**: User wants to reply to, close, reopen, or assign conversations
+
+**Tool sequence**:
+1. `INTERCOM_GET_CONVERSATION` - Get current state [Prerequisite]
+2. `INTERCOM_REPLY_TO_CONVERSATION` - Add a reply [Optional]
+3. `INTERCOM_ASSIGN_CONVERSATION` - Assign to admin/team [Optional]
+4. `INTERCOM_CLOSE_CONVERSATION` - Close conversation [Optional]
+5. `INTERCOM_REOPEN_CONVERSATION` - Reopen closed conversation [Optional]
+
+**Key parameters**:
+- `conversation_id` / `id`: Conversation ID
+- `body`: Reply message body (HTML supported)
+- `type`: Reply type ('admin' or 'user')
+- `admin_id`: Admin ID for replies from admin, assignment, and close/reopen
+- `assignee_id`: Admin or team ID for assignment
+- `message_type`: 'comment' (default) or 'note' (internal)
+
+**Pitfalls**:
+- `admin_id` is REQUIRED for admin replies, close, reopen, and assignment operations
+- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN
+- Duplicate sends can occur on retry; implement idempotency checks
+- Internal notes use `message_type: 'note'`; visible only to workspace members
+- Closing requires an admin_id and optional body message
+
+### 3. Manage Contacts
+
+**When to use**: User wants to search, view, or manage contacts (users and leads)
+
+**Tool sequence**:
+1. `INTERCOM_SEARCH_CONTACTS` - Search contacts with filters [Required]
+2. `INTERCOM_GET_A_CONTACT` - Get specific contact [Optional]
+3. `INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID` - Look up by external ID [Optional]
+4. `INTERCOM_LIST_CONTACTS` - List all contacts [Optional]
+5. `INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT` - Get contact tags [Optional]
+6. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Get contact segments [Optional]
+7. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]
+
+**Key parameters**:
+- `contact_id`: Contact ID for retrieval
+- `external_id`: External system ID for lookup
+- `query`: Search filter object with `field`, `operator`, `value`
+- `pagination`: Object with `per_page` and `starting_after` cursor
+
+**Pitfalls**:
+- SEARCH_CONTACTS uses structured query filters, not free-text; format: `{field, operator, value}`
+- Supported operators: `=`, `!=`, `>`, `<`, `~` (contains), `!~` (not contains), `IN`, `NIN`
+- Contact types are 'user' (identified) or 'lead' (anonymous)
+- LIST_CONTACTS returns paginated results; use `starting_after` cursor for pagination
+- External IDs are case-sensitive
+
+### 4. Manage Admins and Teams
+
+**When to use**: User wants to list workspace admins or identify specific admins
+
+**Tool sequence**:
+1. `INTERCOM_LIST_ALL_ADMINS` - List all admins and teams [Required]
+2. `INTERCOM_IDENTIFY_AN_ADMIN` - Get specific admin details [Optional]
+
+**Key parameters**:
+- `admin_id`: Admin ID for identification
+
+**Pitfalls**:
+- LIST_ALL_ADMINS returns both admins and teams
+- Admin IDs are required for conversation replies, assignment, close, and reopen
+- Teams appear in the admins list with `type: 'team'`
+
+### 5. View Segments and Counts
+
+**When to use**: User wants to view segments or get aggregate counts
+
+**Tool sequence**:
+1. `INTERCOM_LIST_SEGMENTS` - List all segments [Optional]
+2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Segments for a contact [Optional]
+3. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Segments for a company [Optional]
+4. `INTERCOM_GET_COUNTS` - Get aggregate counts [Optional]
+
+**Key parameters**:
+- `contact_id`: Contact ID for segment lookup
+- `company_id`: Company ID for segment lookup
+- `type`: Count type ('conversation', 'company', 'user', 'tag', 'segment')
+- `count`: Sub-count type
+
+**Pitfalls**:
+- GET_COUNTS returns approximate counts, not exact numbers
+- Segment membership is computed; changes may not reflect immediately
+
+### 6. Manage Companies
+
+**When to use**: User wants to list companies or manage company-contact relationships
+
+**Tool sequence**:
+1. `INTERCOM_LIST_ALL_COMPANIES` - List all companies [Required]
+2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Get company segments [Optional]
+3. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]
+
+**Key parameters**:
+- `company_id`: Company ID
+- `contact_id`: Contact ID for detachment
+- `page`: Page number for pagination
+- `per_page`: Results per page
+
+**Pitfalls**:
+- Company-contact relationships are managed through contact endpoints
+- DETACH_A_CONTACT removes the contact-company association, not the contact itself
+
+## Common Patterns
+
+### Search Query Filters
+
+**Single filter**:
+```json
+{
+ "field": "email",
+ "operator": "=",
+ "value": "user@example.com"
+}
+```
+
+**Multiple filters (AND)**:
+```json
+{
+ "operator": "AND",
+ "value": [
+ {"field": "role", "operator": "=", "value": "user"},
+ {"field": "created_at", "operator": ">", "value": 1672531200}
+ ]
+}
+```
+
+**Supported fields for contacts**: email, name, role, created_at, updated_at, signed_up_at, last_seen_at, external_id
+
+**Supported fields for conversations**: created_at, updated_at, source.type, state, open, read
+
+### Pagination
+
+- Most list endpoints use cursor-based pagination
+- Check response for `pages.next` with `starting_after` cursor
+- Pass cursor in `pagination.starting_after` for next page
+- Continue until `pages.next` is null
+
+### Admin ID Resolution
+
+```
+1. Call INTERCOM_LIST_ALL_ADMINS to get all admins
+2. Find the desired admin by name or email
+3. Use admin.id for replies, assignments, and state changes
+```
+
+## Known Pitfalls
+
+**Admin ID Requirement**:
+- Admin ID is required for: reply (as admin), assign, close, reopen
+- Always resolve admin IDs first with LIST_ALL_ADMINS
+
+**HTML Content**:
+- Conversation bodies are HTML
+- Plain text is auto-wrapped in paragraph tags
+- Sanitize HTML input to prevent rendering issues
+
+**Idempotency**:
+- Replies and conversation creation are not idempotent
+- Duplicate sends can occur on retry or timeout
+- Track message IDs to prevent duplicates
+
+**Rate Limits**:
+- Default: ~1000 requests per minute (varies by plan)
+- 429 responses include rate limit headers
+- Implement exponential backoff for retries
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List conversations | INTERCOM_LIST_CONVERSATIONS | (pagination) |
+| Search conversations | INTERCOM_SEARCH_CONVERSATIONS | query |
+| Get conversation | INTERCOM_GET_CONVERSATION | id |
+| Create conversation | INTERCOM_CREATE_CONVERSATION | from, body |
+| Reply to conversation | INTERCOM_REPLY_TO_CONVERSATION | conversation_id, body, admin_id |
+| Assign conversation | INTERCOM_ASSIGN_CONVERSATION | conversation_id, admin_id, assignee_id |
+| Close conversation | INTERCOM_CLOSE_CONVERSATION | id, admin_id |
+| Reopen conversation | INTERCOM_REOPEN_CONVERSATION | id, admin_id |
+| Search contacts | INTERCOM_SEARCH_CONTACTS | query |
+| Get contact | INTERCOM_GET_A_CONTACT | contact_id |
+| Contact by external ID | INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID | external_id |
+| List contacts | INTERCOM_LIST_CONTACTS | (pagination) |
+| Contact tags | INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT | contact_id |
+| Contact segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT | contact_id |
+| Detach contact | INTERCOM_DETACH_A_CONTACT | contact_id, company_id |
+| List admins | INTERCOM_LIST_ALL_ADMINS | (none) |
+| Identify admin | INTERCOM_IDENTIFY_AN_ADMIN | admin_id |
+| List segments | INTERCOM_LIST_SEGMENTS | (none) |
+| 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/plugins/awesome-claude-skills/interzoid-automation/SKILL.md b/plugins/awesome-claude-skills/interzoid-automation/SKILL.md
new file mode 100644
index 0000000..4708b84
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ip2location-automation/SKILL.md b/plugins/awesome-claude-skills/ip2location-automation/SKILL.md
new file mode 100644
index 0000000..29772cd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ip2location-io-automation/SKILL.md b/plugins/awesome-claude-skills/ip2location-io-automation/SKILL.md
new file mode 100644
index 0000000..002f18a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ip2proxy-automation/SKILL.md b/plugins/awesome-claude-skills/ip2proxy-automation/SKILL.md
new file mode 100644
index 0000000..cd3b59d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ip2whois-automation/SKILL.md b/plugins/awesome-claude-skills/ip2whois-automation/SKILL.md
new file mode 100644
index 0000000..daa5060
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ipdata-co-automation/SKILL.md b/plugins/awesome-claude-skills/ipdata-co-automation/SKILL.md
new file mode 100644
index 0000000..47076a2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ipinfo-io-automation/SKILL.md b/plugins/awesome-claude-skills/ipinfo-io-automation/SKILL.md
new file mode 100644
index 0000000..09d0c38
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/iqair-airvisual-automation/SKILL.md b/plugins/awesome-claude-skills/iqair-airvisual-automation/SKILL.md
new file mode 100644
index 0000000..1171aab
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/jigsawstack-automation/SKILL.md b/plugins/awesome-claude-skills/jigsawstack-automation/SKILL.md
new file mode 100644
index 0000000..cc5c468
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/jira-automation/SKILL.md b/plugins/awesome-claude-skills/jira-automation/SKILL.md
new file mode 100644
index 0000000..d3554ef
--- /dev/null
+++ b/plugins/awesome-claude-skills/jira-automation/SKILL.md
@@ -0,0 +1,190 @@
+---
+name: jira-automation
+description: "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Jira Automation via Rube MCP
+
+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)
+- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`
+3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search and Filter Issues
+
+**When to use**: User wants to find issues using JQL or browse project issues
+
+**Tool sequence**:
+1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]
+2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]
+
+**Key parameters**:
+- `jql`: JQL query string (e.g., `project = PROJ AND status = "In Progress"`)
+- `maxResults`: Max results per page (default 50, max 100)
+- `startAt`: Pagination offset
+- `fields`: Array of field names to return
+- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE
+
+**Pitfalls**:
+- JQL field names are case-sensitive and must match Jira configuration
+- Custom fields use IDs like `customfield_10001`, not display names
+- Results are paginated; check `total` vs `startAt + maxResults` to continue
+
+### 2. Create and Edit Issues
+
+**When to use**: User wants to create new issues or update existing ones
+
+**Tool sequence**:
+1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]
+2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]
+3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]
+4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]
+5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]
+
+**Key parameters**:
+- `project`: Project key (e.g., 'PROJ')
+- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')
+- `summary`: Issue title
+- `description`: Issue description (Atlassian Document Format or plain text)
+- `issueIdOrKey`: Issue key for edits
+
+**Pitfalls**:
+- Issue types and required fields vary by project; use GET_FIELDS to check
+- Custom fields require exact field IDs, not display names
+- Description may need Atlassian Document Format (ADF) for rich content
+
+### 3. Manage Sprints and Boards
+
+**When to use**: User wants to work with agile boards, sprints, and backlogs
+
+**Tool sequence**:
+1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]
+2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]
+3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]
+4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]
+
+**Key parameters**:
+- `boardId`: Board ID from LIST_BOARDS
+- `sprintId`: Sprint ID for move operations
+- `name`: Sprint name for creation
+- `startDate`/`endDate`: Sprint dates in ISO format
+
+**Pitfalls**:
+- Boards and sprints are specific to Jira Software (not Jira Core)
+- Only one sprint can be active at a time per board
+
+### 4. Manage Comments
+
+**When to use**: User wants to add or view comments on issues
+
+**Tool sequence**:
+1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]
+2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]
+
+**Key parameters**:
+- `issueIdOrKey`: Issue key like 'PROJ-123'
+- `body`: Comment body (supports ADF for rich text)
+
+**Pitfalls**:
+- Comments support ADF (Atlassian Document Format) for formatting
+- Mentions use account IDs, not usernames
+
+### 5. Manage Projects and Users
+
+**When to use**: User wants to list projects, find users, or manage project roles
+
+**Tool sequence**:
+1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]
+2. `JIRA_GET_PROJECT` - Get project details [Optional]
+3. `JIRA_FIND_USERS` / `JIRA_GET_ALL_USERS` - Search for users [Optional]
+4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]
+5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]
+
+**Key parameters**:
+- `projectIdOrKey`: Project key
+- `query`: Search text for FIND_USERS
+- `roleId`: Role ID for role operations
+
+**Pitfalls**:
+- User operations use account IDs (not email or display name)
+- Project roles differ from global permissions
+
+## Common Patterns
+
+### JQL Syntax
+
+**Common operators**:
+- `project = "PROJ"` - Filter by project
+- `status = "In Progress"` - Filter by status
+- `assignee = currentUser()` - Current user's issues
+- `created >= -7d` - Created in last 7 days
+- `labels = "bug"` - Filter by label
+- `priority = High` - Filter by priority
+- `ORDER BY created DESC` - Sort results
+
+**Combinators**:
+- `AND` - Both conditions
+- `OR` - Either condition
+- `NOT` - Negate condition
+
+### Pagination
+
+- Use `startAt` and `maxResults` parameters
+- Check `total` in response to determine remaining pages
+- Continue until `startAt + maxResults >= total`
+
+## Known Pitfalls
+
+**Field Names**:
+- Custom fields use IDs like `customfield_10001`
+- Use JIRA_GET_FIELDS to discover field IDs and names
+- Field names in JQL may differ from API field names
+
+**Authentication**:
+- Jira Cloud uses account IDs, not usernames
+- Site URL must be configured correctly in the connection
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |
+| Get issue | JIRA_GET_ISSUE | issueIdOrKey |
+| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |
+| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |
+| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |
+| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |
+| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |
+| List projects | JIRA_GET_ALL_PROJECTS | (none) |
+| Get project | JIRA_GET_PROJECT | projectIdOrKey |
+| List boards | JIRA_LIST_BOARDS | (none) |
+| List sprints | JIRA_LIST_SPRINTS | boardId |
+| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |
+| Create sprint | JIRA_CREATE_SPRINT | name, boardId |
+| Find users | JIRA_FIND_USERS | query |
+| Get fields | JIRA_GET_FIELDS | (none) |
+| 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/plugins/awesome-claude-skills/jobnimbus-automation/SKILL.md b/plugins/awesome-claude-skills/jobnimbus-automation/SKILL.md
new file mode 100644
index 0000000..e4bf30c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/jotform-automation/SKILL.md b/plugins/awesome-claude-skills/jotform-automation/SKILL.md
new file mode 100644
index 0000000..b09f8f9
--- /dev/null
+++ b/plugins/awesome-claude-skills/jotform-automation/SKILL.md
@@ -0,0 +1,148 @@
+---
+name: Jotform Automation
+description: "Automate Jotform form listing, user management, activity history, folder organization, and plan inspection through natural language commands"
+requires:
+ mcp:
+ - rube
+---
+
+# Jotform Automation
+
+Automate Jotform workflows -- list and search forms, inspect user details, browse activity history, manage folders and labels, and check plan limits -- all through natural language.
+
+**Toolkit docs:** [composio.dev/toolkits/jotform](https://composio.dev/toolkits/jotform)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Connect your Jotform account when prompted (API key auth via Composio)
+3. Start issuing natural language commands for Jotform automation
+
+---
+
+## Core Workflows
+
+### 1. List and Search Forms
+
+Retrieve all forms created by the authenticated user with search, filtering, sorting, and pagination.
+
+**Tool:** `JOTFORM_GET_USER_FORMS`
+
+Key parameters:
+- `search` -- search query to filter forms by name or content
+- `limit` -- number of forms to return
+- `offset` -- offset for pagination
+- `orderby` -- field to order by
+- `sorting` -- sorting direction: `ASC` or `DESC`
+- `folder` -- filter by folder ID
+
+Example prompt:
+> "List all my Jotform forms that contain 'feedback' in the name, sorted by most recent"
+
+---
+
+### 2. Get User Account Details
+
+Retrieve details about the authenticated user including account type, usage statistics, and limits.
+
+**Tool:** `JOTFORM_GET_USER_DETAILS`
+
+No parameters required. Returns account info such as username, email, account type, form count, submission count, and usage limits.
+
+Example prompt:
+> "Show me my Jotform account details and current usage"
+
+---
+
+### 3. Browse Activity History
+
+Fetch user activity records for auditing, filtered by action type and date range.
+
+**Tool:** `JOTFORM_GET_USER_HISTORY`
+
+Key parameters:
+- `action` -- filter by action type (e.g., `formCreation`, `userLogin`, `formUpdate`, `apiKeyCreated`, `userLogout`)
+- `date` -- predefined date range: `lastWeek`, `lastMonth`, `last3Months`, `last6Months`, `lastYear`, `all`
+- `startDate` -- custom start date in `MM/DD/YYYY` format
+- `endDate` -- custom end date in `MM/DD/YYYY` format
+- `sortBy` -- sort order: `ASC` or `DESC`
+
+Example prompt:
+> "Show me all form creation activity from the last month, sorted newest first"
+
+---
+
+### 4. Manage Folders and Labels
+
+Browse the folder/label structure for organizing forms.
+
+**Tool:** `JOTFORM_GET_USER_FOLDERS`
+
+Key parameters:
+- `add_resources` -- set to `true` to include label resources (forms) in the response
+- `owner` -- owner username or workspace/team ID (conditionally required for some accounts)
+
+> Jotform has migrated from folders to labels. This tool uses the `GET /user/labels` endpoint.
+
+Example prompt:
+> "List all my Jotform folders with their forms included"
+
+---
+
+### 5. Check Plan Limits and Pricing
+
+Retrieve details about a specific Jotform system plan to understand limits and capabilities.
+
+**Tool:** `JOTFORM_GET_SYSTEM_PLAN`
+
+Key parameters:
+- `planName` -- the plan to inspect (required): `FREE`, `BRONZE`, `SILVER`, `GOLD`, or `PLATINUM`
+
+Example prompt:
+> "What are the limits on the Jotform GOLD plan?"
+
+---
+
+### 6. Full Form Management Workflow
+
+Combine tools for comprehensive form management:
+
+1. **Discover**: `JOTFORM_GET_USER_DETAILS` -- check account type and usage limits
+2. **Browse**: `JOTFORM_GET_USER_FORMS` -- list and search forms with filters
+3. **Organize**: `JOTFORM_GET_USER_FOLDERS` -- view folder structure with `add_resources=true`
+4. **Audit**: `JOTFORM_GET_USER_HISTORY` -- track form creation and modification activity
+5. **Plan**: `JOTFORM_GET_SYSTEM_PLAN` -- compare plan features before upgrading
+
+Example prompt:
+> "Show me my account usage, list my recent forms, and tell me if I'm close to my plan limits"
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| API key authentication | Jotform uses API key auth, not OAuth -- ensure valid API key is configured in the connection |
+| Folders migrated to labels | The folders endpoint now maps to Jotform's labels system; the API behavior may differ from legacy folder documentation |
+| Date format for history | Custom date filters use `MM/DD/YYYY` format (e.g., `01/15/2026`), not ISO 8601 |
+| Plan name must be exact | `planName` values are case-sensitive enum: `FREE`, `BRONZE`, `SILVER`, `GOLD`, `PLATINUM` |
+| Pagination is offset-based | Forms use `limit`/`offset` pagination, not cursor or page-based |
+| Owner field conditionally required | `JOTFORM_GET_USER_FOLDERS` may require the `owner` parameter for workspace/team accounts |
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Key Params |
+|--------|-----------|------------|
+| List forms | `JOTFORM_GET_USER_FORMS` | `search`, `limit`, `offset`, `orderby` |
+| Get user details | `JOTFORM_GET_USER_DETAILS` | (none) |
+| Activity history | `JOTFORM_GET_USER_HISTORY` | `action`, `date`, `startDate`, `endDate` |
+| List folders/labels | `JOTFORM_GET_USER_FOLDERS` | `add_resources`, `owner` |
+| Check plan | `JOTFORM_GET_SYSTEM_PLAN` | `planName` |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/jumpcloud-automation/SKILL.md b/plugins/awesome-claude-skills/jumpcloud-automation/SKILL.md
new file mode 100644
index 0000000..9abb4af
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/junglescout-automation/SKILL.md b/plugins/awesome-claude-skills/junglescout-automation/SKILL.md
new file mode 100644
index 0000000..86f7ceb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/kadoa-automation/SKILL.md b/plugins/awesome-claude-skills/kadoa-automation/SKILL.md
new file mode 100644
index 0000000..0838ea6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/kaggle-automation/SKILL.md b/plugins/awesome-claude-skills/kaggle-automation/SKILL.md
new file mode 100644
index 0000000..e43364d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/kaleido-automation/SKILL.md b/plugins/awesome-claude-skills/kaleido-automation/SKILL.md
new file mode 100644
index 0000000..e6243a6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/keap-automation/SKILL.md b/plugins/awesome-claude-skills/keap-automation/SKILL.md
new file mode 100644
index 0000000..eca259f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/keen-io-automation/SKILL.md b/plugins/awesome-claude-skills/keen-io-automation/SKILL.md
new file mode 100644
index 0000000..4eb43b4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/kickbox-automation/SKILL.md b/plugins/awesome-claude-skills/kickbox-automation/SKILL.md
new file mode 100644
index 0000000..00862ca
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/kit-automation/SKILL.md b/plugins/awesome-claude-skills/kit-automation/SKILL.md
new file mode 100644
index 0000000..36da0b4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/klaviyo-automation/SKILL.md b/plugins/awesome-claude-skills/klaviyo-automation/SKILL.md
new file mode 100644
index 0000000..d7e2a97
--- /dev/null
+++ b/plugins/awesome-claude-skills/klaviyo-automation/SKILL.md
@@ -0,0 +1,195 @@
+---
+name: klaviyo-automation
+description: "Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Klaviyo Automation via Rube MCP
+
+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)
+- Active Klaviyo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`
+3. If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Filter Campaigns
+
+**When to use**: User wants to browse, search, or filter marketing campaigns
+
+**Tool sequence**:
+1. `KLAVIYO_GET_CAMPAIGNS` - List campaigns with channel and status filters [Required]
+
+**Key parameters**:
+- `channel`: Campaign channel - 'email' or 'sms' (required by Klaviyo API)
+- `filter`: Additional filter string (e.g., `equals(status,"draft")`)
+- `sort`: Sort field with optional `-` prefix for descending (e.g., '-created_at', 'name')
+- `page_cursor`: Pagination cursor for next page
+- `include_archived`: Include archived campaigns (default: false)
+
+**Pitfalls**:
+- `channel` is required; omitting it can produce incomplete or unexpected results
+- Pagination is mandatory for full coverage; a single call returns only one page (default ~10)
+- Follow `page_cursor` until exhausted to get all campaigns
+- Status filtering via `filter` (e.g., `equals(status,"draft")`) can return mixed statuses; always validate `data[].attributes.status` client-side
+- Status strings are case-sensitive and can be compound (e.g., 'Cancelled: No Recipients')
+- Response shape is nested: `response.data.data` with status at `data[].attributes.status`
+
+### 2. Get Campaign Details
+
+**When to use**: User wants detailed information about a specific campaign
+
+**Tool sequence**:
+1. `KLAVIYO_GET_CAMPAIGNS` - Find campaign to get its ID [Prerequisite]
+2. `KLAVIYO_GET_CAMPAIGN` - Retrieve full campaign details [Required]
+
+**Key parameters**:
+- `campaign_id`: Campaign ID string (e.g., '01GDDKASAP8TKDDA2GRZDSVP4H')
+- `include_messages`: Include campaign messages in response
+- `include_tags`: Include tags in response
+
+**Pitfalls**:
+- Campaign IDs are alphanumeric strings, not numeric
+- `include_messages` and `include_tags` add related data to the response via Klaviyo's include mechanism
+- Campaign details include audiences, send strategy, tracking options, and scheduling info
+
+### 3. Inspect Campaign Messages
+
+**When to use**: User wants to view the email/SMS content of a campaign
+
+**Tool sequence**:
+1. `KLAVIYO_GET_CAMPAIGN` - Find campaign and its message IDs [Prerequisite]
+2. `KLAVIYO_GET_CAMPAIGN_MESSAGE` - Get message content details [Required]
+
+**Key parameters**:
+- `id`: Message ID string
+- `fields__campaign__message`: Sparse fieldset for message attributes (e.g., 'content.subject', 'content.from_email', 'content.body')
+- `fields__campaign`: Sparse fieldset for campaign attributes
+- `fields__template`: Sparse fieldset for template attributes
+- `include`: Related resources to include ('campaign', 'template')
+
+**Pitfalls**:
+- Message IDs are separate from campaign IDs; extract from campaign response
+- Sparse fieldset syntax uses dot notation for nested fields: 'content.subject', 'content.from_email'
+- Email messages have content fields: subject, preview_text, from_email, from_label, reply_to_email
+- SMS messages have content fields: body
+- Including 'template' provides the HTML/text content of the email
+
+### 4. Manage Campaign Tags
+
+**When to use**: User wants to view tags associated with campaigns for organization
+
+**Tool sequence**:
+1. `KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS` - Get tag IDs for a campaign [Required]
+
+**Key parameters**:
+- `id`: Campaign ID string
+
+**Pitfalls**:
+- Returns only tag IDs, not tag names/details
+- Tag IDs can be used with Klaviyo's tag endpoints for full details
+- Rate limit: 3/s burst, 60/m steady (stricter than other endpoints)
+
+### 5. Monitor Campaign Send Jobs
+
+**When to use**: User wants to check the status of a campaign send operation
+
+**Tool sequence**:
+1. `KLAVIYO_GET_CAMPAIGN_SEND_JOB` - Check send job status [Required]
+
+**Key parameters**:
+- `id`: Send job ID
+
+**Pitfalls**:
+- Send job IDs are returned when a campaign send is initiated
+- Job statuses indicate whether the send is queued, in progress, complete, or failed
+- Rate limit: 10/s burst, 150/m steady
+
+## Common Patterns
+
+### Campaign Discovery Pattern
+
+```
+1. Call KLAVIYO_GET_CAMPAIGNS with channel='email'
+2. Paginate through all results via page_cursor
+3. Filter by status client-side for accuracy
+4. Extract campaign IDs for detailed inspection
+```
+
+### Sparse Fieldset Pattern
+
+Klaviyo supports sparse fieldsets to reduce response size:
+```
+fields__campaign__message=['content.subject', 'content.from_email', 'send_times']
+fields__campaign=['name', 'status', 'send_time']
+fields__template=['name', 'html', 'text']
+```
+
+### Pagination
+
+- Klaviyo uses cursor-based pagination
+- Check response for `page_cursor` in the pagination metadata
+- Pass cursor as `page_cursor` in next request
+- Default page size is ~10 campaigns
+- Continue until no more cursor is returned
+
+### Filter Syntax
+
+```
+- equals(status,"draft") - Campaigns in draft status
+- equals(name,"Newsletter") - Campaign named "Newsletter"
+- greater-than(created_at,"2024-01-01T00:00:00Z") - Created after date
+```
+
+## Known Pitfalls
+
+**API Version**:
+- Klaviyo API uses versioned endpoints (e.g., v2024-07-15)
+- Response schemas may change between API versions
+- Tool responses follow the version configured in the Composio integration
+
+**Response Nesting**:
+- Data is nested: `response.data.data[].attributes`
+- Campaign status at `data[].attributes.status`
+- Mis-parsing the nesting yields empty or incorrect results
+- Always navigate through the full path defensively
+
+**Rate Limits**:
+- Burst: 10/s (3/s for tag endpoints)
+- Steady: 150/m (60/m for tag endpoints)
+- Required scope: campaigns:read
+- Implement backoff on 429 responses
+
+**Status Values**:
+- Status strings are case-sensitive
+- Compound statuses exist (e.g., 'Cancelled: No Recipients')
+- Server-side filtering may return mixed statuses; always validate client-side
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List campaigns | KLAVIYO_GET_CAMPAIGNS | channel, filter, sort, page_cursor |
+| Get campaign details | KLAVIYO_GET_CAMPAIGN | campaign_id, include_messages, include_tags |
+| 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/plugins/awesome-claude-skills/klipfolio-automation/SKILL.md b/plugins/awesome-claude-skills/klipfolio-automation/SKILL.md
new file mode 100644
index 0000000..63c93fd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ko-fi-automation/SKILL.md b/plugins/awesome-claude-skills/ko-fi-automation/SKILL.md
new file mode 100644
index 0000000..397c7db
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/kommo-automation/SKILL.md b/plugins/awesome-claude-skills/kommo-automation/SKILL.md
new file mode 100644
index 0000000..b19195a
--- /dev/null
+++ b/plugins/awesome-claude-skills/kommo-automation/SKILL.md
@@ -0,0 +1,163 @@
+---
+name: Kommo Automation
+description: "Automate Kommo CRM operations -- manage leads, pipelines, pipeline stages, tasks, and custom fields -- using natural language through the Composio MCP integration."
+category: crm
+requires:
+ mcp:
+ - rube
+---
+
+# Kommo Automation
+
+Manage your Kommo CRM sales pipeline -- list and filter leads, navigate pipeline stages, create and update deals, assign tasks, and work with custom fields -- all through natural language commands.
+
+**Toolkit docs:** [composio.dev/toolkits/kommo](https://composio.dev/toolkits/kommo)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Kommo account when prompted (OAuth authentication).
+3. Start issuing natural language commands to manage your CRM.
+
+---
+
+## Core Workflows
+
+### 1. Navigate Pipelines and Stages
+List all lead pipelines, then drill into specific pipeline stages to understand your sales funnel structure.
+
+**Tools:** `KOMMO_LIST_LEADS_PIPELINES`, `KOMMO_LIST_PIPELINE_STAGES`
+
+**Example prompt:**
+> "Show all my Kommo pipelines and the stages in my main sales pipeline"
+
+**Key parameters for List Pipelines:** None required.
+
+**Key parameters for List Stages:**
+- `pipeline_id` (required) -- The pipeline ID to list stages for
+- `with_description` -- Include stage descriptions in the response (boolean)
+
+---
+
+### 2. List and Filter Leads
+Retrieve leads with powerful filtering by pipeline, status, date ranges, responsible users, price, and more.
+
+**Tool:** `KOMMO_LIST_LEADS`
+
+**Example prompt:**
+> "Show all leads in pipeline 12345 created this week, sorted by newest first"
+
+**Key parameters:**
+- `query` -- Free-text search across all filled fields
+- `filter_pipeline_ids` -- Filter by pipeline IDs (array of integers)
+- `filter_status` -- Filter by status within a pipeline: `{"pipeline_id": 123, "status_id": 456}`
+- `filter_responsible_user_ids` -- Filter by assigned user IDs
+- `filter_names` -- Filter by lead names
+- `filter_price` -- Filter by deal value
+- `filter_created_at` -- Date range: `{"from": , "to": }`
+- `filter_updated_at` -- Date range for last update
+- `filter_closed_at` -- Date range for closure
+- `order_by_created_at` -- Sort: "asc" or "desc"
+- `order_by_updated_at` -- Sort by update date
+- `limit` -- Max 250 per page
+- `page` -- Page number for pagination
+- `with_params` -- Additional data: "contacts", "loss_reason", "catalog_elements", "source_id"
+
+---
+
+### 3. Create New Leads
+Add new deals to your Kommo pipeline with custom fields, tags, and pipeline placement.
+
+**Tool:** `KOMMO_CREATE_LEAD`
+
+**Example prompt:**
+> "Create a new lead called 'Acme Corp Deal' worth $50,000 in pipeline 12345"
+
+**Key parameters:**
+- `name` (required) -- Name of the lead/deal
+- `price` -- Deal value (integer)
+- `pipeline_id` -- Pipeline to add the lead to
+- `status_id` -- Stage within the pipeline (defaults to first stage of main pipeline)
+- `responsible_user_id` -- Assigned user ID
+- `custom_fields_values` -- Array of custom field value objects
+- `tags_to_add` -- Array of tags (by name or ID)
+- `created_by` -- User ID of creator (0 for robot)
+- `loss_reason_id` -- Reason for loss (if applicable)
+
+---
+
+### 4. Update Existing Leads
+Modify lead properties including name, price, pipeline stage, responsible user, tags, and custom fields.
+
+**Tool:** `KOMMO_UPDATE_LEAD`
+
+**Example prompt:**
+> "Move lead 789 to stage 456 in pipeline 123 and update the price to $75,000"
+
+**Key parameters:**
+- Lead ID (required)
+- Any combination of: `name`, `price`, `pipeline_id`, `status_id`, `responsible_user_id`, `tags_to_add`, `tags_to_delete`, `custom_fields_values`
+
+---
+
+### 5. Create Tasks
+Assign follow-up tasks linked to leads, contacts, or companies.
+
+**Tool:** `KOMMO_CREATE_TASK`
+
+**Example prompt:**
+> "Create a follow-up call task for lead 789 due tomorrow assigned to user 42"
+
+**Key parameters:**
+- Task text/description
+- Entity type and ID (lead, contact, company)
+- Responsible user ID
+- Due date (Unix timestamp)
+- Task type
+
+---
+
+### 6. Discover Custom Fields
+List all custom fields for leads, contacts, or companies to understand your CRM schema.
+
+**Tool:** `KOMMO_LIST_CUSTOM_FIELDS`
+
+**Example prompt:**
+> "What custom fields are available for leads in Kommo?"
+
+**Key parameters:**
+- Entity type (leads, contacts, companies)
+
+---
+
+## Known Pitfalls
+
+- **Date filters use Unix timestamps**: All date range filters (`filter_created_at`, `filter_updated_at`, `filter_closed_at`) require Unix timestamp format in `{"from": , "to": }` structure, not ISO8601 strings.
+- **Pipeline and stage IDs are required**: To filter leads by status, you need both `pipeline_id` and `status_id`. Always call `KOMMO_LIST_LEADS_PIPELINES` and `KOMMO_LIST_PIPELINE_STAGES` first to discover valid IDs.
+- **Max 250 leads per page**: The `limit` parameter caps at 250. For large datasets, implement pagination using the `page` parameter.
+- **Custom field values format**: Custom fields use a specific nested object format. Use `KOMMO_LIST_CUSTOM_FIELDS` to discover field IDs and expected value formats before setting values.
+- **Status filter requires both IDs**: The `filter_status` parameter requires both `pipeline_id` and `status_id` as a combined object -- you cannot filter by status alone.
+- **Created_by 0 means robot**: When setting `created_by` or `updated_by` to 0, the action is attributed to a robot/automation, not a human user.
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Required Params |
+|---|---|---|
+| List pipelines | `KOMMO_LIST_LEADS_PIPELINES` | None |
+| List pipeline stages | `KOMMO_LIST_PIPELINE_STAGES` | `pipeline_id` |
+| List leads | `KOMMO_LIST_LEADS` | None (optional filters) |
+| Create lead | `KOMMO_CREATE_LEAD` | `name` |
+| Update lead | `KOMMO_UPDATE_LEAD` | Lead ID |
+| Create task | `KOMMO_CREATE_TASK` | Task details |
+| List custom fields | `KOMMO_LIST_CUSTOM_FIELDS` | Entity type |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/kontent-ai-automation/SKILL.md b/plugins/awesome-claude-skills/kontent-ai-automation/SKILL.md
new file mode 100644
index 0000000..26bf3eb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/kraken-io-automation/SKILL.md b/plugins/awesome-claude-skills/kraken-io-automation/SKILL.md
new file mode 100644
index 0000000..c18b0d7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/l2s-automation/SKILL.md b/plugins/awesome-claude-skills/l2s-automation/SKILL.md
new file mode 100644
index 0000000..23bbdb2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/labs64-netlicensing-automation/SKILL.md b/plugins/awesome-claude-skills/labs64-netlicensing-automation/SKILL.md
new file mode 100644
index 0000000..78aee58
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/landbot-automation/SKILL.md b/plugins/awesome-claude-skills/landbot-automation/SKILL.md
new file mode 100644
index 0000000..0470075
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/langbase-automation/SKILL.md b/plugins/awesome-claude-skills/langbase-automation/SKILL.md
new file mode 100644
index 0000000..1e29c24
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/langsmith-fetch/SKILL.md b/plugins/awesome-claude-skills/langsmith-fetch/SKILL.md
new file mode 100644
index 0000000..153755e
--- /dev/null
+++ b/plugins/awesome-claude-skills/langsmith-fetch/SKILL.md
@@ -0,0 +1,485 @@
+---
+name: langsmith-fetch
+description: Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
+---
+
+# LangSmith Fetch - Agent Debugging Skill
+
+Debug LangChain and LangGraph agents by fetching execution traces directly from LangSmith Studio in your terminal.
+
+## When to Use This Skill
+
+Automatically activate when user mentions:
+- 🐛 "Debug my agent" or "What went wrong?"
+- 🔍 "Show me recent traces" or "What happened?"
+- ❌ "Check for errors" or "Why did it fail?"
+- 💾 "Analyze memory operations" or "Check LTM"
+- 📊 "Review agent performance" or "Check token usage"
+- 🔧 "What tools were called?" or "Show execution flow"
+
+## Prerequisites
+
+### 1. Install langsmith-fetch
+```bash
+pip install langsmith-fetch
+```
+
+### 2. Set Environment Variables
+```bash
+export LANGSMITH_API_KEY="your_langsmith_api_key"
+export LANGSMITH_PROJECT="your_project_name"
+```
+
+**Verify setup:**
+```bash
+echo $LANGSMITH_API_KEY
+echo $LANGSMITH_PROJECT
+```
+
+## Core Workflows
+
+### Workflow 1: Quick Debug Recent Activity
+
+**When user asks:** "What just happened?" or "Debug my agent"
+
+**Execute:**
+```bash
+langsmith-fetch traces --last-n-minutes 5 --limit 5 --format pretty
+```
+
+**Analyze and report:**
+1. ✅ Number of traces found
+2. ⚠️ Any errors or failures
+3. 🛠️ Tools that were called
+4. ⏱️ Execution times
+5. 💰 Token usage
+
+**Example response format:**
+```
+Found 3 traces in the last 5 minutes:
+
+Trace 1: ✅ Success
+- Agent: memento
+- Tools: recall_memories, create_entities
+- Duration: 2.3s
+- Tokens: 1,245
+
+Trace 2: ❌ Error
+- Agent: cypher
+- Error: "Neo4j connection timeout"
+- Duration: 15.1s
+- Failed at: search_nodes tool
+
+Trace 3: ✅ Success
+- Agent: memento
+- Tools: store_memory
+- Duration: 1.8s
+- Tokens: 892
+
+💡 Issue found: Trace 2 failed due to Neo4j timeout. Recommend checking database connection.
+```
+
+---
+
+### Workflow 2: Deep Dive Specific Trace
+
+**When user provides:** Trace ID or says "investigate that error"
+
+**Execute:**
+```bash
+langsmith-fetch trace --format json
+```
+
+**Analyze JSON and report:**
+1. 🎯 What the agent was trying to do
+2. 🛠️ Which tools were called (in order)
+3. ✅ Tool results (success/failure)
+4. ❌ Error messages (if any)
+5. 💡 Root cause analysis
+6. 🔧 Suggested fix
+
+**Example response format:**
+```
+Deep Dive Analysis - Trace abc123
+
+Goal: User asked "Find all projects in Neo4j"
+
+Execution Flow:
+1. ✅ search_nodes(query: "projects")
+ → Found 24 nodes
+
+2. ❌ get_node_details(node_id: "proj_123")
+ → Error: "Node not found"
+ → This is the failure point
+
+3. ⏹️ Execution stopped
+
+Root Cause:
+The search_nodes tool returned node IDs that no longer exist in the database,
+possibly due to recent deletions.
+
+Suggested Fix:
+1. Add error handling in get_node_details tool
+2. Filter deleted nodes in search results
+3. Update cache invalidation strategy
+
+Token Usage: 1,842 tokens ($0.0276)
+Execution Time: 8.7 seconds
+```
+
+---
+
+### Workflow 3: Export Debug Session
+
+**When user says:** "Save this session" or "Export traces"
+
+**Execute:**
+```bash
+# Create session folder with timestamp
+SESSION_DIR="langsmith-debug/session-$(date +%Y%m%d-%H%M%S)"
+mkdir -p "$SESSION_DIR"
+
+# Export traces
+langsmith-fetch traces "$SESSION_DIR/traces" --last-n-minutes 30 --limit 50 --include-metadata
+
+# Export threads (conversations)
+langsmith-fetch threads "$SESSION_DIR/threads" --limit 20
+```
+
+**Report:**
+```
+✅ Session exported successfully!
+
+Location: langsmith-debug/session-20251224-143022/
+- Traces: 42 files
+- Threads: 8 files
+
+You can now:
+1. Review individual trace files
+2. Share folder with team
+3. Analyze with external tools
+4. Archive for future reference
+
+Session size: 2.3 MB
+```
+
+---
+
+### Workflow 4: Error Detection
+
+**When user asks:** "Show me errors" or "What's failing?"
+
+**Execute:**
+```bash
+# Fetch recent traces
+langsmith-fetch traces --last-n-minutes 30 --limit 50 --format json > recent-traces.json
+
+# Search for errors
+grep -i "error\|failed\|exception" recent-traces.json
+```
+
+**Analyze and report:**
+1. 📊 Total errors found
+2. ❌ Error types and frequency
+3. 🕐 When errors occurred
+4. 🎯 Which agents/tools failed
+5. 💡 Common patterns
+
+**Example response format:**
+```
+Error Analysis - Last 30 Minutes
+
+Total Traces: 50
+Failed Traces: 7 (14% failure rate)
+
+Error Breakdown:
+1. Neo4j Connection Timeout (4 occurrences)
+ - Agent: cypher
+ - Tool: search_nodes
+ - First occurred: 14:32
+ - Last occurred: 14:45
+ - Pattern: Happens during peak load
+
+2. Memory Store Failed (2 occurrences)
+ - Agent: memento
+ - Tool: store_memory
+ - Error: "Pinecone rate limit exceeded"
+ - Occurred: 14:38, 14:41
+
+3. Tool Not Found (1 occurrence)
+ - Agent: sqlcrm
+ - Attempted tool: "export_report" (doesn't exist)
+ - Occurred: 14:35
+
+💡 Recommendations:
+1. Add retry logic for Neo4j timeouts
+2. Implement rate limiting for Pinecone
+3. Fix sqlcrm tool configuration
+```
+
+---
+
+## Common Use Cases
+
+### Use Case 1: "Agent Not Responding"
+
+**User says:** "My agent isn't doing anything"
+
+**Steps:**
+1. Check if traces exist:
+ ```bash
+ langsmith-fetch traces --last-n-minutes 5 --limit 5
+ ```
+
+2. **If NO traces found:**
+ - Tracing might be disabled
+ - Check: `LANGCHAIN_TRACING_V2=true` in environment
+ - Check: `LANGCHAIN_API_KEY` is set
+ - Verify agent actually ran
+
+3. **If traces found:**
+ - Review for errors
+ - Check execution time (hanging?)
+ - Verify tool calls completed
+
+---
+
+### Use Case 2: "Wrong Tool Called"
+
+**User says:** "Why did it use the wrong tool?"
+
+**Steps:**
+1. Get the specific trace
+2. Review available tools at execution time
+3. Check agent's reasoning for tool selection
+4. Examine tool descriptions/instructions
+5. Suggest prompt or tool config improvements
+
+---
+
+### Use Case 3: "Memory Not Working"
+
+**User says:** "Agent doesn't remember things"
+
+**Steps:**
+1. Search for memory operations:
+ ```bash
+ langsmith-fetch traces --last-n-minutes 10 --limit 20 --format raw | grep -i "memory\|recall\|store"
+ ```
+
+2. Check:
+ - Were memory tools called?
+ - Did recall return results?
+ - Were memories actually stored?
+ - Are retrieved memories being used?
+
+---
+
+### Use Case 4: "Performance Issues"
+
+**User says:** "Agent is too slow"
+
+**Steps:**
+1. Export with metadata:
+ ```bash
+ langsmith-fetch traces ./perf-analysis --last-n-minutes 30 --limit 50 --include-metadata
+ ```
+
+2. Analyze:
+ - Execution time per trace
+ - Tool call latencies
+ - Token usage (context size)
+ - Number of iterations
+ - Slowest operations
+
+3. Identify bottlenecks and suggest optimizations
+
+---
+
+## Output Format Guide
+
+### Pretty Format (Default)
+```bash
+langsmith-fetch traces --limit 5 --format pretty
+```
+**Use for:** Quick visual inspection, showing to users
+
+### JSON Format
+```bash
+langsmith-fetch traces --limit 5 --format json
+```
+**Use for:** Detailed analysis, syntax-highlighted review
+
+### Raw Format
+```bash
+langsmith-fetch traces --limit 5 --format raw
+```
+**Use for:** Piping to other commands, automation
+
+---
+
+## Advanced Features
+
+### Time-Based Filtering
+```bash
+# After specific timestamp
+langsmith-fetch traces --after "2025-12-24T13:00:00Z" --limit 20
+
+# Last N minutes (most common)
+langsmith-fetch traces --last-n-minutes 60 --limit 100
+```
+
+### Include Metadata
+```bash
+# Get extra context
+langsmith-fetch traces --limit 10 --include-metadata
+
+# Metadata includes: agent type, model, tags, environment
+```
+
+### Concurrent Fetching (Faster)
+```bash
+# Speed up large exports
+langsmith-fetch traces ./output --limit 100 --concurrent 10
+```
+
+---
+
+## Troubleshooting
+
+### "No traces found matching criteria"
+
+**Possible causes:**
+1. No agent activity in the timeframe
+2. Tracing is disabled
+3. Wrong project name
+4. API key issues
+
+**Solutions:**
+```bash
+# 1. Try longer timeframe
+langsmith-fetch traces --last-n-minutes 1440 --limit 50
+
+# 2. Check environment
+echo $LANGSMITH_API_KEY
+echo $LANGSMITH_PROJECT
+
+# 3. Try fetching threads instead
+langsmith-fetch threads --limit 10
+
+# 4. Verify tracing is enabled in your code
+# Check for: LANGCHAIN_TRACING_V2=true
+```
+
+### "Project not found"
+
+**Solution:**
+```bash
+# View current config
+langsmith-fetch config show
+
+# Set correct project
+export LANGSMITH_PROJECT="correct-project-name"
+
+# Or configure permanently
+langsmith-fetch config set project "your-project-name"
+```
+
+### Environment variables not persisting
+
+**Solution:**
+```bash
+# Add to shell config file (~/.bashrc or ~/.zshrc)
+echo 'export LANGSMITH_API_KEY="your_key"' >> ~/.bashrc
+echo 'export LANGSMITH_PROJECT="your_project"' >> ~/.bashrc
+
+# Reload shell config
+source ~/.bashrc
+```
+
+---
+
+## Best Practices
+
+### 1. Regular Health Checks
+```bash
+# Quick check after making changes
+langsmith-fetch traces --last-n-minutes 5 --limit 5
+```
+
+### 2. Organized Storage
+```
+langsmith-debug/
+├── sessions/
+│ ├── 2025-12-24/
+│ └── 2025-12-25/
+├── error-cases/
+└── performance-tests/
+```
+
+### 3. Document Findings
+When you find bugs:
+1. Export the problematic trace
+2. Save to `error-cases/` folder
+3. Note what went wrong in a README
+4. Share trace ID with team
+
+### 4. Integration with Development
+```bash
+# Before committing code
+langsmith-fetch traces --last-n-minutes 10 --limit 5
+
+# If errors found
+langsmith-fetch trace --format json > pre-commit-error.json
+```
+
+---
+
+## Quick Reference
+
+```bash
+# Most common commands
+
+# Quick debug
+langsmith-fetch traces --last-n-minutes 5 --limit 5 --format pretty
+
+# Specific trace
+langsmith-fetch trace --format pretty
+
+# Export session
+langsmith-fetch traces ./debug-session --last-n-minutes 30 --limit 50
+
+# Find errors
+langsmith-fetch traces --last-n-minutes 30 --limit 50 --format raw | grep -i error
+
+# With metadata
+langsmith-fetch traces --limit 10 --include-metadata
+```
+
+---
+
+## Resources
+
+- **LangSmith Fetch CLI:** https://github.com/langchain-ai/langsmith-fetch
+- **LangSmith Studio:** https://smith.langchain.com/
+- **LangChain Docs:** https://docs.langchain.com/
+- **This Skill Repo:** https://github.com/OthmanAdi/langsmith-fetch-skill
+
+---
+
+## Notes for Claude
+
+- Always check if `langsmith-fetch` is installed before running commands
+- Verify environment variables are set
+- Use `--format pretty` for human-readable output
+- Use `--format json` when you need to parse and analyze data
+- When exporting sessions, create organized folder structures
+- Always provide clear analysis and actionable insights
+- If commands fail, help troubleshoot configuration issues
+
+---
+
+**Version:** 0.1.0
+**Author:** Ahmad Othman Ammar Adi
+**License:** MIT
+**Repository:** https://github.com/OthmanAdi/langsmith-fetch-skill
diff --git a/plugins/awesome-claude-skills/lastpass-automation/SKILL.md b/plugins/awesome-claude-skills/lastpass-automation/SKILL.md
new file mode 100644
index 0000000..36ffdbf
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/launch-darkly-automation/SKILL.md b/plugins/awesome-claude-skills/launch-darkly-automation/SKILL.md
new file mode 100644
index 0000000..b3b2709
--- /dev/null
+++ b/plugins/awesome-claude-skills/launch-darkly-automation/SKILL.md
@@ -0,0 +1,130 @@
+---
+name: LaunchDarkly Automation
+description: "Automate LaunchDarkly feature flag management -- list projects and environments, create and delete trigger workflows, and track code references via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# LaunchDarkly Automation
+
+Automate your LaunchDarkly feature flag workflows -- enumerate projects and environments, create webhook-driven flag triggers, manage trigger lifecycle, and audit code references across repositories.
+
+**Toolkit docs:** [composio.dev/toolkits/launch_darkly](https://composio.dev/toolkits/launch_darkly)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your LaunchDarkly account when prompted (API key authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. List Projects
+
+Use `LAUNCH_DARKLY_LIST_PROJECTS` to discover all projects and their keys for subsequent operations.
+
+```
+Tool: LAUNCH_DARKLY_LIST_PROJECTS
+Inputs:
+ - filter: string (e.g., "query:myproject" or "keys:proj1,proj2" or "tags:mytag")
+ - expand: string (e.g., "environments" to include env list per project)
+ - limit: integer (default 20)
+ - offset: integer (pagination start index)
+ - sort: string (e.g., "name" or "-name" for descending)
+```
+
+### 2. Get Environments for a Project
+
+Use `LAUNCH_DARKLY_GET_ENVIRONMENTS` to list all environments within a project (production, staging, test, etc.).
+
+```
+Tool: LAUNCH_DARKLY_GET_ENVIRONMENTS
+Inputs:
+ - project_key: string (required) -- e.g., "my-project", "default"
+ - filter: string (e.g., "query:production")
+ - limit: integer (default 20)
+ - offset: integer (pagination)
+ - sort: string (e.g., "name" or "-name")
+```
+
+### 3. Create a Flag Trigger Workflow
+
+Use `LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW` to set up automated flag toggles triggered by external events (webhooks, Datadog alerts, etc.).
+
+```
+Tool: LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW
+Inputs:
+ - project_key: string (required)
+ - feature_flag_key: string (required) -- e.g., "new-feature", "enable-dark-mode"
+ - environment_key: string (required) -- e.g., "production", "staging"
+ - integration_key: string (default "generic-trigger") -- or "datadog", "honeycomb", "dynatrace"
+ - instructions: array of objects (optional):
+ - kind: "flag_action" (fixed)
+ - action: "turnFlagOn" | "turnFlagOff"
+ - comment: string (optional) -- description of the trigger purpose
+```
+
+The trigger generates a unique webhook URL that can be called to execute the configured flag action.
+
+### 4. Delete a Flag Trigger Workflow
+
+Use `LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW` to permanently remove a trigger and its URL.
+
+```
+Tool: LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW
+Inputs:
+ - project_key: string (required)
+ - feature_flag_key: string (required)
+ - environment_key: string (required)
+ - id: string (required) -- the trigger ID returned during creation
+```
+
+**Warning:** Deletion is irreversible. The trigger and its URL cannot be recovered.
+
+### 5. List Code Reference Repositories
+
+Use `LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES` to track where feature flags are used in your codebase.
+
+```
+Tool: LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES
+Inputs:
+ - projKey: string (optional) -- filter by project key
+ - flagKey: string (optional) -- filter by feature flag key
+ - withBranches: string (any value to include branch data)
+ - withReferencesForDefaultBranch: string (any value to include code refs for default branch)
+```
+
+**Note:** Code references is an Enterprise feature requiring `code-reference-repository` write permissions.
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| Project key discovery | Always use `LAUNCH_DARKLY_LIST_PROJECTS` first to find valid project keys before calling other tools. |
+| Environment key format | Environment keys are lowercase slugs (e.g., "production", "test"), not display names. |
+| Trigger deletion is permanent | Once deleted via `LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW`, the trigger URL is unrecoverable. |
+| Enterprise-only code refs | `LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES` requires Enterprise plan and write permissions. |
+| Trigger instructions format | Each instruction object requires `kind: "flag_action"` (fixed constant) and `action` as either `turnFlagOn` or `turnFlagOff`. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `LAUNCH_DARKLY_LIST_PROJECTS` | List all projects with filtering and pagination |
+| `LAUNCH_DARKLY_GET_ENVIRONMENTS` | List environments within a project |
+| `LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW` | Create a webhook-driven flag trigger |
+| `LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW` | Permanently delete a flag trigger |
+| `LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES` | List repos with code references to flags |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/launch_darkly-automation/SKILL.md b/plugins/awesome-claude-skills/launch_darkly-automation/SKILL.md
new file mode 100644
index 0000000..4500f91
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/leadfeeder-automation/SKILL.md b/plugins/awesome-claude-skills/leadfeeder-automation/SKILL.md
new file mode 100644
index 0000000..8f8f0ea
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/leadoku-automation/SKILL.md b/plugins/awesome-claude-skills/leadoku-automation/SKILL.md
new file mode 100644
index 0000000..9cd69ee
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/leiga-automation/SKILL.md b/plugins/awesome-claude-skills/leiga-automation/SKILL.md
new file mode 100644
index 0000000..c0cec46
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/lemlist-automation/SKILL.md b/plugins/awesome-claude-skills/lemlist-automation/SKILL.md
new file mode 100644
index 0000000..86f955f
--- /dev/null
+++ b/plugins/awesome-claude-skills/lemlist-automation/SKILL.md
@@ -0,0 +1,135 @@
+---
+name: Lemlist Automation
+description: "Automate Lemlist multichannel outreach -- manage campaigns, enroll leads, add personalization variables, export campaign data, and handle unsubscribes via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Lemlist Automation
+
+Automate your Lemlist multichannel outreach workflows -- manage campaigns, enroll leads at scale, enrich with custom variables, export campaign data, and clean up unsubscribes.
+
+**Toolkit docs:** [composio.dev/toolkits/lemlist](https://composio.dev/toolkits/lemlist)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your Lemlist account when prompted (API key authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. List and Discover Campaigns
+
+Use `LEMLIST_GET_LIST_CAMPAIGNS` to enumerate all campaigns by status, with pagination support.
+
+```
+Tool: LEMLIST_GET_LIST_CAMPAIGNS
+Inputs:
+ - status: "running" | "draft" | "archived" | "ended" | "paused" | "errors" (optional)
+ - limit: integer (max 100, default 100)
+ - offset: integer (pagination offset)
+ - sortBy: "createdAt"
+ - sortOrder: "asc" | "desc"
+```
+
+**Important:** The response may be wrapped as `{campaigns: [...], pagination: {...}}` instead of a flat list. Always extract from the `campaigns` key.
+
+### 2. Get Campaign Details
+
+Use `LEMLIST_GET_CAMPAIGN_BY_ID` to validate campaign configuration before writes.
+
+```
+Tool: LEMLIST_GET_CAMPAIGN_BY_ID
+Inputs:
+ - campaignId: string (required) -- e.g., "cam_A1B2C3D4E5F6G7H8I9"
+```
+
+### 3. Enroll Leads into a Campaign
+
+Use `LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN` to add leads with optional email finding, phone lookup, and LinkedIn enrichment.
+
+```
+Tool: LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN
+Inputs:
+ - campaignId: string (required)
+ - email: string (required)
+ - firstName, lastName, companyName, companyDomain: string (optional)
+ - jobTitle, phone, linkedinUrl, icebreaker: string (optional)
+ - deduplicate: boolean (prevents cross-campaign duplicates)
+ - findEmail, findPhone, verifyEmail, linkedinEnrichment: boolean (optional)
+ - timezone: string (IANA format, e.g., "America/New_York")
+```
+
+**Bulk pattern:** Chunk leads into batches of ~50 and checkpoint progress between batches.
+
+### 4. Add Custom Variables to a Lead
+
+Use `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` to enrich leads with personalization fields after enrollment.
+
+```
+Tool: LEMLIST_POST_ADD_VARIABLES_TO_LEAD
+Inputs:
+ - leadId: string (required) -- internal Lemlist lead ID (NOT email)
+ - company: string (required) -- must match your company name in Lemlist
+ - variables: object (required) -- key-value pairs, e.g., {"score": "42", "color": "yellow"}
+```
+
+**Important:** This is NOT an upsert -- attempting to add variables that already exist will fail. Resolve the internal `leadId` via `LEMLIST_GET_RETRIEVE_LEAD_BY_EMAIL` if you only have the email address.
+
+### 5. Export Campaign Leads
+
+Use `LEMLIST_GET_EXPORT_CAMPAIGN_LEADS` to download leads with state filtering for reporting or QA.
+
+```
+Tool: LEMLIST_GET_EXPORT_CAMPAIGN_LEADS
+Inputs:
+ - campaignId: string (required)
+ - (supports state filtering and JSON/CSV output)
+```
+
+### 6. Unsubscribe Lead from Campaign
+
+Use `LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN` to stop outreach by removing a lead from a campaign.
+
+```
+Tool: LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN
+Inputs:
+ - campaignId: string (required)
+ - leadId or email: string (required)
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| Wrapped campaign list | `LEMLIST_GET_LIST_CAMPAIGNS` may return `{campaigns: [...], pagination: {...}}` instead of a flat array. Always extract from the `campaigns` key. |
+| Cross-campaign deduplication | `LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN` with deduplication enabled fails with HTTP 500 "Lead already in other campaign" -- disable deduplication for intentional cross-campaign enrollment. |
+| Bulk import failures | Chunk bulk imports to ~50 per batch with checkpoints to avoid losing partial progress on intermittent failures. |
+| Invalid leadId | `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` returns HTTP 400 "Invalid leadId" when using an email as the leadId -- resolve the internal ID via `LEMLIST_GET_RETRIEVE_LEAD_BY_EMAIL` first. |
+| Variable collisions | `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` is not an upsert. Adding keys that already exist returns HTTP 400 "Variables X already exist". |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `LEMLIST_GET_LIST_CAMPAIGNS` | List all campaigns with status filter and pagination |
+| `LEMLIST_GET_CAMPAIGN_BY_ID` | Get detailed campaign info by ID |
+| `LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN` | Create and enroll a lead into a campaign |
+| `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` | Add custom personalization variables to a lead |
+| `LEMLIST_GET_RETRIEVE_LEAD_BY_EMAIL` | Look up a lead by email address |
+| `LEMLIST_GET_EXPORT_CAMPAIGN_LEADS` | Export leads from a campaign with state filtering |
+| `LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN` | Remove a lead from a campaign |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/lemon-squeezy-automation/SKILL.md b/plugins/awesome-claude-skills/lemon-squeezy-automation/SKILL.md
new file mode 100644
index 0000000..60e2aaf
--- /dev/null
+++ b/plugins/awesome-claude-skills/lemon-squeezy-automation/SKILL.md
@@ -0,0 +1,156 @@
+---
+name: Lemon Squeezy Automation
+description: "Automate Lemon Squeezy store management -- products, orders, subscriptions, customers, discounts, and checkout tracking -- using natural language through the Composio MCP integration."
+category: e-commerce
+requires:
+ mcp:
+ - rube
+---
+
+# Lemon Squeezy Automation
+
+Manage your Lemon Squeezy digital products business -- track orders, monitor subscriptions, analyze customers, review discounts, and audit checkouts -- all through natural language commands.
+
+**Toolkit docs:** [composio.dev/toolkits/lemon_squeezy](https://composio.dev/toolkits/lemon_squeezy)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Lemon Squeezy account when prompted (API key authentication).
+3. Start issuing natural language commands to manage your store.
+
+---
+
+## Core Workflows
+
+### 1. Discover Stores and Products
+List all stores to get store IDs, then retrieve products and variants for a specific store.
+
+**Tools:** `LEMON_SQUEEZY_LIST_ALL_STORES`, `LEMON_SQUEEZY_LIST_ALL_PRODUCTS`, `LEMON_SQUEEZY_LIST_ALL_VARIANTS`
+
+**Example prompt:**
+> "List all my Lemon Squeezy stores and their products"
+
+**Key parameters:**
+- `LEMON_SQUEEZY_LIST_ALL_STORES` -- No parameters required
+- `LEMON_SQUEEZY_LIST_ALL_PRODUCTS` -- Filter by `filter[store_id]`
+- `LEMON_SQUEEZY_LIST_ALL_VARIANTS` -- Filter by `filter[product_id]`, `filter[status]` (pending/draft/published)
+
+---
+
+### 2. Track Orders and Order Items
+Retrieve all orders with optional filtering by store, user email, or order number, and drill into individual order items.
+
+**Tools:** `LEMON_SQUEEZY_LIST_ALL_ORDERS`, `LEMON_SQUEEZY_LIST_ALL_ORDER_ITEMS`
+
+**Example prompt:**
+> "Show all orders from johndoe@example.com in my Lemon Squeezy store"
+
+**Key parameters for orders:**
+- `filter[store_id]` -- Filter by store ID
+- `filter[user_email]` -- Filter by customer email
+- `filter[order_number]` -- Filter by specific order number
+- `page[number]` / `page[size]` -- Pagination (max 100 per page)
+
+**Key parameters for order items:**
+- `filter[order_id]`, `filter[product_id]`, `filter[variant_id]` -- Filter by related entity
+
+---
+
+### 3. Monitor Subscriptions
+List all subscriptions with rich filtering options to track recurring revenue.
+
+**Tool:** `LEMON_SQUEEZY_LIST_ALL_SUBSCRIPTIONS`
+
+**Example prompt:**
+> "Show all active subscriptions in my Lemon Squeezy store"
+
+**Key parameters:**
+- `filter[status]` -- Filter by status (e.g., `active`, `cancelled`)
+- `filter[store_id]` -- Filter by store
+- `filter[product_id]` -- Filter by product
+- `filter[user_email]` -- Filter by subscriber email
+- `filter[variant_id]` -- Filter by variant
+- `page[number]` / `page[size]` -- Pagination (max 100 per page)
+
+---
+
+### 4. Manage Customers
+Retrieve customer records with details including email, MRR, total revenue, and customer portal URLs.
+
+**Tool:** `LEMON_SQUEEZY_LIST_ALL_CUSTOMERS`
+
+**Example prompt:**
+> "Find the Lemon Squeezy customer with email johndoe@example.com"
+
+**Key parameters:**
+- `filter[email]` -- Filter by exact email address
+- `filter[store_id]` -- Filter by store ID
+- `page[number]` / `page[size]` -- Pagination (max 100 per page)
+
+---
+
+### 5. Audit Discounts and Redemptions
+List all discount codes and track how they have been redeemed across orders.
+
+**Tools:** `LEMON_SQUEEZY_LIST_ALL_DISCOUNTS`, `LEMON_SQUEEZY_LIST_ALL_DISCOUNT_REDEMPTIONS`
+
+**Example prompt:**
+> "Show all discounts for store 12345 and their redemption history"
+
+**Key parameters for discounts:**
+- `filter[store_id]` -- Filter by store
+- `page[number]` / `page[size]` -- Pagination
+
+**Key parameters for redemptions:**
+- `filter[discount_id]` -- Filter by discount
+- `filter[order_id]` -- Filter by order
+
+---
+
+### 6. Review Checkouts
+List all checkout sessions with optional filtering by store or variant.
+
+**Tool:** `LEMON_SQUEEZY_LIST_ALL_CHECKOUTS`
+
+**Example prompt:**
+> "Show all checkouts for variant 42 in my Lemon Squeezy store"
+
+**Key parameters:**
+- `filter[store_id]` -- Filter by store ID
+- `filter[variant_id]` -- Filter by variant ID
+
+---
+
+## Known Pitfalls
+
+- **Store ID is foundational**: Most filters require a `store_id`. Always call `LEMON_SQUEEZY_LIST_ALL_STORES` first to discover valid store IDs before filtering other resources.
+- **Pagination is mandatory for large datasets**: All list endpoints use `page[number]` / `page[size]` pagination (max 100 per page). Do not assume the first page is complete.
+- **Filter parameter naming**: Lemon Squeezy uses bracket notation for filters (e.g., `filter[store_id]`, `page[number]`). Ensure exact parameter names are used.
+- **Subscription invoices vs. orders**: Subscription invoices (`LEMON_SQUEEZY_LIST_ALL_SUBSCRIPTION_INVOICES`) are separate from one-time orders. Use the appropriate endpoint for your use case.
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Required Params |
+|---|---|---|
+| List stores | `LEMON_SQUEEZY_LIST_ALL_STORES` | None |
+| List products | `LEMON_SQUEEZY_LIST_ALL_PRODUCTS` | None (optional filters) |
+| List variants | `LEMON_SQUEEZY_LIST_ALL_VARIANTS` | None (optional filters) |
+| List orders | `LEMON_SQUEEZY_LIST_ALL_ORDERS` | None (optional filters) |
+| List order items | `LEMON_SQUEEZY_LIST_ALL_ORDER_ITEMS` | None (optional filters) |
+| List subscriptions | `LEMON_SQUEEZY_LIST_ALL_SUBSCRIPTIONS` | None (optional filters) |
+| List customers | `LEMON_SQUEEZY_LIST_ALL_CUSTOMERS` | None (optional filters) |
+| List discounts | `LEMON_SQUEEZY_LIST_ALL_DISCOUNTS` | None (optional filters) |
+| List discount redemptions | `LEMON_SQUEEZY_LIST_ALL_DISCOUNT_REDEMPTIONS` | None (optional filters) |
+| List checkouts | `LEMON_SQUEEZY_LIST_ALL_CHECKOUTS` | None (optional filters) |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/lemon_squeezy-automation/SKILL.md b/plugins/awesome-claude-skills/lemon_squeezy-automation/SKILL.md
new file mode 100644
index 0000000..bddd5a5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/lessonspace-automation/SKILL.md b/plugins/awesome-claude-skills/lessonspace-automation/SKILL.md
new file mode 100644
index 0000000..2c66f3c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/lever-automation/SKILL.md b/plugins/awesome-claude-skills/lever-automation/SKILL.md
new file mode 100644
index 0000000..ed56966
--- /dev/null
+++ b/plugins/awesome-claude-skills/lever-automation/SKILL.md
@@ -0,0 +1,149 @@
+---
+name: Lever Automation
+description: "Automate recruiting workflows in Lever ATS -- manage opportunities, job postings, requisitions, pipeline stages, and candidate tags through the Composio Lever integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Lever Automation
+
+Automate your recruiting operations in **Lever ATS** directly from Claude Code. Manage job postings, track candidate pipelines, update requisitions, and query opportunities without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/lever](https://composio.dev/toolkits/lever)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Lever account when prompted by running any Lever command. The agent will provide an OAuth link to authenticate.
+3. Ensure your Lever API key has sufficient scopes for the operations you need (read/write access to postings, opportunities, requisitions).
+
+---
+
+## Core Workflows
+
+### 1. List and Filter Job Postings
+
+Retrieve all job postings with optional filtering by state, team, department, location, or commitment type.
+
+**Tool:** `LEVER_LIST_POSTINGS`
+
+Key parameters:
+- `state` -- filter by `published`, `internal`, `closed`, `draft`, `pending`, `rejected`
+- `team`, `department`, `location`, `commitment` -- narrow results by organizational attributes
+- `limit` (1-100) and `offset` -- paginate through large posting sets
+- `tag` -- filter by posting tag
+
+Example prompt: *"List all published engineering job postings in Lever"*
+
+---
+
+### 2. Browse Candidate Opportunities
+
+List all opportunities in the hiring pipeline with rich filtering for pipeline analysis and candidate tracking.
+
+**Tool:** `LEVER_LIST_OPPORTUNITIES`
+
+Key parameters:
+- `posting_id`, `stage_id`, `tag` -- filter by posting, pipeline stage, or tag
+- `email`, `contact_id` -- find opportunities for a specific candidate
+- `archived` -- filter by archived status (`true`/`false`)
+- `created_at_start`, `created_at_end` -- date range filtering (ISO 8601)
+- `expand` -- expand `applications`, `contact`, `owner`, `stage`, `stageChanges`, `sources`, `sourcedBy` into full objects
+
+Example prompt: *"Show me all active opportunities for the Senior Engineer posting, expanded with contact details"*
+
+---
+
+### 3. Get Opportunity Details
+
+Fetch comprehensive details about a single candidate opportunity including contact info, stage progression, sources, and applications.
+
+**Tool:** `LEVER_GET_OPPORTUNITY`
+
+Key parameters:
+- `opportunity` (required) -- the unique opportunity UID
+- `expand` -- comma-separated fields to expand: `contact`, `stage`, `owner`
+
+Example prompt: *"Get full details for opportunity 31c9716c-d4e3-47e8-a6a1-54078a1151d6 with contact and stage expanded"*
+
+---
+
+### 4. Manage Requisitions
+
+Create, list, update, and delete requisitions to track headcount and hiring needs.
+
+**Tools:** `LEVER_LIST_REQUISITIONS`, `LEVER_GET_REQUISITION`, `LEVER_UPDATE_REQUISITION`, `LEVER_DELETE_REQUISITION`
+
+Update requires these fields:
+- `requisition` (required) -- UUID of the requisition
+- `requisitionCode` (required) -- unique code like `REQ-001`
+- `name` (required) -- requisition title
+- `headcountTotal` (required) -- number of positions (minimum 1)
+- `status` -- `open` or `closed`
+- Optional: `hiringManager`, `owner`, `department`, `team`, `location`, `compensationBand`
+
+Example prompt: *"Update requisition REQ-001 to increase headcount to 3 and change status to open"*
+
+---
+
+### 5. View Pipeline Stages
+
+Retrieve all hiring pipeline stages configured in your Lever account.
+
+**Tool:** `LEVER_LIST_STAGES`
+
+Key parameters:
+- `limit` (1-100) -- max items per page
+- `offset` -- pagination token from previous response
+
+Example prompt: *"List all pipeline stages in our Lever account"*
+
+---
+
+### 6. Manage Tags
+
+List all tags used to categorize candidates, opportunities, and postings.
+
+**Tool:** `LEVER_LIST_TAGS`
+
+Key parameters:
+- `limit` -- max items per page
+- `offset` -- pagination token
+
+Example prompt: *"Show all candidate tags in Lever"*
+
+---
+
+## Known Pitfalls
+
+- **Pagination required for large datasets:** `LEVER_LIST_OPPORTUNITIES` and `LEVER_LIST_POSTINGS` default to 100 results max per page. Always check for an `offset` token in the response and iterate to get complete results.
+- **Expand parameter format:** The `expand` field on `LEVER_LIST_OPPORTUNITIES` accepts an array of strings, while on `LEVER_GET_OPPORTUNITY` and `LEVER_GET_REQUISITION` it accepts a comma-separated string. Follow the exact schema for each tool.
+- **Requisition updates are full replacements:** `LEVER_UPDATE_REQUISITION` requires all mandatory fields (`requisitionCode`, `name`, `headcountTotal`) even if you only want to change one field. Always fetch the current requisition first with `LEVER_GET_REQUISITION`.
+- **Timestamps:** Opportunity date filters use ISO 8601 format, while `LEVER_LIST_POSTINGS` uses Unix timestamps in milliseconds for `updated_at_start`.
+- **Connection scopes:** Write operations (update/delete requisitions) will fail if your API token lacks the necessary permissions, even if reads succeed.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `LEVER_LIST_POSTINGS` | List all job postings with filtering by state, team, department |
+| `LEVER_LIST_OPPORTUNITIES` | List candidate opportunities with pipeline filtering |
+| `LEVER_GET_OPPORTUNITY` | Get detailed info for a single opportunity |
+| `LEVER_GET_REQUISITION` | Retrieve a single requisition by ID |
+| `LEVER_LIST_REQUISITIONS` | List all requisitions with status/code filtering |
+| `LEVER_UPDATE_REQUISITION` | Update an existing requisition (full replacement) |
+| `LEVER_DELETE_REQUISITION` | Delete/archive a requisition |
+| `LEVER_LIST_STAGES` | List all pipeline stages |
+| `LEVER_LIST_TAGS` | List all tags for categorization |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/lever-sandbox-automation/SKILL.md b/plugins/awesome-claude-skills/lever-sandbox-automation/SKILL.md
new file mode 100644
index 0000000..a0b1619
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/leverly-automation/SKILL.md b/plugins/awesome-claude-skills/leverly-automation/SKILL.md
new file mode 100644
index 0000000..bf52fe9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/lexoffice-automation/SKILL.md b/plugins/awesome-claude-skills/lexoffice-automation/SKILL.md
new file mode 100644
index 0000000..66f7143
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/linear-automation/SKILL.md b/plugins/awesome-claude-skills/linear-automation/SKILL.md
new file mode 100644
index 0000000..bd87bd4
--- /dev/null
+++ b/plugins/awesome-claude-skills/linear-automation/SKILL.md
@@ -0,0 +1,183 @@
+---
+name: linear-automation
+description: "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Linear Automation via Rube MCP
+
+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)
+- Active Linear connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`
+3. If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Issues
+
+**When to use**: User wants to create, search, update, or list Linear issues
+
+**Tool sequence**:
+1. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team IDs [Prerequisite]
+2. `LINEAR_LIST_LINEAR_STATES` - Get workflow states for a team [Prerequisite]
+3. `LINEAR_CREATE_LINEAR_ISSUE` - Create a new issue [Optional]
+4. `LINEAR_SEARCH_ISSUES` / `LINEAR_LIST_LINEAR_ISSUES` - Find issues [Optional]
+5. `LINEAR_GET_LINEAR_ISSUE` - Get issue details [Optional]
+6. `LINEAR_UPDATE_ISSUE` - Update issue properties [Optional]
+
+**Key parameters**:
+- `team_id`: Team ID (required for creation)
+- `title`: Issue title
+- `description`: Issue description (Markdown supported)
+- `state_id`: Workflow state ID
+- `assignee_id`: Assignee user ID
+- `priority`: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)
+- `label_ids`: Array of label IDs
+
+**Pitfalls**:
+- Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first
+- State IDs are team-specific; use LIST_LINEAR_STATES with the correct team
+- Priority uses integer values 0-4, not string names
+
+### 2. Manage Projects
+
+**When to use**: User wants to create or update Linear projects
+
+**Tool sequence**:
+1. `LINEAR_LIST_LINEAR_PROJECTS` - List existing projects [Optional]
+2. `LINEAR_CREATE_LINEAR_PROJECT` - Create a new project [Optional]
+3. `LINEAR_UPDATE_LINEAR_PROJECT` - Update project details [Optional]
+
+**Key parameters**:
+- `name`: Project name
+- `description`: Project description
+- `team_ids`: Array of team IDs associated with the project
+- `state`: Project state (e.g., 'planned', 'started', 'completed')
+
+**Pitfalls**:
+- Projects span teams; they can be associated with multiple teams
+
+### 3. Manage Cycles
+
+**When to use**: User wants to work with Linear cycles (sprints)
+
+**Tool sequence**:
+1. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team ID [Prerequisite]
+2. `LINEAR_GET_CYCLES_BY_TEAM_ID` / `LINEAR_LIST_LINEAR_CYCLES` - List cycles [Required]
+
+**Key parameters**:
+- `team_id`: Team ID for cycle operations
+- `number`: Cycle number
+
+**Pitfalls**:
+- Cycles are team-specific; always scope by team_id
+
+### 4. Manage Labels and Comments
+
+**When to use**: User wants to create labels or comment on issues
+
+**Tool sequence**:
+1. `LINEAR_CREATE_LINEAR_LABEL` - Create a new label [Optional]
+2. `LINEAR_CREATE_LINEAR_COMMENT` - Comment on an issue [Optional]
+3. `LINEAR_UPDATE_LINEAR_COMMENT` - Edit a comment [Optional]
+
+**Key parameters**:
+- `name`: Label name
+- `color`: Label color (hex)
+- `issue_id`: Issue ID for comments
+- `body`: Comment body (Markdown)
+
+**Pitfalls**:
+- Labels can be team-scoped or workspace-scoped
+- Comment body supports Markdown formatting
+
+### 5. Custom GraphQL Queries
+
+**When to use**: User needs advanced queries not covered by standard tools
+
+**Tool sequence**:
+1. `LINEAR_RUN_QUERY_OR_MUTATION` - Execute custom GraphQL [Required]
+
+**Key parameters**:
+- `query`: GraphQL query or mutation string
+- `variables`: Variables for the query
+
+**Pitfalls**:
+- Requires knowledge of Linear's GraphQL schema
+- Rate limits apply to GraphQL queries
+
+## Common Patterns
+
+### ID Resolution
+
+**Team name -> Team ID**:
+```
+1. Call LINEAR_GET_ALL_LINEAR_TEAMS
+2. Find team by name in response
+3. Extract id field
+```
+
+**State name -> State ID**:
+```
+1. Call LINEAR_LIST_LINEAR_STATES with team_id
+2. Find state by name
+3. Extract id field
+```
+
+### Pagination
+
+- Linear tools return paginated results
+- Check for pagination cursors in responses
+- Pass cursor to next request for additional pages
+
+## Known Pitfalls
+
+**Team Scoping**:
+- Issues, states, and cycles are team-specific
+- Always resolve team_id before creating issues
+
+**Priority Values**:
+- 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low
+- Use integer values, not string names
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List teams | LINEAR_GET_ALL_LINEAR_TEAMS | (none) |
+| Create issue | LINEAR_CREATE_LINEAR_ISSUE | team_id, title, description |
+| Search issues | LINEAR_SEARCH_ISSUES | query |
+| List issues | LINEAR_LIST_LINEAR_ISSUES | team_id, filters |
+| Get issue | LINEAR_GET_LINEAR_ISSUE | issue_id |
+| Update issue | LINEAR_UPDATE_ISSUE | issue_id, fields |
+| List states | LINEAR_LIST_LINEAR_STATES | team_id |
+| List projects | LINEAR_LIST_LINEAR_PROJECTS | (none) |
+| Create project | LINEAR_CREATE_LINEAR_PROJECT | name, team_ids |
+| Update project | LINEAR_UPDATE_LINEAR_PROJECT | project_id, fields |
+| List cycles | LINEAR_LIST_LINEAR_CYCLES | team_id |
+| Get cycles | LINEAR_GET_CYCLES_BY_TEAM_ID | team_id |
+| Create label | LINEAR_CREATE_LINEAR_LABEL | name, color |
+| Create comment | LINEAR_CREATE_LINEAR_COMMENT | issue_id, body |
+| Update comment | LINEAR_UPDATE_LINEAR_COMMENT | comment_id, body |
+| 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/plugins/awesome-claude-skills/linguapop-automation/SKILL.md b/plugins/awesome-claude-skills/linguapop-automation/SKILL.md
new file mode 100644
index 0000000..1df1a01
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/linkedin-automation/SKILL.md b/plugins/awesome-claude-skills/linkedin-automation/SKILL.md
new file mode 100644
index 0000000..df25535
--- /dev/null
+++ b/plugins/awesome-claude-skills/linkedin-automation/SKILL.md
@@ -0,0 +1,180 @@
+---
+name: linkedin-automation
+description: "Automate LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# LinkedIn Automation via Rube MCP
+
+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)
+- Active LinkedIn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linkedin`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linkedin`
+3. If connection is not ACTIVE, follow the returned auth link to complete LinkedIn OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create a LinkedIn Post
+
+**When to use**: User wants to publish a text post on LinkedIn
+
+**Tool sequence**:
+1. `LINKEDIN_GET_MY_INFO` - Get authenticated user's profile info [Prerequisite]
+2. `LINKEDIN_REGISTER_IMAGE_UPLOAD` - Register image upload if post includes an image [Optional]
+3. `LINKEDIN_CREATE_LINKED_IN_POST` - Publish the post [Required]
+
+**Key parameters**:
+- `text`: Post content text
+- `visibility`: 'PUBLIC' or 'CONNECTIONS'
+- `media_title`: Title for attached media
+- `media_description`: Description for attached media
+
+**Pitfalls**:
+- Must retrieve user profile URN via GET_MY_INFO before creating a post
+- Image uploads require a two-step process: register upload first, then include the asset in the post
+- Post text has character limits enforced by LinkedIn API
+- Visibility defaults may vary; always specify explicitly
+
+### 2. Get Profile Information
+
+**When to use**: User wants to retrieve their LinkedIn profile or company details
+
+**Tool sequence**:
+1. `LINKEDIN_GET_MY_INFO` - Get authenticated user's profile [Required]
+2. `LINKEDIN_GET_COMPANY_INFO` - Get company page details [Optional]
+
+**Key parameters**:
+- No parameters needed for GET_MY_INFO (uses authenticated user)
+- `organization_id`: Company/organization ID for GET_COMPANY_INFO
+
+**Pitfalls**:
+- GET_MY_INFO returns the authenticated user only; cannot look up other users
+- Company info requires the numeric organization ID, not the company name or vanity URL
+- Some profile fields may be restricted based on OAuth scopes granted
+
+### 3. Manage Post Images
+
+**When to use**: User wants to upload and attach images to LinkedIn posts
+
+**Tool sequence**:
+1. `LINKEDIN_REGISTER_IMAGE_UPLOAD` - Register an image upload with LinkedIn [Required]
+2. Upload the image binary to the returned upload URL [Required]
+3. `LINKEDIN_GET_IMAGES` - Verify uploaded image status [Optional]
+4. `LINKEDIN_CREATE_LINKED_IN_POST` - Create post with the image asset [Required]
+
+**Key parameters**:
+- `owner`: URN of the image owner (user or organization)
+- `image_id`: ID of the uploaded image for GET_IMAGES
+
+**Pitfalls**:
+- The upload is a two-phase process: register then upload binary
+- Image asset URN from registration must be used when creating the post
+- Supported formats typically include JPG, PNG, and GIF
+- Large images may take time to process before they are available
+
+### 4. Comment on Posts
+
+**When to use**: User wants to comment on an existing LinkedIn post
+
+**Tool sequence**:
+1. `LINKEDIN_CREATE_COMMENT_ON_POST` - Add a comment to a post [Required]
+
+**Key parameters**:
+- `post_id`: The URN or ID of the post to comment on
+- `text`: Comment content
+- `actor`: URN of the commenter (user or organization)
+
+**Pitfalls**:
+- Post ID must be a valid LinkedIn URN format
+- The actor URN must match the authenticated user or a managed organization
+- Rate limits apply to comment creation; avoid rapid-fire comments
+
+### 5. Delete a Post
+
+**When to use**: User wants to remove a previously published LinkedIn post
+
+**Tool sequence**:
+1. `LINKEDIN_DELETE_LINKED_IN_POST` - Delete the specified post [Required]
+
+**Key parameters**:
+- `post_id`: The URN or ID of the post to delete
+
+**Pitfalls**:
+- Deletion is permanent and cannot be undone
+- Only the post author or organization admin can delete a post
+- The post_id must be the exact URN returned when the post was created
+
+## Common Patterns
+
+### ID Resolution
+
+**User URN from profile**:
+```
+1. Call LINKEDIN_GET_MY_INFO
+2. Extract user URN (e.g., 'urn:li:person:XXXXXXXXXX')
+3. Use URN as actor/owner in subsequent calls
+```
+
+**Organization ID from company**:
+```
+1. Call LINKEDIN_GET_COMPANY_INFO with organization_id
+2. Extract organization URN for posting as a company page
+```
+
+### Image Upload Flow
+
+- Call REGISTER_IMAGE_UPLOAD to get upload URL and asset URN
+- Upload the binary image to the provided URL
+- Use the asset URN when creating a post with media
+- Verify with GET_IMAGES if upload status is uncertain
+
+## Known Pitfalls
+
+**Authentication**:
+- LinkedIn OAuth tokens have limited scopes; ensure required permissions are granted
+- Tokens expire; re-authenticate if API calls return 401 errors
+
+**URN Formats**:
+- LinkedIn uses URN identifiers (e.g., 'urn:li:person:ABC123')
+- Always use the full URN format, not just the alphanumeric ID portion
+- Organization URNs differ from person URNs
+
+**Rate Limits**:
+- LinkedIn API has strict daily rate limits on post creation and comments
+- Implement backoff strategies for bulk operations
+- Monitor 429 responses and respect Retry-After headers
+
+**Content Restrictions**:
+- Posts have character limits enforced by the API
+- Some content types (polls, documents) may require additional API features
+- HTML markup in post text is not supported
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Get my profile | LINKEDIN_GET_MY_INFO | (none) |
+| Create post | LINKEDIN_CREATE_LINKED_IN_POST | text, visibility |
+| Get company info | LINKEDIN_GET_COMPANY_INFO | organization_id |
+| Register image upload | LINKEDIN_REGISTER_IMAGE_UPLOAD | owner |
+| 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/plugins/awesome-claude-skills/linkhut-automation/SKILL.md b/plugins/awesome-claude-skills/linkhut-automation/SKILL.md
new file mode 100644
index 0000000..7402447
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/linkup-automation/SKILL.md b/plugins/awesome-claude-skills/linkup-automation/SKILL.md
new file mode 100644
index 0000000..16cde6a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/listclean-automation/SKILL.md b/plugins/awesome-claude-skills/listclean-automation/SKILL.md
new file mode 100644
index 0000000..983050e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/listennotes-automation/SKILL.md b/plugins/awesome-claude-skills/listennotes-automation/SKILL.md
new file mode 100644
index 0000000..5e1b442
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/livesession-automation/SKILL.md b/plugins/awesome-claude-skills/livesession-automation/SKILL.md
new file mode 100644
index 0000000..0fb6712
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/lmnt-automation/SKILL.md b/plugins/awesome-claude-skills/lmnt-automation/SKILL.md
new file mode 100644
index 0000000..d8e6faa
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/lodgify-automation/SKILL.md b/plugins/awesome-claude-skills/lodgify-automation/SKILL.md
new file mode 100644
index 0000000..b878146
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/logo-dev-automation/SKILL.md b/plugins/awesome-claude-skills/logo-dev-automation/SKILL.md
new file mode 100644
index 0000000..35283a8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/loomio-automation/SKILL.md b/plugins/awesome-claude-skills/loomio-automation/SKILL.md
new file mode 100644
index 0000000..edf0b34
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/loyverse-automation/SKILL.md b/plugins/awesome-claude-skills/loyverse-automation/SKILL.md
new file mode 100644
index 0000000..7fad652
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/magnetic-automation/SKILL.md b/plugins/awesome-claude-skills/magnetic-automation/SKILL.md
new file mode 100644
index 0000000..5e4155d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mailbluster-automation/SKILL.md b/plugins/awesome-claude-skills/mailbluster-automation/SKILL.md
new file mode 100644
index 0000000..c1ddc1d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mailboxlayer-automation/SKILL.md b/plugins/awesome-claude-skills/mailboxlayer-automation/SKILL.md
new file mode 100644
index 0000000..c83442e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mailcheck-automation/SKILL.md b/plugins/awesome-claude-skills/mailcheck-automation/SKILL.md
new file mode 100644
index 0000000..1d07d58
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mailchimp-automation/SKILL.md b/plugins/awesome-claude-skills/mailchimp-automation/SKILL.md
new file mode 100644
index 0000000..f7497b7
--- /dev/null
+++ b/plugins/awesome-claude-skills/mailchimp-automation/SKILL.md
@@ -0,0 +1,236 @@
+---
+name: mailchimp-automation
+description: Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Mailchimp Automation via Rube MCP
+
+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)
+- Active Mailchimp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mailchimp`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mailchimp`
+3. If connection is not ACTIVE, follow the returned auth link to complete Mailchimp OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Send Email Campaigns
+
+**When to use**: User wants to create, configure, test, and send an email campaign.
+
+**Tool sequence**:
+1. `MAILCHIMP_GET_LISTS_INFO` - List available audiences and get list_id [Prerequisite]
+2. `MAILCHIMP_ADD_CAMPAIGN` - Create a new campaign with type, audience, subject, from name [Required]
+3. `MAILCHIMP_SET_CAMPAIGN_CONTENT` - Set HTML content for the campaign [Required]
+4. `MAILCHIMP_SEND_TEST_EMAIL` - Send preview to reviewers before live send [Optional]
+5. `MAILCHIMP_SEND_CAMPAIGN` - Send the campaign immediately [Required]
+6. `MAILCHIMP_SCHEDULE_CAMPAIGN` - Schedule for future delivery instead of immediate send [Optional]
+
+**Key parameters for MAILCHIMP_ADD_CAMPAIGN**:
+- `type`: "regular", "plaintext", "rss", or "variate" (required)
+- `recipients__list__id`: Audience/list ID for recipients
+- `settings__subject__line`: Email subject line
+- `settings__from__name`: Sender display name
+- `settings__reply__to`: Reply-to email address (required for sending)
+- `settings__title`: Internal campaign title
+- `settings__preview__text`: Preview text shown in inbox
+
+**Key parameters for MAILCHIMP_SET_CAMPAIGN_CONTENT**:
+- `campaign_id`: Campaign ID from creation step (required)
+- `html`: Raw HTML content for the email
+- `plain_text`: Plain-text version (auto-generated if omitted)
+- `template__id`: Use a pre-built template instead of raw HTML
+
+**Pitfalls**:
+- `MAILCHIMP_SEND_CAMPAIGN` is irreversible; always send a test email first and get explicit user approval
+- Campaign must be in "save" (draft) status with valid audience, subject, from name, verified email, and content before sending
+- `MAILCHIMP_SCHEDULE_CAMPAIGN` requires a valid future datetime; past timestamps fail
+- Templates and HTML content must include compliant footer/unsubscribe merge tags
+- Mailchimp uses double-underscore notation for nested params (e.g., `settings__subject__line`)
+
+### 2. Manage Audiences and Subscribers
+
+**When to use**: User wants to view audiences, list subscribers, or check subscriber details.
+
+**Tool sequence**:
+1. `MAILCHIMP_GET_LISTS_INFO` - List all audiences with member counts [Required]
+2. `MAILCHIMP_GET_LIST_INFO` - Get details for a specific audience [Optional]
+3. `MAILCHIMP_LIST_MEMBERS_INFO` - List members with status filter and pagination [Required]
+4. `MAILCHIMP_SEARCH_MEMBERS` - Search by email or name across lists [Optional]
+5. `MAILCHIMP_GET_MEMBER_INFO` - Get detailed profile for a specific subscriber [Optional]
+6. `MAILCHIMP_LIST_SEGMENTS` - List segments within an audience [Optional]
+
+**Key parameters for MAILCHIMP_LIST_MEMBERS_INFO**:
+- `list_id`: Audience ID (required)
+- `status`: "subscribed", "unsubscribed", "cleaned", "pending", "transactional", "archived"
+- `count`: Records per page (default 10, max 1000)
+- `offset`: Pagination offset (default 0)
+- `sort_field`: "timestamp_opt", "timestamp_signup", or "last_changed"
+- `fields`: Comma-separated list to limit response size
+
+**Pitfalls**:
+- `stats.avg_open_rate` and `stats.avg_click_rate` are 0-1 fractions, NOT 0-100 percentages
+- Always use `status="subscribed"` to filter active subscribers; omitting returns all statuses
+- Must paginate using `count` and `offset` until collected members match `total_items`
+- Large list responses may be truncated; data is under `response.data.members`
+
+### 3. Add and Update Subscribers
+
+**When to use**: User wants to add new subscribers, update existing ones, or bulk-manage list membership.
+
+**Tool sequence**:
+1. `MAILCHIMP_GET_LIST_INFO` - Validate target audience exists [Prerequisite]
+2. `MAILCHIMP_SEARCH_MEMBERS` - Check if contact already exists [Optional]
+3. `MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER` - Upsert subscriber (create or update) [Required]
+4. `MAILCHIMP_ADD_MEMBER_TO_LIST` - Add new subscriber (create only) [Optional]
+5. `MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS` - Bulk manage segment membership [Optional]
+
+**Key parameters for MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER**:
+- `list_id`: Audience ID (required)
+- `subscriber_hash`: MD5 hash of lowercase email (required)
+- `email_address`: Subscriber email (required)
+- `status_if_new`: Status for new subscribers: "subscribed", "pending", etc. (required)
+- `status`: Status for existing subscribers
+- `merge_fields`: Object with merge tag keys (e.g., `{"FNAME": "John", "LNAME": "Doe"}`)
+- `tags`: Array of tag strings
+
+**Key parameters for MAILCHIMP_ADD_MEMBER_TO_LIST**:
+- `list_id`: Audience ID (required)
+- `email_address`: Subscriber email (required)
+- `status`: "subscribed", "pending", "unsubscribed", "cleaned", "transactional" (required)
+
+**Pitfalls**:
+- `subscriber_hash` must be MD5 of the **lowercase** email; incorrect casing causes 404s or duplicates
+- Use `MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER` (upsert) instead of `MAILCHIMP_ADD_MEMBER_TO_LIST` to avoid duplicate errors
+- `status_if_new` determines status only for new contacts; existing contacts use `status`
+- Use `skip_merge_validation: true` to bypass required merge field validation
+- `MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS` manages static segment membership, not list membership
+
+### 4. View Campaign Reports and Analytics
+
+**When to use**: User wants to review campaign performance, open rates, click rates, or subscriber engagement.
+
+**Tool sequence**:
+1. `MAILCHIMP_LIST_CAMPAIGNS` - List sent campaigns with report summaries [Required]
+2. `MAILCHIMP_SEARCH_CAMPAIGNS` - Find campaigns by name, subject, or content [Optional]
+3. `MAILCHIMP_GET_CAMPAIGN_REPORT` - Get detailed performance report for a campaign [Required]
+4. `MAILCHIMP_LIST_CAMPAIGN_REPORTS` - Bulk fetch reports across multiple campaigns [Optional]
+5. `MAILCHIMP_LIST_CAMPAIGN_DETAILS` - Get link-level click statistics [Optional]
+6. `MAILCHIMP_GET_CAMPAIGN_LINK_DETAILS` - Drill into specific link click data [Optional]
+7. `MAILCHIMP_LIST_CLICKED_LINK_SUBSCRIBERS` - See who clicked a specific link [Optional]
+8. `MAILCHIMP_GET_SUBSCRIBER_EMAIL_ACTIVITY` - Get per-subscriber campaign activity [Optional]
+9. `MAILCHIMP_GET_CAMPAIGN_CONTENT` - Retrieve campaign HTML content [Optional]
+
+**Key parameters for MAILCHIMP_LIST_CAMPAIGNS**:
+- `status`: "save", "paused", "schedule", "sending", "sent"
+- `count` / `offset`: Pagination (default 10, max 1000)
+- `since_send_time` / `before_send_time`: ISO 8601 date range filter
+- `sort_field`: "create_time" or "send_time"
+- `fields`: Limit response fields for performance
+
+**Key parameters for MAILCHIMP_GET_CAMPAIGN_REPORT**:
+- `campaign_id`: Campaign ID (required)
+- Returns: opens, clicks, bounces, unsubscribes, timeseries, industry_stats
+
+**Pitfalls**:
+- `MAILCHIMP_LIST_CAMPAIGNS` only returns high-level `report_summary`; use `MAILCHIMP_GET_CAMPAIGN_REPORT` for detailed metrics
+- Draft/unsent campaigns lack meaningful report data
+- When using `fields` parameter on LIST_CAMPAIGNS, explicitly request `send_time` and `report_summary` subfields
+- Pagination defaults are low (10 records); iterate with `count` and `offset` until `total_items` is covered
+- `send_time` is ISO 8601 with timezone; parse carefully
+
+## Common Patterns
+
+### ID Resolution
+Always resolve names to IDs before operations:
+- **Audience name -> list_id**: `MAILCHIMP_GET_LISTS_INFO` and match by name
+- **Subscriber email -> subscriber_hash**: Compute MD5 of lowercase email in code
+- **Campaign name -> campaign_id**: `MAILCHIMP_SEARCH_CAMPAIGNS` with query
+- **Segment name -> segment_id**: `MAILCHIMP_LIST_SEGMENTS` with list_id
+
+### Pagination
+Mailchimp uses offset-based pagination:
+- Use `count` (page size, max 1000) and `offset` (skip N records)
+- Continue until collected records match `total_items` from the response
+- Default `count` is 10; always set explicitly for bulk operations
+- Search endpoints max at 10 pages (300 results for 30/page)
+
+### Subscriber Hash
+Many endpoints require `subscriber_hash` (MD5 of lowercase email):
+```
+import hashlib
+subscriber_hash = hashlib.md5(email.lower().encode()).hexdigest()
+```
+
+## Known Pitfalls
+
+### ID Formats
+- `list_id` (audience ID) is a short alphanumeric string (e.g., "abc123def4")
+- `campaign_id` is an alphanumeric string
+- `subscriber_hash` is an MD5 hex string (32 characters)
+- Segment IDs are integers
+
+### Rate Limits
+- Mailchimp enforces API rate limits; use batching for bulk subscriber operations
+- High-volume use of GET_MEMBER_INFO and ADD_OR_UPDATE_LIST_MEMBER can trigger throttling
+- Use `MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS` for bulk segment operations
+
+### Parameter Quirks
+- Nested parameters use double-underscore notation: `settings__subject__line`, `recipients__list__id`
+- `avg_open_rate` and `avg_click_rate` are 0-1 fractions, not percentages
+- `status_if_new` only applies to new contacts in upsert operations
+- `subscriber_hash` must be MD5 of lowercase email; wrong casing creates phantom records
+- Campaign `type` is required for creation; most common is "regular"
+- `MAILCHIMP_SEND_CAMPAIGN` returns HTTP 204 on success (no body)
+
+### Content and Compliance
+- Campaign HTML must include unsubscribe link and physical address (merge tags)
+- Content must be set via `MAILCHIMP_SET_CAMPAIGN_CONTENT` before sending
+- Test emails require campaign to have content already set
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List audiences | `MAILCHIMP_GET_LISTS_INFO` | `count`, `offset` |
+| Get audience details | `MAILCHIMP_GET_LIST_INFO` | `list_id` |
+| Create campaign | `MAILCHIMP_ADD_CAMPAIGN` | `type`, `recipients__list__id`, `settings__subject__line` |
+| Set campaign content | `MAILCHIMP_SET_CAMPAIGN_CONTENT` | `campaign_id`, `html` |
+| Send test email | `MAILCHIMP_SEND_TEST_EMAIL` | `campaign_id`, `test_emails` |
+| Send campaign | `MAILCHIMP_SEND_CAMPAIGN` | `campaign_id` |
+| Schedule campaign | `MAILCHIMP_SCHEDULE_CAMPAIGN` | `campaign_id`, `schedule_time` |
+| Get campaign info | `MAILCHIMP_GET_CAMPAIGN_INFO` | `campaign_id` |
+| Search campaigns | `MAILCHIMP_SEARCH_CAMPAIGNS` | `query` |
+| List campaigns | `MAILCHIMP_LIST_CAMPAIGNS` | `status`, `count`, `offset` |
+| Replicate campaign | `MAILCHIMP_REPLICATE_CAMPAIGN` | `campaign_id` |
+| List subscribers | `MAILCHIMP_LIST_MEMBERS_INFO` | `list_id`, `status`, `count`, `offset` |
+| Search members | `MAILCHIMP_SEARCH_MEMBERS` | `query`, `list_id` |
+| Get member info | `MAILCHIMP_GET_MEMBER_INFO` | `list_id`, `subscriber_hash` |
+| Add subscriber | `MAILCHIMP_ADD_MEMBER_TO_LIST` | `list_id`, `email_address`, `status` |
+| Upsert subscriber | `MAILCHIMP_ADD_OR_UPDATE_LIST_MEMBER` | `list_id`, `subscriber_hash`, `email_address`, `status_if_new` |
+| Batch members | `MAILCHIMP_BATCH_ADD_OR_REMOVE_MEMBERS` | `list_id`, `segment_id` |
+| List segments | `MAILCHIMP_LIST_SEGMENTS` | `list_id` |
+| Campaign report | `MAILCHIMP_GET_CAMPAIGN_REPORT` | `campaign_id` |
+| All reports | `MAILCHIMP_LIST_CAMPAIGN_REPORTS` | `count`, `offset` |
+| Link click details | `MAILCHIMP_LIST_CAMPAIGN_DETAILS` | `campaign_id`, `count` |
+| 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/plugins/awesome-claude-skills/mailcoach-automation/SKILL.md b/plugins/awesome-claude-skills/mailcoach-automation/SKILL.md
new file mode 100644
index 0000000..cc95b66
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mailerlite-automation/SKILL.md b/plugins/awesome-claude-skills/mailerlite-automation/SKILL.md
new file mode 100644
index 0000000..f6f3298
--- /dev/null
+++ b/plugins/awesome-claude-skills/mailerlite-automation/SKILL.md
@@ -0,0 +1,139 @@
+---
+name: MailerLite Automation
+description: "Automate email marketing workflows including subscriber management, campaign analytics, group segmentation, and account monitoring through MailerLite via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# MailerLite Automation
+
+Automate email marketing operations -- manage subscribers, analyze campaign performance, organize groups and segments, and monitor account health -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/mailerlite](https://composio.dev/toolkits/mailerlite)
+
+---
+
+## Setup
+
+1. Connect your MailerLite account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `MAILERLITE_*` tools become available for execution
+
+---
+
+## Core Workflows
+
+### 1. Verify Account & Fetch Metadata
+Retrieve account details including plan limits and timezone to ensure consistent reporting.
+
+**Tool:** `MAILERLITE_GET_ACCOUNT_INFO`
+
+```
+No parameters required -- returns account metadata, plan details, and timezone configuration.
+```
+
+Always run this first to establish plan constraints and timezone for consistent time-windowed queries.
+
+---
+
+### 2. Get Account-Wide Performance Stats
+Retrieve aggregate subscriber counts, sent email totals, and engagement metrics for a health snapshot.
+
+**Tool:** `MAILERLITE_GET_ACCOUNT_STATS`
+
+```
+No parameters required -- returns overall subscriber counts, sent emails, and performance metrics.
+```
+
+---
+
+### 3. List & Paginate Subscribers
+Retrieve subscribers with optional status filtering and cursor-based pagination.
+
+**Tool:** `MAILERLITE_GET_SUBSCRIBERS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `filter[status]` | string | No | Filter by: `active`, `unsubscribed`, `unconfirmed`, `bounced`, `junk` |
+| `limit` | integer | No | Subscribers per page (default: 25) |
+| `cursor` | string | No | Pagination cursor from previous response `meta.cursor` |
+| `include` | string | No | Set to `groups` to include group memberships |
+
+**Important:** Loop with `meta.next_cursor` until `null` to build a complete subscriber list.
+
+---
+
+### 4. List & Analyze Campaigns
+Retrieve campaigns with optional status/type filters and page-based pagination.
+
+**Tool:** `MAILERLITE_GET_CAMPAIGNS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `filter[status]` | string | No | Filter by: `sent`, `draft`, `ready` |
+| `filter[type]` | string | No | Filter by: `regular`, `ab`, `resend`, `rss` |
+| `limit` | integer | No | Items per page (default: 25) |
+| `page` | integer | No | Page number (default: 1) |
+
+**Important:** Paginate using `meta.last_page` to avoid omitting campaigns from historical analysis.
+
+---
+
+### 5. Manage Subscriber Groups
+List, filter, and sort subscriber groups for audience organization.
+
+**Tool:** `MAILERLITE_GET_GROUPS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `filter[name]` | string | No | Partial name match filter |
+| `limit` | integer | No | Max groups to return |
+| `page` | integer | No | Page number (starting from 1) |
+| `sort` | string | No | Sort by: `name`, `total`, `open_rate`, `click_rate`, `created_at` (prefix `-` for descending) |
+
+---
+
+### 6. Retrieve Audience Segments & Custom Fields
+Fetch segments and custom field definitions for advanced audience analysis.
+
+**Tools:** `MAILERLITE_GET_SEGMENTS` and `MAILERLITE_GET_FIELDS`
+
+**Segments:**
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `limit` | integer | No | Max segments to return (max 250) |
+| `page` | integer | No | Page number (starting from 1) |
+
+**Fields:** No parameters required -- returns all custom field definitions.
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **Subscriber pagination is cursor-based** | `MAILERLITE_GET_SUBSCRIBERS` uses `meta.next_cursor` -- you must loop until `null` or counts will be incomplete |
+| **Campaign pagination is page-based** | `MAILERLITE_GET_CAMPAIGNS` uses `page`/`limit` with `meta.last_page` -- stopping early omits campaigns and distorts trends |
+| **Sampling bias** | Computing engagement metrics from only the first page introduces bias; always aggregate across all pages |
+| **Nested response shape** | MailerLite payloads are nested under `results[i].response.data` with `data` and `meta` subkeys, not a flat `data` key -- parse accordingly |
+| **API quotas** | Subscriber listing is limited by MailerLite Connect API quotas -- plan batch operations accordingly |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `MAILERLITE_GET_ACCOUNT_INFO` | Verify auth and review account metadata |
+| `MAILERLITE_GET_ACCOUNT_STATS` | Get aggregate performance metrics |
+| `MAILERLITE_GET_SUBSCRIBERS` | List subscribers with filtering and pagination |
+| `MAILERLITE_GET_CAMPAIGNS` | List campaigns with status/type filters |
+| `MAILERLITE_GET_GROUPS` | List and sort subscriber groups |
+| `MAILERLITE_GET_SEGMENTS` | List audience segments |
+| `MAILERLITE_GET_FIELDS` | Retrieve custom field definitions |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/mailersend-automation/SKILL.md b/plugins/awesome-claude-skills/mailersend-automation/SKILL.md
new file mode 100644
index 0000000..ba26156
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mails-so-automation/SKILL.md b/plugins/awesome-claude-skills/mails-so-automation/SKILL.md
new file mode 100644
index 0000000..dafdbc8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mailsoftly-automation/SKILL.md b/plugins/awesome-claude-skills/mailsoftly-automation/SKILL.md
new file mode 100644
index 0000000..e56c29c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/maintainx-automation/SKILL.md b/plugins/awesome-claude-skills/maintainx-automation/SKILL.md
new file mode 100644
index 0000000..988be8e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/make-automation/SKILL.md b/plugins/awesome-claude-skills/make-automation/SKILL.md
new file mode 100644
index 0000000..ebcfb02
--- /dev/null
+++ b/plugins/awesome-claude-skills/make-automation/SKILL.md
@@ -0,0 +1,206 @@
+---
+name: make-automation
+description: "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Make Automation via Rube MCP
+
+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)
+- Active Make connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `make`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `make`
+3. If connection is not ACTIVE, follow the returned auth link to complete Make authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Get Operations Data
+
+**When to use**: User wants to retrieve operation logs or usage data from Make scenarios
+
+**Tool sequence**:
+1. `MAKE_GET_OPERATIONS` - Retrieve operation records [Required]
+
+**Key parameters**:
+- Check current schema via RUBE_SEARCH_TOOLS for available filters
+- May include date range, scenario ID, or status filters
+
+**Pitfalls**:
+- Operations data may be paginated; check for pagination tokens
+- Date filters must match expected format from schema
+- Large result sets should be filtered by date range or scenario
+
+### 2. List Available Languages
+
+**When to use**: User wants to see supported languages for Make scenarios or interfaces
+
+**Tool sequence**:
+1. `MAKE_LIST_ENUMS_LANGUAGES` - Get all supported language codes [Required]
+
+**Key parameters**:
+- No required parameters; returns complete language list
+
+**Pitfalls**:
+- Language codes follow standard locale format (e.g., 'en', 'fr', 'de')
+- List is static and rarely changes; cache results when possible
+
+### 3. List Available Timezones
+
+**When to use**: User wants to see supported timezones for scheduling Make scenarios
+
+**Tool sequence**:
+1. `MAKE_LIST_ENUMS_TIMEZONES` - Get all supported timezone identifiers [Required]
+
+**Key parameters**:
+- No required parameters; returns complete timezone list
+
+**Pitfalls**:
+- Timezone identifiers use IANA format (e.g., 'America/New_York', 'Europe/London')
+- List is static and rarely changes; cache results when possible
+- Use these exact timezone strings when configuring scenario schedules
+
+### 4. Scenario Configuration Lookup
+
+**When to use**: User needs to configure scenarios with correct language and timezone values
+
+**Tool sequence**:
+1. `MAKE_LIST_ENUMS_LANGUAGES` - Get valid language codes [Required]
+2. `MAKE_LIST_ENUMS_TIMEZONES` - Get valid timezone identifiers [Required]
+
+**Key parameters**:
+- No parameters needed for either call
+
+**Pitfalls**:
+- Always verify language and timezone values against these enums before using in configuration
+- Using invalid values in scenario configuration will cause errors
+
+## Common Patterns
+
+### Enum Validation
+
+Before configuring any Make scenario properties that accept language or timezone:
+```
+1. Call MAKE_LIST_ENUMS_LANGUAGES or MAKE_LIST_ENUMS_TIMEZONES
+2. Verify the desired value exists in the returned list
+3. Use the exact string value from the enum list
+```
+
+### Operations Monitoring
+
+```
+1. Call MAKE_GET_OPERATIONS with date range filters
+2. Analyze operation counts, statuses, and error rates
+3. Identify failed operations for troubleshooting
+```
+
+### Caching Strategy for Enums
+
+Since language and timezone lists are static:
+```
+1. Call MAKE_LIST_ENUMS_LANGUAGES once at workflow start
+2. Store results in memory or local cache
+3. Validate user inputs against cached values
+4. Refresh cache only when starting a new session
+```
+
+### Operations Analysis Workflow
+
+For scenario health monitoring:
+```
+1. Call MAKE_GET_OPERATIONS with recent date range
+2. Group operations by scenario ID
+3. Calculate success/failure ratios per scenario
+4. Identify scenarios with high error rates
+5. Report findings to user or notification channel
+```
+
+### Integration with Other Toolkits
+
+Make workflows often connect to other apps. Compose multi-tool workflows:
+```
+1. Call RUBE_SEARCH_TOOLS to find tools for the target app
+2. Connect required toolkits via RUBE_MANAGE_CONNECTIONS
+3. Use Make operations data to understand workflow execution patterns
+4. Execute equivalent workflows directly via individual app toolkits
+```
+
+## Known Pitfalls
+
+**Limited Toolkit**:
+- The Make toolkit in Composio currently has limited tools (operations, languages, timezones)
+- For full scenario management (creating, editing, running scenarios), consider using Make's native API
+- Always call RUBE_SEARCH_TOOLS to check for newly available tools
+- The toolkit may be expanded over time; re-check periodically
+
+**Operations Data**:
+- Operation records may have significant volume for active accounts
+- Always filter by date range to avoid fetching excessive data
+- Operation counts relate to Make's pricing tiers and quota usage
+- Failed operations should be investigated; they may indicate scenario configuration issues
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Enum lists return arrays of objects with code and label fields
+- Operations data includes nested metadata about scenario execution
+- Parse defensively with fallbacks for optional fields
+
+**Rate Limits**:
+- Make API has rate limits per API token
+- Avoid rapid repeated calls to the same endpoint
+- Cache enum results (languages, timezones) as they rarely change
+- Operations queries should use targeted date ranges
+
+**Authentication**:
+- Make API uses token-based authentication
+- Tokens may have different permission scopes
+- Some operations data may be restricted based on token scope
+- Check that the authenticated user has access to the target organization
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Get operations | MAKE_GET_OPERATIONS | (check schema for filters) |
+| List languages | MAKE_LIST_ENUMS_LANGUAGES | (none) |
+| List timezones | MAKE_LIST_ENUMS_TIMEZONES | (none) |
+
+## Additional Notes
+
+### Alternative Approaches
+
+Since the Make toolkit has limited tools, consider these alternatives for common Make use cases:
+
+| Make Use Case | Alternative Approach |
+|--------------|---------------------|
+| Trigger a scenario | Use Make's native webhook or API endpoint directly |
+| Create a scenario | Use Make's scenario management API directly |
+| Schedule execution | Use RUBE_MANAGE_RECIPE_SCHEDULE with composed workflows |
+| Multi-app workflow | Compose individual toolkit tools via RUBE_MULTI_EXECUTE_TOOL |
+| Data transformation | Use RUBE_REMOTE_WORKBENCH for complex processing |
+
+### Composing Equivalent Workflows
+
+Instead of relying solely on Make's toolkit, build equivalent automation directly:
+1. Identify the apps involved in your Make scenario
+2. Search for each app's tools via RUBE_SEARCH_TOOLS
+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/plugins/awesome-claude-skills/many-chat-automation/SKILL.md b/plugins/awesome-claude-skills/many-chat-automation/SKILL.md
new file mode 100644
index 0000000..bd6824d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/many_chat-automation/SKILL.md b/plugins/awesome-claude-skills/many_chat-automation/SKILL.md
new file mode 100644
index 0000000..a59b7ef
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mapbox-automation/SKILL.md b/plugins/awesome-claude-skills/mapbox-automation/SKILL.md
new file mode 100644
index 0000000..ddf1dcf
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mapulus-automation/SKILL.md b/plugins/awesome-claude-skills/mapulus-automation/SKILL.md
new file mode 100644
index 0000000..41661c8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mboum-automation/SKILL.md b/plugins/awesome-claude-skills/mboum-automation/SKILL.md
new file mode 100644
index 0000000..1b56133
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/melo-automation/SKILL.md b/plugins/awesome-claude-skills/melo-automation/SKILL.md
new file mode 100644
index 0000000..cecfc50
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mem-automation/SKILL.md b/plugins/awesome-claude-skills/mem-automation/SKILL.md
new file mode 100644
index 0000000..bceac58
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mem0-automation/SKILL.md b/plugins/awesome-claude-skills/mem0-automation/SKILL.md
new file mode 100644
index 0000000..af24b4d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/memberspot-automation/SKILL.md b/plugins/awesome-claude-skills/memberspot-automation/SKILL.md
new file mode 100644
index 0000000..756e68a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/memberstack-automation/SKILL.md b/plugins/awesome-claude-skills/memberstack-automation/SKILL.md
new file mode 100644
index 0000000..37ff909
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/membervault-automation/SKILL.md b/plugins/awesome-claude-skills/membervault-automation/SKILL.md
new file mode 100644
index 0000000..661cd3c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/metaads-automation/SKILL.md b/plugins/awesome-claude-skills/metaads-automation/SKILL.md
new file mode 100644
index 0000000..463ea3a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/metaphor-automation/SKILL.md b/plugins/awesome-claude-skills/metaphor-automation/SKILL.md
new file mode 100644
index 0000000..89c78e6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mezmo-automation/SKILL.md b/plugins/awesome-claude-skills/mezmo-automation/SKILL.md
new file mode 100644
index 0000000..011eb72
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/microsoft-clarity-automation/SKILL.md b/plugins/awesome-claude-skills/microsoft-clarity-automation/SKILL.md
new file mode 100644
index 0000000..fda424a
--- /dev/null
+++ b/plugins/awesome-claude-skills/microsoft-clarity-automation/SKILL.md
@@ -0,0 +1,150 @@
+---
+name: Microsoft Clarity Automation
+description: "Automate user behavior analytics with Microsoft Clarity -- export heatmap data, session metrics, and engagement analytics segmented by browser, device, country, source, and more through the Composio Microsoft Clarity integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Microsoft Clarity Automation
+
+Export **Microsoft Clarity** user behavior analytics directly from Claude Code. Pull heatmap data, session metrics, and engagement insights segmented by multiple dimensions without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/microsoft_clarity](https://composio.dev/toolkits/microsoft_clarity)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Microsoft Clarity account when prompted. The agent will provide an authentication link.
+3. Ensure your Clarity project has sufficient data collection enabled for the dimensions you want to analyze.
+
+---
+
+## Core Workflows
+
+### 1. Export Recent Analytics Data
+
+Export Clarity analytics data for the last 1-3 days, segmented by up to three dimensions simultaneously.
+
+**Tool:** `MICROSOFT_CLARITY_DATA_EXPORT`
+
+Key parameters:
+- `numOfDays` (required) -- number of days to export: `1` (last 24h), `2` (last 48h), or `3` (last 72h)
+- `dimension1` -- first breakdown dimension
+- `dimension2` -- second breakdown dimension (optional)
+- `dimension3` -- third breakdown dimension (optional)
+
+Available dimensions:
+- `Browser` -- Chrome, Firefox, Safari, Edge, etc.
+- `Device` -- Desktop, Mobile, Tablet
+- `Country/Region` -- geographic location of users
+- `OS` -- Windows, macOS, iOS, Android, etc.
+- `Source` -- traffic source (e.g., google, direct, referral)
+- `Medium` -- traffic medium (organic, cpc, referral, etc.)
+- `Campaign` -- marketing campaign name
+- `Channel` -- traffic channel grouping
+- `URL` -- specific page URLs
+
+Example prompt: *"Export Clarity data for the last 24 hours broken down by Device and Country/Region"*
+
+---
+
+### 2. Device Performance Analysis
+
+Analyze how user behavior differs across device types to optimize responsive design.
+
+**Tool:** `MICROSOFT_CLARITY_DATA_EXPORT`
+
+Configuration: `numOfDays: 3`, `dimension1: "Device"`, `dimension2: "Browser"`
+
+Example prompt: *"Show me Clarity metrics for the last 3 days by Device and Browser"*
+
+---
+
+### 3. Traffic Source Breakdown
+
+Understand which traffic sources drive the most engaged users.
+
+**Tool:** `MICROSOFT_CLARITY_DATA_EXPORT`
+
+Configuration: `numOfDays: 2`, `dimension1: "Source"`, `dimension2: "Medium"`
+
+Example prompt: *"Export Clarity data for the last 48 hours broken down by Source and Medium"*
+
+---
+
+### 4. Geographic User Behavior
+
+Analyze user engagement patterns across different countries and regions.
+
+**Tool:** `MICROSOFT_CLARITY_DATA_EXPORT`
+
+Configuration: `numOfDays: 3`, `dimension1: "Country/Region"`, `dimension2: "Device"`
+
+Example prompt: *"Get Clarity data for the last 72 hours segmented by Country/Region and Device type"*
+
+---
+
+### 5. Page-Level Performance
+
+Examine which specific URLs have the highest or lowest engagement metrics.
+
+**Tool:** `MICROSOFT_CLARITY_DATA_EXPORT`
+
+Configuration: `numOfDays: 1`, `dimension1: "URL"`, `dimension2: "Device"`
+
+Example prompt: *"Export yesterday's Clarity data broken down by URL and Device"*
+
+---
+
+### 6. Campaign Attribution Analysis
+
+Evaluate marketing campaign effectiveness through user behavior metrics.
+
+**Tool:** `MICROSOFT_CLARITY_DATA_EXPORT`
+
+Configuration: `numOfDays: 3`, `dimension1: "Campaign"`, `dimension2: "Channel"`, `dimension3: "Device"`
+
+Example prompt: *"Show Clarity engagement data for the last 3 days by Campaign, Channel, and Device"*
+
+---
+
+## Known Pitfalls
+
+- **Limited time window:** Data export is limited to the last 1, 2, or 3 days only. The `numOfDays` parameter only accepts values of 1, 2, or 3. For longer historical analysis, you need to run exports periodically and aggregate them externally.
+- **Dimension name exact match:** Dimension values must match exactly as listed (e.g., `Country/Region` not `country` or `region`). Case and slashes matter.
+- **Maximum three dimensions:** You can segment by up to three dimensions per export. For more complex analysis, run multiple exports with different dimension combinations.
+- **Data availability lag:** Clarity data may have a short processing delay. Very recent sessions (last few minutes) may not appear in exports.
+- **Single tool limitation:** The Clarity integration currently offers only the data export tool. For heatmap visualizations and session recordings, use the Clarity web dashboard directly.
+- **Response size:** Exports with high-cardinality dimensions like `URL` combined with other dimensions can produce large response payloads. Consider narrowing your time window or using fewer dimensions.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `MICROSOFT_CLARITY_DATA_EXPORT` | Export analytics data with up to 3 dimensional breakdowns |
+
+**Available Dimensions:**
+
+| Dimension | Description |
+|---|---|
+| `Browser` | Web browser (Chrome, Firefox, Safari, etc.) |
+| `Device` | Device type (Desktop, Mobile, Tablet) |
+| `Country/Region` | Geographic location |
+| `OS` | Operating system |
+| `Source` | Traffic source |
+| `Medium` | Traffic medium |
+| `Campaign` | Marketing campaign |
+| `Channel` | Traffic channel grouping |
+| `URL` | Specific page URL |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/microsoft-teams-automation/SKILL.md b/plugins/awesome-claude-skills/microsoft-teams-automation/SKILL.md
new file mode 100644
index 0000000..91cac3c
--- /dev/null
+++ b/plugins/awesome-claude-skills/microsoft-teams-automation/SKILL.md
@@ -0,0 +1,216 @@
+---
+name: microsoft-teams-automation
+description: "Automate Microsoft Teams tasks via Rube MCP (Composio): send messages, manage channels, create meetings, handle chats, and search messages. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Microsoft Teams Automation via Rube MCP
+
+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)
+- Active Microsoft Teams connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_teams`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add 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_teams`
+3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Channel Messages
+
+**When to use**: User wants to post a message to a Teams channel
+
+**Tool sequence**:
+1. `MICROSOFT_TEAMS_TEAMS_LIST` - List teams to find target team [Prerequisite]
+2. `MICROSOFT_TEAMS_TEAMS_LIST_CHANNELS` - List channels in the team [Prerequisite]
+3. `MICROSOFT_TEAMS_TEAMS_POST_CHANNEL_MESSAGE` - Post the message [Required]
+
+**Key parameters**:
+- `team_id`: UUID of the team (from TEAMS_LIST)
+- `channel_id`: Channel ID (from LIST_CHANNELS, format: '19:...@thread.tacv2')
+- `content`: Message text or HTML
+- `content_type`: 'text' or 'html'
+
+**Pitfalls**:
+- team_id must be a valid UUID format
+- channel_id must be in thread format (e.g., '19:abc@thread.tacv2')
+- TEAMS_LIST may paginate (~100 items/page); follow @odata.nextLink to find all teams
+- LIST_CHANNELS can return 403 if user lacks access to the team
+- Messages over ~28KB can trigger 400/413 errors; split long content
+- Throttling may return 429; use exponential backoff (1s/2s/4s)
+
+### 2. Send Chat Messages
+
+**When to use**: User wants to send a direct or group chat message
+
+**Tool sequence**:
+1. `MICROSOFT_TEAMS_CHATS_GET_ALL_CHATS` - List existing chats [Optional]
+2. `MICROSOFT_TEAMS_LIST_USERS` - Find users for new chats [Optional]
+3. `MICROSOFT_TEAMS_TEAMS_CREATE_CHAT` - Create a new chat [Optional]
+4. `MICROSOFT_TEAMS_TEAMS_POST_CHAT_MESSAGE` - Send the message [Required]
+
+**Key parameters**:
+- `chat_id`: Chat ID (from GET_ALL_CHATS or CREATE_CHAT)
+- `content`: Message content
+- `content_type`: 'text' or 'html'
+- `chatType`: 'oneOnOne' or 'group' (for CREATE_CHAT)
+- `members`: Array of member objects (for CREATE_CHAT)
+
+**Pitfalls**:
+- CREATE_CHAT requires the authenticated user as one of the members
+- oneOnOne chats return existing chat if one already exists between the two users
+- group chats require at least one member with 'owner' role
+- member user_odata_bind must use full Microsoft Graph URL format
+- Chat filter support is very limited; filter client-side when needed
+
+### 3. Create Online Meetings
+
+**When to use**: User wants to schedule a Microsoft Teams meeting
+
+**Tool sequence**:
+1. `MICROSOFT_TEAMS_LIST_USERS` - Find participant user IDs [Optional]
+2. `MICROSOFT_TEAMS_CREATE_MEETING` - Create the meeting [Required]
+
+**Key parameters**:
+- `subject`: Meeting title
+- `start_date_time`: ISO 8601 start time (e.g., '2024-08-15T10:00:00Z')
+- `end_date_time`: ISO 8601 end time (must be after start)
+- `participants`: Array of user objects with user_id and role
+
+**Pitfalls**:
+- end_date_time must be strictly after start_date_time
+- Participants require valid Microsoft user_id (GUID) values, not emails
+- This creates a standalone meeting not linked to a calendar event
+- For calendar-linked meetings, use OUTLOOK_CALENDAR_CREATE_EVENT with is_online_meeting=true
+
+### 4. Manage Teams and Channels
+
+**When to use**: User wants to list, create, or manage teams and channels
+
+**Tool sequence**:
+1. `MICROSOFT_TEAMS_TEAMS_LIST` - List all accessible teams [Required]
+2. `MICROSOFT_TEAMS_GET_TEAM` - Get details for a specific team [Optional]
+3. `MICROSOFT_TEAMS_TEAMS_LIST_CHANNELS` - List channels in a team [Optional]
+4. `MICROSOFT_TEAMS_GET_CHANNEL` - Get channel details [Optional]
+5. `MICROSOFT_TEAMS_TEAMS_CREATE_CHANNEL` - Create a new channel [Optional]
+6. `MICROSOFT_TEAMS_LIST_TEAM_MEMBERS` - List team members [Optional]
+7. `MICROSOFT_TEAMS_ADD_MEMBER_TO_TEAM` - Add a member to the team [Optional]
+
+**Key parameters**:
+- `team_id`: Team UUID
+- `channel_id`: Channel ID in thread format
+- `filter`: OData filter string (e.g., "startsWith(displayName,'Project')")
+- `select`: Comma-separated properties to return
+
+**Pitfalls**:
+- TEAMS_LIST pagination: follow @odata.nextLink in large tenants
+- Private/shared channels may be omitted unless permissions align
+- GET_CHANNEL returns 404 if team_id or channel_id is wrong
+- Always source IDs from list operations; do not guess ID formats
+
+### 5. Search Messages
+
+**When to use**: User wants to find messages across Teams chats and channels
+
+**Tool sequence**:
+1. `MICROSOFT_TEAMS_SEARCH_MESSAGES` - Search with KQL syntax [Required]
+
+**Key parameters**:
+- `query`: KQL search query (supports from:, sent:, attachments, boolean logic)
+
+**Pitfalls**:
+- Newly posted messages may take 30-60 seconds to appear in search
+- Search is eventually consistent; do not rely on it for immediate delivery confirmation
+- Use message listing tools for real-time message verification
+
+## Common Patterns
+
+### Team and Channel ID Resolution
+
+```
+1. Call MICROSOFT_TEAMS_TEAMS_LIST
+2. Find team by displayName
+3. Extract team id (UUID format)
+4. Call MICROSOFT_TEAMS_TEAMS_LIST_CHANNELS with team_id
+5. Find channel by displayName
+6. Extract channel id (19:...@thread.tacv2 format)
+```
+
+### User Resolution
+
+```
+1. Call MICROSOFT_TEAMS_LIST_USERS
+2. Filter by displayName or email
+3. Extract user id (UUID format)
+4. Use for meeting participants, chat members, or team operations
+```
+
+### Pagination
+
+- Teams/Users: Follow @odata.nextLink URL for next page
+- Chats: Auto-paginates up to limit; use top for page size (max 50)
+- Use `top` parameter to control page size
+- Continue until @odata.nextLink is absent
+
+## Known Pitfalls
+
+**Authentication and Permissions**:
+- Different operations require different Microsoft Graph permissions
+- 403 errors indicate insufficient permissions or team access
+- Some operations require admin consent in the Azure AD tenant
+
+**ID Formats**:
+- Team IDs: UUID format (e.g., '87b0560f-fc0d-4442-add8-b380ca926707')
+- Channel IDs: Thread format (e.g., '19:abc123@thread.tacv2')
+- Chat IDs: Various formats (e.g., '19:meeting_xxx@thread.v2')
+- User IDs: UUID format
+- Never guess IDs; always resolve from list operations
+
+**Rate Limits**:
+- Microsoft Graph enforces throttling
+- 429 responses include Retry-After header
+- Keep requests to a few per second
+- Batch operations help reduce total request count
+
+**Message Formatting**:
+- HTML content_type supports rich formatting
+- Adaptive cards require additional handling
+- Message size limit is approximately 28KB
+- Split long content into multiple messages
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List teams | MICROSOFT_TEAMS_TEAMS_LIST | filter, select, top |
+| Get team details | MICROSOFT_TEAMS_GET_TEAM | team_id |
+| List channels | MICROSOFT_TEAMS_TEAMS_LIST_CHANNELS | team_id, filter |
+| Get channel | MICROSOFT_TEAMS_GET_CHANNEL | team_id, channel_id |
+| Create channel | MICROSOFT_TEAMS_TEAMS_CREATE_CHANNEL | team_id, displayName |
+| Post to channel | MICROSOFT_TEAMS_TEAMS_POST_CHANNEL_MESSAGE | team_id, channel_id, content |
+| List chats | MICROSOFT_TEAMS_CHATS_GET_ALL_CHATS | user_id, limit |
+| Create chat | MICROSOFT_TEAMS_TEAMS_CREATE_CHAT | chatType, members, topic |
+| Post to chat | MICROSOFT_TEAMS_TEAMS_POST_CHAT_MESSAGE | chat_id, content |
+| Create meeting | MICROSOFT_TEAMS_CREATE_MEETING | subject, start_date_time, end_date_time |
+| List users | MICROSOFT_TEAMS_LIST_USERS | filter, select, top |
+| List team members | MICROSOFT_TEAMS_LIST_TEAM_MEMBERS | team_id |
+| Add team member | MICROSOFT_TEAMS_ADD_MEMBER_TO_TEAM | team_id, user_id |
+| 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/plugins/awesome-claude-skills/microsoft-tenant-automation/SKILL.md b/plugins/awesome-claude-skills/microsoft-tenant-automation/SKILL.md
new file mode 100644
index 0000000..5f412d6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/microsoft_clarity-automation/SKILL.md b/plugins/awesome-claude-skills/microsoft_clarity-automation/SKILL.md
new file mode 100644
index 0000000..d180520
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/minerstat-automation/SKILL.md b/plugins/awesome-claude-skills/minerstat-automation/SKILL.md
new file mode 100644
index 0000000..83f9c27
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/miro-automation/SKILL.md b/plugins/awesome-claude-skills/miro-automation/SKILL.md
new file mode 100644
index 0000000..77cf784
--- /dev/null
+++ b/plugins/awesome-claude-skills/miro-automation/SKILL.md
@@ -0,0 +1,210 @@
+---
+name: miro-automation
+description: "Automate Miro tasks via Rube MCP (Composio): boards, items, sticky notes, frames, sharing, connectors. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Miro Automation via Rube MCP
+
+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)
+- Active Miro connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `miro`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `miro`
+3. If connection is not ACTIVE, follow the returned auth link to complete Miro OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Browse Boards
+
+**When to use**: User wants to find boards or get board details
+
+**Tool sequence**:
+1. `MIRO_GET_BOARDS2` - List all accessible boards [Required]
+2. `MIRO_GET_BOARD` - Get detailed info for a specific board [Optional]
+
+**Key parameters**:
+- `query`: Search term to filter boards by name
+- `sort`: Sort by 'default', 'last_modified', 'last_opened', 'last_created', 'alphabetically'
+- `limit`: Number of results per page (max 50)
+- `offset`: Pagination offset
+- `board_id`: Specific board ID for detailed retrieval
+
+**Pitfalls**:
+- Pagination uses offset-based approach, not cursor-based
+- Maximum 50 boards per page; iterate with offset for full list
+- Board IDs are long alphanumeric strings; always resolve by search first
+
+### 2. Create Boards and Items
+
+**When to use**: User wants to create a new board or add items to an existing board
+
+**Tool sequence**:
+1. `MIRO_CREATE_BOARD` - Create a new empty board [Optional]
+2. `MIRO_CREATE_STICKY_NOTE_ITEM` - Add sticky notes to a board [Optional]
+3. `MIRO_CREATE_FRAME_ITEM2` - Add frames to organize content [Optional]
+4. `MIRO_CREATE_ITEMS_IN_BULK` - Add multiple items at once [Optional]
+
+**Key parameters**:
+- `name` / `description`: Board name and description (for CREATE_BOARD)
+- `board_id`: Target board ID (required for all item creation)
+- `data`: Content object with `content` field for sticky note text
+- `style`: Styling object with `fillColor` for sticky note color
+- `position`: Object with `x` and `y` coordinates
+- `geometry`: Object with `width` and `height`
+
+**Pitfalls**:
+- `board_id` is required for ALL item operations; resolve via GET_BOARDS2 first
+- Sticky note colors use hex codes (e.g., '#FF0000') in the `fillColor` field
+- Position coordinates use the board's coordinate system (origin at center)
+- BULK create has a maximum items-per-request limit; check current schema
+- Frame items require `geometry` with both width and height
+
+### 3. Browse and Manage Board Items
+
+**When to use**: User wants to view, find, or organize items on a board
+
+**Tool sequence**:
+1. `MIRO_GET_BOARD_ITEMS` - List all items on a board [Required]
+2. `MIRO_GET_CONNECTORS2` - List connections between items [Optional]
+
+**Key parameters**:
+- `board_id`: Target board ID (required)
+- `type`: Filter by item type ('sticky_note', 'shape', 'text', 'frame', 'image', 'card')
+- `limit`: Number of items per page
+- `cursor`: Pagination cursor from previous response
+
+**Pitfalls**:
+- Results are paginated; follow `cursor` until absent for complete item list
+- Item types must match Miro's predefined types exactly
+- Large boards may have thousands of items; use type filtering to narrow results
+- Connectors are separate from items; use GET_CONNECTORS2 for relationship data
+
+### 4. Share and Collaborate on Boards
+
+**When to use**: User wants to share a board with team members or manage access
+
+**Tool sequence**:
+1. `MIRO_GET_BOARDS2` - Find the board to share [Prerequisite]
+2. `MIRO_SHARE_BOARD` - Share the board with users [Required]
+3. `MIRO_GET_BOARD_MEMBERS` - Verify current board members [Optional]
+
+**Key parameters**:
+- `board_id`: Board to share (required)
+- `emails`: Array of email addresses to invite
+- `role`: Access level ('viewer', 'commenter', 'editor')
+- `message`: Optional invitation message
+
+**Pitfalls**:
+- Email addresses must be valid; invalid emails cause the entire request to fail
+- Role must be one of the predefined values; case-sensitive
+- Sharing with users outside the organization may require admin approval
+- GET_BOARD_MEMBERS returns all members including the owner
+
+### 5. Create Visual Connections
+
+**When to use**: User wants to connect items on a board with lines or arrows
+
+**Tool sequence**:
+1. `MIRO_GET_BOARD_ITEMS` - Find items to connect [Prerequisite]
+2. `MIRO_GET_CONNECTORS2` - View existing connections [Optional]
+
+**Key parameters**:
+- `board_id`: Target board ID
+- `startItem`: Object with `id` of the source item
+- `endItem`: Object with `id` of the target item
+- `style`: Connector style (line type, color, arrows)
+
+**Pitfalls**:
+- Both start and end items must exist on the same board
+- Item IDs are required for connections; resolve via GET_BOARD_ITEMS first
+- Connector styles vary; check available options in schema
+- Self-referencing connections (same start and end) are not allowed
+
+## Common Patterns
+
+### ID Resolution
+
+**Board name -> Board ID**:
+```
+1. Call MIRO_GET_BOARDS2 with query=board_name
+2. Find board by name in results
+3. Extract id field
+```
+
+**Item lookup on board**:
+```
+1. Call MIRO_GET_BOARD_ITEMS with board_id and optional type filter
+2. Find item by content or position
+3. Extract item id for further operations
+```
+
+### Pagination
+
+- Boards: Use `offset` and `limit` (offset-based)
+- Board items: Use `cursor` and `limit` (cursor-based)
+- Continue until no more results or cursor is absent
+- Default page sizes vary by endpoint
+
+### Coordinate System
+
+- Board origin (0,0) is at the center
+- Positive X is right, positive Y is down
+- Items positioned by their center point
+- Use `position: {x: 0, y: 0}` for center of board
+- Frames define bounded areas; items inside inherit frame position
+
+## Known Pitfalls
+
+**Board IDs**:
+- Board IDs are required for virtually all operations
+- Always resolve board names to IDs via GET_BOARDS2 first
+- Do not hardcode board IDs; they vary by account
+
+**Item Creation**:
+- Each item type has different required fields
+- Sticky notes need `data.content` for text
+- Frames need `geometry.width` and `geometry.height`
+- Position defaults to (0,0) if not specified; items may overlap
+
+**Rate Limits**:
+- Miro API has rate limits per token
+- Bulk operations preferred over individual item creation
+- Use MIRO_CREATE_ITEMS_IN_BULK for multiple items
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Item types determine which fields are present in response
+- Parse defensively; optional fields may be absent
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List boards | MIRO_GET_BOARDS2 | query, sort, limit, offset |
+| Get board details | MIRO_GET_BOARD | board_id |
+| Create board | MIRO_CREATE_BOARD | name, description |
+| Add sticky note | MIRO_CREATE_STICKY_NOTE_ITEM | board_id, data, style, position |
+| Add frame | MIRO_CREATE_FRAME_ITEM2 | board_id, data, geometry, position |
+| Bulk add items | MIRO_CREATE_ITEMS_IN_BULK | board_id, items |
+| Get board items | MIRO_GET_BOARD_ITEMS | board_id, type, cursor |
+| 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/plugins/awesome-claude-skills/missive-automation/SKILL.md b/plugins/awesome-claude-skills/missive-automation/SKILL.md
new file mode 100644
index 0000000..50c19ac
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mistral-ai-automation/SKILL.md b/plugins/awesome-claude-skills/mistral-ai-automation/SKILL.md
new file mode 100644
index 0000000..7d7eba2
--- /dev/null
+++ b/plugins/awesome-claude-skills/mistral-ai-automation/SKILL.md
@@ -0,0 +1,134 @@
+---
+name: Mistral AI Automation
+description: "Automate Mistral AI operations -- manage files and libraries, upload documents for fine-tuning, batch processing, and OCR, track fine-tuning jobs, and build RAG pipelines via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Mistral AI Automation
+
+Automate your Mistral AI workflows -- upload files for fine-tuning, batch processing, and OCR, manage document libraries for RAG-enabled agents, list and retrieve files, track fine-tuning jobs, and integrate Mistral AI into cross-app data pipelines.
+
+**Toolkit docs:** [composio.dev/toolkits/mistral_ai](https://composio.dev/toolkits/mistral_ai)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your Mistral AI account when prompted (API key authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. Upload Files to Mistral AI
+
+Use `MISTRAL_AI_UPLOAD_FILE` to upload files for fine-tuning, batch processing, or OCR.
+
+```
+Tool: MISTRAL_AI_UPLOAD_FILE
+Inputs:
+ - file: object (required)
+ - name: string -- destination filename (e.g., "training_data.jsonl")
+ - mimetype: string -- MIME type (e.g., "application/pdf", "application/jsonl")
+ - s3key: string -- S3 key of a previously downloaded/stored file
+ - purpose: "fine-tune" | "batch" | "ocr" (default "fine-tune")
+```
+
+**Limits:** Maximum file size is 512 MB. For fine-tuning, only `.jsonl` files are supported.
+
+### 2. List and Retrieve Files
+
+Use `MISTRAL_AI_LIST_FILES` to browse uploaded files with pagination, and `MISTRAL_AI_RETRIEVE_FILE` to get metadata for a specific file.
+
+```
+Tool: MISTRAL_AI_LIST_FILES
+Inputs:
+ - limit: integer (optional, min 1)
+ - after: string (file ID cursor for next page)
+ - order: "asc" | "desc" (default "desc")
+
+Tool: MISTRAL_AI_RETRIEVE_FILE
+Inputs:
+ - file_id: string (required) -- UUID obtained from List Files
+```
+
+### 3. Create Document Libraries
+
+Use `MISTRAL_AI_CREATE_LIBRARY` to group documents into libraries for use with RAG-enabled Mistral AI agents.
+
+```
+Tool: MISTRAL_AI_CREATE_LIBRARY
+Inputs:
+ - name: string (required) -- e.g., "Project Documents"
+ - description: string (optional)
+```
+
+### 4. Upload Documents to a Library
+
+Use `MISTRAL_AI_UPLOAD_LIBRARY_DOCUMENT` to add documents to a library for RAG retrieval by Mistral AI agents.
+
+```
+Tool: MISTRAL_AI_UPLOAD_LIBRARY_DOCUMENT
+ - Requires library_id and file details
+ - Call RUBE_GET_TOOL_SCHEMAS for full input schema before use
+```
+
+### 5. List Libraries and Download Files
+
+Use `MISTRAL_AI_LIST_LIBRARIES` to discover available document libraries, and `MISTRAL_AI_DOWNLOAD_FILE` to retrieve file content.
+
+```
+Tool: MISTRAL_AI_LIST_LIBRARIES
+ - Lists all document libraries with metadata (id, name, document counts)
+ - Call RUBE_GET_TOOL_SCHEMAS for full input schema
+
+Tool: MISTRAL_AI_DOWNLOAD_FILE
+ - Downloads raw binary content of a previously uploaded file
+ - Call RUBE_GET_TOOL_SCHEMAS for full input schema
+```
+
+### 6. Track Fine-Tuning Jobs
+
+Use `MISTRAL_AI_GET_FINE_TUNING_JOBS` to list and filter fine-tuning jobs by model, status, and creation time.
+
+```
+Tool: MISTRAL_AI_GET_FINE_TUNING_JOBS
+ - Supports filtering by model, status, creation time, and W&B integration
+ - Call RUBE_GET_TOOL_SCHEMAS for full input schema
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| Fine-tune file format | Only `.jsonl` files are supported for fine-tuning uploads. Other formats will be rejected. |
+| File size limit | Maximum upload size is 512 MB per file. |
+| File object structure | `MISTRAL_AI_UPLOAD_FILE` requires an `s3key` referencing a previously stored file, not raw binary content. Use a download action first to stage files in S3. |
+| Pagination cursors | `MISTRAL_AI_LIST_FILES` uses cursor-based pagination via the `after` parameter (file ID). Continue fetching until no more results are returned. |
+| Library document processing | Uploaded library documents are processed asynchronously. They may not be immediately available for RAG queries after upload. |
+| Schema references | Several tools (`MISTRAL_AI_UPLOAD_LIBRARY_DOCUMENT`, `MISTRAL_AI_LIST_LIBRARIES`, `MISTRAL_AI_GET_FINE_TUNING_JOBS`, `MISTRAL_AI_DOWNLOAD_FILE`) require calling `RUBE_GET_TOOL_SCHEMAS` to load full input schemas before execution. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `MISTRAL_AI_UPLOAD_FILE` | Upload files for fine-tuning, batch processing, or OCR |
+| `MISTRAL_AI_LIST_FILES` | List uploaded files with pagination |
+| `MISTRAL_AI_RETRIEVE_FILE` | Get metadata for a specific file by ID |
+| `MISTRAL_AI_DOWNLOAD_FILE` | Download content of an uploaded file |
+| `MISTRAL_AI_CREATE_LIBRARY` | Create a document library for RAG |
+| `MISTRAL_AI_LIST_LIBRARIES` | List all document libraries with metadata |
+| `MISTRAL_AI_UPLOAD_LIBRARY_DOCUMENT` | Add a document to a library for RAG |
+| `MISTRAL_AI_GET_FINE_TUNING_JOBS` | List and filter fine-tuning jobs |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/mistral_ai-automation/SKILL.md b/plugins/awesome-claude-skills/mistral_ai-automation/SKILL.md
new file mode 100644
index 0000000..446c72e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mixpanel-automation/SKILL.md b/plugins/awesome-claude-skills/mixpanel-automation/SKILL.md
new file mode 100644
index 0000000..edf3b3c
--- /dev/null
+++ b/plugins/awesome-claude-skills/mixpanel-automation/SKILL.md
@@ -0,0 +1,229 @@
+---
+name: mixpanel-automation
+description: "Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Mixpanel Automation via Rube MCP
+
+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)
+- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`
+3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Aggregate Event Data
+
+**When to use**: User wants to count events, get totals, or track event trends over time
+
+**Tool sequence**:
+1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]
+2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]
+
+**Key parameters**:
+- `event`: Event name or array of event names to aggregate
+- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format
+- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')
+- `type`: Aggregation type ('general', 'unique', 'average')
+- `where`: Filter expression for event properties
+
+**Pitfalls**:
+- Date format must be 'YYYY-MM-DD'; other formats cause errors
+- Event names are case-sensitive; use exact names from your Mixpanel project
+- `where` filter uses Mixpanel expression syntax (e.g., `properties["country"] == "US"`)
+- Maximum date range may be limited depending on your Mixpanel plan
+
+### 2. Run Segmentation Queries
+
+**When to use**: User wants to break down events by properties for detailed analysis
+
+**Tool sequence**:
+1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]
+
+**Key parameters**:
+- `event`: Event name to segment
+- `from_date` / `to_date`: Date range in 'YYYY-MM-DD' format
+- `on`: Property to segment by (e.g., `properties["country"]`)
+- `unit`: Time granularity
+- `type`: Count type ('general', 'unique', 'average')
+- `where`: Filter expression
+- `limit`: Maximum number of segments to return
+
+**Pitfalls**:
+- The `on` parameter uses Mixpanel property expression syntax
+- Property references must use `properties["prop_name"]` format
+- Segmentation on high-cardinality properties returns capped results; use `limit`
+- Results are grouped by the segmentation property and time unit
+
+### 3. Analyze Funnels
+
+**When to use**: User wants to track conversion funnels and identify drop-off points
+
+**Tool sequence**:
+1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]
+2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]
+
+**Key parameters**:
+- `funnel_id`: ID of the saved funnel to query
+- `from_date` / `to_date`: Date range
+- `unit`: Time granularity
+- `where`: Filter expression
+- `on`: Property to segment funnel by
+- `length`: Conversion window in days
+
+**Pitfalls**:
+- `funnel_id` is required; resolve via LIST_FUNNELS first
+- Funnels must be created in Mixpanel UI first; API only queries existing funnels
+- Conversion window (`length`) defaults vary; set explicitly for accuracy
+- Large date ranges with segmentation can produce very large responses
+
+### 4. Manage User Profiles
+
+**When to use**: User wants to query or update user profiles in Mixpanel
+
+**Tool sequence**:
+1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]
+2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]
+
+**Key parameters**:
+- `where`: Filter expression for profile properties (e.g., `properties["plan"] == "premium"`)
+- `output_properties`: Array of property names to include in results
+- `page`: Page number for pagination
+- `session_id`: Session ID for consistent pagination (from first response)
+- For batch update: array of profile updates with `$distinct_id` and property operations
+
+**Pitfalls**:
+- Profile queries return paginated results; use `session_id` from first response for consistent paging
+- `where` uses Mixpanel expression syntax for profile properties
+- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles
+- Batch update has a maximum number of profiles per request; chunk larger updates
+- Profile property names are case-sensitive
+
+### 5. Manage Cohorts
+
+**When to use**: User wants to list or analyze user cohorts
+
+**Tool sequence**:
+1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]
+
+**Key parameters**:
+- No required parameters; returns all accessible cohorts
+- Response includes cohort `id`, `name`, `description`, `count`
+
+**Pitfalls**:
+- Cohorts are created and managed in Mixpanel UI; API provides read access
+- Cohort IDs are numeric; use exact ID from list results
+- Cohort counts may be approximate for very large cohorts
+- Cohorts can be used as filters in other queries via `where` expressions
+
+### 6. Run JQL and Insight Queries
+
+**When to use**: User wants to run custom JQL queries or insight analyses
+
+**Tool sequence**:
+1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]
+2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]
+
+**Key parameters**:
+- For JQL: `script` containing the JQL JavaScript code
+- For Insight: `bookmark_id` of the saved insight
+- `project_id`: Project context for the query
+
+**Pitfalls**:
+- JQL uses JavaScript-like syntax specific to Mixpanel
+- JQL queries have execution time limits; optimize for efficiency
+- Insight `bookmark_id` must reference an existing saved insight
+- JQL is a legacy feature; check Mixpanel documentation for current availability
+
+## Common Patterns
+
+### ID Resolution
+
+**Project name -> Project ID**:
+```
+1. Call MIXPANEL_GET_ALL_PROJECTS
+2. Find project by name in results
+3. Extract project id
+```
+
+**Funnel name -> Funnel ID**:
+```
+1. Call MIXPANEL_LIST_FUNNELS
+2. Find funnel by name
+3. Extract funnel_id
+```
+
+### Mixpanel Expression Syntax
+
+Used in `where` and `on` parameters:
+- Property reference: `properties["property_name"]`
+- Equality: `properties["country"] == "US"`
+- Comparison: `properties["age"] > 25`
+- Boolean: `properties["is_premium"] == true`
+- Contains: `"search_term" in properties["name"]`
+- AND/OR: `properties["country"] == "US" and properties["plan"] == "pro"`
+
+### Pagination
+
+- Event queries: Follow date-based pagination by adjusting date ranges
+- Profile queries: Use `page` number and `session_id` for consistent results
+- Funnel/cohort lists: Typically return complete results without pagination
+
+## Known Pitfalls
+
+**Date Formats**:
+- Always use 'YYYY-MM-DD' format
+- Date ranges are inclusive on both ends
+- Data freshness depends on Mixpanel ingestion delay (typically minutes)
+
+**Expression Syntax**:
+- Property references always use `properties["name"]` format
+- String values must be quoted: `properties["status"] == "active"`
+- Numeric values are unquoted: `properties["count"] > 10`
+- Boolean values: `true` / `false` (lowercase)
+
+**Rate Limits**:
+- Mixpanel API has rate limits per project
+- Large segmentation queries may time out; reduce date range or segments
+- Use batch operations where available to minimize API calls
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Event data is typically grouped by date and segment
+- Numeric values may be returned as strings; parse explicitly
+- Empty date ranges return empty objects, not empty arrays
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |
+| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |
+| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |
+| List funnels | MIXPANEL_LIST_FUNNELS | (none) |
+| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |
+| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |
+| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |
+| 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/plugins/awesome-claude-skills/mocean-automation/SKILL.md b/plugins/awesome-claude-skills/mocean-automation/SKILL.md
new file mode 100644
index 0000000..998659f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/moco-automation/SKILL.md b/plugins/awesome-claude-skills/moco-automation/SKILL.md
new file mode 100644
index 0000000..055f373
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/modelry-automation/SKILL.md b/plugins/awesome-claude-skills/modelry-automation/SKILL.md
new file mode 100644
index 0000000..cb8ec6d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/monday-automation/SKILL.md b/plugins/awesome-claude-skills/monday-automation/SKILL.md
new file mode 100644
index 0000000..ca3ca4a
--- /dev/null
+++ b/plugins/awesome-claude-skills/monday-automation/SKILL.md
@@ -0,0 +1,238 @@
+---
+name: monday-automation
+description: Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Monday.com Automation via Rube MCP
+
+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)
+- Active Monday.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `monday`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `monday`
+3. If connection is not ACTIVE, follow the returned auth link to complete Monday.com OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Boards
+
+**When to use**: User wants to create a new board, list existing boards, or set up workspace structure.
+
+**Tool sequence**:
+1. `MONDAY_GET_WORKSPACES` - List available workspaces and resolve workspace ID [Prerequisite]
+2. `MONDAY_LIST_BOARDS` - List existing boards to check for duplicates [Optional]
+3. `MONDAY_CREATE_BOARD` - Create a new board with name, kind, and workspace [Required]
+4. `MONDAY_CREATE_COLUMN` - Add columns to the new board [Optional]
+5. `MONDAY_CREATE_GROUP` - Add groups to organize items [Optional]
+6. `MONDAY_BOARDS` - Retrieve detailed board metadata [Optional]
+
+**Key parameters**:
+- `board_name`: Name for the new board (required)
+- `board_kind`: "public", "private", or "share" (required)
+- `workspace_id`: Numeric workspace ID; omit for default workspace
+- `folder_id`: Folder ID; must be within `workspace_id` if both provided
+- `template_id`: ID of accessible template to clone
+
+**Pitfalls**:
+- `board_kind` is required and must be one of: "public", "private", "share"
+- If both `workspace_id` and `folder_id` are provided, the folder must exist within that workspace
+- `template_id` must reference a template the authenticated user can access
+- Board IDs are large integers; always use the exact value from API responses
+
+### 2. Create and Manage Items
+
+**When to use**: User wants to add tasks/items to a board, list existing items, or move items between groups.
+
+**Tool sequence**:
+1. `MONDAY_LIST_BOARDS` - Resolve board name to board ID [Prerequisite]
+2. `MONDAY_LIST_GROUPS` - List groups on the board to get group_id [Prerequisite]
+3. `MONDAY_LIST_COLUMNS` - Get column IDs and types for setting values [Prerequisite]
+4. `MONDAY_CREATE_ITEM` - Create a new item with name and column values [Required]
+5. `MONDAY_LIST_BOARD_ITEMS` - List all items on the board [Optional]
+6. `MONDAY_MOVE_ITEM_TO_GROUP` - Move an item to a different group [Optional]
+7. `MONDAY_ITEMS_PAGE` - Paginated item retrieval with filtering [Optional]
+
+**Key parameters**:
+- `board_id`: Board ID (required, integer)
+- `item_name`: Item name, max 256 characters (required)
+- `group_id`: Group ID string to place the item in (optional)
+- `column_values`: JSON object or string mapping column IDs to values
+
+**Pitfalls**:
+- `column_values` must use column IDs (not titles); get them from `MONDAY_LIST_COLUMNS`
+- Column value formats vary by type: status uses `{"index": 0}` or `{"label": "Done"}`, date uses `{"date": "YYYY-MM-DD"}`, people uses `{"personsAndTeams": [{"id": 123, "kind": "person"}]}`
+- `item_name` has a 256-character maximum
+- Subitem boards are NOT supported by `MONDAY_CREATE_ITEM`; use GraphQL via `MONDAY_CREATE_OBJECT`
+
+### 3. Update Item Column Values
+
+**When to use**: User wants to change status, date, text, or other column values on existing items.
+
+**Tool sequence**:
+1. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Get column IDs and types [Prerequisite]
+2. `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE` - Find the target item ID [Prerequisite]
+3. `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` - Update text, status, or dropdown with a string value [Required]
+4. `MONDAY_UPDATE_ITEM` - Update complex column types (timeline, people, date) with JSON [Required]
+
+**Key parameters for MONDAY_CHANGE_SIMPLE_COLUMN_VALUE**:
+- `board_id`: Board ID (integer, required)
+- `item_id`: Item ID (integer, required)
+- `column_id`: Column ID string (required)
+- `value`: Simple string value (e.g., "Done", "Working on it")
+- `create_labels_if_missing`: true to auto-create status/dropdown labels (default true)
+
+**Key parameters for MONDAY_UPDATE_ITEM**:
+- `board_id`: Board ID (integer, required)
+- `item_id`: Item ID (integer, required)
+- `column_id`: Column ID string (required)
+- `value`: JSON object matching the column type schema
+- `create_labels_if_missing`: false by default; set true for status/dropdown
+
+**Pitfalls**:
+- Use `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` for simple text/status/dropdown updates (string value)
+- Use `MONDAY_UPDATE_ITEM` for complex types like timeline, people, date (JSON value)
+- Column IDs are lowercase strings with underscores (e.g., "status_1", "date_2", "text"); get them from `MONDAY_LIST_COLUMNS`
+- Status values can be set by label name ("Done") or index number ("1")
+- `create_labels_if_missing` defaults differ: true for CHANGE_SIMPLE, false for UPDATE_ITEM
+
+### 4. Work with Groups and Board Structure
+
+**When to use**: User wants to organize items into groups, add columns, or inspect board structure.
+
+**Tool sequence**:
+1. `MONDAY_LIST_BOARDS` - Resolve board ID [Prerequisite]
+2. `MONDAY_LIST_GROUPS` - List all groups on a board [Required]
+3. `MONDAY_CREATE_GROUP` - Create a new group [Optional]
+4. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Inspect column structure [Required]
+5. `MONDAY_CREATE_COLUMN` - Add a new column to the board [Optional]
+6. `MONDAY_MOVE_ITEM_TO_GROUP` - Reorganize items across groups [Optional]
+
+**Key parameters**:
+- `board_id`: Board ID (required for all group/column operations)
+- `group_name`: Name for new group (CREATE_GROUP)
+- `column_type`: Must be a valid GraphQL enum token in snake_case (e.g., "status", "text", "long_text", "numbers", "date", "dropdown", "people")
+- `title`: Column display title
+- `defaults`: JSON string for status/dropdown labels, e.g., `'{"labels": ["To Do", "In Progress", "Done"]}'`
+
+**Pitfalls**:
+- `column_type` must be exact snake_case values; "person" is NOT valid, use "people"
+- Group IDs are strings (e.g., "topics", "new_group_12345"), not integers
+- `MONDAY_COLUMNS` accepts an array of `board_ids` and returns column metadata including settings
+- `MONDAY_LIST_COLUMNS` is simpler and takes a single `board_id`
+
+### 5. Manage Subitems and Updates
+
+**When to use**: User wants to view subitems of a task or add comments/updates to items.
+
+**Tool sequence**:
+1. `MONDAY_LIST_BOARD_ITEMS` - Find parent item IDs [Prerequisite]
+2. `MONDAY_LIST_SUBITEMS_BY_PARENT` - Retrieve subitems with column values [Required]
+3. `MONDAY_CREATE_UPDATE` - Add a comment/update to an item [Optional]
+4. `MONDAY_CREATE_OBJECT` - Create subitems via GraphQL mutation [Optional]
+
+**Key parameters for MONDAY_LIST_SUBITEMS_BY_PARENT**:
+- `parent_item_ids`: Array of parent item IDs (integer array, required)
+- `include_column_values`: true to include column data (default true)
+- `include_parent_fields`: true to include parent item info (default true)
+
+**Key parameters for MONDAY_CREATE_OBJECT** (GraphQL):
+- `query`: Full GraphQL mutation string
+- `variables`: Optional variables object
+
+**Pitfalls**:
+- Subitems can only be queried through their parent items
+- To create subitems, use `MONDAY_CREATE_OBJECT` with a `create_subitem` GraphQL mutation
+- `MONDAY_CREATE_UPDATE` is for adding comments/updates to items (Monday's "updates" feature), not for modifying item values
+- `MONDAY_CREATE_OBJECT` is a raw GraphQL endpoint; ensure correct mutation syntax
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to IDs before operations:
+- **Board name -> board_id**: `MONDAY_LIST_BOARDS` and match by name
+- **Group name -> group_id**: `MONDAY_LIST_GROUPS` with `board_id`
+- **Column title -> column_id**: `MONDAY_LIST_COLUMNS` with `board_id`
+- **Workspace name -> workspace_id**: `MONDAY_GET_WORKSPACES` and match by name
+- **Item name -> item_id**: `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE`
+
+### Pagination
+Monday.com uses cursor-based pagination for items:
+- `MONDAY_ITEMS_PAGE` returns a `cursor` in the response for the next page
+- Pass the `cursor` to the next call; `board_id` and `query_params` are ignored when cursor is provided
+- Cursors are cached for 60 minutes
+- Maximum `limit` is 500 per page
+- `MONDAY_LIST_BOARDS` and `MONDAY_GET_WORKSPACES` use page-based pagination with `page` and `limit`
+
+### Column Value Formatting
+Different column types require different value formats:
+- **Status**: `{"index": 0}` or `{"label": "Done"}` or simple string "Done"
+- **Date**: `{"date": "YYYY-MM-DD"}`
+- **People**: `{"personsAndTeams": [{"id": 123, "kind": "person"}]}`
+- **Text/Numbers**: Plain string or number
+- **Timeline**: `{"from": "YYYY-MM-DD", "to": "YYYY-MM-DD"}`
+
+## Known Pitfalls
+
+### ID Formats
+- Board IDs and item IDs are large integers (e.g., 1234567890)
+- Group IDs are strings (e.g., "topics", "new_group_12345")
+- Column IDs are short strings (e.g., "status_1", "date4", "text")
+- Workspace IDs are integers
+
+### Rate Limits
+- Monday.com GraphQL API has complexity-based rate limits
+- Large boards with many columns increase query complexity
+- Use `limit` parameter to reduce items per request if hitting limits
+
+### Parameter Quirks
+- `column_type` for CREATE_COLUMN must be exact snake_case enum values; "people" not "person"
+- `column_values` in CREATE_ITEM accepts both JSON string and object formats
+- `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` auto-creates missing labels by default; `MONDAY_UPDATE_ITEM` does not
+- `MONDAY_CREATE_OBJECT` is a raw GraphQL interface; use it for operations without dedicated tools (e.g., create_subitem, delete_item, archive_board)
+
+### Response Structure
+- Board items are returned as arrays with `id`, `name`, and `state` fields
+- Column values include both raw `value` (JSON) and rendered `text` (display string)
+- Subitems are nested under parent items and cannot be queried independently
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List workspaces | `MONDAY_GET_WORKSPACES` | `kind`, `state`, `limit` |
+| Create workspace | `MONDAY_CREATE_WORKSPACE` | `name`, `kind` |
+| List boards | `MONDAY_LIST_BOARDS` | `limit`, `page`, `state` |
+| Create board | `MONDAY_CREATE_BOARD` | `board_name`, `board_kind`, `workspace_id` |
+| Get board metadata | `MONDAY_BOARDS` | `board_ids`, `board_kind` |
+| List groups | `MONDAY_LIST_GROUPS` | `board_id` |
+| Create group | `MONDAY_CREATE_GROUP` | `board_id`, `group_name` |
+| List columns | `MONDAY_LIST_COLUMNS` | `board_id` |
+| Get column metadata | `MONDAY_COLUMNS` | `board_ids`, `column_types` |
+| Create column | `MONDAY_CREATE_COLUMN` | `board_id`, `column_type`, `title` |
+| Create item | `MONDAY_CREATE_ITEM` | `board_id`, `item_name`, `column_values` |
+| List board items | `MONDAY_LIST_BOARD_ITEMS` | `board_id` |
+| Paginated items | `MONDAY_ITEMS_PAGE` | `board_id`, `limit`, `query_params` |
+| Update column (simple) | `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` | `board_id`, `item_id`, `column_id`, `value` |
+| Update column (complex) | `MONDAY_UPDATE_ITEM` | `board_id`, `item_id`, `column_id`, `value` |
+| Move item to group | `MONDAY_MOVE_ITEM_TO_GROUP` | `item_id`, `group_id` |
+| 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/plugins/awesome-claude-skills/moneybird-automation/SKILL.md b/plugins/awesome-claude-skills/moneybird-automation/SKILL.md
new file mode 100644
index 0000000..0ef7dee
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/moonclerk-automation/SKILL.md b/plugins/awesome-claude-skills/moonclerk-automation/SKILL.md
new file mode 100644
index 0000000..5599530
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/moosend-automation/SKILL.md b/plugins/awesome-claude-skills/moosend-automation/SKILL.md
new file mode 100644
index 0000000..4bb09e2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mopinion-automation/SKILL.md b/plugins/awesome-claude-skills/mopinion-automation/SKILL.md
new file mode 100644
index 0000000..e7a2a3d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/more-trees-automation/SKILL.md b/plugins/awesome-claude-skills/more-trees-automation/SKILL.md
new file mode 100644
index 0000000..ca7ead0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/moxie-automation/SKILL.md b/plugins/awesome-claude-skills/moxie-automation/SKILL.md
new file mode 100644
index 0000000..7db2e65
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/moz-automation/SKILL.md b/plugins/awesome-claude-skills/moz-automation/SKILL.md
new file mode 100644
index 0000000..5133ac1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/msg91-automation/SKILL.md b/plugins/awesome-claude-skills/msg91-automation/SKILL.md
new file mode 100644
index 0000000..b060a1d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mural-automation/SKILL.md b/plugins/awesome-claude-skills/mural-automation/SKILL.md
new file mode 100644
index 0000000..b33170f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mx-technologies-automation/SKILL.md b/plugins/awesome-claude-skills/mx-technologies-automation/SKILL.md
new file mode 100644
index 0000000..bc0bf07
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/mx-toolbox-automation/SKILL.md b/plugins/awesome-claude-skills/mx-toolbox-automation/SKILL.md
new file mode 100644
index 0000000..d1db90b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/nango-automation/SKILL.md b/plugins/awesome-claude-skills/nango-automation/SKILL.md
new file mode 100644
index 0000000..ac7e4b7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/nano-nets-automation/SKILL.md b/plugins/awesome-claude-skills/nano-nets-automation/SKILL.md
new file mode 100644
index 0000000..8d73abf
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/nasa-automation/SKILL.md b/plugins/awesome-claude-skills/nasa-automation/SKILL.md
new file mode 100644
index 0000000..7f8826b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/nasdaq-automation/SKILL.md b/plugins/awesome-claude-skills/nasdaq-automation/SKILL.md
new file mode 100644
index 0000000..38f147b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ncscale-automation/SKILL.md b/plugins/awesome-claude-skills/ncscale-automation/SKILL.md
new file mode 100644
index 0000000..587ac5f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/needle-automation/SKILL.md b/plugins/awesome-claude-skills/needle-automation/SKILL.md
new file mode 100644
index 0000000..c9b55ef
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/neon-automation/SKILL.md b/plugins/awesome-claude-skills/neon-automation/SKILL.md
new file mode 100644
index 0000000..dd88c19
--- /dev/null
+++ b/plugins/awesome-claude-skills/neon-automation/SKILL.md
@@ -0,0 +1,139 @@
+---
+name: Neon Automation
+description: "Automate Neon serverless Postgres operations -- manage projects, branches, databases, roles, and connection URIs via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Neon Automation
+
+Automate your Neon serverless Postgres workflows -- list projects and branches, inspect databases, retrieve connection URIs, manage roles, and integrate Neon database operations into cross-app pipelines.
+
+**Toolkit docs:** [composio.dev/toolkits/neon](https://composio.dev/toolkits/neon)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your Neon account when prompted (API key authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. List Projects
+
+Use `NEON_RETRIEVE_PROJECTS_LIST` to discover all projects associated with the authenticated user.
+
+```
+Tool: NEON_RETRIEVE_PROJECTS_LIST
+Inputs:
+ - org_id: string (REQUIRED when using a personal API key)
+ - limit: integer (1-400, default 10)
+ - cursor: string (pagination cursor from previous response)
+ - search: string (search by project name or ID, supports partial match)
+ - timeout: integer (milliseconds; returns partial results on timeout)
+```
+
+**Important:** When using a personal API key, `org_id` is required. Retrieve it first via `NEON_GET_USER_ORGANIZATIONS`.
+
+### 2. Get Project Details
+
+Use `NEON_ACCESS_PROJECT_DETAILS_BY_ID` to inspect project configuration, owner info, and consumption metrics.
+
+```
+Tool: NEON_ACCESS_PROJECT_DETAILS_BY_ID
+Inputs:
+ - project_id: string (required) -- format: "adjective-noun-number", e.g., "dry-smoke-26258271"
+```
+
+### 3. List Branches for a Project
+
+Use `NEON_GET_BRANCHES_FOR_PROJECT` to enumerate branches (development stages) within a project.
+
+```
+Tool: NEON_GET_BRANCHES_FOR_PROJECT
+Inputs:
+ - project_id: string (required)
+ - search: string (optional, search by branch name or ID)
+```
+
+### 4. List Databases on a Branch
+
+Use `NEON_FETCH_DATABASE_FOR_BRANCH` to inventory databases within a specific project and branch.
+
+```
+Tool: NEON_FETCH_DATABASE_FOR_BRANCH
+Inputs:
+ - project_id: string (required)
+ - branch_id: string (required)
+```
+
+### 5. Get Connection URI
+
+Use `NEON_GET_PROJECT_CONNECTION_URI` to obtain a Postgres connection string for a project/branch/database.
+
+```
+Tool: NEON_GET_PROJECT_CONNECTION_URI
+Inputs:
+ - project_id: string (required)
+ - database_name: string (required) -- e.g., "neondb"
+ - role_name: string (required) -- e.g., "neondb_owner"
+ - branch_id: string (optional, defaults to project default branch)
+ - endpoint_id: string (optional, defaults to read-write endpoint)
+ - pooled: boolean (optional, adds -pooler for connection pooling)
+```
+
+**Security:** The returned URI includes credentials. Treat it as a secret -- do not log or share it.
+
+### 6. Inspect Database Details and Roles
+
+Use `NEON_RETRIEVE_BRANCH_DATABASE_DETAILS` to verify a database before connecting, and `NEON_GET_BRANCH_ROLES_FOR_PROJECT` to list available roles.
+
+```
+Tool: NEON_RETRIEVE_BRANCH_DATABASE_DETAILS
+Inputs:
+ - project_id: string (required)
+ - branch_id: string (required)
+ - database_name: string (required)
+
+Tool: NEON_GET_BRANCH_ROLES_FOR_PROJECT
+Inputs:
+ - project_id: string (required)
+ - branch_id: string (required)
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| org_id required | `NEON_RETRIEVE_PROJECTS_LIST` returns HTTP 400 "org_id is required" when using a personal API key. Call `NEON_GET_USER_ORGANIZATIONS` first. |
+| Incomplete pagination | Project lists may be incomplete without pagination. Iterate using `cursor` until it is empty. |
+| Rate limiting | `NEON_RETRIEVE_PROJECTS_LIST` returns HTTP 429 on bursty listing. Avoid redundant calls and back off before retrying. |
+| Invalid role/database pairing | `NEON_GET_PROJECT_CONNECTION_URI` returns 401/403 when the database_name/role_name pairing is invalid. Use `NEON_GET_BRANCH_ROLES_FOR_PROJECT` to select an allowed role. |
+| Connection URI is a secret | The returned URI includes credentials. Never log, display, or share it in plain text. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `NEON_RETRIEVE_PROJECTS_LIST` | List all Neon projects with pagination and search |
+| `NEON_ACCESS_PROJECT_DETAILS_BY_ID` | Get project configuration and consumption metrics |
+| `NEON_GET_BRANCHES_FOR_PROJECT` | List branches within a project |
+| `NEON_FETCH_DATABASE_FOR_BRANCH` | List databases on a specific branch |
+| `NEON_GET_PROJECT_CONNECTION_URI` | Get a Postgres connection URI (with credentials) |
+| `NEON_RETRIEVE_BRANCH_DATABASE_DETAILS` | Inspect database metadata and settings |
+| `NEON_GET_USER_ORGANIZATIONS` | List organizations for the authenticated user |
+| `NEON_CREATE_API_KEY_FOR_ORGANIZATION` | Create a new API key for an organization |
+| `NEON_GET_BRANCH_ROLES_FOR_PROJECT` | List roles available on a branch |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/netsuite-automation/SKILL.md b/plugins/awesome-claude-skills/netsuite-automation/SKILL.md
new file mode 100644
index 0000000..4402ea5
--- /dev/null
+++ b/plugins/awesome-claude-skills/netsuite-automation/SKILL.md
@@ -0,0 +1,231 @@
+---
+name: NetSuite Automation
+description: "NetSuite Automation: manage customers, sales orders, invoices, inventory, and records via Oracle NetSuite ERP with SuiteQL queries"
+requires:
+ mcp: [rube]
+---
+
+# NetSuite Automation
+
+Automate Oracle NetSuite ERP operations including creating customers and sales orders, running SuiteQL queries, upserting records by external ID, and inspecting record metadata for comprehensive business management.
+
+**Toolkit docs:** [composio.dev/toolkits/netsuite](https://composio.dev/toolkits/netsuite)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure an active connection exists for the `netsuite` toolkit. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+---
+
+## Core Workflows
+
+### 1. Create Sales Orders
+
+Create customer orders with line items including item references, quantities, and pricing.
+
+**Tool:** `NETSUITE_CREATE_SALES_ORDER`
+
+**Key Parameters:**
+- `entity` (required) -- Customer reference: `{"id": ""}`
+- `item` (required) -- Container with `items` array, each containing:
+ - `item` (required) -- Item reference: `{"id": ""}`
+ - `quantity` (required) -- Units to order (non-negative)
+ - `rate` -- Unit price (optional if item has default pricing)
+ - `amount` -- Total line amount (alternative to rate)
+ - `taxcode` -- Tax code reference: `{"id": ""}` (required if SuiteTax enabled)
+ - `description` -- Line item notes
+- `tranDate` -- Transaction date in `YYYY-MM-DD` format
+- `memo` -- Header memo
+- `orderStatus` -- `"A"` (Pending Approval) or `"B"` (Pending Fulfillment)
+- `otherrefnum` -- External reference or PO number
+
+**Example:**
+```
+Tool: NETSUITE_CREATE_SALES_ORDER
+Arguments:
+ entity: {"id": "1234"}
+ item: {
+ "items": [
+ {"item": {"id": "56"}, "quantity": 10, "rate": 25.00},
+ {"item": {"id": "78"}, "quantity": 5, "rate": 50.00}
+ ]
+ }
+ tranDate: "2026-02-11"
+ memo: "Q1 bulk order"
+ orderStatus: "B"
+```
+
+---
+
+### 2. Run SuiteQL Queries
+
+Execute ad-hoc SQL queries against NetSuite data with server-side paging.
+
+**Tool:** `NETSUITE_RUN_SUITEQL_QUERY`
+
+**Key Parameters:**
+- `q` (required) -- SuiteQL SELECT statement
+- `limit` -- Rows per page (default varies)
+- `offset` -- Zero-based index of first row (must be a multiple of `limit`)
+
+**Examples:**
+```
+Tool: NETSUITE_RUN_SUITEQL_QUERY
+Arguments:
+ q: "SELECT id, companyname, email FROM customer WHERE isinactive = 'F' ORDER BY companyname"
+ limit: 100
+ offset: 0
+```
+
+```
+Tool: NETSUITE_RUN_SUITEQL_QUERY
+Arguments:
+ q: "SELECT id, entitystatus, total FROM transaction WHERE type = 'SalesOrd' AND trandate >= '2026-01-01'"
+ limit: 50
+```
+
+---
+
+### 3. Create and Manage Customers
+
+Create new customer records with subsidiary assignment and contact details.
+
+**Tools:**
+- `NETSUITE_CREATE_CUSTOMER` -- Create a new customer
+- `NETSUITE_GET_CUSTOMER` -- Retrieve customer by internal ID
+- `NETSUITE_UPDATE_CUSTOMER` -- Update existing customer (PATCH semantics)
+
+**Key Parameters for `NETSUITE_CREATE_CUSTOMER`:**
+- `body` (required) -- JSON object with customer data. Required fields:
+ - `subsidiary` -- Object with `id` (subsidiary internal ID)
+ - Either `companyName` (for businesses) or `firstName` + `lastName` (for individuals)
+ - Optional: `email`, `phone`, `isPerson` (set to `"T"` for individuals), `comments`
+- `replace` -- Comma-separated sublist names to fully replace (e.g., `"contacts,addressbook"`)
+
+**Example:**
+```
+Tool: NETSUITE_CREATE_CUSTOMER
+Arguments:
+ body: {
+ "companyName": "Acme Corp",
+ "subsidiary": {"id": "1"},
+ "email": "info@acme.com",
+ "phone": "555-0100"
+ }
+```
+
+---
+
+### 4. Upsert Records by External ID
+
+Create or update records idempotently using an external identifier. Essential for sync workflows.
+
+**Tool:** `NETSUITE_UPSERT_RECORD_BY_EXTERNAL_ID`
+
+**Key Parameters:**
+- `record_type` (required) -- Record type name, e.g., `"customer"`, `"salesorder"`, `"customrecord_myrec"`
+- `external_id` (required) -- External ID value (letters, numbers, underscore, hyphen only)
+- `body` (required) -- JSON object matching the record schema; include mandatory fields when creating
+
+**Example:**
+```
+Tool: NETSUITE_UPSERT_RECORD_BY_EXTERNAL_ID
+Arguments:
+ record_type: "customer"
+ external_id: "CRM-CUST-42"
+ body: {
+ "companyName": "Acme Corp",
+ "subsidiary": {"id": "1"},
+ "email": "updated@acme.com"
+ }
+```
+
+> **Warning:** Idempotency depends on consistent external ID usage. Mismatches silently create additional records instead of updating.
+
+---
+
+### 5. Inspect Record Metadata
+
+Discover available fields, data types, constraints, and requirements before creating or updating records.
+
+**Tool:** `NETSUITE_GET_RECORD_METADATA`
+
+**Key Parameters:**
+- `record_type` (required) -- e.g., `"customer"`, `"salesorder"`, `"invoice"`, `"vendor"`, `"employee"`, `"item"`
+- `accept` -- `"application/schema+json"` (default, JSON Schema) or `"application/swagger+json"` (OpenAPI 3.0)
+
+**Example:**
+```
+Tool: NETSUITE_GET_RECORD_METADATA
+Arguments:
+ record_type: "salesorder"
+```
+
+---
+
+### 6. List and Filter Records
+
+Retrieve multiple records with optional filtering and pagination.
+
+**Tool:** `NETSUITE_LIST_RECORDS`
+
+**Key Parameters:**
+- `recordType` (required) -- e.g., `"customer"`, `"salesorder"`
+- `q` -- Filter expression using N/query operators, e.g., `"email START_WITH \"barbara\""`
+- `limit` -- Max records per page (1--1000, default 1000)
+- `offset` -- Zero-based index (must be divisible by limit)
+
+**Supporting Tools:**
+- `NETSUITE_FILTER_RECORD_COLLECTION` -- Alternative filtering (secondary to SuiteQL)
+- `NETSUITE_GET_RECORD_SELECTED_FIELDS` -- Retrieve specific fields only (reduced payload)
+
+---
+
+## Recommended Execution Plan
+
+1. **Inspect the record schema** using `NETSUITE_GET_RECORD_METADATA` to discover required fields
+2. **Search for existing records** using `NETSUITE_RUN_SUITEQL_QUERY` to avoid duplicates
+3. **Look up customer** by email using SuiteQL; fetch details with `NETSUITE_GET_CUSTOMER` if found
+4. **Create customer if needed** using `NETSUITE_CREATE_CUSTOMER` (ensure `subsidiary` is set)
+5. **Validate item internal IDs** using `NETSUITE_LIST_RECORDS` or SuiteQL
+6. **Create the sales order** using `NETSUITE_CREATE_SALES_ORDER` with validated references
+7. **Optionally upsert by external ID** using `NETSUITE_UPSERT_RECORD_BY_EXTERNAL_ID` for sync workflows
+8. **Verify results** using `NETSUITE_GET_RECORD_SELECTED_FIELDS` to confirm pricing/totals
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **Invalid item IDs** | `NETSUITE_CREATE_SALES_ORDER` throws USER_ERROR when item internal ID is invalid. Pre-validate via `NETSUITE_LIST_RECORDS` or `NETSUITE_RUN_SUITEQL_QUERY`. |
+| **Missing required fields** | `NETSUITE_CREATE_CUSTOMER` returns 400 when required fields (e.g., `subsidiary`) are missing. Always inspect with `NETSUITE_GET_RECORD_METADATA` first. |
+| **SuiteQL field names** | Query differences by account can cause empty results. Confirm field names via `NETSUITE_GET_RECORD_METADATA` when results look wrong. |
+| **Filter expression limits** | `NETSUITE_FILTER_RECORD_COLLECTION` may fail if filter syntax is unsupported. Treat as secondary to SuiteQL. |
+| **External ID idempotency** | `NETSUITE_UPSERT_RECORD_BY_EXTERNAL_ID` depends on consistent external IDs. Mismatches silently create duplicates instead of updating. |
+| **SuiteTax line items** | Accounts with SuiteTax enabled require `taxcode` on every line item. Omitting it causes creation failures. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `NETSUITE_CREATE_SALES_ORDER` | Create a new sales order with line items |
+| `NETSUITE_RUN_SUITEQL_QUERY` | Execute ad-hoc SuiteQL queries with paging |
+| `NETSUITE_CREATE_CUSTOMER` | Create a new customer record |
+| `NETSUITE_GET_CUSTOMER` | Retrieve a customer by internal ID |
+| `NETSUITE_UPDATE_CUSTOMER` | Update an existing customer (PATCH) |
+| `NETSUITE_UPSERT_RECORD_BY_EXTERNAL_ID` | Create or update a record by external ID |
+| `NETSUITE_GET_RECORD_METADATA` | Inspect record schema and field definitions |
+| `NETSUITE_LIST_RECORDS` | List records with filtering and pagination |
+| `NETSUITE_FILTER_RECORD_COLLECTION` | Alternative record filtering |
+| `NETSUITE_GET_RECORD_SELECTED_FIELDS` | Retrieve specific fields from a record |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/neuronwriter-automation/SKILL.md b/plugins/awesome-claude-skills/neuronwriter-automation/SKILL.md
new file mode 100644
index 0000000..fb9dfa6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/neutrino-automation/SKILL.md b/plugins/awesome-claude-skills/neutrino-automation/SKILL.md
new file mode 100644
index 0000000..ec1d596
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/neverbounce-automation/SKILL.md b/plugins/awesome-claude-skills/neverbounce-automation/SKILL.md
new file mode 100644
index 0000000..653ae38
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/new-relic-automation/SKILL.md b/plugins/awesome-claude-skills/new-relic-automation/SKILL.md
new file mode 100644
index 0000000..46be1dc
--- /dev/null
+++ b/plugins/awesome-claude-skills/new-relic-automation/SKILL.md
@@ -0,0 +1,148 @@
+---
+name: New Relic Automation
+description: "Automate New Relic observability workflows -- manage alert policies, notification channels, alert conditions, and monitor applications and browser apps via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# New Relic Automation
+
+Automate your New Relic observability workflows -- create and manage alert policies, configure notification channels (email, Slack, webhook, PagerDuty), monitor APM applications, inspect alert conditions, and integrate New Relic alerting into cross-app pipelines.
+
+**Toolkit docs:** [composio.dev/toolkits/new_relic](https://composio.dev/toolkits/new_relic)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your New Relic account when prompted (API key authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. List Alert Policies
+
+Use `NEW_RELIC_GET_ALERT_POLICIES` to discover existing alert policies with optional filtering.
+
+```
+Tool: NEW_RELIC_GET_ALERT_POLICIES
+Inputs:
+ - name: string (optional, partial match supported)
+ - incident_preference: "PER_POLICY" | "PER_CONDITION" | "PER_CONDITION_AND_TARGET"
+ - page: integer (1-indexed pagination)
+```
+
+### 2. Create an Alert Policy
+
+Use `NEW_RELIC_CREATE_ALERT_POLICY` to set up a new policy container for alert conditions.
+
+```
+Tool: NEW_RELIC_CREATE_ALERT_POLICY
+Inputs:
+ - name: string (required) -- must be unique within the account
+ - incident_preference: "PER_POLICY" | "PER_CONDITION" | "PER_CONDITION_AND_TARGET" (default: PER_POLICY)
+```
+
+**Incident preferences explained:**
+- `PER_POLICY` -- one issue per policy (recommended for most use cases)
+- `PER_CONDITION` -- one issue per alert condition
+- `PER_CONDITION_AND_TARGET` -- one issue per condition and signal/target
+
+### 3. Create Alert Notification Channels
+
+Use `NEW_RELIC_CREATE_ALERT_CHANNEL` to register notification endpoints for alert delivery.
+
+```
+Tool: NEW_RELIC_CREATE_ALERT_CHANNEL
+Inputs:
+ - type: "email" | "slack" | "webhook" | "pagerduty" | "opsgenie" | "victorops" (required)
+ - name: string (required) -- human-readable channel name
+ - configuration: object (required) -- varies by type:
+ Email: { recipients: "devops@example.com,oncall@example.com" }
+ Slack: { url: "", channel: "alerts" }
+ Webhook: { url: "https://hooks.example.com/alerts", auth_username, auth_password }
+ PagerDuty: { service_key: "" }
+ OpsGenie: { api_key, recipients, tags, teams }
+ VictorOps: { key: "", route_key: "" }
+```
+
+### 4. Get Alert Conditions for a Policy
+
+Use `NEW_RELIC_GET_ALERT_CONDITIONS` to inspect the conditions attached to a specific policy.
+
+```
+Tool: NEW_RELIC_GET_ALERT_CONDITIONS
+Inputs:
+ - policy_id: integer (required)
+```
+
+### 5. Monitor Applications
+
+Use `NEW_RELIC_GET_APPLICATIONS` and `NEW_RELIC_GET_BROWSER_APPLICATIONS` to list APM and browser-monitored apps.
+
+```
+Tool: NEW_RELIC_GET_APPLICATIONS
+Inputs:
+ - name: string (optional, case-insensitive partial match)
+ - host: string (optional, case-insensitive partial match)
+ - ids: string (optional, comma-separated list of app IDs)
+ - page: integer (1-indexed)
+
+Tool: NEW_RELIC_GET_BROWSER_APPLICATIONS
+Inputs:
+ - filter[name]: string (optional, case-insensitive partial match)
+ - page: integer (1-indexed)
+```
+
+### 6. Manage Channels and Policies
+
+Use `NEW_RELIC_UPDATE_ALERT_CHANNEL` to modify existing channels and `NEW_RELIC_DELETE_ALERT_POLICY` to remove policies.
+
+```
+Tool: NEW_RELIC_UPDATE_ALERT_CHANNEL
+Inputs:
+ - alert_channel_id: integer (required)
+ - name: string (optional)
+ - type: string (optional, only to change type)
+ - configuration: object (optional, fields vary by type)
+
+Tool: NEW_RELIC_DELETE_ALERT_POLICY
+Inputs:
+ - policy_id: string (required) -- ID of the policy to delete
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| Unique policy names | `NEW_RELIC_CREATE_ALERT_POLICY` requires the name to be unique within the account. |
+| Channel config varies by type | The `configuration` object for `NEW_RELIC_CREATE_ALERT_CHANNEL` has different required fields per channel type (e.g., `recipients` for email, `service_key` for PagerDuty). |
+| Pagination required | All list endpoints return paginated results. Iterate pages until results are exhausted. |
+| Policy ID type mismatch | `NEW_RELIC_GET_ALERT_CONDITIONS` expects `policy_id` as an integer, while `NEW_RELIC_DELETE_ALERT_POLICY` expects it as a string. |
+| Channel-policy linking | After creating a channel, you must separately associate it with a policy for alerts to flow to that channel. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `NEW_RELIC_GET_ALERT_POLICIES` | List alert policies with optional filtering |
+| `NEW_RELIC_CREATE_ALERT_POLICY` | Create a new alert policy |
+| `NEW_RELIC_DELETE_ALERT_POLICY` | Delete an alert policy by ID |
+| `NEW_RELIC_CREATE_ALERT_CHANNEL` | Create a notification channel (email, Slack, webhook, etc.) |
+| `NEW_RELIC_GET_ALERT_CHANNELS` | List all configured alert channels |
+| `NEW_RELIC_UPDATE_ALERT_CHANNEL` | Update an existing alert channel |
+| `NEW_RELIC_GET_ALERT_CONDITIONS` | Get alert conditions for a policy |
+| `NEW_RELIC_GET_APPLICATIONS` | List APM applications |
+| `NEW_RELIC_GET_BROWSER_APPLICATIONS` | List browser-monitored applications |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/new_relic-automation/SKILL.md b/plugins/awesome-claude-skills/new_relic-automation/SKILL.md
new file mode 100644
index 0000000..3c2ac3d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/news-api-automation/SKILL.md b/plugins/awesome-claude-skills/news-api-automation/SKILL.md
new file mode 100644
index 0000000..b5ea0d8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/nextdns-automation/SKILL.md b/plugins/awesome-claude-skills/nextdns-automation/SKILL.md
new file mode 100644
index 0000000..f6e87cd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ngrok-automation/SKILL.md b/plugins/awesome-claude-skills/ngrok-automation/SKILL.md
new file mode 100644
index 0000000..8065109
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ninox-automation/SKILL.md b/plugins/awesome-claude-skills/ninox-automation/SKILL.md
new file mode 100644
index 0000000..402b762
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/nocrm-io-automation/SKILL.md b/plugins/awesome-claude-skills/nocrm-io-automation/SKILL.md
new file mode 100644
index 0000000..0e9f41d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/notion-automation/SKILL.md b/plugins/awesome-claude-skills/notion-automation/SKILL.md
new file mode 100644
index 0000000..dc37411
--- /dev/null
+++ b/plugins/awesome-claude-skills/notion-automation/SKILL.md
@@ -0,0 +1,220 @@
+---
+name: notion-automation
+description: "Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Notion Automation via Rube MCP
+
+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)
+- Active Notion connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `notion`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `notion`
+3. If connection is not ACTIVE, follow the returned auth link to complete Notion OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Pages
+
+**When to use**: User wants to create, update, or archive Notion pages
+
+**Tool sequence**:
+1. `NOTION_SEARCH_NOTION_PAGE` - Find parent page or existing page [Prerequisite]
+2. `NOTION_CREATE_NOTION_PAGE` - Create a new page under a parent [Optional]
+3. `NOTION_RETRIEVE_PAGE` - Get page metadata/properties [Optional]
+4. `NOTION_UPDATE_PAGE` - Update page properties, title, icon, cover [Optional]
+5. `NOTION_ARCHIVE_NOTION_PAGE` - Soft-delete (archive) a page [Optional]
+
+**Key parameters**:
+- `query`: Search text for SEARCH_NOTION_PAGE
+- `parent_id`: Parent page or database ID
+- `page_id`: Page ID for retrieval/update/archive
+- `properties`: Page property values matching parent schema
+
+**Pitfalls**:
+- RETRIEVE_PAGE returns only metadata/properties, NOT body content; use FETCH_BLOCK_CONTENTS for page body
+- ARCHIVE_NOTION_PAGE is a soft-delete (sets archived=true), not permanent deletion
+- Broad searches can look incomplete unless has_more/next_cursor is fully paginated
+
+### 2. Query and Manage Databases
+
+**When to use**: User wants to query database rows, insert entries, or update records
+
+**Tool sequence**:
+1. `NOTION_SEARCH_NOTION_PAGE` - Find the database by name [Prerequisite]
+2. `NOTION_FETCH_DATABASE` - Inspect schema and properties [Prerequisite]
+3. `NOTION_QUERY_DATABASE` / `NOTION_QUERY_DATABASE_WITH_FILTER` - Query rows [Required]
+4. `NOTION_INSERT_ROW_DATABASE` - Add new entries [Optional]
+5. `NOTION_UPDATE_ROW_DATABASE` - Update existing entries [Optional]
+
+**Key parameters**:
+- `database_id`: Database ID (from search or URL)
+- `filter`: Filter object matching Notion filter syntax
+- `sorts`: Array of sort objects
+- `start_cursor`: Pagination cursor from previous response
+- `properties`: Property values matching database schema for inserts/updates
+
+**Pitfalls**:
+- 404 object_not_found usually means wrong database_id or the database is not shared with the integration
+- Results are paginated; ignoring has_more/next_cursor silently truncates reads
+- Schema mismatches or missing required properties cause 400 validation_error
+- Formula and read-only fields cannot be set via INSERT_ROW_DATABASE
+- Property names in filters must match schema exactly (case-sensitive)
+
+### 3. Manage Blocks and Page Content
+
+**When to use**: User wants to read, append, or modify content blocks in a page
+
+**Tool sequence**:
+1. `NOTION_FETCH_BLOCK_CONTENTS` - Read child blocks of a page [Required]
+2. `NOTION_ADD_MULTIPLE_PAGE_CONTENT` - Append blocks to a page [Optional]
+3. `NOTION_APPEND_TEXT_BLOCKS` - Append text-only blocks [Optional]
+4. `NOTION_REPLACE_PAGE_CONTENT` - Replace all page content [Optional]
+5. `NOTION_DELETE_BLOCK` - Remove a specific block [Optional]
+
+**Key parameters**:
+- `block_id` / `page_id`: Target page or block ID
+- `content_blocks`: Array of block objects (NOT child_blocks)
+- `text`: Plain text content for APPEND_TEXT_BLOCKS
+
+**Pitfalls**:
+- Use `content_blocks` parameter, NOT `child_blocks` -- the latter fails validation
+- ADD_MULTIPLE_PAGE_CONTENT fails on archived pages; unarchive via UPDATE_PAGE first
+- Created blocks are in response.data.results; persist block IDs for later edits
+- DELETE_BLOCK is archival (archived=true), not permanent deletion
+
+### 4. Manage Database Schema
+
+**When to use**: User wants to create databases or modify their structure
+
+**Tool sequence**:
+1. `NOTION_FETCH_DATABASE` - Inspect current schema [Prerequisite]
+2. `NOTION_CREATE_DATABASE` - Create a new database [Optional]
+3. `NOTION_UPDATE_SCHEMA_DATABASE` - Modify database properties [Optional]
+
+**Key parameters**:
+- `parent_id`: Parent page ID for new databases
+- `title`: Database title
+- `properties`: Property definitions with types and options
+- `database_id`: Database ID for schema updates
+
+**Pitfalls**:
+- Cannot change property types via UPDATE_SCHEMA; must create new property and migrate data
+- Formula, rollup, and relation properties have complex configuration requirements
+
+### 5. Manage Users and Comments
+
+**When to use**: User wants to list workspace users or manage comments on pages
+
+**Tool sequence**:
+1. `NOTION_LIST_USERS` - List all workspace users [Optional]
+2. `NOTION_GET_ABOUT_ME` - Get current authenticated user [Optional]
+3. `NOTION_CREATE_COMMENT` - Add a comment to a page [Optional]
+4. `NOTION_FETCH_COMMENTS` - List comments on a page [Optional]
+
+**Key parameters**:
+- `page_id`: Page ID for comments (also called `discussion_id`)
+- `rich_text`: Comment content as rich text array
+
+**Pitfalls**:
+- Comments are linked to pages, not individual blocks
+- User IDs from LIST_USERS are needed for people-type property filters
+
+## Common Patterns
+
+### ID Resolution
+
+**Page/Database name -> ID**:
+```
+1. Call NOTION_SEARCH_NOTION_PAGE with query=name
+2. Paginate with has_more/next_cursor until found
+3. Extract id from matching result
+```
+
+**Database schema inspection**:
+```
+1. Call NOTION_FETCH_DATABASE with database_id
+2. Extract properties object for field names and types
+3. Use exact property names in queries and inserts
+```
+
+### Pagination
+
+- Set `page_size` for results per page (max 100)
+- Check response for `has_more` boolean
+- Pass `start_cursor` or `next_cursor` in next request
+- Continue until `has_more` is false
+
+### Notion Filter Syntax
+
+**Single filter**:
+```json
+{"property": "Status", "select": {"equals": "Done"}}
+```
+
+**Compound filter**:
+```json
+{"and": [
+ {"property": "Status", "select": {"equals": "In Progress"}},
+ {"property": "Assignee", "people": {"contains": "user-id"}}
+]}
+```
+
+## Known Pitfalls
+
+**Integration Sharing**:
+- Pages and databases must be shared with the Notion integration to be accessible
+- Title queries can return 0 when the item is not shared with the integration
+
+**Property Types**:
+- Property names are case-sensitive and must match schema exactly
+- Formula, rollup, and created_time fields are read-only
+- Select/multi-select values must match existing options unless creating new ones
+
+**Response Parsing**:
+- Response data may be nested under `data_preview` or `data.results`
+- Parse defensively with fallbacks for different nesting levels
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search pages/databases | NOTION_SEARCH_NOTION_PAGE | query |
+| Create page | NOTION_CREATE_NOTION_PAGE | parent_id, properties |
+| Get page metadata | NOTION_RETRIEVE_PAGE | page_id |
+| Update page | NOTION_UPDATE_PAGE | page_id, properties |
+| Archive page | NOTION_ARCHIVE_NOTION_PAGE | page_id |
+| Duplicate page | NOTION_DUPLICATE_PAGE | page_id |
+| Get page blocks | NOTION_FETCH_BLOCK_CONTENTS | block_id |
+| Append blocks | NOTION_ADD_MULTIPLE_PAGE_CONTENT | page_id, content_blocks |
+| Append text | NOTION_APPEND_TEXT_BLOCKS | page_id, text |
+| Replace content | NOTION_REPLACE_PAGE_CONTENT | page_id, content_blocks |
+| Delete block | NOTION_DELETE_BLOCK | block_id |
+| Query database | NOTION_QUERY_DATABASE | database_id, filter, sorts |
+| Query with filter | NOTION_QUERY_DATABASE_WITH_FILTER | database_id, filter |
+| Insert row | NOTION_INSERT_ROW_DATABASE | database_id, properties |
+| Update row | NOTION_UPDATE_ROW_DATABASE | page_id, properties |
+| Get database schema | NOTION_FETCH_DATABASE | database_id |
+| Create database | NOTION_CREATE_DATABASE | parent_id, title, properties |
+| Update schema | NOTION_UPDATE_SCHEMA_DATABASE | database_id, properties |
+| 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/plugins/awesome-claude-skills/npm-automation/SKILL.md b/plugins/awesome-claude-skills/npm-automation/SKILL.md
new file mode 100644
index 0000000..fbbcbf5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ocr-web-service-automation/SKILL.md b/plugins/awesome-claude-skills/ocr-web-service-automation/SKILL.md
new file mode 100644
index 0000000..6892da7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ocrspace-automation/SKILL.md b/plugins/awesome-claude-skills/ocrspace-automation/SKILL.md
new file mode 100644
index 0000000..5f82166
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/omnisend-automation/SKILL.md b/plugins/awesome-claude-skills/omnisend-automation/SKILL.md
new file mode 100644
index 0000000..0a4a89c
--- /dev/null
+++ b/plugins/awesome-claude-skills/omnisend-automation/SKILL.md
@@ -0,0 +1,125 @@
+---
+name: Omnisend Automation
+description: "Automate ecommerce marketing workflows including contact management, bulk operations, and subscriber segmentation through Omnisend via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# Omnisend Automation
+
+Automate ecommerce marketing operations -- create and update contacts, manage subscriber lists with cursor pagination, run bulk batch operations, and segment audiences -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/omnisend](https://composio.dev/toolkits/omnisend)
+
+---
+
+## Setup
+
+1. Connect your Omnisend account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `OMNISEND_*` tools become available for execution
+
+---
+
+## Core Workflows
+
+### 1. Create or Update a Contact
+Upsert a contact by email identifier with subscription status, profile fields, and optional welcome message.
+
+**Tool:** `OMNISEND_CREATE_OR_UPDATE_CONTACT`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `identifiers` | array | Yes | At least one identifier object with `id` (email), `type` (`email`), optional `channels.email.status` (`subscribed`, `nonSubscribed`, `unsubscribed`), and `sendWelcomeMessage` (boolean) |
+| `firstName` | string | No | Contact's first name |
+| `lastName` | string | No | Contact's last name |
+| `gender` | string | No | `m` or `f` |
+| `birthdate` | string | No | Format: `YYYY-MM-DD` |
+| `country` | string | No | Full country name |
+| `countryCode` | string | No | ISO 3166-1 alpha-2 code (e.g., `US`) |
+| `city` | string | No | City name |
+| `address` | string | No | Street address |
+| `postalCode` | string | No | ZIP/postal code |
+
+---
+
+### 2. List Contacts with Pagination
+Retrieve contacts in batches with optional filters for email, phone, status, segment, or tag.
+
+**Tool:** `OMNISEND_LIST_CONTACTS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `limit` | integer | No | Results per page (default: 100, max: 250) |
+| `after` | string | No | Cursor for next page (base64-encoded ContactID) |
+| `before` | string | No | Cursor for previous page |
+| `email` | string | No | Filter by exact email address |
+| `phone` | string | No | Filter by full phone number with country code |
+| `status` | string | No | Filter by: `subscribed`, `nonSubscribed`, `unsubscribed` |
+| `segmentID` | integer | No | Filter by segment ID |
+| `tag` | string | No | Filter by tag (e.g., `VIP`) |
+
+---
+
+### 3. Get Contact Details
+Retrieve the full profile for a single contact when you already have their contact ID.
+
+**Tool:** `OMNISEND_GET_CONTACT`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `contactId` | string | Yes | Unique contact identifier (e.g., `60e7412b1234567890abcdef`) |
+
+---
+
+### 4. Update an Existing Contact
+Patch specific fields on a contact by ID without overwriting the entire record.
+
+**Tool:** `OMNISEND_UPDATE_CONTACT`
+
+Requires the `contactId` and the fields to update. Retrieve the contact ID first via `OMNISEND_LIST_CONTACTS` or `OMNISEND_GET_CONTACT`.
+
+---
+
+### 5. Bulk Batch Operations
+Process many records asynchronously in a single call -- contacts, products, orders, events, or categories.
+
+**Tool:** `OMNISEND_CREATE_BATCH`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `method` | string | Yes | `POST` or `PUT` |
+| `endpoint` | string | Yes | Target: `contacts`, `orders`, `products`, `events`, `categories` |
+| `items` | array | Yes | Array of payload objects for each operation |
+| `eventID` | string | Conditional | Required when endpoint is `events` |
+
+Use batch operations to avoid rate limits when processing large data sets.
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **Identifier required** | `OMNISEND_CREATE_OR_UPDATE_CONTACT` requires at least one identifier in the `identifiers` array -- only `email` type is supported |
+| **Cursor-based pagination** | `OMNISEND_LIST_CONTACTS` uses base64-encoded `after`/`before` cursors, not page numbers -- follow cursors to avoid incomplete data |
+| **Contact ID resolution** | `OMNISEND_UPDATE_CONTACT` requires a `contactId` -- always resolve it first via list or get operations |
+| **Batch method constraints** | `OMNISEND_CREATE_BATCH` only accepts `POST` or `PUT` methods -- no `DELETE` or `PATCH` |
+| **Event ID dependency** | When batching events, the `eventID` parameter is mandatory -- omitting it causes the batch to fail |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `OMNISEND_CREATE_OR_UPDATE_CONTACT` | Create or upsert a contact by email |
+| `OMNISEND_LIST_CONTACTS` | List contacts with filtering and cursor pagination |
+| `OMNISEND_GET_CONTACT` | Get full profile for a single contact by ID |
+| `OMNISEND_UPDATE_CONTACT` | Patch specific fields on an existing contact |
+| `OMNISEND_CREATE_BATCH` | Bulk async operations for contacts, products, orders, events |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/oncehub-automation/SKILL.md b/plugins/awesome-claude-skills/oncehub-automation/SKILL.md
new file mode 100644
index 0000000..45db549
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/one-drive-automation/SKILL.md b/plugins/awesome-claude-skills/one-drive-automation/SKILL.md
new file mode 100644
index 0000000..4f220cc
--- /dev/null
+++ b/plugins/awesome-claude-skills/one-drive-automation/SKILL.md
@@ -0,0 +1,243 @@
+---
+name: one-drive-automation
+description: Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# OneDrive Automation via Rube MCP
+
+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)
+- Active OneDrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `one_drive`
+3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search and Browse Files
+
+**When to use**: User wants to find files or browse folder contents in OneDrive
+
+**Tool sequence**:
+1. `ONE_DRIVE_GET_DRIVE` - Verify drive access and get drive details [Prerequisite]
+2. `ONE_DRIVE_SEARCH_ITEMS` - Keyword search across filenames, metadata, and content [Required]
+3. `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` - List all items in the root of a drive [Optional]
+4. `ONE_DRIVE_GET_ITEM` - Get detailed metadata for a specific item, expand children [Optional]
+5. `ONE_DRIVE_ONEDRIVE_FIND_FILE` - Find a specific file by exact name in a folder [Optional]
+6. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Find a specific folder by name [Optional]
+7. `ONE_DRIVE_LIST_DRIVES` - List all accessible drives [Optional]
+
+**Key parameters**:
+- `q`: Search query (plain keywords only, NOT KQL syntax)
+- `search_scope`: `"root"` (folder hierarchy) or `"drive"` (includes shared items)
+- `top`: Max items per page (default 200)
+- `skip_token`: Pagination token from `@odata.nextLink`
+- `select`: Comma-separated fields to return (e.g., `"id,name,webUrl,size"`)
+- `orderby`: Sort order (e.g., `"name asc"`, `"name desc"`)
+- `item_id`: Item ID for `GET_ITEM`
+- `expand_relations`: Array like `["children"]` or `["thumbnails"]` for `GET_ITEM`
+- `user_id`: `"me"` (default) or specific user ID/email
+
+**Pitfalls**:
+- `ONE_DRIVE_SEARCH_ITEMS` does NOT support KQL operators (`folder:`, `file:`, `filetype:`, `path:`); these are treated as literal text
+- Wildcard characters (`*`, `?`) are NOT supported and are auto-removed; use file extension keywords instead (e.g., `"pdf"` not `"*.pdf"`)
+- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` returns only root-level contents; use recursive `ONE_DRIVE_GET_ITEM` with `expand_relations: ["children"]` for deeper levels
+- Large folders paginate; always follow `skip_token` / `@odata.nextLink` until exhausted
+- Some drive ID formats may return "ObjectHandle is Invalid" errors due to Microsoft Graph API limitations
+
+### 2. Upload and Download Files
+
+**When to use**: User wants to upload files to OneDrive or download files from it
+
+**Tool sequence**:
+1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the target folder [Prerequisite]
+2. `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` - Upload a file to a specified folder [Required for upload]
+3. `ONE_DRIVE_DOWNLOAD_FILE` - Download a file by item ID [Required for download]
+4. `ONE_DRIVE_GET_ITEM` - Get file details before download [Optional]
+
+**Key parameters**:
+- `file`: FileUploadable object with `s3key`, `mimetype`, and `name` for uploads
+- `folder`: Destination path (e.g., `"/Documents/Reports"`) or folder ID for uploads
+- `item_id`: File's unique identifier for downloads
+- `file_name`: Desired filename with extension for downloads
+- `drive_id`: Specific drive ID (for SharePoint or OneDrive for Business)
+- `user_id`: `"me"` (default) or specific user identifier
+
+**Pitfalls**:
+- Upload automatically renames on conflict (no overwrite option by default)
+- Large files are automatically handled via chunking
+- `drive_id` overrides `user_id` when both are provided
+- Item IDs vary by platform: OneDrive for Business uses `01...` prefix, OneDrive Personal uses `HASH!NUMBER` format
+- Item IDs are case-sensitive; use exactly as returned from API
+
+### 3. Share Files and Manage Permissions
+
+**When to use**: User wants to share files/folders or manage who has access
+
+**Tool sequence**:
+1. `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate the item [Prerequisite]
+2. `ONE_DRIVE_GET_ITEM_PERMISSIONS` - Check current permissions [Prerequisite]
+3. `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` - Grant access to specific users [Required]
+4. `ONE_DRIVE_CREATE_LINK` - Create a shareable link [Optional]
+5. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Update item metadata [Optional]
+
+**Key parameters**:
+- `item_id`: The file or folder to share
+- `recipients`: Array of objects with `email` or `object_id`
+- `roles`: Array with `"read"` or `"write"`
+- `send_invitation`: `true` to send notification email, `false` for silent permission grant
+- `require_sign_in`: `true` to require authentication to access
+- `message`: Custom message for invitation (max 2000 characters)
+- `expiration_date_time`: ISO 8601 date for permission expiry
+- `retain_inherited_permissions`: `true` (default) to keep existing inherited permissions
+
+**Pitfalls**:
+- Using wrong `item_id` with `INVITE_USER_TO_DRIVE_ITEM` changes permissions on unintended items; always verify first
+- Write or higher roles are impactful; get explicit user confirmation before granting
+- `GET_ITEM_PERMISSIONS` returns inherited and owner entries; do not assume response only reflects recent changes
+- `permissions` cannot be expanded via `ONE_DRIVE_GET_ITEM`; use the separate permissions endpoint
+- At least one of `require_sign_in` or `send_invitation` must be `true`
+
+### 4. Manage Folders (Create, Move, Delete, Copy)
+
+**When to use**: User wants to create, move, rename, delete, or copy files and folders
+
+**Tool sequence**:
+1. `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` - Locate source and destination folders [Prerequisite]
+2. `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` - Create a new folder [Required for create]
+3. `ONE_DRIVE_MOVE_ITEM` - Move a file or folder to a new location [Required for move]
+4. `ONE_DRIVE_COPY_ITEM` - Copy a file or folder (async operation) [Required for copy]
+5. `ONE_DRIVE_DELETE_ITEM` - Move item to recycle bin [Required for delete]
+6. `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` - Rename or update item properties [Optional]
+
+**Key parameters**:
+- `name`: Folder name for creation or new name for rename/copy
+- `parent_folder`: Path (e.g., `"/Documents/Reports"`) or folder ID for creation
+- `itemId`: Item to move
+- `parentReference`: Object with `id` (destination folder ID) for moves: `{"id": "folder_id"}`
+- `item_id`: Item to copy or delete
+- `parent_reference`: Object with `id` and optional `driveId` for copy destination
+- `@microsoft.graph.conflictBehavior`: `"fail"`, `"replace"`, or `"rename"` for copies
+- `if_match`: ETag for optimistic concurrency on deletes
+
+**Pitfalls**:
+- `ONE_DRIVE_MOVE_ITEM` does NOT support cross-drive moves; use `ONE_DRIVE_COPY_ITEM` for cross-drive transfers
+- `parentReference` for moves requires folder ID (not folder name); resolve with `ONEDRIVE_FIND_FOLDER` first
+- `ONE_DRIVE_COPY_ITEM` is asynchronous; response provides a URL to monitor progress
+- `ONE_DRIVE_DELETE_ITEM` moves to recycle bin, not permanent deletion
+- Folder creation auto-renames on conflict (e.g., "New Folder" becomes "New Folder 1")
+- Provide either `name` or `parent_reference` (or both) for `ONE_DRIVE_COPY_ITEM`
+
+### 5. Track Changes and Drive Information
+
+**When to use**: User wants to monitor changes or get drive/quota information
+
+**Tool sequence**:
+1. `ONE_DRIVE_GET_DRIVE` - Get drive properties and metadata [Required]
+2. `ONE_DRIVE_GET_QUOTA` - Check storage quota (total, used, remaining) [Optional]
+3. `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` - Track changes in SharePoint site drives [Optional]
+4. `ONE_DRIVE_GET_ITEM_VERSIONS` - Get version history of a file [Optional]
+
+**Key parameters**:
+- `drive_id`: Drive identifier (or `"me"` for personal drive)
+- `site_id`: SharePoint site identifier for delta tracking
+- `token`: Delta token (`"latest"` for current state, URL for next page, or timestamp)
+- `item_id`: File ID for version history
+
+**Pitfalls**:
+- Delta queries are only available for SharePoint site drives via `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA`
+- Token `"latest"` returns current delta token without items (useful as starting point)
+- Deep or large drives can take several minutes to crawl; use batching and resume logic
+
+## Common Patterns
+
+### ID Resolution
+- **User**: Use `"me"` for authenticated user or specific user email/GUID
+- **Item ID from find**: Use `ONE_DRIVE_ONEDRIVE_FIND_FILE` or `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` to get item IDs
+- **Item ID from search**: Extract from `ONE_DRIVE_SEARCH_ITEMS` results
+- **Drive ID**: Use `ONE_DRIVE_LIST_DRIVES` or `ONE_DRIVE_GET_DRIVE` to discover drives
+- **Folder path to ID**: Use `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` with path, then extract ID from response
+
+ID formats vary by platform:
+- OneDrive for Business/SharePoint: `01NKDM7HMOJTVYMDOSXFDK2QJDXCDI3WUK`
+- OneDrive Personal: `D4648F06C91D9D3D!54927`
+
+### Pagination
+OneDrive uses token-based pagination:
+- Follow `@odata.nextLink` or `skip_token` until no more pages
+- Set `top` for page size (varies by endpoint)
+- `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` auto-handles pagination internally
+- Aggressive parallel requests can trigger HTTP 429; honor `Retry-After` headers
+
+### Path vs ID
+Most OneDrive tools accept either paths or IDs:
+- **Paths**: Start with `/` (e.g., `"/Documents/Reports"`)
+- **IDs**: Use unique item identifiers from API responses
+- **Item paths for permissions**: Use `:/path/to/item:/` format
+
+## Known Pitfalls
+
+### ID Formats
+- Item IDs are case-sensitive and platform-specific
+- Never use web URLs, sharing links, or manually constructed identifiers as item IDs
+- Always use IDs exactly as returned from Microsoft Graph API
+
+### Rate Limits
+- Aggressive parallel `ONE_DRIVE_GET_ITEM` calls can trigger HTTP 429 Too Many Requests
+- Honor `Retry-After` headers and implement throttling
+- Deep drive crawls should use batching with delays
+
+### Search Limitations
+- No KQL support; use plain keywords only
+- No wildcard characters; use extension keywords (e.g., `"pdf"` not `"*.pdf"`)
+- No path-based filtering in search; use folder listing instead
+- `q='*'` wildcard-only queries return HTTP 400 invalidRequest
+
+### Parameter Quirks
+- `drive_id` overrides `user_id` when both are provided
+- `permissions` cannot be expanded via `GET_ITEM`; use dedicated permissions endpoint
+- Move operations require folder IDs in `parentReference`, not folder names
+- Copy operations are asynchronous; response provides monitoring URL
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search files | `ONE_DRIVE_SEARCH_ITEMS` | `q`, `search_scope`, `top` |
+| List root items | `ONE_DRIVE_ONEDRIVE_LIST_ITEMS` | `user_id`, `select`, `top` |
+| Get item details | `ONE_DRIVE_GET_ITEM` | `item_id`, `expand_relations` |
+| Find file by name | `ONE_DRIVE_ONEDRIVE_FIND_FILE` | `name`, `folder` |
+| Find folder by name | `ONE_DRIVE_ONEDRIVE_FIND_FOLDER` | `name`, `folder` |
+| Upload file | `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` | `file`, `folder` |
+| Download file | `ONE_DRIVE_DOWNLOAD_FILE` | `item_id`, `file_name` |
+| Create folder | `ONE_DRIVE_ONEDRIVE_CREATE_FOLDER` | `name`, `parent_folder` |
+| Move item | `ONE_DRIVE_MOVE_ITEM` | `itemId`, `parentReference` |
+| Copy item | `ONE_DRIVE_COPY_ITEM` | `item_id`, `parent_reference`, `name` |
+| Delete item | `ONE_DRIVE_DELETE_ITEM` | `item_id` |
+| Share with users | `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` | `item_id`, `recipients`, `roles` |
+| Create share link | `ONE_DRIVE_CREATE_LINK` | `item_id`, link type |
+| Get permissions | `ONE_DRIVE_GET_ITEM_PERMISSIONS` | `item_id` |
+| Update metadata | `ONE_DRIVE_UPDATE_DRIVE_ITEM_METADATA` | `item_id`, fields |
+| Get drive info | `ONE_DRIVE_GET_DRIVE` | `drive_id` |
+| List drives | `ONE_DRIVE_LIST_DRIVES` | user/group/site scope |
+| 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/plugins/awesome-claude-skills/onedesk-automation/SKILL.md b/plugins/awesome-claude-skills/onedesk-automation/SKILL.md
new file mode 100644
index 0000000..9f0ccbe
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/onepage-automation/SKILL.md b/plugins/awesome-claude-skills/onepage-automation/SKILL.md
new file mode 100644
index 0000000..3695e0e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/onesignal-rest-api-automation/SKILL.md b/plugins/awesome-claude-skills/onesignal-rest-api-automation/SKILL.md
new file mode 100644
index 0000000..807ab8b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/onesignal-user-auth-automation/SKILL.md b/plugins/awesome-claude-skills/onesignal-user-auth-automation/SKILL.md
new file mode 100644
index 0000000..adb1d07
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/onesignal_rest_api-automation/SKILL.md b/plugins/awesome-claude-skills/onesignal_rest_api-automation/SKILL.md
new file mode 100644
index 0000000..82bc226
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/open-sea-automation/SKILL.md b/plugins/awesome-claude-skills/open-sea-automation/SKILL.md
new file mode 100644
index 0000000..8a1e419
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/openai-automation/SKILL.md b/plugins/awesome-claude-skills/openai-automation/SKILL.md
new file mode 100644
index 0000000..eac3886
--- /dev/null
+++ b/plugins/awesome-claude-skills/openai-automation/SKILL.md
@@ -0,0 +1,122 @@
+---
+name: OpenAI Automation
+description: "Automate OpenAI API operations -- generate responses with multimodal and structured output support, create embeddings, generate images, and list models via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# OpenAI Automation
+
+Automate your OpenAI API workflows -- generate text with the Responses API (including multimodal image+text inputs and structured JSON outputs), create embeddings for search and clustering, generate images with DALL-E and GPT Image models, and list available models.
+
+**Toolkit docs:** [composio.dev/toolkits/openai](https://composio.dev/toolkits/openai)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your OpenAI account when prompted (API key authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. Generate a Response (Text, Multimodal, Structured)
+
+Use `OPENAI_CREATE_RESPONSE` for one-shot model responses including text, image analysis, OCR, and structured JSON outputs.
+
+```
+Tool: OPENAI_CREATE_RESPONSE
+Inputs:
+ - model: string (required) -- e.g., "gpt-5", "gpt-4o", "o3-mini"
+ - input: string | array (required)
+ Simple: "Explain quantum computing"
+ Multimodal: [
+ { role: "user", content: [
+ { type: "input_text", text: "What is in this image?" },
+ { type: "input_image", image_url: { url: "https://..." } }
+ ]}
+ ]
+ - temperature: number (0-2, optional -- not supported with reasoning models)
+ - max_output_tokens: integer (optional)
+ - reasoning: { effort: "none" | "minimal" | "low" | "medium" | "high" }
+ - text: object (structured output config)
+ - format: { type: "json_schema", name: "...", schema: {...}, strict: true }
+ - tools: array (function, code_interpreter, file_search, web_search)
+ - tool_choice: "auto" | "none" | "required" | { type: "function", function: { name: "..." } }
+ - store: boolean (false to opt out of model distillation)
+ - stream: boolean
+```
+
+**Structured output example:** Set `text.format` to `{ type: "json_schema", name: "person", schema: { type: "object", properties: { name: { type: "string" }, age: { type: "integer" } }, required: ["name", "age"], additionalProperties: false }, strict: true }`.
+
+### 2. Create Embeddings
+
+Use `OPENAI_CREATE_EMBEDDINGS` for vector search, clustering, recommendations, and RAG pipelines.
+
+```
+Tool: OPENAI_CREATE_EMBEDDINGS
+Inputs:
+ - input: string | string[] | int[] | int[][] (required) -- max 8192 tokens, max 2048 items
+ - model: string (required) -- "text-embedding-3-small", "text-embedding-3-large", "text-embedding-ada-002"
+ - dimensions: integer (optional, only for text-embedding-3 and later)
+ - encoding_format: "float" | "base64" (default "float")
+ - user: string (optional, end-user ID for abuse monitoring)
+```
+
+### 3. Generate Images
+
+Use `OPENAI_CREATE_IMAGE` to create images from text prompts using GPT Image or DALL-E models.
+
+```
+Tool: OPENAI_CREATE_IMAGE
+Inputs:
+ - model: string (required) -- "gpt-image-1", "gpt-image-1.5", "dall-e-3", "dall-e-2"
+ - prompt: string (required) -- max 32000 chars (GPT Image), 4000 (DALL-E 3), 1000 (DALL-E 2)
+ - size: "1024x1024" | "1536x1024" | "1024x1536" | "auto" | "256x256" | "512x512" | "1792x1024" | "1024x1792"
+ - quality: "standard" | "hd" | "auto" | "high" | "medium" | "low"
+ - n: integer (1-10; DALL-E 3 supports n=1 only)
+ - background: "transparent" | "opaque" | "auto" (GPT Image models only)
+ - style: "vivid" | "natural" (DALL-E 3 only)
+ - user: string (optional)
+```
+
+### 4. List Available Models
+
+Use `OPENAI_LIST_MODELS` to discover which models are accessible with your API key.
+
+```
+Tool: OPENAI_LIST_MODELS
+Inputs: (none)
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| DALL-E deprecation | DALL-E 2 and DALL-E 3 are deprecated and will stop being supported on 05/12/2026. Prefer GPT Image models. |
+| DALL-E 3 single image only | `OPENAI_CREATE_IMAGE` with DALL-E 3 only supports `n=1`. Use GPT Image models or DALL-E 2 for multiple images. |
+| Token limits for embeddings | Input must not exceed 8192 tokens per item and 2048 items per batch for embedding models. |
+| Reasoning model restrictions | `temperature` and `top_p` are not supported with reasoning models (o3-mini, etc.). Use `reasoning.effort` instead. |
+| Structured output strict mode | When `strict: true` in json_schema format, ALL schema properties must be listed in the `required` array. |
+| Prompt length varies by model | Image prompt max lengths differ: 32000 (GPT Image), 4000 (DALL-E 3), 1000 (DALL-E 2). |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `OPENAI_CREATE_RESPONSE` | Generate text/multimodal responses with structured output support |
+| `OPENAI_CREATE_EMBEDDINGS` | Create text embeddings for search, clustering, and RAG |
+| `OPENAI_CREATE_IMAGE` | Generate images from text prompts |
+| `OPENAI_LIST_MODELS` | List all models available to your API key |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/opencage-automation/SKILL.md b/plugins/awesome-claude-skills/opencage-automation/SKILL.md
new file mode 100644
index 0000000..d1e07dc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/opengraph-io-automation/SKILL.md b/plugins/awesome-claude-skills/opengraph-io-automation/SKILL.md
new file mode 100644
index 0000000..d1104ee
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/openperplex-automation/SKILL.md b/plugins/awesome-claude-skills/openperplex-automation/SKILL.md
new file mode 100644
index 0000000..0c1fede
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/openrouter-automation/SKILL.md b/plugins/awesome-claude-skills/openrouter-automation/SKILL.md
new file mode 100644
index 0000000..ff705ce
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/openweather-api-automation/SKILL.md b/plugins/awesome-claude-skills/openweather-api-automation/SKILL.md
new file mode 100644
index 0000000..b9d85bb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/optimoroute-automation/SKILL.md b/plugins/awesome-claude-skills/optimoroute-automation/SKILL.md
new file mode 100644
index 0000000..5df9a75
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/outlook-automation/SKILL.md b/plugins/awesome-claude-skills/outlook-automation/SKILL.md
new file mode 100644
index 0000000..dafb200
--- /dev/null
+++ b/plugins/awesome-claude-skills/outlook-automation/SKILL.md
@@ -0,0 +1,196 @@
+---
+name: outlook-automation
+description: "Automate Outlook tasks via Rube MCP (Composio): emails, calendar, contacts, folders, attachments. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Outlook Automation via Rube MCP
+
+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)
+- Active Outlook connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`
+3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search and Filter Emails
+
+**When to use**: User wants to find specific emails across their mailbox
+
+**Tool sequence**:
+1. `OUTLOOK_SEARCH_MESSAGES` - Search with KQL syntax across all folders [Required]
+2. `OUTLOOK_GET_MESSAGE` - Get full message details [Optional]
+3. `OUTLOOK_LIST_OUTLOOK_ATTACHMENTS` - List message attachments [Optional]
+4. `OUTLOOK_DOWNLOAD_OUTLOOK_ATTACHMENT` - Download attachment [Optional]
+
+**Key parameters**:
+- `query`: KQL search string (from:, to:, subject:, received:, hasattachment:)
+- `from_index`: Pagination start (0-based)
+- `size`: Results per page (max 25)
+- `message_id`: Message ID (use hitId from search results)
+
+**Pitfalls**:
+- Only works with Microsoft 365/Enterprise accounts (not @hotmail.com/@outlook.com)
+- Pagination relies on hitsContainers[0].moreResultsAvailable; stop only when false
+- Use hitId from search results as message_id for downstream calls, not resource.id
+- Index latency: very recent emails may not appear immediately
+- Inline images appear as attachments; filter by mimetype for real documents
+
+### 2. Query Emails in a Folder
+
+**When to use**: User wants to list emails in a specific folder with OData filters
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_MAIL_FOLDERS` - List mail folders to get folder IDs [Prerequisite]
+2. `OUTLOOK_QUERY_EMAILS` - Query emails with structured filters [Required]
+
+**Key parameters**:
+- `folder`: Folder name ('inbox', 'sentitems', 'drafts') or folder ID
+- `filter`: OData filter (e.g., `isRead eq false and importance eq 'high'`)
+- `top`: Max results (1-1000)
+- `orderby`: Sort field and direction
+- `select`: Array of fields to return
+
+**Pitfalls**:
+- QUERY_EMAILS searches a SINGLE folder only; use SEARCH_MESSAGES for cross-folder search
+- Custom folders require folder IDs, not display names; use LIST_MAIL_FOLDERS
+- Always check response['@odata.nextLink'] for pagination
+- Cannot filter by recipient or body content; use SEARCH_MESSAGES for that
+
+### 3. Manage Calendar Events
+
+**When to use**: User wants to list, search, or inspect calendar events
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_EVENTS` - List events with filters [Optional]
+2. `OUTLOOK_GET_CALENDAR_VIEW` - Get events in a time window [Optional]
+3. `OUTLOOK_GET_EVENT` - Get specific event details [Optional]
+4. `OUTLOOK_LIST_CALENDARS` - List available calendars [Optional]
+5. `OUTLOOK_GET_SCHEDULE` - Get free/busy info [Optional]
+
+**Key parameters**:
+- `filter`: OData filter (use start/dateTime, NOT receivedDateTime)
+- `start_datetime`/`end_datetime`: ISO 8601 for calendar view
+- `timezone`: IANA timezone (e.g., 'America/New_York')
+- `calendar_id`: Optional non-primary calendar ID
+- `select`: Fields to return
+
+**Pitfalls**:
+- Use calendar event properties only (start/dateTime, end/dateTime), NOT email properties (receivedDateTime)
+- Calendar view requires start_datetime and end_datetime
+- Recurring events need `expand_recurring_events=true` to see individual occurrences
+- Decline status is per-attendee via attendees[].status.response
+
+### 4. Manage Contacts
+
+**When to use**: User wants to list, create, or organize contacts
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_CONTACTS` - List contacts [Optional]
+2. `OUTLOOK_CREATE_CONTACT` - Create a new contact [Optional]
+3. `OUTLOOK_GET_CONTACT_FOLDERS` - List contact folders [Optional]
+4. `OUTLOOK_CREATE_CONTACT_FOLDER` - Create contact folder [Optional]
+
+**Key parameters**:
+- `givenName`/`surname`: Contact name
+- `emailAddresses`: Array of email objects
+- `displayName`: Full display name
+- `contact_folder_id`: Optional folder for contacts
+
+**Pitfalls**:
+- Contact creation supports many fields but only givenName or surname is needed
+
+### 5. Manage Mail Folders
+
+**When to use**: User wants to organize mail folders
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_MAIL_FOLDERS` - List top-level folders [Required]
+2. `OUTLOOK_LIST_CHILD_MAIL_FOLDERS` - List subfolders [Optional]
+3. `OUTLOOK_CREATE_MAIL_FOLDER` - Create a new folder [Optional]
+
+**Key parameters**:
+- `parent_folder_id`: Well-known name or folder ID
+- `displayName`: New folder name
+- `include_hidden_folders`: Show hidden folders
+
+**Pitfalls**:
+- Well-known folder names: 'inbox', 'sentitems', 'drafts', 'deleteditems', 'junkemail', 'archive'
+- Custom folder operations require the folder ID, not display name
+
+## Common Patterns
+
+### KQL Search Syntax
+
+**Property filters**:
+- `from:user@example.com` - From sender
+- `to:recipient@example.com` - To recipient
+- `subject:invoice` - Subject contains
+- `received>=2025-01-01` - Date filter
+- `hasattachment:yes` - Has attachments
+
+**Combinators**:
+- `AND` - Both conditions
+- `OR` - Either condition
+- Parentheses for grouping
+
+### OData Filter Syntax
+
+**Email filters**:
+- `isRead eq false` - Unread emails
+- `importance eq 'high'` - High importance
+- `hasAttachments eq true` - Has attachments
+- `receivedDateTime ge 2025-01-01T00:00:00Z` - Date filter
+
+**Calendar filters**:
+- `start/dateTime ge '2025-01-01T00:00:00Z'` - Events after date
+- `contains(subject, 'Meeting')` - Subject contains text
+
+## Known Pitfalls
+
+**Account Types**:
+- SEARCH_MESSAGES requires Microsoft 365/Enterprise accounts
+- Personal accounts (@hotmail.com, @outlook.com) have limited API access
+
+**Field Confusion**:
+- Email properties (receivedDateTime) differ from calendar properties (start/dateTime)
+- Do NOT use email fields in calendar queries or vice versa
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search emails | OUTLOOK_SEARCH_MESSAGES | query, from_index, size |
+| Query folder | OUTLOOK_QUERY_EMAILS | folder, filter, top |
+| Get message | OUTLOOK_GET_MESSAGE | message_id |
+| List attachments | OUTLOOK_LIST_OUTLOOK_ATTACHMENTS | message_id |
+| Download attachment | OUTLOOK_DOWNLOAD_OUTLOOK_ATTACHMENT | message_id, attachment_id |
+| List folders | OUTLOOK_LIST_MAIL_FOLDERS | (none) |
+| Child folders | OUTLOOK_LIST_CHILD_MAIL_FOLDERS | parent_folder_id |
+| List events | OUTLOOK_LIST_EVENTS | filter, timezone |
+| Calendar view | OUTLOOK_GET_CALENDAR_VIEW | start_datetime, end_datetime |
+| Get event | OUTLOOK_GET_EVENT | event_id |
+| List calendars | OUTLOOK_LIST_CALENDARS | (none) |
+| Free/busy | OUTLOOK_GET_SCHEDULE | schedules, times |
+| 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/plugins/awesome-claude-skills/outlook-calendar-automation/SKILL.md b/plugins/awesome-claude-skills/outlook-calendar-automation/SKILL.md
new file mode 100644
index 0000000..5b9753a
--- /dev/null
+++ b/plugins/awesome-claude-skills/outlook-calendar-automation/SKILL.md
@@ -0,0 +1,241 @@
+---
+name: outlook-calendar-automation
+description: "Automate Outlook Calendar tasks via Rube MCP (Composio): create events, manage attendees, find meeting times, and handle invitations. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Outlook Calendar Automation via Rube MCP
+
+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)
+- Active Outlook connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `outlook`
+3. If connection is not ACTIVE, follow the returned auth link to complete Microsoft OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create Calendar Events
+
+**When to use**: User wants to schedule a new event on their Outlook calendar
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_CALENDARS` - List available calendars [Optional]
+2. `OUTLOOK_CALENDAR_CREATE_EVENT` - Create the event [Required]
+
+**Key parameters**:
+- `subject`: Event title
+- `start_datetime`: ISO 8601 start time (e.g., '2025-01-03T10:00:00')
+- `end_datetime`: ISO 8601 end time (must be after start)
+- `time_zone`: IANA or Windows timezone (e.g., 'America/New_York', 'Pacific Standard Time')
+- `attendees_info`: Array of email strings or attendee objects
+- `body`: Event description (plain text or HTML)
+- `is_html`: Set true if body contains HTML
+- `location`: Physical location string
+- `is_online_meeting`: Set true for Teams meeting link
+- `online_meeting_provider`: 'teamsForBusiness' for Teams integration
+- `show_as`: 'free', 'tentative', 'busy', 'oof'
+
+**Pitfalls**:
+- start_datetime must be chronologically before end_datetime
+- time_zone is required and must be a valid IANA or Windows timezone name
+- Adding attendees can trigger invitation emails immediately
+- To generate a Teams meeting link, set BOTH is_online_meeting=true AND online_meeting_provider='teamsForBusiness'
+- user_id defaults to 'me'; use email or UUID for other users' calendars
+
+### 2. List and Search Events
+
+**When to use**: User wants to find events on their calendar
+
+**Tool sequence**:
+1. `OUTLOOK_GET_MAILBOX_SETTINGS` - Get user timezone for accurate queries [Prerequisite]
+2. `OUTLOOK_LIST_EVENTS` - Search events with filters [Required]
+3. `OUTLOOK_GET_EVENT` - Get full details for a specific event [Optional]
+4. `OUTLOOK_GET_CALENDAR_VIEW` - Get events active during a time window [Alternative]
+
+**Key parameters**:
+- `filter`: OData filter string (e.g., "start/dateTime ge '2024-07-01T00:00:00Z'")
+- `select`: Array of properties to return
+- `orderby`: Sort criteria (e.g., ['start/dateTime desc'])
+- `top`: Results per page (1-999)
+- `timezone`: Display timezone for results
+- `start_datetime`/`end_datetime`: For CALENDAR_VIEW time window (UTC with Z suffix)
+
+**Pitfalls**:
+- OData filter datetime values require single quotes and Z suffix
+- Use 'start/dateTime' for event start filtering, NOT 'receivedDateTime' (that is for emails)
+- 'createdDateTime' supports orderby/select but NOT filtering
+- Pagination: follow @odata.nextLink until all pages are collected
+- CALENDAR_VIEW is better for "what's on my calendar today" queries (includes spanning events)
+- LIST_EVENTS is better for keyword/category filtering
+- Response events have start/end nested as start.dateTime and end.dateTime
+
+### 3. Update Events
+
+**When to use**: User wants to modify an existing calendar event
+
+**Tool sequence**:
+1. `OUTLOOK_LIST_EVENTS` - Find the event to update [Prerequisite]
+2. `OUTLOOK_UPDATE_CALENDAR_EVENT` - Update the event [Required]
+
+**Key parameters**:
+- `event_id`: Unique event identifier (from LIST_EVENTS)
+- `subject`: New event title (optional)
+- `start_datetime`/`end_datetime`: New times (optional)
+- `time_zone`: Timezone for new times
+- `attendees`: Updated attendee list (replaces existing if provided)
+- `body`: Updated description with contentType and content
+- `location`: Updated location
+
+**Pitfalls**:
+- UPDATE merges provided fields with existing event; unspecified fields are preserved
+- Providing attendees replaces the ENTIRE attendee list; include all desired attendees
+- Providing categories replaces the ENTIRE category list
+- Updating times may trigger re-sends to attendees
+- event_id is required; obtain from LIST_EVENTS first
+
+### 4. Delete Events and Decline Invitations
+
+**When to use**: User wants to remove an event or decline a meeting invitation
+
+**Tool sequence**:
+1. `OUTLOOK_DELETE_EVENT` - Delete an event [Optional]
+2. `OUTLOOK_DECLINE_EVENT` - Decline a meeting invitation [Optional]
+
+**Key parameters**:
+- `event_id`: Event to delete or decline
+- `send_notifications`: Send cancellation notices to attendees (default true)
+- `comment`: Reason for declining (for DECLINE_EVENT)
+- `proposedNewTime`: Suggest alternative time when declining
+
+**Pitfalls**:
+- Deletion with send_notifications=true sends cancellation emails
+- Declining supports proposing a new time with start/end in ISO 8601 format
+- Deleting a recurring event master deletes all occurrences
+- sendResponse in DECLINE_EVENT controls whether the organizer is notified
+
+### 5. Find Available Meeting Times
+
+**When to use**: User wants to find optimal meeting slots across multiple people
+
+**Tool sequence**:
+1. `OUTLOOK_FIND_MEETING_TIMES` - Get meeting time suggestions [Required]
+2. `OUTLOOK_GET_SCHEDULE` - Check free/busy for specific people [Alternative]
+
+**Key parameters**:
+- `attendees`: Array of attendee objects with email and type
+- `meetingDuration`: ISO 8601 duration (e.g., 'PT1H' for 1 hour, 'PT30M' for 30 min)
+- `timeConstraint`: Time slots to search within
+- `minimumAttendeePercentage`: Minimum confidence threshold (0-100)
+- `Schedules`: Email array for GET_SCHEDULE
+- `StartTime`/`EndTime`: Time window for schedule lookup (max 62 days)
+
+**Pitfalls**:
+- FIND_MEETING_TIMES searches within work hours by default; use activityDomain='unrestricted' for 24/7
+- Time constraint time slots require dateTime and timeZone for both start and end
+- GET_SCHEDULE period cannot exceed 62 days
+- Meeting suggestions respect attendee availability but may return suboptimal times for complex groups
+
+## Common Patterns
+
+### Event ID Resolution
+
+```
+1. Call OUTLOOK_LIST_EVENTS with time-bound filter
+2. Find target event by subject or other criteria
+3. Extract event id (e.g., 'AAMkAGI2TAAA=')
+4. Use in UPDATE, DELETE, or GET_EVENT calls
+```
+
+### OData Filter Syntax for Calendar
+
+**Time range filter**:
+```
+filter: "start/dateTime ge '2024-07-01T00:00:00Z' and start/dateTime le '2024-07-31T23:59:59Z'"
+```
+
+**Subject contains**:
+```
+filter: "contains(subject, 'Project Review')"
+```
+
+**Combined**:
+```
+filter: "contains(subject, 'Review') and categories/any(c:c eq 'Work')"
+```
+
+### Timezone Handling
+
+- Get user timezone: `OUTLOOK_GET_MAILBOX_SETTINGS` with select=['timeZone']
+- Use consistent timezone in filter datetime values
+- Calendar View requires UTC timestamps with Z suffix
+- LIST_EVENTS filter accepts timezone in datetime values
+
+### Online Meeting Creation
+
+```
+1. Set is_online_meeting: true
+2. Set online_meeting_provider: 'teamsForBusiness'
+3. Create event with OUTLOOK_CALENDAR_CREATE_EVENT
+4. Teams join link available in response onlineMeeting field
+5. Or retrieve via OUTLOOK_GET_EVENT for the full join URL
+```
+
+## Known Pitfalls
+
+**DateTime Formats**:
+- ISO 8601 format required: '2025-01-03T10:00:00'
+- Calendar View requires UTC with Z: '2025-01-03T10:00:00Z'
+- Filter values need single quotes: "'2025-01-03T00:00:00Z'"
+- Timezone mismatches shift event boundaries; always resolve user timezone first
+
+**OData Filter Errors**:
+- 400 Bad Request usually indicates filter syntax issues
+- Not all event properties support filtering (createdDateTime does not)
+- Retry with adjusted syntax/bounds on 400 errors
+- Valid filter fields: start/dateTime, end/dateTime, subject, categories, isAllDay
+
+**Attendee Management**:
+- Adding attendees triggers invitation emails
+- Updating attendees replaces the full list; include all desired attendees
+- Attendee types: 'required', 'optional', 'resource'
+- Calendar delegation affects which calendars are accessible
+
+**Response Structure**:
+- Events nested at response.data.value
+- Event times at event.start.dateTime and event.end.dateTime
+- Calendar View may nest at data.results[i].response.data.value
+- Parse defensively with fallbacks for different nesting levels
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create event | OUTLOOK_CALENDAR_CREATE_EVENT | subject, start_datetime, end_datetime, time_zone |
+| List events | OUTLOOK_LIST_EVENTS | filter, select, top, timezone |
+| Get event details | OUTLOOK_GET_EVENT | event_id |
+| Calendar view | OUTLOOK_GET_CALENDAR_VIEW | start_datetime, end_datetime |
+| Update event | OUTLOOK_UPDATE_CALENDAR_EVENT | event_id, subject, start_datetime |
+| Delete event | OUTLOOK_DELETE_EVENT | event_id, send_notifications |
+| Decline event | OUTLOOK_DECLINE_EVENT | event_id, comment |
+| Find meeting times | OUTLOOK_FIND_MEETING_TIMES | attendees, meetingDuration |
+| 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/plugins/awesome-claude-skills/owl-protocol-automation/SKILL.md b/plugins/awesome-claude-skills/owl-protocol-automation/SKILL.md
new file mode 100644
index 0000000..100e8e8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/page-x-automation/SKILL.md b/plugins/awesome-claude-skills/page-x-automation/SKILL.md
new file mode 100644
index 0000000..3bfba49
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pagerduty-automation/SKILL.md b/plugins/awesome-claude-skills/pagerduty-automation/SKILL.md
new file mode 100644
index 0000000..820b4de
--- /dev/null
+++ b/plugins/awesome-claude-skills/pagerduty-automation/SKILL.md
@@ -0,0 +1,250 @@
+---
+name: pagerduty-automation
+description: "Automate PagerDuty tasks via Rube MCP (Composio): manage incidents, services, schedules, escalation policies, and on-call rotations. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# PagerDuty Automation via Rube MCP
+
+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)
+- Active PagerDuty connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pagerduty`
+3. If connection is not ACTIVE, follow the returned auth link to complete PagerDuty authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Incidents
+
+**When to use**: User wants to create, update, acknowledge, or resolve incidents
+
+**Tool sequence**:
+1. `PAGERDUTY_FETCH_INCIDENT_LIST` - List incidents with filters [Required]
+2. `PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID` - Get specific incident details [Optional]
+3. `PAGERDUTY_CREATE_INCIDENT_RECORD` - Create a new incident [Optional]
+4. `PAGERDUTY_UPDATE_INCIDENT_BY_ID` - Update incident status or assignment [Optional]
+5. `PAGERDUTY_POST_INCIDENT_NOTE_USING_ID` - Add a note to an incident [Optional]
+6. `PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION` - Snooze an incident for a period [Optional]
+
+**Key parameters**:
+- `statuses[]`: Filter by status ('triggered', 'acknowledged', 'resolved')
+- `service_ids[]`: Filter by service IDs
+- `urgencies[]`: Filter by urgency ('high', 'low')
+- `title`: Incident title (for creation)
+- `service`: Service object with `id` and `type` (for creation)
+- `status`: New status for update operations
+
+**Pitfalls**:
+- Incident creation requires a `service` object with both `id` and `type: 'service_reference'`
+- Status transitions follow: triggered -> acknowledged -> resolved
+- Cannot transition from resolved back to triggered directly
+- `PAGERDUTY_UPDATE_INCIDENT_BY_ID` requires the incident ID as a path parameter
+- Snooze duration is in seconds; the incident re-triggers after the snooze period
+
+### 2. Inspect Incident Alerts and Analytics
+
+**When to use**: User wants to review alerts within an incident or analyze incident metrics
+
+**Tool sequence**:
+1. `PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID` - List alerts for an incident [Required]
+2. `PAGERDUTY_GET_INCIDENT_ALERT_DETAILS` - Get details of a specific alert [Optional]
+3. `PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID` - Get incident analytics/metrics [Optional]
+
+**Key parameters**:
+- `incident_id`: The incident ID
+- `alert_id`: Specific alert ID within the incident
+- `statuses[]`: Filter alerts by status
+
+**Pitfalls**:
+- An incident can have multiple alerts; each alert has its own status
+- Alert IDs are scoped to the incident
+- Analytics data includes response times, engagement metrics, and resolution times
+
+### 3. Manage Services
+
+**When to use**: User wants to create, update, or list services
+
+**Tool sequence**:
+1. `PAGERDUTY_RETRIEVE_LIST_OF_SERVICES` - List all services [Required]
+2. `PAGERDUTY_RETRIEVE_SERVICE_BY_ID` - Get service details [Optional]
+3. `PAGERDUTY_CREATE_NEW_SERVICE` - Create a new technical service [Optional]
+4. `PAGERDUTY_UPDATE_SERVICE_BY_ID` - Update service configuration [Optional]
+5. `PAGERDUTY_CREATE_INTEGRATION_FOR_SERVICE` - Add an integration to a service [Optional]
+6. `PAGERDUTY_CREATE_BUSINESS_SERVICE` - Create a business service [Optional]
+7. `PAGERDUTY_UPDATE_BUSINESS_SERVICE_BY_ID` - Update a business service [Optional]
+
+**Key parameters**:
+- `name`: Service name
+- `escalation_policy`: Escalation policy object with `id` and `type`
+- `alert_creation`: Alert creation mode ('create_alerts_and_incidents' or 'create_incidents')
+- `status`: Service status ('active', 'warning', 'critical', 'maintenance', 'disabled')
+
+**Pitfalls**:
+- Creating a service requires an existing escalation policy
+- Business services are different from technical services; they represent business-level groupings
+- Service integrations define how alerts are created (email, API, events)
+- Disabling a service stops all incident creation for that service
+
+### 4. Manage Schedules and On-Call
+
+**When to use**: User wants to view or manage on-call schedules and rotations
+
+**Tool sequence**:
+1. `PAGERDUTY_GET_SCHEDULES` - List all schedules [Required]
+2. `PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID` - Get specific schedule details [Optional]
+3. `PAGERDUTY_CREATE_NEW_SCHEDULE_LAYER` - Create a new schedule [Optional]
+4. `PAGERDUTY_UPDATE_SCHEDULE_BY_ID` - Update an existing schedule [Optional]
+5. `PAGERDUTY_RETRIEVE_ONCALL_LIST` - View who is currently on-call [Optional]
+6. `PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION` - Create temporary overrides [Optional]
+7. `PAGERDUTY_DELETE_SCHEDULE_OVERRIDE_BY_ID` - Remove an override [Optional]
+8. `PAGERDUTY_RETRIEVE_USERS_BY_SCHEDULE_ID` - List users in a schedule [Optional]
+9. `PAGERDUTY_PREVIEW_SCHEDULE_OBJECT` - Preview schedule changes before saving [Optional]
+
+**Key parameters**:
+- `schedule_id`: Schedule identifier
+- `time_zone`: Schedule timezone (e.g., 'America/New_York')
+- `schedule_layers`: Array of rotation layer configurations
+- `since`/`until`: Date range for on-call queries (ISO 8601)
+- `override`: Override object with user, start, and end times
+
+**Pitfalls**:
+- Schedule layers define rotation order; multiple layers can overlap
+- Overrides are temporary and take precedence over the normal schedule
+- `since` and `until` are required for on-call queries to scope the time range
+- Time zones must be valid IANA timezone strings
+- Preview before saving complex schedule changes to verify correctness
+
+### 5. Manage Escalation Policies
+
+**When to use**: User wants to create or modify escalation policies
+
+**Tool sequence**:
+1. `PAGERDUTY_FETCH_ESCALATION_POLICES_LIST` - List all escalation policies [Required]
+2. `PAGERDUTY_GET_ESCALATION_POLICY_BY_ID` - Get policy details [Optional]
+3. `PAGERDUTY_CREATE_ESCALATION_POLICY` - Create a new policy [Optional]
+4. `PAGERDUTY_UPDATE_ESCALATION_POLICY_BY_ID` - Update an existing policy [Optional]
+5. `PAGERDUTY_AUDIT_ESCALATION_POLICY_RECORDS` - View audit trail for a policy [Optional]
+
+**Key parameters**:
+- `name`: Policy name
+- `escalation_rules`: Array of escalation rule objects
+- `num_loops`: Number of times to loop through rules before stopping (0 = no loop)
+- `escalation_delay_in_minutes`: Delay between escalation levels
+
+**Pitfalls**:
+- Each escalation rule requires at least one target (user, schedule, or team)
+- `escalation_delay_in_minutes` defines how long before escalating to the next level
+- Setting `num_loops` to 0 means the policy runs once and stops
+- Deleting a policy fails if services still reference it
+
+### 6. Manage Teams
+
+**When to use**: User wants to create or manage PagerDuty teams
+
+**Tool sequence**:
+1. `PAGERDUTY_CREATE_NEW_TEAM_WITH_DETAILS` - Create a new team [Required]
+
+**Key parameters**:
+- `name`: Team name
+- `description`: Team description
+
+**Pitfalls**:
+- Team names must be unique within the account
+- Teams are used to scope services, escalation policies, and schedules
+
+## Common Patterns
+
+### ID Resolution
+
+**Service name -> Service ID**:
+```
+1. Call PAGERDUTY_RETRIEVE_LIST_OF_SERVICES
+2. Find service by name in response
+3. Extract id field
+```
+
+**Schedule name -> Schedule ID**:
+```
+1. Call PAGERDUTY_GET_SCHEDULES
+2. Find schedule by name in response
+3. Extract id field
+```
+
+### Incident Lifecycle
+
+```
+1. Incident triggered (via API, integration, or manual creation)
+2. On-call user notified per escalation policy
+3. User acknowledges -> status: 'acknowledged'
+4. User resolves -> status: 'resolved'
+```
+
+### Pagination
+
+- PagerDuty uses offset-based pagination
+- Check response for `more` boolean field
+- Use `offset` and `limit` parameters
+- Continue until `more` is false
+
+## Known Pitfalls
+
+**ID Formats**:
+- All PagerDuty IDs are alphanumeric strings (e.g., 'P1234AB')
+- Service references require `type: 'service_reference'`
+- User references require `type: 'user_reference'`
+
+**Status Transitions**:
+- Incidents: triggered -> acknowledged -> resolved (forward only)
+- Services: active, warning, critical, maintenance, disabled
+
+**Rate Limits**:
+- PagerDuty API enforces rate limits per account
+- Implement exponential backoff on 429 responses
+- Bulk operations should be spaced out
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Pagination uses `offset`/`limit`/`more` pattern
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List incidents | PAGERDUTY_FETCH_INCIDENT_LIST | statuses[], service_ids[] |
+| Get incident | PAGERDUTY_RETRIEVE_INCIDENT_BY_INCIDENT_ID | incident_id |
+| Create incident | PAGERDUTY_CREATE_INCIDENT_RECORD | title, service |
+| Update incident | PAGERDUTY_UPDATE_INCIDENT_BY_ID | incident_id, status |
+| Add incident note | PAGERDUTY_POST_INCIDENT_NOTE_USING_ID | incident_id, content |
+| Snooze incident | PAGERDUTY_SNOOZE_INCIDENT_BY_DURATION | incident_id, duration |
+| Get incident alerts | PAGERDUTY_GET_ALERTS_BY_INCIDENT_ID | incident_id |
+| Incident analytics | PAGERDUTY_FETCH_INCIDENT_ANALYTICS_BY_ID | incident_id |
+| List services | PAGERDUTY_RETRIEVE_LIST_OF_SERVICES | (none) |
+| Get service | PAGERDUTY_RETRIEVE_SERVICE_BY_ID | service_id |
+| Create service | PAGERDUTY_CREATE_NEW_SERVICE | name, escalation_policy |
+| Update service | PAGERDUTY_UPDATE_SERVICE_BY_ID | service_id |
+| List schedules | PAGERDUTY_GET_SCHEDULES | (none) |
+| Get schedule | PAGERDUTY_RETRIEVE_SCHEDULE_BY_ID | schedule_id |
+| Get on-call | PAGERDUTY_RETRIEVE_ONCALL_LIST | since, until |
+| Create schedule override | PAGERDUTY_CREATE_SCHEDULE_OVERRIDES_CONFIGURATION | schedule_id |
+| 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/plugins/awesome-claude-skills/pandadoc-automation/SKILL.md b/plugins/awesome-claude-skills/pandadoc-automation/SKILL.md
new file mode 100644
index 0000000..19de67c
--- /dev/null
+++ b/plugins/awesome-claude-skills/pandadoc-automation/SKILL.md
@@ -0,0 +1,162 @@
+---
+name: PandaDoc Automation
+description: "Automate document workflows with PandaDoc -- create documents from files, manage contacts, organize folders, set up webhooks, create templates, and track document status through the Composio PandaDoc integration."
+requires:
+ mcp:
+ - rube
+---
+
+# PandaDoc Automation
+
+Manage **PandaDoc** document workflows directly from Claude Code. Create documents from uploaded files, manage recipients and contacts, organize with folders, set up event webhooks, create templates, and track document status without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/pandadoc](https://composio.dev/toolkits/pandadoc)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your PandaDoc account when prompted. The agent will provide an OAuth link to authenticate.
+3. Ensure your PandaDoc workspace has the appropriate plan for the features you need (e.g., e-signatures, templates, webhooks).
+
+---
+
+## Core Workflows
+
+### 1. Create a Document from File
+
+Upload a PDF, DOCX, or RTF file to create a new PandaDoc document with designated recipients for signing and tracking.
+
+**Tool:** `PANDADOC_CREATE_DOCUMENT_FROM_FILE`
+
+Key parameters:
+- `name` (required) -- document name
+- `recipients` (required) -- array of recipient objects, each with:
+ - `email` (required) -- recipient email
+ - `first_name`, `last_name` -- recipient name
+ - `role` -- `signer` (default), `approver`, or `cc` (must be unique per recipient)
+ - `signing_order` -- numeric order (if set for one, must be set for all)
+- `file` -- uploaded file object with `name`, `mimetype`, and `s3key`
+- `url` -- alternatively, a public HTTPS URL to the file
+- `parse_form_fields` (default false) -- parse PDF form fields
+- `tags` -- array of strings for categorization
+- `owner` -- document owner (email or membership_id)
+
+Example prompt: *"Create a PandaDoc document from contract.pdf with john@example.com as signer and jane@example.com as approver"*
+
+---
+
+### 2. Get Document Details
+
+Fetch comprehensive metadata for a document including recipients, fields, tokens, pricing, tags, and content-block references.
+
+**Tool:** `PANDADOC_GET_DOCUMENT_DETAILS`
+
+Key parameters:
+- `id` (required) -- the unique document identifier (e.g., `BhVzRcxH9Z2LgfPPGXFUqa`)
+
+Use this to check document status, inspect recipient completion, review field values, or gather metadata for reporting.
+
+Example prompt: *"Get the full details and status for PandaDoc document BhVzRcxH9Z2LgfPPGXFUqa"*
+
+---
+
+### 3. Manage Contacts
+
+Create new contacts or update existing ones in PandaDoc. Contacts are matched by email -- if a contact with the given email exists, it gets updated; otherwise, a new one is created.
+
+**Tool:** `PANDADOC_CREATE_OR_UPDATE_CONTACT`
+
+Key parameters:
+- `email` (required) -- contact email address
+- `first_name`, `last_name` -- contact name
+- `company` -- company name
+- `job_title` -- role/title
+- `phone` -- phone number
+- `street_address`, `city`, `state`, `postal_code`, `country` -- address fields
+
+Example prompt: *"Create a PandaDoc contact for john.doe@example.com at Acme Corp as Software Engineer"*
+
+---
+
+### 4. Organize with Folders
+
+Create folders and move documents to organize your PandaDoc workspace.
+
+**Tools:** `PANDADOC_CREATE_FOLDER`, `PANDADOC_LIST_DOCUMENT_FOLDERS`, `PANDADOC_MOVE_DOCUMENT_TO_FOLDER`
+
+For creating folders:
+- `name` (required) -- folder name
+- `parent_uuid` -- parent folder UUID for nested structures
+
+Example prompt: *"Create a 'Q1 2026 Contracts' folder in PandaDoc and move document BhVzRcxH9Z to it"*
+
+---
+
+### 5. Set Up Webhooks
+
+Create webhook subscriptions to receive real-time notifications when document events occur.
+
+**Tool:** `PANDADOC_CREATE_WEBHOOK`
+
+Key parameters:
+- `name` (required) -- descriptive name for the webhook
+- `url` (required) -- endpoint URL for notifications
+- `triggers` (required) -- event types: `document_state_changed`, `recipient_completed`, `document_updated`, etc.
+- `active` (default true) -- enable/disable the webhook
+- `payload` -- additional data to include: `fields`, `products`, `metadata`, `tokens`, `pricing`
+
+Example prompt: *"Set up a PandaDoc webhook to notify https://api.example.com/hooks when documents change state or recipients complete"*
+
+---
+
+### 6. Create Templates
+
+Create reusable templates from PDF files or from scratch with structured content blocks.
+
+**Tool:** `PANDADOC_CREATE_TEMPLATE`
+
+Key parameters:
+- `name` (required) -- template name
+- `file_path` -- path to PDF file for template creation
+- `content` -- structured content object with `title` and `blocks` array for building from scratch
+- `description` -- template description
+- `tags` -- categorization tags
+
+Example prompt: *"Create a PandaDoc template called 'Standard NDA' from the nda-template.pdf file"*
+
+---
+
+## Known Pitfalls
+
+- **Unique recipient roles:** PandaDoc API does not allow duplicate roles within a single document. Each recipient must have a unique `role` value (e.g., `signer`, `signer_2`, `approver`, `cc`).
+- **Signing order consistency:** If you specify `signing_order` for any recipient, you must specify it for ALL recipients in the document. Partial ordering will cause errors.
+- **File upload requirements:** Either `file` (with `s3key`) or `url` must be provided for document creation, not both. The URL must be publicly accessible HTTPS.
+- **Contact upsert behavior:** `PANDADOC_CREATE_OR_UPDATE_CONTACT` matches by email. If you need to update a contact's email itself, you must create a new contact and handle the old one separately.
+- **Document ID format:** Document IDs are alphanumeric strings (e.g., `BhVzRcxH9Z2LgfPPGXFUqa`). They are returned when documents are created and can be found via the PandaDoc dashboard.
+- **Webhook event naming:** Trigger event names must match exactly (e.g., `document_state_changed`, not `stateChanged` or `state_changed`). Check PandaDoc API docs for the complete list.
+- **Folder operations require UUIDs:** Moving documents requires both the document ID and the destination folder UUID. List folders first to get the correct UUID.
+- **Template content blocks:** When creating templates from scratch, the `blocks` array must contain valid content block objects per PandaDoc's schema. Check their API documentation for supported block types.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `PANDADOC_CREATE_DOCUMENT_FROM_FILE` | Create a document from PDF/DOCX/RTF with recipients |
+| `PANDADOC_GET_DOCUMENT_DETAILS` | Get full document metadata, status, and fields |
+| `PANDADOC_CREATE_OR_UPDATE_CONTACT` | Create or update a contact by email |
+| `PANDADOC_CREATE_FOLDER` | Create a folder for document organization |
+| `PANDADOC_LIST_DOCUMENT_FOLDERS` | List all document folders |
+| `PANDADOC_MOVE_DOCUMENT_TO_FOLDER` | Move a document to a specific folder |
+| `PANDADOC_CREATE_WEBHOOK` | Set up event notification webhooks |
+| `PANDADOC_CREATE_TEMPLATE` | Create a reusable document template |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/paradym-automation/SKILL.md b/plugins/awesome-claude-skills/paradym-automation/SKILL.md
new file mode 100644
index 0000000..b96b715
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/parallel-automation/SKILL.md b/plugins/awesome-claude-skills/parallel-automation/SKILL.md
new file mode 100644
index 0000000..6182042
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/parma-automation/SKILL.md b/plugins/awesome-claude-skills/parma-automation/SKILL.md
new file mode 100644
index 0000000..7632823
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/parsehub-automation/SKILL.md b/plugins/awesome-claude-skills/parsehub-automation/SKILL.md
new file mode 100644
index 0000000..deb4ba7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/parsera-automation/SKILL.md b/plugins/awesome-claude-skills/parsera-automation/SKILL.md
new file mode 100644
index 0000000..fde0982
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/parseur-automation/SKILL.md b/plugins/awesome-claude-skills/parseur-automation/SKILL.md
new file mode 100644
index 0000000..f49927e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/passcreator-automation/SKILL.md b/plugins/awesome-claude-skills/passcreator-automation/SKILL.md
new file mode 100644
index 0000000..d7a17cb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/passslot-automation/SKILL.md b/plugins/awesome-claude-skills/passslot-automation/SKILL.md
new file mode 100644
index 0000000..1bdab27
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/payhip-automation/SKILL.md b/plugins/awesome-claude-skills/payhip-automation/SKILL.md
new file mode 100644
index 0000000..99789f6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pdf-api-io-automation/SKILL.md b/plugins/awesome-claude-skills/pdf-api-io-automation/SKILL.md
new file mode 100644
index 0000000..64a7b7d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pdf-co-automation/SKILL.md b/plugins/awesome-claude-skills/pdf-co-automation/SKILL.md
new file mode 100644
index 0000000..027462b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pdf4me-automation/SKILL.md b/plugins/awesome-claude-skills/pdf4me-automation/SKILL.md
new file mode 100644
index 0000000..75d6b89
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pdfless-automation/SKILL.md b/plugins/awesome-claude-skills/pdfless-automation/SKILL.md
new file mode 100644
index 0000000..a8ae20b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pdfmonkey-automation/SKILL.md b/plugins/awesome-claude-skills/pdfmonkey-automation/SKILL.md
new file mode 100644
index 0000000..22cd4bd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/peopledatalabs-automation/SKILL.md b/plugins/awesome-claude-skills/peopledatalabs-automation/SKILL.md
new file mode 100644
index 0000000..b6247bb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/perigon-automation/SKILL.md b/plugins/awesome-claude-skills/perigon-automation/SKILL.md
new file mode 100644
index 0000000..b041451
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/perplexityai-automation/SKILL.md b/plugins/awesome-claude-skills/perplexityai-automation/SKILL.md
new file mode 100644
index 0000000..ecb290a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/persistiq-automation/SKILL.md b/plugins/awesome-claude-skills/persistiq-automation/SKILL.md
new file mode 100644
index 0000000..1760298
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pexels-automation/SKILL.md b/plugins/awesome-claude-skills/pexels-automation/SKILL.md
new file mode 100644
index 0000000..9826635
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/phantombuster-automation/SKILL.md b/plugins/awesome-claude-skills/phantombuster-automation/SKILL.md
new file mode 100644
index 0000000..8a06069
--- /dev/null
+++ b/plugins/awesome-claude-skills/phantombuster-automation/SKILL.md
@@ -0,0 +1,128 @@
+---
+name: PhantomBuster Automation
+description: "Automate lead generation, web scraping, and social media data extraction workflows through PhantomBuster's cloud platform via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# PhantomBuster Automation
+
+Automate cloud-based data extraction and lead generation -- manage agents and scripts, monitor organization resources and usage, track container execution, and solve captcha challenges -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/phantombuster](https://composio.dev/toolkits/phantombuster)
+
+---
+
+## Setup
+
+1. Connect your PhantomBuster account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `PHANTOMBUSTER_*` tools become available for execution
+
+---
+
+## Core Workflows
+
+### 1. List All Agents
+Fetch every agent associated with your account or organization to inventory automation workflows.
+
+**Tool:** `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL`
+
+```
+No parameters required -- returns all agents with IDs and metadata.
+Authenticate your API key first.
+```
+
+Use agent IDs from this response when fetching containers or monitoring specific automations.
+
+---
+
+### 2. List All Scripts
+Retrieve all scripts available under your account (without code bodies) for script management.
+
+**Tool:** `PHANTOMBUSTER_GET_SCRIPTS_FETCH_ALL`
+
+```
+No parameters required -- returns script metadata without source code.
+```
+
+---
+
+### 3. Monitor Organization Resources & Quotas
+Check your organization's current resource usage and quota limits to plan automation capacity.
+
+**Tool:** `PHANTOMBUSTER_GET_ORGS_FETCH_RESOURCES`
+
+```
+No parameters required -- returns resource allocation and current usage metrics.
+```
+
+---
+
+### 4. Retrieve Agent Containers
+Fetch all execution containers for a specific agent to monitor run history and status.
+
+**Tool:** `PHANTOMBUSTER_GET_CONTAINERS_FETCH_ALL`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `agentId` | string | Yes | Agent ID from `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL` |
+
+---
+
+### 5. Export Agent Usage Report
+Download a CSV report of all agents' run statistics for your organization.
+
+**Tool:** `PHANTOMBUSTER_GET_ORGS_EXPORT_AGENT_USAGE`
+
+```
+Returns a downloadable CSV with comprehensive agent execution statistics.
+```
+
+---
+
+### 6. Solve hCaptcha Challenges
+Obtain a valid hCaptcha token for automated form submissions or scraping flows that require captcha solving.
+
+**Tool:** `PHANTOMBUSTER_POST_HCAPTCHA`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `siteKey` | string | Yes | Public site key of the hCaptcha widget |
+| `pageUrl` | string | Yes | Full URL of the page with the captcha |
+| `proxy` | string | No | Proxy URL (e.g., `http://user:pass@host:port`) |
+| `userAgent` | string | No | Custom User-Agent string to simulate |
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **Agent ID required for containers** | `PHANTOMBUSTER_GET_CONTAINERS_FETCH_ALL` requires a valid `agentId` -- always resolve it first via `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL` |
+| **API key authentication** | All PhantomBuster tools require a valid API key connection -- verify authentication before calling any tools |
+| **Script bodies not included** | `PHANTOMBUSTER_GET_SCRIPTS_FETCH_ALL` returns metadata only, not source code |
+| **Organization scope** | Resource and usage tools operate at the organization level tied to your API key -- ensure the correct org is targeted |
+| **Branch operations** | `PHANTOMBUSTER_GET_BRANCHES_FETCH_ALL` and `PHANTOMBUSTER_GET_BRANCHES_DIFF` are for advanced script versioning -- use them to assess staging vs. release changes before deployment |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `PHANTOMBUSTER_GET_AGENTS_FETCH_ALL` | List all agents in your account |
+| `PHANTOMBUSTER_GET_SCRIPTS_FETCH_ALL` | List all scripts (metadata only) |
+| `PHANTOMBUSTER_GET_ORGS_FETCH_RESOURCES` | Check organization resource usage and quotas |
+| `PHANTOMBUSTER_GET_CONTAINERS_FETCH_ALL` | Get all containers for a specific agent |
+| `PHANTOMBUSTER_GET_ORGS_EXPORT_AGENT_USAGE` | Export agent usage as CSV |
+| `PHANTOMBUSTER_POST_HCAPTCHA` | Solve hCaptcha challenges for automation |
+| `PHANTOMBUSTER_GET_ORGS_FETCH` | Fetch organization details |
+| `PHANTOMBUSTER_GET_ORGS_FETCH_AGENT_GROUPS` | Get agent groups and ordering |
+| `PHANTOMBUSTER_GET_BRANCHES_FETCH_ALL` | List all script branches |
+| `PHANTOMBUSTER_GET_BRANCHES_DIFF` | Compare staging vs. release branches |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/piggy-automation/SKILL.md b/plugins/awesome-claude-skills/piggy-automation/SKILL.md
new file mode 100644
index 0000000..bcbd872
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/piloterr-automation/SKILL.md b/plugins/awesome-claude-skills/piloterr-automation/SKILL.md
new file mode 100644
index 0000000..159191d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pilvio-automation/SKILL.md b/plugins/awesome-claude-skills/pilvio-automation/SKILL.md
new file mode 100644
index 0000000..a4e9cbb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pingdom-automation/SKILL.md b/plugins/awesome-claude-skills/pingdom-automation/SKILL.md
new file mode 100644
index 0000000..62bc17f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pipedrive-automation/SKILL.md b/plugins/awesome-claude-skills/pipedrive-automation/SKILL.md
new file mode 100644
index 0000000..643c060
--- /dev/null
+++ b/plugins/awesome-claude-skills/pipedrive-automation/SKILL.md
@@ -0,0 +1,229 @@
+---
+name: pipedrive-automation
+description: Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Pipedrive Automation via Rube MCP
+
+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)
+- Active Pipedrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`
+3. If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Deals
+
+**When to use**: User wants to create a new deal, update an existing deal, or review deal details in the sales pipeline.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Find existing org to link to the deal [Optional]
+2. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create organization if none found [Optional]
+3. `PIPEDRIVE_SEARCH_PERSONS` - Find existing contact to link [Optional]
+4. `PIPEDRIVE_ADD_A_PERSON` - Create contact if none found [Optional]
+5. `PIPEDRIVE_GET_ALL_PIPELINES` - Resolve pipeline ID [Prerequisite]
+6. `PIPEDRIVE_GET_ALL_STAGES` - Resolve stage ID within the pipeline [Prerequisite]
+7. `PIPEDRIVE_ADD_A_DEAL` - Create the deal with title, value, org_id, person_id, stage_id [Required]
+8. `PIPEDRIVE_UPDATE_A_DEAL` - Modify deal properties after creation [Optional]
+9. `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` - Attach line items/products [Optional]
+
+**Key parameters**:
+- `title`: Deal title (required for creation)
+- `value`: Monetary value of the deal
+- `currency`: 3-letter ISO currency code (e.g., "USD")
+- `pipeline_id` / `stage_id`: Numeric IDs for pipeline placement
+- `org_id` / `person_id`: Link to organization and contact
+- `status`: "open", "won", or "lost"
+- `expected_close_date`: Format YYYY-MM-DD
+
+**Pitfalls**:
+- `title` is the only required field for `PIPEDRIVE_ADD_A_DEAL`; all others are optional
+- Custom fields appear as long hash keys in responses; use dealFields endpoint to map them
+- `PIPEDRIVE_UPDATE_A_DEAL` requires the numeric `id` of the deal
+- Setting `status` to "lost" requires also providing `lost_reason`
+
+### 2. Manage Contacts (Persons and Organizations)
+
+**When to use**: User wants to create, update, search, or list contacts and companies in Pipedrive.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` - Search for existing person by name, email, or phone [Prerequisite]
+2. `PIPEDRIVE_ADD_A_PERSON` - Create new contact if not found [Required]
+3. `PIPEDRIVE_UPDATE_A_PERSON` - Modify existing contact details [Optional]
+4. `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` - Retrieve full contact record [Optional]
+5. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Search for existing organization [Prerequisite]
+6. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create new organization if not found [Required]
+7. `PIPEDRIVE_UPDATE_AN_ORGANIZATION` - Modify organization properties [Optional]
+8. `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` - Retrieve full org record [Optional]
+
+**Key parameters**:
+- `name`: Required for both person and organization creation
+- `email`: Array of objects with `value`, `label`, `primary` fields for persons
+- `phone`: Array of objects with `value`, `label`, `primary` fields for persons
+- `org_id`: Link a person to an organization
+- `visible_to`: 1 = owner only, 3 = entire company
+- `term`: Search term for SEARCH_PERSONS / SEARCH_ORGANIZATIONS (minimum 2 characters)
+
+**Pitfalls**:
+- `PIPEDRIVE_ADD_AN_ORGANIZATION` may auto-merge with an existing org; check `response.additional_data.didMerge`
+- Email and phone fields are arrays of objects, not plain strings: `[{"value": "test@example.com", "label": "work", "primary": true}]`
+- `PIPEDRIVE_SEARCH_PERSONS` wildcards like `*` or `@` are NOT supported; use `PIPEDRIVE_GET_ALL_PERSONS` to list all
+- Deletion via `PIPEDRIVE_DELETE_A_PERSON` or `PIPEDRIVE_DELETE_AN_ORGANIZATION` is soft-delete with 30-day retention, then permanent
+
+### 3. Schedule and Track Activities
+
+**When to use**: User wants to create calls, meetings, tasks, or other activities linked to deals, contacts, or organizations.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve linked entity IDs [Prerequisite]
+2. `PIPEDRIVE_ADD_AN_ACTIVITY` - Create the activity with subject, type, due date [Required]
+3. `PIPEDRIVE_UPDATE_AN_ACTIVITY` - Modify activity details or mark as done [Optional]
+4. `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` - Retrieve activity record [Optional]
+5. `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` - List user's activities [Optional]
+
+**Key parameters**:
+- `subject`: Activity title (required)
+- `type`: Activity type key string, e.g., "call", "meeting", "task", "email" (required)
+- `due_date`: Format YYYY-MM-DD
+- `due_time`: Format HH:MM
+- `duration`: Format HH:MM (e.g., "00:30" for 30 minutes)
+- `deal_id` / `person_id` / `org_id`: Link to related entities
+- `done`: 0 = not done, 1 = done
+
+**Pitfalls**:
+- Both `subject` and `type` are required for `PIPEDRIVE_ADD_AN_ACTIVITY`
+- `type` must match an existing ActivityTypes key_string in the account
+- `done` is an integer (0 or 1), not a boolean
+- Response includes `more_activities_scheduled_in_context` in additional_data
+
+### 4. Add and Manage Notes
+
+**When to use**: User wants to attach notes to deals, persons, organizations, leads, or projects.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve entity ID [Prerequisite]
+2. `PIPEDRIVE_ADD_A_NOTE` - Create note with HTML content linked to an entity [Required]
+3. `PIPEDRIVE_UPDATE_A_NOTE` - Modify note content [Optional]
+4. `PIPEDRIVE_GET_ALL_NOTES` - List notes filtered by entity [Optional]
+5. `PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE` - Retrieve comments on a note [Optional]
+
+**Key parameters**:
+- `content`: Note body in HTML format (required)
+- `deal_id` / `person_id` / `org_id` / `lead_id` / `project_id`: At least one entity link required
+- `pinned_to_deal_flag` / `pinned_to_person_flag`: Filter pinned notes when listing
+
+**Pitfalls**:
+- `content` is required and supports HTML; plain text works but is sanitized server-side
+- At least one of `deal_id`, `person_id`, `org_id`, `lead_id`, or `project_id` must be provided
+- `PIPEDRIVE_GET_ALL_NOTES` returns notes across all entities by default; filter with entity ID params
+
+### 5. Query Pipelines and Stages
+
+**When to use**: User wants to view sales pipelines, stages, or deals within a pipeline/stage.
+
+**Tool sequence**:
+1. `PIPEDRIVE_GET_ALL_PIPELINES` - List all pipelines and their IDs [Required]
+2. `PIPEDRIVE_GET_ONE_PIPELINE` - Get details and deal summary for a specific pipeline [Optional]
+3. `PIPEDRIVE_GET_ALL_STAGES` - List all stages, optionally filtered by pipeline [Required]
+4. `PIPEDRIVE_GET_ONE_STAGE` - Get details for a specific stage [Optional]
+5. `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` - List all deals across stages in a pipeline [Optional]
+6. `PIPEDRIVE_GET_DEALS_IN_A_STAGE` - List deals in a specific stage [Optional]
+
+**Key parameters**:
+- `id`: Pipeline or stage ID (required for single-item endpoints)
+- `pipeline_id`: Filter stages by pipeline
+- `totals_convert_currency`: 3-letter currency code or "default_currency" for converted totals
+- `get_summary`: Set to 1 for deal summary in pipeline responses
+
+**Pitfalls**:
+- `PIPEDRIVE_GET_ALL_PIPELINES` takes no parameters; returns all pipelines
+- `PIPEDRIVE_GET_ALL_STAGES` returns stages for ALL pipelines unless `pipeline_id` is specified
+- Deal counts in pipeline summaries use `per_stages_converted` only when `totals_convert_currency` is set
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to numeric IDs before operations:
+- **Organization name -> org_id**: `PIPEDRIVE_SEARCH_ORGANIZATIONS` with `term` param
+- **Person name -> person_id**: `PIPEDRIVE_SEARCH_PERSONS` with `term` param
+- **Pipeline name -> pipeline_id**: `PIPEDRIVE_GET_ALL_PIPELINES` then match by name
+- **Stage name -> stage_id**: `PIPEDRIVE_GET_ALL_STAGES` with `pipeline_id` then match by name
+
+### Pagination
+Most list endpoints use offset-based pagination:
+- Use `start` (offset) and `limit` (page size) parameters
+- Check `additional_data.pagination.more_items_in_collection` to know if more pages exist
+- Use `additional_data.pagination.next_start` as the `start` value for the next page
+- Default limit is ~500 for some endpoints; set explicitly for predictable paging
+
+## Known Pitfalls
+
+### ID Formats
+- All entity IDs (deal, person, org, activity, pipeline, stage) are numeric integers
+- Lead IDs are UUID strings, not integers
+- Custom field keys are long alphanumeric hashes (e.g., "a1b2c3d4e5f6...")
+
+### Rate Limits
+- Pipedrive enforces per-company API rate limits; bulk operations should be paced
+- `PIPEDRIVE_GET_ALL_PERSONS` and `PIPEDRIVE_GET_ALL_ORGANIZATIONS` can return large datasets; always paginate
+
+### Parameter Quirks
+- Email and phone on persons are arrays of objects, not plain strings
+- `visible_to` is numeric: 1 = owner only, 3 = entire company, 5 = specific groups
+- `done` on activities is integer 0/1, not boolean true/false
+- Organization creation may auto-merge duplicates silently; check `didMerge` in response
+- `PIPEDRIVE_SEARCH_PERSONS` requires minimum 2 characters and does not support wildcards
+
+### Response Structure
+- Custom fields appear as hash keys in responses; map them via the respective Fields endpoints
+- Responses often nest data under `response.data.data` in wrapped executions
+- Search results are under `response.data.items`, not top-level
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create deal | `PIPEDRIVE_ADD_A_DEAL` | `title`, `value`, `org_id`, `stage_id` |
+| Update deal | `PIPEDRIVE_UPDATE_A_DEAL` | `id`, `status`, `value`, `stage_id` |
+| Get deal details | `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` | `id` |
+| Search persons | `PIPEDRIVE_SEARCH_PERSONS` | `term`, `fields` |
+| Add person | `PIPEDRIVE_ADD_A_PERSON` | `name`, `email`, `phone`, `org_id` |
+| Update person | `PIPEDRIVE_UPDATE_A_PERSON` | `id`, `name`, `email` |
+| Get person details | `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` | `id` |
+| List all persons | `PIPEDRIVE_GET_ALL_PERSONS` | `start`, `limit`, `filter_id` |
+| Search organizations | `PIPEDRIVE_SEARCH_ORGANIZATIONS` | `term`, `fields` |
+| Add organization | `PIPEDRIVE_ADD_AN_ORGANIZATION` | `name`, `visible_to` |
+| Update organization | `PIPEDRIVE_UPDATE_AN_ORGANIZATION` | `id`, `name`, `address` |
+| Get org details | `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` | `id` |
+| Add activity | `PIPEDRIVE_ADD_AN_ACTIVITY` | `subject`, `type`, `due_date`, `deal_id` |
+| Update activity | `PIPEDRIVE_UPDATE_AN_ACTIVITY` | `id`, `done`, `due_date` |
+| Get activity details | `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` | `id` |
+| List user activities | `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` | `user_id`, `start`, `limit` |
+| Add note | `PIPEDRIVE_ADD_A_NOTE` | `content`, `deal_id` or `person_id` |
+| List notes | `PIPEDRIVE_GET_ALL_NOTES` | `deal_id`, `person_id`, `start`, `limit` |
+| List pipelines | `PIPEDRIVE_GET_ALL_PIPELINES` | (none) |
+| Get pipeline details | `PIPEDRIVE_GET_ONE_PIPELINE` | `id` |
+| List stages | `PIPEDRIVE_GET_ALL_STAGES` | `pipeline_id` |
+| 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/plugins/awesome-claude-skills/pipeline-crm-automation/SKILL.md b/plugins/awesome-claude-skills/pipeline-crm-automation/SKILL.md
new file mode 100644
index 0000000..5961b16
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/placekey-automation/SKILL.md b/plugins/awesome-claude-skills/placekey-automation/SKILL.md
new file mode 100644
index 0000000..824385e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/placid-automation/SKILL.md b/plugins/awesome-claude-skills/placid-automation/SKILL.md
new file mode 100644
index 0000000..6620147
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/plain-automation/SKILL.md b/plugins/awesome-claude-skills/plain-automation/SKILL.md
new file mode 100644
index 0000000..8f68543
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/plasmic-automation/SKILL.md b/plugins/awesome-claude-skills/plasmic-automation/SKILL.md
new file mode 100644
index 0000000..4928626
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/platerecognizer-automation/SKILL.md b/plugins/awesome-claude-skills/platerecognizer-automation/SKILL.md
new file mode 100644
index 0000000..fdc9636
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/plisio-automation/SKILL.md b/plugins/awesome-claude-skills/plisio-automation/SKILL.md
new file mode 100644
index 0000000..582fb1e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/polygon-automation/SKILL.md b/plugins/awesome-claude-skills/polygon-automation/SKILL.md
new file mode 100644
index 0000000..c2e8195
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/polygon-io-automation/SKILL.md b/plugins/awesome-claude-skills/polygon-io-automation/SKILL.md
new file mode 100644
index 0000000..7681dd5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/poptin-automation/SKILL.md b/plugins/awesome-claude-skills/poptin-automation/SKILL.md
new file mode 100644
index 0000000..7a7cd35
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/postgrid-automation/SKILL.md b/plugins/awesome-claude-skills/postgrid-automation/SKILL.md
new file mode 100644
index 0000000..4ea98e3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/postgrid-verify-automation/SKILL.md b/plugins/awesome-claude-skills/postgrid-verify-automation/SKILL.md
new file mode 100644
index 0000000..1ef88fd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/posthog-automation/SKILL.md b/plugins/awesome-claude-skills/posthog-automation/SKILL.md
new file mode 100644
index 0000000..34b3fa2
--- /dev/null
+++ b/plugins/awesome-claude-skills/posthog-automation/SKILL.md
@@ -0,0 +1,229 @@
+---
+name: posthog-automation
+description: "Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# PostHog Automation via Rube MCP
+
+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)
+- Active PostHog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `posthog`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `posthog`
+3. If connection is not ACTIVE, follow the returned auth link to complete PostHog authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Capture Events
+
+**When to use**: User wants to send event data to PostHog for analytics tracking
+
+**Tool sequence**:
+1. `POSTHOG_CAPTURE_EVENT` - Send one or more events to PostHog [Required]
+
+**Key parameters**:
+- `event`: Event name (e.g., '$pageview', 'user_signed_up', 'purchase_completed')
+- `distinct_id`: Unique user identifier (required)
+- `properties`: Object with event-specific properties
+- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)
+
+**Pitfalls**:
+- `distinct_id` is required for every event; identifies the user/device
+- PostHog system events use `$` prefix (e.g., '$pageview', '$identify')
+- Custom events should NOT use the `$` prefix
+- Properties are freeform; maintain consistent schemas across events
+- Events are processed asynchronously; ingestion delay is typically seconds
+
+### 2. List and Filter Events
+
+**When to use**: User wants to browse or search through captured events
+
+**Tool sequence**:
+1. `POSTHOG_LIST_AND_FILTER_PROJECT_EVENTS` - Query events with filters [Required]
+
+**Key parameters**:
+- `project_id`: PostHog project ID (required)
+- `event`: Filter by event name
+- `person_id`: Filter by person ID
+- `after`: Events after this ISO 8601 timestamp
+- `before`: Events before this ISO 8601 timestamp
+- `limit`: Maximum events to return
+- `offset`: Pagination offset
+
+**Pitfalls**:
+- `project_id` is required; resolve via LIST_PROJECTS first
+- Date filters use ISO 8601 format (e.g., '2024-01-15T00:00:00Z')
+- Large event volumes require pagination; use `offset` and `limit`
+- Results are returned in reverse chronological order by default
+- Event properties are nested; parse carefully
+
+### 3. Manage Feature Flags
+
+**When to use**: User wants to create, view, or manage feature flags
+
+**Tool sequence**:
+1. `POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS` - List existing feature flags [Required]
+2. `POSTHOG_RETRIEVE_FEATURE_FLAG_DETAILS` - Get detailed flag configuration [Optional]
+3. `POSTHOG_CREATE_FEATURE_FLAGS_FOR_PROJECT` - Create a new feature flag [Optional]
+
+**Key parameters**:
+- For listing: `project_id` (required)
+- For details: `project_id`, `id` (feature flag ID)
+- For creation:
+ - `project_id`: Target project
+ - `key`: Flag key (e.g., 'new-dashboard-beta')
+ - `name`: Human-readable name
+ - `filters`: Targeting rules and rollout percentage
+ - `active`: Whether the flag is enabled
+
+**Pitfalls**:
+- Feature flag `key` must be unique within a project
+- Flag keys should use kebab-case (e.g., 'my-feature-flag')
+- `filters` define targeting groups with properties and rollout percentages
+- Creating a flag with `active: true` immediately enables it for matching users
+- Flag changes take effect within seconds due to PostHog's polling mechanism
+
+### 4. Manage Projects
+
+**When to use**: User wants to list or inspect PostHog projects and organizations
+
+**Tool sequence**:
+1. `POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION` - List all projects [Required]
+
+**Key parameters**:
+- `organization_id`: Organization identifier (may be optional depending on auth)
+- `limit`: Number of results per page
+- `offset`: Pagination offset
+
+**Pitfalls**:
+- Project IDs are numeric; used as parameters in most other endpoints
+- Organization ID may be required; check your PostHog setup
+- Pagination is offset-based; iterate until results are empty
+- Project settings include API keys and configuration details
+
+### 5. User Profile and Authentication
+
+**When to use**: User wants to check current user details or verify API access
+
+**Tool sequence**:
+1. `POSTHOG_WHOAMI` - Get current API user information [Optional]
+2. `POSTHOG_RETRIEVE_CURRENT_USER_PROFILE` - Get detailed user profile [Optional]
+
+**Key parameters**:
+- No required parameters for either call
+- Returns current authenticated user's details, permissions, and organization info
+
+**Pitfalls**:
+- WHOAMI is a lightweight check; use for verifying API connectivity
+- User profile includes organization membership and permissions
+- These endpoints confirm the API key's access level and scope
+
+## Common Patterns
+
+### ID Resolution
+
+**Organization -> Project ID**:
+```
+1. Call POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION
+2. Find project by name in results
+3. Extract id (numeric) for use in other endpoints
+```
+
+**Feature flag name -> Flag ID**:
+```
+1. Call POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS with project_id
+2. Find flag by key or name
+3. Extract id for detailed operations
+```
+
+### Feature Flag Targeting
+
+Feature flags support sophisticated targeting:
+```json
+{
+ "filters": {
+ "groups": [
+ {
+ "properties": [
+ {"key": "email", "value": "@company.com", "operator": "icontains"}
+ ],
+ "rollout_percentage": 100
+ },
+ {
+ "properties": [],
+ "rollout_percentage": 10
+ }
+ ]
+ }
+}
+```
+- Groups are evaluated in order; first matching group determines the rollout
+- Properties filter users by their traits
+- Rollout percentage determines what fraction of matching users see the flag
+
+### Pagination
+
+- Events: Use `offset` and `limit` (offset-based)
+- Feature flags: Use `offset` and `limit` (offset-based)
+- Projects: Use `offset` and `limit` (offset-based)
+- Continue until results array is empty or smaller than `limit`
+
+## Known Pitfalls
+
+**Project IDs**:
+- Required for most API endpoints
+- Always resolve project names to numeric IDs first
+- Multiple projects can exist in one organization
+
+**Event Naming**:
+- System events use `$` prefix ($pageview, $identify, $autocapture)
+- Custom events should NOT use `$` prefix
+- Event names are case-sensitive; maintain consistency
+
+**Feature Flags**:
+- Flag keys must be unique within a project
+- Use kebab-case for flag keys
+- Changes propagate within seconds
+- Deleting a flag is permanent; consider disabling instead
+
+**Rate Limits**:
+- Event ingestion has throughput limits
+- Batch events where possible for efficiency
+- API endpoints have per-minute rate limits
+
+**Response Parsing**:
+- Response data may be nested under `data` or `results` key
+- Paginated responses include `count`, `next`, `previous` fields
+- Event properties are nested objects; access carefully
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Capture event | POSTHOG_CAPTURE_EVENT | event, distinct_id, properties |
+| List events | POSTHOG_LIST_AND_FILTER_PROJECT_EVENTS | project_id, event, after, before |
+| List feature flags | POSTHOG_LIST_AND_MANAGE_PROJECT_FEATURE_FLAGS | project_id |
+| Get flag details | POSTHOG_RETRIEVE_FEATURE_FLAG_DETAILS | project_id, id |
+| Create flag | POSTHOG_CREATE_FEATURE_FLAGS_FOR_PROJECT | project_id, key, filters |
+| 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/plugins/awesome-claude-skills/postmark-automation/SKILL.md b/plugins/awesome-claude-skills/postmark-automation/SKILL.md
new file mode 100644
index 0000000..2e2fca5
--- /dev/null
+++ b/plugins/awesome-claude-skills/postmark-automation/SKILL.md
@@ -0,0 +1,192 @@
+---
+name: postmark-automation
+description: "Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Postmark Automation via Rube MCP
+
+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)
+- Active Postmark connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `postmark`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `postmark`
+3. If connection is not ACTIVE, follow the returned auth link to complete Postmark authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Templated Batch Emails
+
+**When to use**: User wants to send templated emails to multiple recipients in one call
+
+**Tool sequence**:
+1. `POSTMARK_LIST_TEMPLATES` - Find available templates and their IDs [Prerequisite]
+2. `POSTMARK_VALIDATE_TEMPLATE` - Validate template with model data before sending [Optional]
+3. `POSTMARK_SEND_BATCH_WITH_TEMPLATES` - Send batch emails using a template [Required]
+
+**Key parameters**:
+- `TemplateId` or `TemplateAlias`: Identifier for the template to use
+- `Messages`: Array of message objects with `From`, `To`, `TemplateModel`
+- `TemplateModel`: Key-value pairs matching template variables
+
+**Pitfalls**:
+- Maximum 500 messages per batch call
+- Either `TemplateId` or `TemplateAlias` is required, not both
+- `TemplateModel` keys must match template variable names exactly (case-sensitive)
+- Sender address must be a verified Sender Signature or from a verified domain
+
+### 2. Manage Email Templates
+
+**When to use**: User wants to create, edit, or inspect email templates
+
+**Tool sequence**:
+1. `POSTMARK_LIST_TEMPLATES` - List all templates with IDs and names [Required]
+2. `POSTMARK_GET_TEMPLATE` - Get full template details including HTML/text body [Optional]
+3. `POSTMARK_EDIT_TEMPLATE` - Update template content or settings [Optional]
+4. `POSTMARK_VALIDATE_TEMPLATE` - Test template rendering with sample data [Optional]
+
+**Key parameters**:
+- `TemplateId`: Numeric template ID for GET/EDIT operations
+- `Name`: Template display name
+- `Subject`: Email subject line (supports template variables)
+- `HtmlBody`: HTML content of the template
+- `TextBody`: Plain text fallback content
+- `TemplateType`: 'Standard' or 'Layout'
+
+**Pitfalls**:
+- Template IDs are numeric integers, not strings
+- Editing a template replaces the entire content; include all fields you want to keep
+- Layout templates wrap Standard templates; changing a layout affects all linked templates
+- Validate before sending to catch missing variables early
+
+### 3. Monitor Delivery Statistics
+
+**When to use**: User wants to check email delivery health, open/click rates, or outbound overview
+
+**Tool sequence**:
+1. `POSTMARK_GET_DELIVERY_STATS` - Get bounce counts by type [Required]
+2. `POSTMARK_GET_OUTBOUND_OVERVIEW` - Get sent/opened/clicked/bounced summary [Required]
+3. `POSTMARK_GET_TRACKED_EMAIL_COUNTS` - Get tracked email volume over time [Optional]
+
+**Key parameters**:
+- `fromdate`: Start date for filtering stats (YYYY-MM-DD)
+- `todate`: End date for filtering stats (YYYY-MM-DD)
+- `tag`: Filter stats by message tag
+- `messagestreamid`: Filter by message stream (e.g., 'outbound', 'broadcast')
+
+**Pitfalls**:
+- Date parameters use YYYY-MM-DD format without time component
+- Stats are aggregated; individual message tracking requires separate API calls
+- `messagestreamid` defaults to all streams if not specified
+
+### 4. Manage Bounces and Complaints
+
+**When to use**: User wants to review bounced emails or spam complaints
+
+**Tool sequence**:
+1. `POSTMARK_GET_BOUNCES` - List bounced messages with details [Required]
+2. `POSTMARK_GET_SPAM_COMPLAINTS` - List spam complaint records [Optional]
+3. `POSTMARK_GET_DELIVERY_STATS` - Get bounce summary counts [Optional]
+
+**Key parameters**:
+- `count`: Number of records to return per page
+- `offset`: Pagination offset for results
+- `type`: Bounce type filter (e.g., 'HardBounce', 'SoftBounce', 'SpamNotification')
+- `fromdate`/`todate`: Date range filters
+- `emailFilter`: Filter by recipient email address
+
+**Pitfalls**:
+- Bounce types include: HardBounce, SoftBounce, SpamNotification, SpamComplaint, Transient, and others
+- Hard bounces indicate permanent delivery failures; these addresses should be removed
+- Spam complaints affect sender reputation; monitor regularly
+- Pagination uses `count` and `offset`, not page tokens
+
+### 5. Configure Server Settings
+
+**When to use**: User wants to view or modify Postmark server configuration
+
+**Tool sequence**:
+1. `POSTMARK_GET_SERVER` - Retrieve current server settings [Required]
+2. `POSTMARK_EDIT_SERVER` - Update server configuration [Optional]
+
+**Key parameters**:
+- `Name`: Server display name
+- `SmtpApiActivated`: Enable/disable SMTP API access
+- `BounceHookUrl`: Webhook URL for bounce notifications
+- `InboundHookUrl`: Webhook URL for inbound email processing
+- `TrackOpens`: Enable/disable open tracking
+- `TrackLinks`: Link tracking mode ('None', 'HtmlAndText', 'HtmlOnly', 'TextOnly')
+
+**Pitfalls**:
+- Server edits affect all messages sent through that server
+- Webhook URLs must be publicly accessible HTTPS endpoints
+- Changing `SmtpApiActivated` affects SMTP relay access immediately
+- Track settings apply to future messages only, not retroactively
+
+## Common Patterns
+
+### Template Variable Resolution
+
+```
+1. Call POSTMARK_GET_TEMPLATE with TemplateId
+2. Inspect HtmlBody/TextBody for {{variable}} placeholders
+3. Build TemplateModel dict with matching keys
+4. Call POSTMARK_VALIDATE_TEMPLATE to verify rendering
+```
+
+### Pagination
+
+- Set `count` for results per page (varies by endpoint)
+- Use `offset` to skip previously fetched results
+- Increment offset by count each page until results returned < count
+- Total records may be returned in response metadata
+
+## Known Pitfalls
+
+**Authentication**:
+- Postmark uses server-level API tokens, not account-level
+- Each server has its own token; ensure correct server context
+- Sender addresses must be verified Sender Signatures or from verified domains
+
+**Rate Limits**:
+- Batch send limited to 500 messages per call
+- API rate limits vary by endpoint; implement backoff on 429 responses
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Template IDs are always numeric integers
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Send batch templated emails | POSTMARK_SEND_BATCH_WITH_TEMPLATES | Messages, TemplateId/TemplateAlias |
+| List templates | POSTMARK_LIST_TEMPLATES | Count, Offset, TemplateType |
+| Get template details | POSTMARK_GET_TEMPLATE | TemplateId |
+| Edit template | POSTMARK_EDIT_TEMPLATE | TemplateId, Name, Subject, HtmlBody |
+| Validate template | POSTMARK_VALIDATE_TEMPLATE | TemplateId, TemplateModel |
+| Delivery stats | POSTMARK_GET_DELIVERY_STATS | (none or date filters) |
+| Outbound overview | POSTMARK_GET_OUTBOUND_OVERVIEW | fromdate, todate, tag |
+| Get bounces | POSTMARK_GET_BOUNCES | count, offset, type, emailFilter |
+| Get spam complaints | POSTMARK_GET_SPAM_COMPLAINTS | count, offset, fromdate, todate |
+| 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/plugins/awesome-claude-skills/precoro-automation/SKILL.md b/plugins/awesome-claude-skills/precoro-automation/SKILL.md
new file mode 100644
index 0000000..0edfb9c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/prerender-automation/SKILL.md b/plugins/awesome-claude-skills/prerender-automation/SKILL.md
new file mode 100644
index 0000000..c6dda58
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/printautopilot-automation/SKILL.md b/plugins/awesome-claude-skills/printautopilot-automation/SKILL.md
new file mode 100644
index 0000000..bf243fa
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/prisma-automation/SKILL.md b/plugins/awesome-claude-skills/prisma-automation/SKILL.md
new file mode 100644
index 0000000..3f9fecc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/prismic-automation/SKILL.md b/plugins/awesome-claude-skills/prismic-automation/SKILL.md
new file mode 100644
index 0000000..de309b5
--- /dev/null
+++ b/plugins/awesome-claude-skills/prismic-automation/SKILL.md
@@ -0,0 +1,150 @@
+---
+name: Prismic Automation
+description: "Automate headless CMS operations in Prismic -- query documents, search content, retrieve custom types, and manage repository refs through the Composio Prismic integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Prismic Automation
+
+Manage your **Prismic** headless CMS directly from Claude Code. Query documents by type, full-text search content, inspect custom types, and work with repository refs for content versioning.
+
+**Toolkit docs:** [composio.dev/toolkits/prismic](https://composio.dev/toolkits/prismic)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your Prismic account when prompted. The agent will provide an authentication link.
+3. Most content queries require a `ref` token. Always start by calling `PRISMIC_REPOSITORY_API_GET_REFS` or `PRISMIC_REPOSITORY_API_GET_INFO` to obtain the master ref.
+
+---
+
+## Core Workflows
+
+### 1. Get Repository Info and Refs
+
+Retrieve comprehensive repository metadata including available refs (content versions), custom types, languages, tags, and bookmarks. This is typically your first API call.
+
+**Tools:** `PRISMIC_REPOSITORY_API_GET_INFO`, `PRISMIC_REPOSITORY_API_GET_REFS`
+
+No parameters required -- these endpoints return the full repository configuration. The `refs` field is critical since refs are required for all content queries.
+
+Example prompt: *"Get my Prismic repository info and the current master ref"*
+
+---
+
+### 2. Query Documents with Predicates
+
+Fetch documents using Prismic's predicate query syntax with full pagination and filtering support.
+
+**Tool:** `PRISMIC_CONTENT_API_QUERY_DOCUMENTS`
+
+Key parameters:
+- `ref` (required) -- content release reference ID (typically the master ref)
+- `q` -- predicate query, e.g., `[[at(document.type, "page")]]`
+- `page` (min 1) and `pageSize` (1-100) -- pagination
+- `lang` -- language code, e.g., `en-us` (default `*` for all)
+- `orderings` -- sort order, e.g., `[my.article.date desc]`
+- `fetch` -- comma-separated fields to fetch, reducing response size
+- `fetchLinks` -- resolve linked document fields inline
+
+Example prompt: *"Query all published blog posts in Prismic, sorted by date descending, in English"*
+
+---
+
+### 3. Fetch Documents by Type
+
+Retrieve all documents of a specific custom type with automatic master ref resolution.
+
+**Tool:** `PRISMIC_GET_DOCUMENTS_BY_TYPE`
+
+Key parameters:
+- `type` (required) -- custom type API ID, e.g., `blog_post`, `article`, `page`
+- `page` (default 1) and `pageSize` (1-100, default 20)
+- `lang` -- language code filter
+- `orderings` -- sort order, e.g., `[my.article.date desc]`
+- `after` -- cursor-based pagination for deep pagination beyond page 50
+
+Example prompt: *"Get all blog_post documents in Prismic, 20 per page"*
+
+---
+
+### 4. Full-Text Search
+
+Search across all text fields in documents for specified terms. Case-insensitive, matches on root words.
+
+**Tool:** `PRISMIC_CONTENT_API_GET_DOCUMENTS_WITH_FULLTEXT_SEARCH`
+
+Key parameters:
+- `q` (required) -- full-text predicate, e.g., `[[fulltext(document, "machine learning")]]`
+- `page`, `pageSize`, `lang`, `orderings` -- same pagination/filtering as other queries
+
+Example prompt: *"Search all Prismic documents for 'machine learning'"*
+
+---
+
+### 5. Get a Single Document by ID
+
+Retrieve a specific document by its unique identifier.
+
+**Tool:** `PRISMIC_GET_DOCUMENT_BY_ID`
+
+Key parameters:
+- `document_id` (required) -- unique document identifier
+- `ref` (required) -- content ref from repository
+- `lang` -- optional language filter
+
+Example prompt: *"Fetch Prismic document Xx2KLhEAAJljVWaA"*
+
+---
+
+### 6. List Custom Types
+
+Discover all custom types (content models) defined in the repository, including their structure definitions.
+
+**Tool:** `PRISMIC_TYPES_API_GET_TYPES`
+
+Key parameters:
+- `limit` -- max number of types to return per page
+- `page` -- page number (1-indexed)
+- `sort` -- sort order, e.g., `name`
+
+Example prompt: *"List all custom types in my Prismic repository"*
+
+---
+
+## Known Pitfalls
+
+- **Ref is required for all content queries:** You must obtain a valid `ref` (typically the master ref) from `PRISMIC_REPOSITORY_API_GET_REFS` or `PRISMIC_REPOSITORY_API_GET_INFO` before querying any documents. Queries without a ref will fail.
+- **Predicate syntax requires double brackets:** Prismic queries use double square brackets: `[[at(document.type, "page")]]`. For multiple predicates, combine them: `[[at(document.type, "blog")][at(document.tags, ["featured"])]]`.
+- **Deep pagination limit:** Standard page-based pagination may fail beyond page 50. For deep pagination, use the `after` parameter with the last document ID from your previous result set.
+- **pageSize cap is 100:** Requesting more than 100 documents per page will be rejected. Use pagination to iterate through larger result sets.
+- **Language filtering:** The default language filter is `*` (all languages). If you need documents in a specific locale, always pass `lang` explicitly (e.g., `en-us`, `fr-fr`).
+- **Integration fields require separate ref:** When using `PRISMIC_CONTENT_API_GET_DOCUMENTS_WITH_INTEGRATION_FIELDS`, you need an `integrationFieldsRef` in addition to the standard content `ref`.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `PRISMIC_REPOSITORY_API_GET_INFO` | Get repository metadata, refs, types, languages |
+| `PRISMIC_REPOSITORY_API_GET_REFS` | List all refs (master + releases) |
+| `PRISMIC_TYPES_API_GET_TYPES` | List all custom types / content models |
+| `PRISMIC_CONTENT_API_QUERY_DOCUMENTS` | Query documents with predicates and pagination |
+| `PRISMIC_GET_DOCUMENTS_BY_TYPE` | Fetch documents filtered by custom type |
+| `PRISMIC_GET_DOCUMENT_BY_ID` | Retrieve a single document by ID |
+| `PRISMIC_CONTENT_API_GET_DOCUMENTS_WITH_FULLTEXT_SEARCH` | Full-text search across all documents |
+| `PRISMIC_CONTENT_API_GET_DOCUMENTS_WITH_PREDICATES` | Filter documents with multiple predicate conditions |
+| `PRISMIC_CONTENT_API_GET_DOCUMENTS_WITH_INTEGRATION_FIELDS` | Fetch documents with integration fields data |
+| `PRISMIC_GET_DOCUMENTS_ORDERED` | Fetch documents sorted by specified fields |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/process-street-automation/SKILL.md b/plugins/awesome-claude-skills/process-street-automation/SKILL.md
new file mode 100644
index 0000000..a5634c8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/procfu-automation/SKILL.md b/plugins/awesome-claude-skills/procfu-automation/SKILL.md
new file mode 100644
index 0000000..0e5e61a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/productboard-automation/SKILL.md b/plugins/awesome-claude-skills/productboard-automation/SKILL.md
new file mode 100644
index 0000000..f49f99e
--- /dev/null
+++ b/plugins/awesome-claude-skills/productboard-automation/SKILL.md
@@ -0,0 +1,157 @@
+---
+name: Productboard Automation
+description: "Automate product management workflows in Productboard -- manage features, notes, objectives, components, and releases through natural language commands."
+requires:
+ mcp:
+ - rube
+---
+
+# Productboard Automation
+
+Automate your Productboard product management operations directly from Claude Code. Create notes from customer feedback, browse features and objectives, link entities, and track releases -- all without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/productboard](https://composio.dev/toolkits/productboard)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your Claude Code config with URL: `https://rube.app/mcp`
+2. When prompted, authenticate your Productboard account through the connection link provided
+3. Start automating your product management workflows with natural language
+
+---
+
+## Core Workflows
+
+### 1. Manage Customer Notes
+
+Create notes from customer feedback and organize them with tags, links, and followers.
+
+**Tools:** `PRODUCTBOARD_CREATE_NOTE`, `PRODUCTBOARD_LIST_NOTES`, `PRODUCTBOARD_ADD_NOTE_TAG`, `PRODUCTBOARD_ADD_NOTE_FOLLOWERS`, `PRODUCTBOARD_CREATE_NOTE_LINK`
+
+```
+Create a note titled "Mobile app crash report" with content from customer feedback, tagged "bug" and linked to feature abc-123
+```
+
+Key parameters for `PRODUCTBOARD_CREATE_NOTE`:
+- `title` (required) and `content` (required) -- note title and body
+- `customer_email` or `user.email` -- attribute to a customer/user
+- `tags` -- array of tag strings for categorization
+- `display_url` -- URL linked from the note title
+- `source` -- origin system with `origin` and `record_id`
+- `company` -- associate with a company
+
+Key parameters for `PRODUCTBOARD_LIST_NOTES`:
+- `createdFrom` / `createdTo` -- ISO 8601 date range
+- `last` -- relative time window (e.g., `"6m"`, `"10d"`, `"24h"`)
+- `term` -- full-text search by title or content
+- `allTags` / `anyTag` -- filter by tags (cannot combine both)
+- `featureId`, `companyId`, `ownerEmail`, `source` -- entity filters
+- `pageLimit` (max 100) / `pageCursor` -- pagination
+
+### 2. Browse and Retrieve Features
+
+List all features/subfeatures and retrieve detailed information.
+
+**Tools:** `PRODUCTBOARD_LIST_FEATURES`, `PRODUCTBOARD_RETRIEVE_FEATURE`
+
+```
+List the first 50 features in Productboard, then get details on feature abc-def-123
+```
+
+- `PRODUCTBOARD_LIST_FEATURES` supports `pageLimit` (default 100) and `pageOffset` for pagination
+- `PRODUCTBOARD_RETRIEVE_FEATURE` requires feature `id` (UUID) to get complete details
+
+### 3. Objectives and Key Results (OKRs)
+
+List objectives, view feature-objective links, and browse key results.
+
+**Tools:** `PRODUCTBOARD_LIST_OBJECTIVES`, `PRODUCTBOARD_LIST_FEATURE_OBJECTIVES`, `PRODUCTBOARD_LIST_KEY_RESULTS`
+
+```
+Show me all in-progress objectives owned by alice@example.com
+```
+
+Key parameters for `PRODUCTBOARD_LIST_OBJECTIVES`:
+- `status.name` -- filter by status (e.g., `"In Progress"`)
+- `owner.email` -- filter by owner email
+- `parent.id` -- filter by parent objective
+- `archived` -- filter by archived state
+
+`PRODUCTBOARD_LIST_FEATURE_OBJECTIVES`:
+- Requires `id` (UUID) of a **top-level feature** (not subfeatures)
+- Supports `pageCursor` for pagination
+
+### 4. Component Management
+
+List product components for organizing features and the product hierarchy.
+
+**Tool:** `PRODUCTBOARD_LIST_COMPONENTS`
+
+```
+List all components in our Productboard workspace
+```
+
+- Supports `page_limit` and `page_offset` for pagination
+- Follow `links.next` for additional pages
+
+### 5. Release Tracking
+
+View feature-release assignments with state and date filters.
+
+**Tool:** `PRODUCTBOARD_LIST_FEATURE_RELEASE_ASSIGNMENTS`
+
+```
+Show all active release assignments for feature abc-123
+```
+
+- Filter by `feature.id`, `release.id`, `release.state` (planned, active, closed)
+- Date range filters: `release.timeframe.endDate.from` and `release.timeframe.endDate.to` (YYYY-MM-DD)
+
+### 6. Link Notes to Features
+
+Connect customer feedback notes to product features for insight aggregation.
+
+**Tool:** `PRODUCTBOARD_CREATE_NOTE_LINK`
+
+```
+Link note 3fa85f64-5717 to feature 1b6c8c76-8f5d for tracking
+```
+
+- Requires `noteId` (UUID) and `entityId` (UUID of feature, component, or product)
+- Use after creating notes to ensure feedback is connected to the right product areas
+
+---
+
+## Known Pitfalls
+
+- **Top-level features only for objectives:** `PRODUCTBOARD_LIST_FEATURE_OBJECTIVES` only works with top-level feature IDs, not subfeature IDs. Use `PRODUCTBOARD_LIST_FEATURES` to identify which features are top-level.
+- **Tag filter exclusivity:** `allTags` and `anyTag` cannot be combined in `PRODUCTBOARD_LIST_NOTES`. Choose one filter strategy per query.
+- **Relative vs. absolute dates:** The `last` parameter (e.g., `"24h"`) cannot be combined with `createdFrom`/`createdTo` in `PRODUCTBOARD_LIST_NOTES`. Use one approach, not both.
+- **Cursor-based pagination:** Follow `links.next` or use `pageCursor` from responses for multi-page results. Offset-based and cursor-based pagination are used on different endpoints -- check each tool.
+- **Note attribution:** Either `user.email` or `customer_email` must be provided in `PRODUCTBOARD_CREATE_NOTE` to attribute feedback. Without it, the note will have no customer association.
+- **UUID formats required:** All entity IDs (features, notes, components) must be valid UUIDs. Passing malformed IDs causes 400 errors.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `PRODUCTBOARD_CREATE_NOTE` | Create a customer feedback note (requires `title`, `content`) |
+| `PRODUCTBOARD_LIST_NOTES` | List notes with search, date, and tag filters |
+| `PRODUCTBOARD_ADD_NOTE_TAG` | Add a tag to a note |
+| `PRODUCTBOARD_ADD_NOTE_FOLLOWERS` | Add followers to a note by email |
+| `PRODUCTBOARD_CREATE_NOTE_LINK` | Link a note to a feature/component (requires `noteId`, `entityId`) |
+| `PRODUCTBOARD_LIST_FEATURES` | List all features with pagination |
+| `PRODUCTBOARD_RETRIEVE_FEATURE` | Get detailed feature info by UUID |
+| `PRODUCTBOARD_LIST_OBJECTIVES` | List objectives with status/owner filters |
+| `PRODUCTBOARD_LIST_FEATURE_OBJECTIVES` | List objectives linked to a top-level feature |
+| `PRODUCTBOARD_LIST_KEY_RESULTS` | List key results for objectives |
+| `PRODUCTBOARD_LIST_COMPONENTS` | List product components with pagination |
+| `PRODUCTBOARD_LIST_FEATURE_RELEASE_ASSIGNMENTS` | List feature-release assignments with filters |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/productlane-automation/SKILL.md b/plugins/awesome-claude-skills/productlane-automation/SKILL.md
new file mode 100644
index 0000000..e36f646
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/project-bubble-automation/SKILL.md b/plugins/awesome-claude-skills/project-bubble-automation/SKILL.md
new file mode 100644
index 0000000..55f93d7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/proofly-automation/SKILL.md b/plugins/awesome-claude-skills/proofly-automation/SKILL.md
new file mode 100644
index 0000000..b6212fb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/proxiedmail-automation/SKILL.md b/plugins/awesome-claude-skills/proxiedmail-automation/SKILL.md
new file mode 100644
index 0000000..8206d2f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pushbullet-automation/SKILL.md b/plugins/awesome-claude-skills/pushbullet-automation/SKILL.md
new file mode 100644
index 0000000..5118f82
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/pushover-automation/SKILL.md b/plugins/awesome-claude-skills/pushover-automation/SKILL.md
new file mode 100644
index 0000000..2d23ad0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/quaderno-automation/SKILL.md b/plugins/awesome-claude-skills/quaderno-automation/SKILL.md
new file mode 100644
index 0000000..bc0b060
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/qualaroo-automation/SKILL.md b/plugins/awesome-claude-skills/qualaroo-automation/SKILL.md
new file mode 100644
index 0000000..1da1ad3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/quickbooks-automation/SKILL.md b/plugins/awesome-claude-skills/quickbooks-automation/SKILL.md
new file mode 100644
index 0000000..845b7c4
--- /dev/null
+++ b/plugins/awesome-claude-skills/quickbooks-automation/SKILL.md
@@ -0,0 +1,160 @@
+---
+name: QuickBooks Automation
+description: "QuickBooks Automation: manage invoices, customers, accounts, and payments in QuickBooks Online for streamlined bookkeeping"
+requires:
+ mcp: [rube]
+---
+
+# QuickBooks Automation
+
+Automate QuickBooks Online operations including creating invoices, managing customers, querying accounts, and listing invoices for financial reporting.
+
+**Toolkit docs:** [composio.dev/toolkits/quickbooks](https://composio.dev/toolkits/quickbooks)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure an active connection exists for the `quickbooks` toolkit. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+---
+
+## Core Workflows
+
+### 1. Create an Invoice
+
+Create a new invoice for a customer with line items.
+
+**Tool:** `QUICKBOOKS_CREATE_INVOICE`
+
+**Key Parameters:**
+- `customer_id` (required) -- ID of the customer (CustomerRef.value)
+- `lines` (required) -- Array of line item objects. Each must include:
+ - `DetailType` -- e.g., `"SalesItemLineDetail"`
+ - `Amount` -- Line item total
+ - `SalesItemLineDetail` -- Object with `ItemRef` containing `value` (item ID)
+- `minorversion` -- Optional API version parameter
+
+**Example:**
+```
+Tool: QUICKBOOKS_CREATE_INVOICE
+Arguments:
+ customer_id: "21"
+ lines: [
+ {
+ "DetailType": "SalesItemLineDetail",
+ "Amount": 150.00,
+ "SalesItemLineDetail": {
+ "ItemRef": {"value": "1", "name": "Services"}
+ }
+ }
+ ]
+```
+
+**Prerequisites:** Resolve the customer ID using `QUICKBOOKS_READ_CUSTOMER` or create one with `QUICKBOOKS_CREATE_CUSTOMER`. Resolve item/account IDs using `QUICKBOOKS_QUERY_ACCOUNT`.
+
+---
+
+### 2. Manage Customers
+
+Create and read customer records.
+
+**Tools:**
+- `QUICKBOOKS_CREATE_CUSTOMER` -- Create a new customer
+- `QUICKBOOKS_READ_CUSTOMER` -- Read a customer by ID
+
+**Key Parameters for `QUICKBOOKS_CREATE_CUSTOMER`:**
+- `display_name` -- Display name (must be unique across customers, vendors, employees; max 500 chars)
+- `given_name` -- First name (max 100 chars)
+- `family_name` -- Last name (max 100 chars)
+- `middle_name` -- Middle name (max 100 chars)
+- `title` -- Title, e.g., `"Mr."`, `"Dr."` (max 16 chars)
+- `suffix` -- Name suffix, e.g., `"Jr."` (max 16 chars)
+
+> At least one of `display_name`, `title`, `given_name`, `middle_name`, `family_name`, or `suffix` is required.
+
+**Key Parameters for `QUICKBOOKS_READ_CUSTOMER`:**
+- `customer_id` (required) -- ID of the customer to read
+
+**Example:**
+```
+Tool: QUICKBOOKS_CREATE_CUSTOMER
+Arguments:
+ display_name: "Acme Corporation"
+ given_name: "John"
+ family_name: "Doe"
+```
+
+---
+
+### 3. Query and Read Accounts
+
+Retrieve account information for use in invoice line items and financial reporting.
+
+**Tools:**
+- `QUICKBOOKS_QUERY_ACCOUNT` -- Execute a query against accounts
+- `QUICKBOOKS_READ_ACCOUNT` -- Read a specific account by ID
+
+**Key Parameters for `QUICKBOOKS_QUERY_ACCOUNT`:**
+- `query` (required) -- SQL-like query string, e.g., `"SELECT * FROM Account WHERE AccountType = 'Income'"`
+
+**Example:**
+```
+Tool: QUICKBOOKS_QUERY_ACCOUNT
+Arguments:
+ query: "SELECT * FROM Account WHERE AccountType = 'Income' MAXRESULTS 10"
+```
+
+---
+
+### 4. List and Filter Invoices
+
+Retrieve invoices with optional pagination and filtering.
+
+**Tool:** `QUICKBOOKS_LIST_INVOICES`
+
+**Steps:**
+1. Call `QUICKBOOKS_LIST_INVOICES` with pagination parameters
+2. Use `start_position` and `max_results` to page through results
+3. Filter by specific criteria as needed
+
+---
+
+## Recommended Execution Plan
+
+1. **Resolve the customer** using `QUICKBOOKS_READ_CUSTOMER` (if you have a customer ID) or create one with `QUICKBOOKS_CREATE_CUSTOMER`
+2. **Resolve item/revenue accounts** using `QUICKBOOKS_QUERY_ACCOUNT` and `QUICKBOOKS_READ_ACCOUNT` to get account or item IDs for invoice line items
+3. **Create the invoice** using `QUICKBOOKS_CREATE_INVOICE` with the resolved `customer_id` and well-formed line items
+4. **Verify creation** using `QUICKBOOKS_LIST_INVOICES` to locate the new invoice by ID or DocNumber
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **Invalid references** | `QUICKBOOKS_CREATE_INVOICE` fails if `customer_id` or `ItemRef.value` point to non-existent or inactive records. Always resolve IDs first. |
+| **Line item validation** | Incorrect `DetailType` or missing `SalesItemLineDetail` fields cause schema/validation errors during invoice creation. |
+| **Pagination** | `QUICKBOOKS_LIST_INVOICES` uses `start_position` and `max_results`. Incomplete pagination settings can miss invoices in larger books. |
+| **Sync tokens** | Any later edits require the latest `SyncToken` from a fresh invoice read. Stale sync tokens cause update rejections. |
+| **Rate limits** | QuickBooks enforces per-minute and daily API caps. High-volume runs should include backoff to avoid throttling errors. |
+| **DisplayName uniqueness** | Customer `display_name` must be unique across all Customer, Vendor, and Employee objects. Duplicates cause creation failures. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `QUICKBOOKS_CREATE_INVOICE` | Create a new invoice with line items |
+| `QUICKBOOKS_READ_CUSTOMER` | Read a customer record by ID |
+| `QUICKBOOKS_CREATE_CUSTOMER` | Create a new customer record |
+| `QUICKBOOKS_QUERY_ACCOUNT` | Query accounts with SQL-like syntax |
+| `QUICKBOOKS_READ_ACCOUNT` | Read a specific account by ID |
+| `QUICKBOOKS_LIST_INVOICES` | List invoices with pagination |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/radar-automation/SKILL.md b/plugins/awesome-claude-skills/radar-automation/SKILL.md
new file mode 100644
index 0000000..0a2c08d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/rafflys-automation/SKILL.md b/plugins/awesome-claude-skills/rafflys-automation/SKILL.md
new file mode 100644
index 0000000..84b6688
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ragic-automation/SKILL.md b/plugins/awesome-claude-skills/ragic-automation/SKILL.md
new file mode 100644
index 0000000..e2b1529
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/raisely-automation/SKILL.md b/plugins/awesome-claude-skills/raisely-automation/SKILL.md
new file mode 100644
index 0000000..bdc70ee
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ramp-automation/SKILL.md b/plugins/awesome-claude-skills/ramp-automation/SKILL.md
new file mode 100644
index 0000000..e8b2743
--- /dev/null
+++ b/plugins/awesome-claude-skills/ramp-automation/SKILL.md
@@ -0,0 +1,203 @@
+---
+name: Ramp Automation
+description: "Ramp Automation: manage corporate card transactions, reimbursements, users, and expense tracking via the Ramp platform"
+requires:
+ mcp: [rube]
+---
+
+# Ramp Automation
+
+Automate Ramp corporate finance operations including retrieving transactions, managing reimbursements, searching expenses, viewing card details, and listing users for expense management and accounting workflows.
+
+**Toolkit docs:** [composio.dev/toolkits/ramp](https://composio.dev/toolkits/ramp)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure an active connection exists for the `ramp` toolkit. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+---
+
+## Core Workflows
+
+### 1. List All Transactions
+
+Retrieve all corporate card transactions with comprehensive filtering options.
+
+**Tool:** `RAMP_GET_ALL_TRANSACTIONS`
+
+**Key Parameters:**
+- `from_date` -- Transactions after this date (ISO 8601 datetime)
+- `to_date` -- Transactions before this date (ISO 8601 datetime, default: today)
+- `user_id` -- Filter by user UUID
+- `card_id` -- Filter by physical card UUID
+- `department_id` -- Filter by department UUID
+- `merchant_id` -- Filter by merchant UUID
+- `entity_id` -- Filter by business entity UUID
+- `min_amount` / `max_amount` -- Amount range filter (USD)
+- `state` -- Transaction state; set to `"ALL"` to include declined transactions
+- `approval_status` -- Filter by approval status
+- `sync_status` -- Filter by ERP sync status (supersedes `sync_ready` and `has_no_sync_commits`)
+- `has_no_sync_commits` -- `true` for unsynced transactions
+- `sync_ready` -- `true` for transactions ready to sync to ERP
+- `requires_memo` -- `true` for transactions missing required memos
+- `include_merchant_data` -- `true` to include full purchase data from merchant
+- `page_size` -- Results per page (2--100, default: 20)
+- `start` -- Pagination cursor: ID of last entity from previous page
+- `order_by_date_desc` / `order_by_date_asc` -- Sort by date
+- `order_by_amount_desc` / `order_by_amount_asc` -- Sort by amount
+
+**Example:**
+```
+Tool: RAMP_GET_ALL_TRANSACTIONS
+Arguments:
+ from_date: "2026-02-01T00:00:00Z"
+ to_date: "2026-02-11T23:59:59Z"
+ page_size: 50
+ order_by_date_desc: true
+```
+
+---
+
+### 2. Search Transactions
+
+Search transactions by merchant name, memo, or other transaction details.
+
+**Tool:** `RAMP_SEARCH_TRANSACTIONS`
+
+**Key Parameters:**
+- `query` (required) -- Search text for merchant name, memo, or other details
+- All filter parameters from `RAMP_GET_ALL_TRANSACTIONS` are also available
+
+**Example:**
+```
+Tool: RAMP_SEARCH_TRANSACTIONS
+Arguments:
+ query: "AWS"
+ from_date: "2026-01-01T00:00:00Z"
+ page_size: 25
+```
+
+---
+
+### 3. Get Transaction Details
+
+Retrieve complete details of a specific transaction including merchant details, receipts, accounting codes, and dispute information.
+
+**Tool:** `RAMP_GET_TRANSACTION`
+
+**Key Parameters:**
+- `transaction_id` (required) -- ID of the transaction
+
+**Example:**
+```
+Tool: RAMP_GET_TRANSACTION
+Arguments:
+ transaction_id: "txn_abc123def456"
+```
+
+---
+
+### 4. Manage Reimbursements
+
+List and retrieve reimbursement records for approval workflows and expense analysis.
+
+**Tools:**
+- `RAMP_LIST_REIMBURSEMENTS` -- List reimbursements with filtering
+- `RAMP_GET_REIMBURSEMENT` -- Get complete details of a specific reimbursement
+
+**Key Parameters for `RAMP_LIST_REIMBURSEMENTS`:**
+- `user_id` -- Filter by employee UUID
+- `entity_id` -- Filter by business entity UUID
+- `from_date` / `to_date` -- Date range for creation date
+- `from_submitted_at` / `to_submitted_at` -- Date range for submission date
+- `from_transaction_date` / `to_transaction_date` -- Underlying transaction date range
+- `awaiting_approval_by_user_id` -- Filter for reimbursements pending a specific approver
+- `sync_status` -- Filter by ERP sync status
+- `has_no_sync_commits` -- `true` for unsynced reimbursements
+- `sync_ready` -- `true` for reimbursements ready to sync
+- `direction` -- `"BUSINESS_TO_USER"` (default) or `"USER_TO_BUSINESS"` (repayments)
+- `page_size` -- Results per page (2--100, default: 20)
+- `start` -- Pagination cursor
+
+**Example:**
+```
+Tool: RAMP_LIST_REIMBURSEMENTS
+Arguments:
+ from_date: "2026-02-01T00:00:00Z"
+ sync_ready: true
+ page_size: 50
+```
+
+---
+
+### 5. List Users and Get My Transactions
+
+View organization users and personal transaction history.
+
+**Tools:**
+- `RAMP_LIST_USERS` -- List users with filtering by department, role, location, entity
+- `RAMP_GET_MY_TRANSACTIONS` -- Get transactions for the authenticated user
+
+**Key Parameters for `RAMP_LIST_USERS`:**
+- `department_id` -- Filter by department UUID
+- `role` -- Filter by user role
+- `email` -- Filter by email address
+- `employee_id` -- Filter by employee ID
+- `entity_id` -- Filter by business entity UUID
+- `location_id` -- Filter by location UUID
+- `page_size` -- Results per page (2--100, default: 20)
+
+**Example:**
+```
+Tool: RAMP_LIST_USERS
+Arguments:
+ role: "ADMIN"
+ page_size: 50
+```
+
+---
+
+### 6. View Card Details and Accounting Fields
+
+Retrieve card information and custom accounting field configurations.
+
+**Tools:**
+- `RAMP_GET_CARD` -- Get detailed card information (spending limits, cardholder, fulfillment status)
+- `RAMP_FETCH_CUSTOM_ACCOUNTING_FIELD` -- Fetch custom accounting field definitions
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **Pagination required** | All list endpoints return paginated results. Use the `start` parameter with the ID of the last entity from the previous page to iterate. |
+| **Date format** | All date parameters must be ISO 8601 datetime format (e.g., `"2026-02-11T00:00:00Z"`). Plain date strings will fail. |
+| **sync_status priority** | When `sync_status` is set, it supersedes both `has_no_sync_commits` and `sync_ready` parameters. |
+| **Amount filters in USD** | `min_amount` and `max_amount` are in USD. Ensure correct currency context when filtering. |
+| **state=ALL for declined** | By default, declined transactions are excluded. Set `state: "ALL"` to include them in results. |
+| **page_size bounds** | Must be between 2 and 100. Default is 20. Values outside this range cause errors. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `RAMP_GET_ALL_TRANSACTIONS` | List all transactions with filtering |
+| `RAMP_SEARCH_TRANSACTIONS` | Search transactions by text query |
+| `RAMP_GET_TRANSACTION` | Get details of a specific transaction |
+| `RAMP_GET_MY_TRANSACTIONS` | Get authenticated user's transactions |
+| `RAMP_LIST_REIMBURSEMENTS` | List reimbursements with filtering |
+| `RAMP_GET_REIMBURSEMENT` | Get details of a specific reimbursement |
+| `RAMP_LIST_USERS` | List organization users |
+| `RAMP_GET_CARD` | Get card details |
+| `RAMP_FETCH_CUSTOM_ACCOUNTING_FIELD` | Fetch custom accounting field config |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/ravenseotools-automation/SKILL.md b/plugins/awesome-claude-skills/ravenseotools-automation/SKILL.md
new file mode 100644
index 0000000..c231011
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/re-amaze-automation/SKILL.md b/plugins/awesome-claude-skills/re-amaze-automation/SKILL.md
new file mode 100644
index 0000000..4d8d04e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/realphonevalidation-automation/SKILL.md b/plugins/awesome-claude-skills/realphonevalidation-automation/SKILL.md
new file mode 100644
index 0000000..ac0348d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/recallai-automation/SKILL.md b/plugins/awesome-claude-skills/recallai-automation/SKILL.md
new file mode 100644
index 0000000..69170c1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/recruitee-automation/SKILL.md b/plugins/awesome-claude-skills/recruitee-automation/SKILL.md
new file mode 100644
index 0000000..a217196
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/reddit-automation/SKILL.md b/plugins/awesome-claude-skills/reddit-automation/SKILL.md
new file mode 100644
index 0000000..ebc1557
--- /dev/null
+++ b/plugins/awesome-claude-skills/reddit-automation/SKILL.md
@@ -0,0 +1,217 @@
+---
+name: reddit-automation
+description: "Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Reddit Automation via Rube MCP
+
+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)
+- Active Reddit connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `reddit`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `reddit`
+3. If connection is not ACTIVE, follow the returned auth link to complete Reddit OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search Reddit
+
+**When to use**: User wants to find posts across subreddits
+
+**Tool sequence**:
+1. `REDDIT_SEARCH_ACROSS_SUBREDDITS` - Search for posts matching a query [Required]
+
+**Key parameters**:
+- `query`: Search terms
+- `subreddit`: Limit search to a specific subreddit (optional)
+- `sort`: Sort results by 'relevance', 'hot', 'top', 'new', 'comments'
+- `time_filter`: Time range ('hour', 'day', 'week', 'month', 'year', 'all')
+- `limit`: Number of results to return
+
+**Pitfalls**:
+- Search results may not include very recent posts due to indexing delay
+- The `time_filter` parameter only works with certain sort options
+- Results are paginated; use after/before tokens for additional pages
+- NSFW content may be filtered based on account settings
+
+### 2. Create Posts
+
+**When to use**: User wants to submit a new post to a subreddit
+
+**Tool sequence**:
+1. `REDDIT_LIST_SUBREDDIT_POST_FLAIRS` - Get available post flairs [Optional]
+2. `REDDIT_CREATE_REDDIT_POST` - Submit the post [Required]
+
+**Key parameters**:
+- `subreddit`: Target subreddit name (without 'r/' prefix)
+- `title`: Post title
+- `text`: Post body text (for text posts)
+- `url`: Link URL (for link posts)
+- `flair_id`: Flair ID from the subreddit's flair list
+
+**Pitfalls**:
+- Some subreddits require flair; use LIST_SUBREDDIT_POST_FLAIRS first
+- Subreddit posting rules vary widely; karma/age restrictions may apply
+- Text and URL are mutually exclusive; a post is either text or link
+- Rate limits apply; avoid rapid successive post creation
+- The subreddit name should not include 'r/' prefix
+
+### 3. Manage Comments
+
+**When to use**: User wants to comment on posts or manage existing comments
+
+**Tool sequence**:
+1. `REDDIT_RETRIEVE_POST_COMMENTS` - Get comments on a post [Optional]
+2. `REDDIT_POST_REDDIT_COMMENT` - Add a comment to a post or reply to a comment [Required]
+3. `REDDIT_EDIT_REDDIT_COMMENT_OR_POST` - Edit an existing comment [Optional]
+4. `REDDIT_DELETE_REDDIT_COMMENT` - Delete a comment [Optional]
+
+**Key parameters**:
+- `post_id`: ID of the post (for retrieving or commenting on)
+- `parent_id`: Full name of the parent (e.g., 't3_abc123' for post, 't1_xyz789' for comment)
+- `body`: Comment text content
+- `thing_id`: Full name of the item to edit or delete
+
+**Pitfalls**:
+- Reddit uses 'fullname' format: 't1_' prefix for comments, 't3_' for posts
+- Editing replaces the entire comment body; include all desired content
+- Deleted comments show as '[deleted]' but the tree structure remains
+- Comment depth limits may apply in some subreddits
+
+### 4. Browse Subreddit Content
+
+**When to use**: User wants to view top or trending content from a subreddit
+
+**Tool sequence**:
+1. `REDDIT_GET_R_TOP` - Get top posts from a subreddit [Required]
+2. `REDDIT_GET` - Get posts from a subreddit endpoint [Alternative]
+3. `REDDIT_RETRIEVE_REDDIT_POST` - Get full details for a specific post [Optional]
+
+**Key parameters**:
+- `subreddit`: Subreddit name
+- `time_filter`: Time range for top posts ('hour', 'day', 'week', 'month', 'year', 'all')
+- `limit`: Number of posts to retrieve
+- `post_id`: Specific post ID for full details
+
+**Pitfalls**:
+- Top posts with time_filter='all' returns all-time top content
+- Post details include the body text but comments require a separate call
+- Some posts may be removed or hidden based on subreddit rules
+- NSFW posts are included unless filtered at the account level
+
+### 5. Manage Posts
+
+**When to use**: User wants to edit or delete their own posts
+
+**Tool sequence**:
+1. `REDDIT_EDIT_REDDIT_COMMENT_OR_POST` - Edit a post's text content [Optional]
+2. `REDDIT_DELETE_REDDIT_POST` - Delete a post [Optional]
+3. `REDDIT_GET_USER_FLAIR` - Get user's flair in a subreddit [Optional]
+
+**Key parameters**:
+- `thing_id`: Full name of the post (e.g., 't3_abc123')
+- `body`: New text content (for editing)
+- `subreddit`: Subreddit name (for flair)
+
+**Pitfalls**:
+- Only text posts can have their body edited; link posts cannot be modified
+- Post titles cannot be edited after submission
+- Deletion is permanent; deleted posts show as '[deleted]'
+- User flair is per-subreddit and may be restricted
+
+## Common Patterns
+
+### Reddit Fullname Format
+
+**Prefixes**:
+```
+t1_ = Comment (e.g., 't1_abc123')
+t2_ = Account (e.g., 't2_xyz789')
+t3_ = Post/Link (e.g., 't3_def456')
+t4_ = Message
+t5_ = Subreddit
+```
+
+**Usage**:
+```
+1. Retrieve a post to get its fullname (t3_XXXXX)
+2. Use fullname as parent_id when commenting
+3. Use fullname as thing_id when editing/deleting
+```
+
+### Pagination
+
+- Reddit uses cursor-based pagination with 'after' and 'before' tokens
+- Set `limit` for items per page (max 100)
+- Check response for `after` token
+- Pass `after` value in subsequent requests to get next page
+
+### Flair Resolution
+
+```
+1. Call REDDIT_LIST_SUBREDDIT_POST_FLAIRS with subreddit name
+2. Find matching flair by text or category
+3. Extract flair_id
+4. Include flair_id when creating the post
+```
+
+## Known Pitfalls
+
+**Rate Limits**:
+- Reddit enforces rate limits per account and per OAuth app
+- Posting is limited to approximately 1 post per 10 minutes for new accounts
+- Commenting has similar but less restrictive limits
+- 429 errors should trigger exponential backoff
+
+**Content Rules**:
+- Each subreddit has its own posting rules and requirements
+- Some subreddits are restricted or private
+- Karma requirements may prevent posting in certain subreddits
+- Auto-moderator rules may remove posts that match certain patterns
+
+**ID Formats**:
+- Always use fullname format (with prefix) for parent_id and thing_id
+- Raw IDs without prefix will cause 'Invalid ID' errors
+- Post IDs from search results may need 't3_' prefix added
+
+**Text Formatting**:
+- Reddit uses Markdown for post and comment formatting
+- Code blocks, tables, and headers are supported
+- Links use `[text](url)` format
+- Mention users with `u/username`, subreddits with `r/subreddit`
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search Reddit | REDDIT_SEARCH_ACROSS_SUBREDDITS | query, subreddit, sort, time_filter |
+| Create post | REDDIT_CREATE_REDDIT_POST | subreddit, title, text/url |
+| Get post comments | REDDIT_RETRIEVE_POST_COMMENTS | post_id |
+| Add comment | REDDIT_POST_REDDIT_COMMENT | parent_id, body |
+| Edit comment/post | REDDIT_EDIT_REDDIT_COMMENT_OR_POST | thing_id, body |
+| Delete comment | REDDIT_DELETE_REDDIT_COMMENT | thing_id |
+| Delete post | REDDIT_DELETE_REDDIT_POST | thing_id |
+| Get top posts | REDDIT_GET_R_TOP | subreddit, time_filter, limit |
+| Browse subreddit | REDDIT_GET | subreddit |
+| Get post details | REDDIT_RETRIEVE_REDDIT_POST | post_id |
+| 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/plugins/awesome-claude-skills/refiner-automation/SKILL.md b/plugins/awesome-claude-skills/refiner-automation/SKILL.md
new file mode 100644
index 0000000..245213b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/remarkety-automation/SKILL.md b/plugins/awesome-claude-skills/remarkety-automation/SKILL.md
new file mode 100644
index 0000000..e247442
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/remote-retrieval-automation/SKILL.md b/plugins/awesome-claude-skills/remote-retrieval-automation/SKILL.md
new file mode 100644
index 0000000..9c84f74
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/remove-bg-automation/SKILL.md b/plugins/awesome-claude-skills/remove-bg-automation/SKILL.md
new file mode 100644
index 0000000..9bbb61e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/render-automation/SKILL.md b/plugins/awesome-claude-skills/render-automation/SKILL.md
new file mode 100644
index 0000000..dabd3c1
--- /dev/null
+++ b/plugins/awesome-claude-skills/render-automation/SKILL.md
@@ -0,0 +1,186 @@
+---
+name: render-automation
+description: "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Render Automation via Rube MCP
+
+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)
+- Active Render connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `render`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `render`
+3. If connection is not ACTIVE, follow the returned auth link to complete Render authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Browse Services
+
+**When to use**: User wants to find or inspect Render services (web services, static sites, workers, cron jobs)
+
+**Tool sequence**:
+1. `RENDER_LIST_SERVICES` - List all services with optional filters [Required]
+
+**Key parameters**:
+- `name`: Filter services by name substring
+- `type`: Filter by service type ('web_service', 'static_site', 'private_service', 'background_worker', 'cron_job')
+- `limit`: Maximum results per page (default 20, max 100)
+- `cursor`: Pagination cursor from previous response
+
+**Pitfalls**:
+- Service types must match exact enum values: 'web_service', 'static_site', 'private_service', 'background_worker', 'cron_job'
+- Pagination uses cursor-based approach; follow `cursor` until absent
+- Name filter is substring-based, not exact match
+- Service IDs follow the format 'srv-xxxxxxxxxxxx'
+- Default limit is 20; set higher for comprehensive listing
+
+### 2. Trigger Deployments
+
+**When to use**: User wants to manually deploy or redeploy a service
+
+**Tool sequence**:
+1. `RENDER_LIST_SERVICES` - Find the service to deploy [Prerequisite]
+2. `RENDER_TRIGGER_DEPLOY` - Trigger a new deployment [Required]
+3. `RENDER_RETRIEVE_DEPLOY` - Monitor deployment progress [Optional]
+
+**Key parameters**:
+- For TRIGGER_DEPLOY:
+ - `serviceId`: Service ID to deploy (required, format: 'srv-xxxxxxxxxxxx')
+ - `clearCache`: Set `true` to clear build cache before deploying
+- For RETRIEVE_DEPLOY:
+ - `serviceId`: Service ID
+ - `deployId`: Deploy ID from trigger response (format: 'dep-xxxxxxxxxxxx')
+
+**Pitfalls**:
+- `serviceId` is required; resolve via LIST_SERVICES first
+- Service IDs start with 'srv-' prefix
+- Deploy IDs start with 'dep-' prefix
+- `clearCache: true` forces a clean build; takes longer but resolves cache-related issues
+- Deployment is asynchronous; use RETRIEVE_DEPLOY to poll status
+- Triggering a deploy while another is in progress may queue the new one
+
+### 3. Monitor Deployment Status
+
+**When to use**: User wants to check the progress or result of a deployment
+
+**Tool sequence**:
+1. `RENDER_RETRIEVE_DEPLOY` - Get deployment details and status [Required]
+
+**Key parameters**:
+- `serviceId`: Service ID (required)
+- `deployId`: Deployment ID (required)
+- Response includes `status`, `createdAt`, `updatedAt`, `finishedAt`, `commit`
+
+**Pitfalls**:
+- Both `serviceId` and `deployId` are required
+- Deploy statuses include: 'created', 'build_in_progress', 'update_in_progress', 'live', 'deactivated', 'build_failed', 'update_failed', 'canceled'
+- 'live' indicates successful deployment
+- 'build_failed' or 'update_failed' indicate deployment errors
+- Poll at reasonable intervals (10-30 seconds) to avoid rate limits
+
+### 4. Manage Projects
+
+**When to use**: User wants to list and organize Render projects
+
+**Tool sequence**:
+1. `RENDER_LIST_PROJECTS` - List all projects [Required]
+
+**Key parameters**:
+- `limit`: Maximum results per page (max 100)
+- `cursor`: Pagination cursor from previous response
+
+**Pitfalls**:
+- Projects group related services together
+- Pagination uses cursor-based approach
+- Project IDs are used for organizational purposes
+- Not all services may be assigned to a project
+
+## Common Patterns
+
+### ID Resolution
+
+**Service name -> Service ID**:
+```
+1. Call RENDER_LIST_SERVICES with name=service_name
+2. Find service by name in results
+3. Extract id (format: 'srv-xxxxxxxxxxxx')
+```
+
+**Deployment lookup**:
+```
+1. Store deployId from RENDER_TRIGGER_DEPLOY response
+2. Call RENDER_RETRIEVE_DEPLOY with serviceId and deployId
+3. Check status for completion
+```
+
+### Deploy and Monitor Pattern
+
+```
+1. RENDER_LIST_SERVICES -> find service by name -> get serviceId
+2. RENDER_TRIGGER_DEPLOY with serviceId -> get deployId
+3. Loop: RENDER_RETRIEVE_DEPLOY with serviceId + deployId
+4. Check status: 'live' = success, 'build_failed'/'update_failed' = error
+5. Continue polling until terminal state reached
+```
+
+### Pagination
+
+- Use `cursor` from response for next page
+- Continue until `cursor` is absent or results are empty
+- Both LIST_SERVICES and LIST_PROJECTS use cursor-based pagination
+- Set `limit` to max (100) for fewer pagination rounds
+
+## Known Pitfalls
+
+**Service IDs**:
+- Always prefixed with 'srv-' (e.g., 'srv-abcd1234efgh')
+- Deploy IDs prefixed with 'dep-' (e.g., 'dep-d2mqkf9r0fns73bham1g')
+- Always resolve service names to IDs via LIST_SERVICES
+
+**Service Types**:
+- Must use exact enum values when filtering
+- Available types: web_service, static_site, private_service, background_worker, cron_job
+- Different service types have different deployment behaviors
+
+**Deployment Behavior**:
+- Deployments are asynchronous; always poll for completion
+- Clear cache deploys take longer but resolve stale cache issues
+- Failed deploys do not roll back automatically; the previous version stays live
+- Concurrent deploy triggers may be queued
+
+**Rate Limits**:
+- Render API has rate limits
+- Avoid rapid polling; use 10-30 second intervals
+- Bulk operations should be throttled
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Timestamps use ISO 8601 format
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List services | RENDER_LIST_SERVICES | name, type, limit, cursor |
+| 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/plugins/awesome-claude-skills/renderform-automation/SKILL.md b/plugins/awesome-claude-skills/renderform-automation/SKILL.md
new file mode 100644
index 0000000..9aee89e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/repairshopr-automation/SKILL.md b/plugins/awesome-claude-skills/repairshopr-automation/SKILL.md
new file mode 100644
index 0000000..6cc63e8
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/replicate-automation/SKILL.md b/plugins/awesome-claude-skills/replicate-automation/SKILL.md
new file mode 100644
index 0000000..abcdfb0
--- /dev/null
+++ b/plugins/awesome-claude-skills/replicate-automation/SKILL.md
@@ -0,0 +1,138 @@
+---
+name: Replicate Automation
+description: "Automate Replicate AI model operations -- run predictions, upload files, inspect model schemas, list versions, and manage prediction history via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Replicate Automation
+
+Automate your Replicate AI model workflows -- run predictions on any public model (image generation, LLMs, audio, video), upload input files, inspect model schemas and documentation, list model versions, and track prediction history.
+
+**Toolkit docs:** [composio.dev/toolkits/replicate](https://composio.dev/toolkits/replicate)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your Replicate account when prompted (API token authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. Get Model Details and Schema
+
+Use `REPLICATE_MODELS_GET` to inspect a model's input/output schema before running predictions.
+
+```
+Tool: REPLICATE_MODELS_GET
+Inputs:
+ - model_owner: string (required) -- e.g., "meta", "black-forest-labs", "stability-ai"
+ - model_name: string (required) -- e.g., "meta-llama-3-8b-instruct", "flux-1.1-pro"
+```
+
+**Important:** Each model has unique input keys and types. Always check the `openapi_schema` from this response before constructing prediction inputs.
+
+### 2. Run a Prediction
+
+Use `REPLICATE_MODELS_PREDICTIONS_CREATE` to run inference on any model with optional synchronous waiting and webhooks.
+
+```
+Tool: REPLICATE_MODELS_PREDICTIONS_CREATE
+Inputs:
+ - model_owner: string (required) -- e.g., "meta", "black-forest-labs"
+ - model_name: string (required) -- e.g., "flux-1.1-pro", "sdxl"
+ - input: object (required) -- model-specific inputs, e.g., { "prompt": "A sunset over mountains" }
+ - wait_for: integer (1-60 seconds, optional) -- synchronous wait for completion
+ - cancel_after: string (optional) -- max execution time, e.g., "300s", "5m"
+ - webhook: string (optional) -- HTTPS URL for async completion notifications
+ - webhook_events_filter: array (optional) -- ["start", "output", "logs", "completed"]
+```
+
+**Sync vs Async:** Use `wait_for` (1-60s) for fast models. For long-running jobs, omit it and use webhooks or poll via `REPLICATE_PREDICTIONS_LIST`.
+
+### 3. Upload Files for Model Input
+
+Use `REPLICATE_CREATE_FILE` to upload images, documents, or other binary inputs that models need.
+
+```
+Tool: REPLICATE_CREATE_FILE
+Inputs:
+ - content: string (required) -- base64-encoded file content
+ - filename: string (required) -- e.g., "input.png", "audio.wav" (max 255 bytes UTF-8)
+ - content_type: string (default "application/octet-stream") -- MIME type
+ - metadata: object (optional) -- custom JSON metadata
+```
+
+### 4. Read Model Documentation
+
+Use `REPLICATE_MODELS_README_GET` to access a model's README in Markdown format for detailed usage instructions.
+
+```
+Tool: REPLICATE_MODELS_README_GET
+Inputs:
+ - model_owner: string (required)
+ - model_name: string (required)
+```
+
+### 5. List Model Versions
+
+Use `REPLICATE_MODELS_VERSIONS_LIST` to see all available versions of a model, sorted newest first.
+
+```
+Tool: REPLICATE_MODELS_VERSIONS_LIST
+Inputs:
+ - model_owner: string (required)
+ - model_name: string (required)
+```
+
+### 6. Track Prediction History and Files
+
+Use `REPLICATE_PREDICTIONS_LIST` to retrieve prediction history, and `REPLICATE_FILES_GET`/`REPLICATE_FILES_LIST` to manage uploaded files.
+
+```
+Tool: REPLICATE_PREDICTIONS_LIST
+ - Lists all predictions for the authenticated user with pagination
+
+Tool: REPLICATE_FILES_LIST
+ - Lists uploaded files, most recent first
+
+Tool: REPLICATE_FILES_GET
+ - Get details of a specific file by ID
+```
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| Model-specific input keys | Each model has unique input keys and types. Using the wrong key causes validation errors. Always call `REPLICATE_MODELS_GET` first to check the `openapi_schema`. |
+| File upload encoding | `REPLICATE_CREATE_FILE` requires base64-encoded content. Binary files treated as text (UTF-8) will fail with decode errors. |
+| Public vs deployment paths | Public models must be run via `REPLICATE_MODELS_PREDICTIONS_CREATE`. Using deployment-oriented paths causes HTTP 404 failures. |
+| Sync wait limits | `wait_for` supports 1-60 seconds only. Long-running jobs need async handling via webhooks or polling `REPLICATE_PREDICTIONS_LIST`. |
+| Image model constraints | Image models like flux-1.1-pro have specific constraints (e.g., max width/height 1440px, valid aspect ratios). Check the model schema first. |
+| Stale file references | Heavy usage creates many uploads. Routinely check `REPLICATE_FILES_LIST` to avoid using stale `file_id` references. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `REPLICATE_MODELS_GET` | Get model details, schema, and metadata |
+| `REPLICATE_MODELS_PREDICTIONS_CREATE` | Run a prediction on a model |
+| `REPLICATE_CREATE_FILE` | Upload a file for model input |
+| `REPLICATE_MODELS_README_GET` | Get model README documentation |
+| `REPLICATE_MODELS_VERSIONS_LIST` | List all versions of a model |
+| `REPLICATE_PREDICTIONS_LIST` | List prediction history with pagination |
+| `REPLICATE_FILES_LIST` | List uploaded files |
+| `REPLICATE_FILES_GET` | Get file details by ID |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/reply-automation/SKILL.md b/plugins/awesome-claude-skills/reply-automation/SKILL.md
new file mode 100644
index 0000000..8dbc31e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/reply-io-automation/SKILL.md b/plugins/awesome-claude-skills/reply-io-automation/SKILL.md
new file mode 100644
index 0000000..3041346
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/resend-automation/SKILL.md b/plugins/awesome-claude-skills/resend-automation/SKILL.md
new file mode 100644
index 0000000..91030c4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/respond-io-automation/SKILL.md b/plugins/awesome-claude-skills/respond-io-automation/SKILL.md
new file mode 100644
index 0000000..fe4258e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/retailed-automation/SKILL.md b/plugins/awesome-claude-skills/retailed-automation/SKILL.md
new file mode 100644
index 0000000..dc29b71
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/retellai-automation/SKILL.md b/plugins/awesome-claude-skills/retellai-automation/SKILL.md
new file mode 100644
index 0000000..258565b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/retently-automation/SKILL.md b/plugins/awesome-claude-skills/retently-automation/SKILL.md
new file mode 100644
index 0000000..6f15806
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/rev-ai-automation/SKILL.md b/plugins/awesome-claude-skills/rev-ai-automation/SKILL.md
new file mode 100644
index 0000000..e83e89c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/revolt-automation/SKILL.md b/plugins/awesome-claude-skills/revolt-automation/SKILL.md
new file mode 100644
index 0000000..a690fa5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ring-central-automation/SKILL.md b/plugins/awesome-claude-skills/ring-central-automation/SKILL.md
new file mode 100644
index 0000000..929a010
--- /dev/null
+++ b/plugins/awesome-claude-skills/ring-central-automation/SKILL.md
@@ -0,0 +1,56 @@
+---
+name: RingCentral Automation
+description: "RingCentral automation via Rube MCP -- toolkit not currently available in Composio; no RING_CENTRAL_ tools found"
+requires:
+ mcp:
+ - rube
+---
+
+# RingCentral Automation
+
+> **Status: Toolkit Not Available** -- RUBE_SEARCH_TOOLS returned no `ring_central`-specific tools. The RingCentral toolkit is not currently available in Composio's tool catalog. Searches returned tools from unrelated toolkits (ClickSend, Telnyx, Slack) instead.
+
+**Toolkit docs:** [composio.dev/toolkits/ring_central](https://composio.dev/toolkits/ring_central)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Check availability by calling `RUBE_SEARCH_TOOLS` with RingCentral-related queries
+3. If `RING_CENTRAL_*` tools appear in the future, connect via `RUBE_MANAGE_CONNECTIONS` with toolkit `ring_central`
+
+---
+
+## Current Status
+
+As of the last tool discovery scan, no `RING_CENTRAL_*` tool slugs were returned by RUBE_SEARCH_TOOLS. Queries for RingCentral messaging, call logs, fax, and extension management all returned tools from other toolkits:
+
+- SMS/messaging queries returned **ClickSend** tools (`CLICKSEND_CREATE_SMS_SEND`, etc.)
+- Call management queries returned **Pipedrive** call log tools
+- Telephony/VoIP queries returned **Telnyx** notification tools
+- Fax queries returned **ClickSend** fax automation tools
+
+This indicates the `ring_central` toolkit either has no tools registered or is not yet integrated into the Composio platform.
+
+---
+
+## Alternatives
+
+If you need telephony, SMS, or communication automation, consider these available toolkits:
+
+| Need | Alternative Toolkit | Example Tool |
+|------|-------------------|--------------|
+| SMS messaging | ClickSend | `CLICKSEND_CREATE_SMS_SEND` |
+| VoIP/telephony | Telnyx | `TELNYX_CREATE_NOTIFICATION_CHANNEL` |
+| Team messaging | Slack / Webex | `SLACK_SEND_MESSAGE` / `WEBEX_MESSAGING_CREATE_MESSAGE` |
+
+---
+
+## When Tools Become Available
+
+Once RingCentral tools are added to Composio, this skill should be updated with real tool slugs, schemas, and pitfalls following the same pattern as other automation skills in this collection.
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/ring_central-automation/SKILL.md b/plugins/awesome-claude-skills/ring_central-automation/SKILL.md
new file mode 100644
index 0000000..809ab46
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/rippling-automation/SKILL.md b/plugins/awesome-claude-skills/rippling-automation/SKILL.md
new file mode 100644
index 0000000..db5ebcb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ritekit-automation/SKILL.md b/plugins/awesome-claude-skills/ritekit-automation/SKILL.md
new file mode 100644
index 0000000..9504527
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/rkvst-automation/SKILL.md b/plugins/awesome-claude-skills/rkvst-automation/SKILL.md
new file mode 100644
index 0000000..6d3efde
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/rocketlane-automation/SKILL.md b/plugins/awesome-claude-skills/rocketlane-automation/SKILL.md
new file mode 100644
index 0000000..152d782
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/rootly-automation/SKILL.md b/plugins/awesome-claude-skills/rootly-automation/SKILL.md
new file mode 100644
index 0000000..6b788e9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/rosette-text-analytics-automation/SKILL.md b/plugins/awesome-claude-skills/rosette-text-analytics-automation/SKILL.md
new file mode 100644
index 0000000..6760530
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/route4me-automation/SKILL.md b/plugins/awesome-claude-skills/route4me-automation/SKILL.md
new file mode 100644
index 0000000..e3a6666
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/safetyculture-automation/SKILL.md b/plugins/awesome-claude-skills/safetyculture-automation/SKILL.md
new file mode 100644
index 0000000..0686c36
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sage-automation/SKILL.md b/plugins/awesome-claude-skills/sage-automation/SKILL.md
new file mode 100644
index 0000000..dbd475a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/salesforce-automation/SKILL.md b/plugins/awesome-claude-skills/salesforce-automation/SKILL.md
new file mode 100644
index 0000000..4697bf4
--- /dev/null
+++ b/plugins/awesome-claude-skills/salesforce-automation/SKILL.md
@@ -0,0 +1,195 @@
+---
+name: salesforce-automation
+description: "Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Salesforce Automation via Rube MCP
+
+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)
+- Active Salesforce connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add 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`
+3. If connection is not ACTIVE, follow the returned auth link to complete Salesforce OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Leads
+
+**When to use**: User wants to create, search, update, or list leads
+
+**Tool sequence**:
+1. `SALESFORCE_SEARCH_LEADS` - Search leads by criteria [Optional]
+2. `SALESFORCE_LIST_LEADS` - List all leads [Optional]
+3. `SALESFORCE_CREATE_LEAD` - Create a new lead [Optional]
+4. `SALESFORCE_UPDATE_LEAD` - Update lead fields [Optional]
+5. `SALESFORCE_ADD_LEAD_TO_CAMPAIGN` - Add lead to campaign [Optional]
+6. `SALESFORCE_APPLY_LEAD_ASSIGNMENT_RULES` - Apply assignment rules [Optional]
+
+**Key parameters**:
+- `LastName`: Required for lead creation
+- `Company`: Required for lead creation
+- `Email`, `Phone`, `Title`: Common lead fields
+- `lead_id`: Lead ID for updates
+- `campaign_id`: Campaign ID for campaign operations
+
+**Pitfalls**:
+- LastName and Company are required fields for lead creation
+- Lead IDs are 15 or 18 character Salesforce IDs
+
+### 2. Manage Contacts and Accounts
+
+**When to use**: User wants to manage contacts and their associated accounts
+
+**Tool sequence**:
+1. `SALESFORCE_SEARCH_CONTACTS` - Search contacts [Optional]
+2. `SALESFORCE_LIST_CONTACTS` - List contacts [Optional]
+3. `SALESFORCE_CREATE_CONTACT` - Create a new contact [Optional]
+4. `SALESFORCE_SEARCH_ACCOUNTS` - Search accounts [Optional]
+5. `SALESFORCE_CREATE_ACCOUNT` - Create a new account [Optional]
+6. `SALESFORCE_ASSOCIATE_CONTACT_TO_ACCOUNT` - Link contact to account [Optional]
+
+**Key parameters**:
+- `LastName`: Required for contact creation
+- `Name`: Account name for creation
+- `AccountId`: Account ID to associate with contact
+- `contact_id`, `account_id`: IDs for association
+
+**Pitfalls**:
+- Contact requires at least LastName
+- Account association requires both valid contact and account IDs
+
+### 3. Manage Opportunities
+
+**When to use**: User wants to track and manage sales opportunities
+
+**Tool sequence**:
+1. `SALESFORCE_SEARCH_OPPORTUNITIES` - Search opportunities [Optional]
+2. `SALESFORCE_LIST_OPPORTUNITIES` - List all opportunities [Optional]
+3. `SALESFORCE_GET_OPPORTUNITY` - Get opportunity details [Optional]
+4. `SALESFORCE_CREATE_OPPORTUNITY` - Create new opportunity [Optional]
+5. `SALESFORCE_RETRIEVE_OPPORTUNITIES_DATA` - Retrieve opportunity data [Optional]
+
+**Key parameters**:
+- `Name`: Opportunity name (required)
+- `StageName`: Sales stage (required)
+- `CloseDate`: Expected close date (required)
+- `Amount`: Deal value
+- `AccountId`: Associated account
+
+**Pitfalls**:
+- Name, StageName, and CloseDate are required for creation
+- Stage names must match exactly what is configured in Salesforce
+
+### 4. Run SOQL Queries
+
+**When to use**: User wants to query Salesforce data with custom SOQL
+
+**Tool sequence**:
+1. `SALESFORCE_RUN_SOQL_QUERY` / `SALESFORCE_QUERY` - Execute SOQL [Required]
+
+**Key parameters**:
+- `query`: SOQL query string
+
+**Pitfalls**:
+- SOQL syntax differs from SQL; uses Salesforce object and field API names
+- Field API names may differ from display labels (e.g., `Account.Name` not `Account Name`)
+- Results are paginated for large datasets
+
+### 5. Manage Tasks
+
+**When to use**: User wants to create, search, update, or complete tasks
+
+**Tool sequence**:
+1. `SALESFORCE_SEARCH_TASKS` - Search tasks [Optional]
+2. `SALESFORCE_UPDATE_TASK` - Update task fields [Optional]
+3. `SALESFORCE_COMPLETE_TASK` - Mark task as complete [Optional]
+
+**Key parameters**:
+- `task_id`: Task ID for updates
+- `Status`: Task status value
+- `Subject`: Task subject
+
+**Pitfalls**:
+- Task status values must match picklist options in Salesforce
+
+## Common Patterns
+
+### SOQL Syntax
+
+**Basic query**:
+```
+SELECT Id, Name, Email FROM Contact WHERE LastName = 'Smith'
+```
+
+**With relationships**:
+```
+SELECT Id, Name, Account.Name FROM Contact WHERE Account.Industry = 'Technology'
+```
+
+**Date filtering**:
+```
+SELECT Id, Name FROM Lead WHERE CreatedDate = TODAY
+SELECT Id, Name FROM Opportunity WHERE CloseDate = NEXT_MONTH
+```
+
+### Pagination
+
+- SOQL queries with large results return pagination tokens
+- Use `SALESFORCE_QUERY` with nextRecordsUrl for pagination
+- Check `done` field in response; if false, continue paging
+
+## Known Pitfalls
+
+**Field API Names**:
+- Always use API names, not display labels
+- Custom fields end with `__c` suffix
+- Use SALESFORCE_GET_ALL_CUSTOM_OBJECTS to discover custom objects
+
+**ID Formats**:
+- Salesforce IDs are 15 (case-sensitive) or 18 (case-insensitive) characters
+- Both formats are accepted in most operations
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create lead | SALESFORCE_CREATE_LEAD | LastName, Company |
+| Search leads | SALESFORCE_SEARCH_LEADS | query |
+| List leads | SALESFORCE_LIST_LEADS | (filters) |
+| Update lead | SALESFORCE_UPDATE_LEAD | lead_id, fields |
+| Create contact | SALESFORCE_CREATE_CONTACT | LastName |
+| Search contacts | SALESFORCE_SEARCH_CONTACTS | query |
+| Create account | SALESFORCE_CREATE_ACCOUNT | Name |
+| Search accounts | SALESFORCE_SEARCH_ACCOUNTS | query |
+| Link contact | SALESFORCE_ASSOCIATE_CONTACT_TO_ACCOUNT | contact_id, account_id |
+| Create opportunity | SALESFORCE_CREATE_OPPORTUNITY | Name, StageName, CloseDate |
+| Get opportunity | SALESFORCE_GET_OPPORTUNITY | opportunity_id |
+| Search opportunities | SALESFORCE_SEARCH_OPPORTUNITIES | query |
+| Run SOQL | SALESFORCE_RUN_SOQL_QUERY | query |
+| Query | SALESFORCE_QUERY | query |
+| Search tasks | SALESFORCE_SEARCH_TASKS | query |
+| Update task | SALESFORCE_UPDATE_TASK | task_id, fields |
+| Complete task | SALESFORCE_COMPLETE_TASK | task_id |
+| Get user info | SALESFORCE_GET_USER_INFO | (none) |
+| 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/plugins/awesome-claude-skills/salesforce-marketing-cloud-automation/SKILL.md b/plugins/awesome-claude-skills/salesforce-marketing-cloud-automation/SKILL.md
new file mode 100644
index 0000000..b59cadc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/salesforce-service-cloud-automation/SKILL.md b/plugins/awesome-claude-skills/salesforce-service-cloud-automation/SKILL.md
new file mode 100644
index 0000000..63cd666
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/salesmate-automation/SKILL.md b/plugins/awesome-claude-skills/salesmate-automation/SKILL.md
new file mode 100644
index 0000000..0b647f0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sap-successfactors-automation/SKILL.md b/plugins/awesome-claude-skills/sap-successfactors-automation/SKILL.md
new file mode 100644
index 0000000..6725b25
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/satismeter-automation/SKILL.md b/plugins/awesome-claude-skills/satismeter-automation/SKILL.md
new file mode 100644
index 0000000..8d68ef5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/scrape-do-automation/SKILL.md b/plugins/awesome-claude-skills/scrape-do-automation/SKILL.md
new file mode 100644
index 0000000..4cc6309
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/scrapegraph-ai-automation/SKILL.md b/plugins/awesome-claude-skills/scrapegraph-ai-automation/SKILL.md
new file mode 100644
index 0000000..8b515d2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/scrapfly-automation/SKILL.md b/plugins/awesome-claude-skills/scrapfly-automation/SKILL.md
new file mode 100644
index 0000000..fb9f40a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/scrapingant-automation/SKILL.md b/plugins/awesome-claude-skills/scrapingant-automation/SKILL.md
new file mode 100644
index 0000000..19c6e35
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/scrapingbee-automation/SKILL.md b/plugins/awesome-claude-skills/scrapingbee-automation/SKILL.md
new file mode 100644
index 0000000..41bd749
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/screenshot-fyi-automation/SKILL.md b/plugins/awesome-claude-skills/screenshot-fyi-automation/SKILL.md
new file mode 100644
index 0000000..c20663d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/screenshotone-automation/SKILL.md b/plugins/awesome-claude-skills/screenshotone-automation/SKILL.md
new file mode 100644
index 0000000..a9f30b6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/seat-geek-automation/SKILL.md b/plugins/awesome-claude-skills/seat-geek-automation/SKILL.md
new file mode 100644
index 0000000..9334728
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/securitytrails-automation/SKILL.md b/plugins/awesome-claude-skills/securitytrails-automation/SKILL.md
new file mode 100644
index 0000000..d3fb003
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/segment-automation/SKILL.md b/plugins/awesome-claude-skills/segment-automation/SKILL.md
new file mode 100644
index 0000000..9313dcc
--- /dev/null
+++ b/plugins/awesome-claude-skills/segment-automation/SKILL.md
@@ -0,0 +1,230 @@
+---
+name: segment-automation
+description: "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Segment Automation via Rube MCP
+
+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)
+- Active Segment connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`
+3. If connection is not ACTIVE, follow the returned auth link to complete Segment authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Track Events
+
+**When to use**: User wants to send event data to Segment for downstream destinations
+
+**Tool sequence**:
+1. `SEGMENT_TRACK` - Send a single track event [Required]
+
+**Key parameters**:
+- `userId`: User identifier (required if no `anonymousId`)
+- `anonymousId`: Anonymous identifier (required if no `userId`)
+- `event`: Event name (e.g., 'Order Completed', 'Button Clicked')
+- `properties`: Object with event-specific properties
+- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)
+- `context`: Object with contextual metadata (IP, user agent, etc.)
+
+**Pitfalls**:
+- At least one of `userId` or `anonymousId` is required
+- `event` name is required and should follow consistent naming conventions
+- Properties are freeform objects; ensure consistent schema across events
+- Timestamp must be ISO 8601 format (e.g., '2024-01-15T10:30:00Z')
+- Events are processed asynchronously; successful API response means accepted, not delivered
+
+### 2. Identify Users
+
+**When to use**: User wants to associate traits with a user profile in Segment
+
+**Tool sequence**:
+1. `SEGMENT_IDENTIFY` - Set user traits and identity [Required]
+
+**Key parameters**:
+- `userId`: User identifier (required if no `anonymousId`)
+- `anonymousId`: Anonymous identifier
+- `traits`: Object with user properties (email, name, plan, etc.)
+- `timestamp`: ISO 8601 timestamp
+- `context`: Contextual metadata
+
+**Pitfalls**:
+- At least one of `userId` or `anonymousId` is required
+- Traits are merged with existing traits, not replaced
+- To remove a trait, set it to `null`
+- Identify calls should be made before track calls for new users
+- Avoid sending PII in traits unless destinations are configured for it
+
+### 3. Batch Operations
+
+**When to use**: User wants to send multiple events, identifies, or other calls in a single request
+
+**Tool sequence**:
+1. `SEGMENT_BATCH` - Send multiple Segment calls in one request [Required]
+
+**Key parameters**:
+- `batch`: Array of message objects, each with:
+ - `type`: Message type ('track', 'identify', 'group', 'page', 'alias')
+ - `userId` / `anonymousId`: User identifier
+ - Additional fields based on type (event, properties, traits, etc.)
+
+**Pitfalls**:
+- Each message in the batch must have a valid `type` field
+- Maximum batch size limit applies; check schema for current limit
+- All messages in a batch are processed independently; one failure does not affect others
+- Each message must independently satisfy its type's requirements (e.g., track needs event name)
+- Batch is the most efficient way to send multiple calls; prefer over individual calls
+
+### 4. Group Users
+
+**When to use**: User wants to associate a user with a company, team, or organization
+
+**Tool sequence**:
+1. `SEGMENT_GROUP` - Associate user with a group [Required]
+
+**Key parameters**:
+- `userId`: User identifier (required if no `anonymousId`)
+- `anonymousId`: Anonymous identifier
+- `groupId`: Group/organization identifier (required)
+- `traits`: Object with group properties (name, industry, size, plan)
+- `timestamp`: ISO 8601 timestamp
+
+**Pitfalls**:
+- `groupId` is required; it identifies the company or organization
+- Group traits are merged with existing traits for that group
+- A user can belong to multiple groups
+- Group traits update the group profile, not the user profile
+
+### 5. Track Page Views
+
+**When to use**: User wants to record page view events in Segment
+
+**Tool sequence**:
+1. `SEGMENT_PAGE` - Send a page view event [Required]
+
+**Key parameters**:
+- `userId`: User identifier (required if no `anonymousId`)
+- `anonymousId`: Anonymous identifier
+- `name`: Page name (e.g., 'Home', 'Pricing', 'Dashboard')
+- `category`: Page category (e.g., 'Docs', 'Marketing')
+- `properties`: Object with page-specific properties (url, title, referrer)
+
+**Pitfalls**:
+- At least one of `userId` or `anonymousId` is required
+- `name` and `category` are optional but recommended for proper analytics
+- Standard properties include `url`, `title`, `referrer`, `path`, `search`
+- Page calls are often automated; manual use is for server-side page tracking
+
+### 6. Alias Users and Manage Sources
+
+**When to use**: User wants to merge anonymous and identified users, or manage source configuration
+
+**Tool sequence**:
+1. `SEGMENT_ALIAS` - Link two user identities together [Optional]
+2. `SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE` - View source schema settings [Optional]
+3. `SEGMENT_UPDATE_SOURCE` - Update source configuration [Optional]
+
+**Key parameters**:
+- For ALIAS:
+ - `userId`: New user identifier (the identified ID)
+ - `previousId`: Old user identifier (the anonymous ID)
+- For source operations:
+ - `sourceId`: Source identifier
+
+**Pitfalls**:
+- ALIAS is a one-way operation; cannot be undone
+- `previousId` is the anonymous/old ID, `userId` is the new/identified ID
+- Not all destinations support alias calls; check destination documentation
+- ALIAS should be called once when a user first identifies (e.g., signs up)
+- Source updates may affect data collection; review changes carefully
+
+## Common Patterns
+
+### User Lifecycle
+
+Standard Segment user lifecycle:
+```
+1. Anonymous user visits -> PAGE call with anonymousId
+2. User interacts -> TRACK call with anonymousId
+3. User signs up -> ALIAS (anonymousId -> userId), then IDENTIFY with traits
+4. User takes action -> TRACK call with userId
+5. User joins org -> GROUP call linking userId to groupId
+```
+
+### Batch Optimization
+
+For bulk data ingestion:
+```
+1. Collect events in memory (array of message objects)
+2. Each message includes type, userId/anonymousId, and type-specific fields
+3. Call SEGMENT_BATCH with the collected messages
+4. Check response for any individual message errors
+```
+
+### Naming Conventions
+
+Segment recommends consistent event naming:
+- **Events**: Use "Object Action" format (e.g., 'Order Completed', 'Article Viewed')
+- **Properties**: Use snake_case (e.g., 'order_total', 'product_name')
+- **Traits**: Use snake_case (e.g., 'first_name', 'plan_type')
+
+## Known Pitfalls
+
+**Identity Resolution**:
+- Always include `userId` or `anonymousId` on every call
+- Use ALIAS only once per user identity merge
+- Identify before tracking to ensure proper user association
+
+**Data Quality**:
+- Event names should be consistent across all sources
+- Properties should follow a defined schema for downstream compatibility
+- Avoid sending sensitive PII unless destinations are configured for it
+
+**Rate Limits**:
+- Use BATCH for bulk operations to stay within rate limits
+- Individual calls are rate-limited per source
+- Batch calls are more efficient and less likely to be throttled
+
+**Response Parsing**:
+- Successful responses indicate acceptance, not delivery to destinations
+- Response data may be nested under `data` key
+- Check for error fields in batch responses for individual message failures
+
+**Timestamps**:
+- Must be ISO 8601 format with timezone (e.g., '2024-01-15T10:30:00Z')
+- Omitting timestamp uses server receive time
+- Historical data imports should include explicit timestamps
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Track event | SEGMENT_TRACK | userId, event, properties |
+| Identify user | SEGMENT_IDENTIFY | userId, traits |
+| Batch calls | SEGMENT_BATCH | batch (array of messages) |
+| Group user | SEGMENT_GROUP | userId, groupId, traits |
+| Page view | SEGMENT_PAGE | userId, name, properties |
+| Alias identity | SEGMENT_ALIAS | userId, previousId |
+| 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/plugins/awesome-claude-skills/segmetrics-automation/SKILL.md b/plugins/awesome-claude-skills/segmetrics-automation/SKILL.md
new file mode 100644
index 0000000..330425f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/seismic-automation/SKILL.md b/plugins/awesome-claude-skills/seismic-automation/SKILL.md
new file mode 100644
index 0000000..17960d4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/semanticscholar-automation/SKILL.md b/plugins/awesome-claude-skills/semanticscholar-automation/SKILL.md
new file mode 100644
index 0000000..33a2146
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/semrush-automation/SKILL.md b/plugins/awesome-claude-skills/semrush-automation/SKILL.md
new file mode 100644
index 0000000..07b8389
--- /dev/null
+++ b/plugins/awesome-claude-skills/semrush-automation/SKILL.md
@@ -0,0 +1,161 @@
+---
+name: SEMrush Automation
+description: "Automate SEO analysis with SEMrush -- research keywords, analyze domain organic rankings, audit backlinks, assess keyword difficulty, and discover related terms through the Composio SEMrush integration."
+requires:
+ mcp:
+ - rube
+---
+
+# SEMrush Automation
+
+Run **SEMrush** SEO analytics directly from Claude Code. Analyze domain keywords, audit backlink profiles, research keyword difficulty, discover related terms, and track organic page performance without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/semrush](https://composio.dev/toolkits/semrush)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Connect your SEMrush account when prompted. The agent will provide an authentication link.
+3. All SEMrush tools require a `database` parameter specifying the regional database (e.g., `us`, `uk`, `de`). Choose the correct region for your target audience.
+
+---
+
+## Core Workflows
+
+### 1. Domain Organic Keywords Analysis
+
+Retrieve all organic search keywords for a domain, including positions, traffic estimates, CPC, and keyword difficulty.
+
+**Tool:** `SEMRUSH_DOMAIN_ORGANIC_SEARCH_KEYWORDS`
+
+Key parameters:
+- `domain` (required) -- e.g., `example.com`
+- `database` (required) -- regional database code (e.g., `us`, `uk`, `de`)
+- `display_limit` (default 10000) and `display_offset` (default 0) -- pagination
+- `display_sort` -- sort by position, traffic, volume, etc. (e.g., `tr_desc` for traffic descending)
+- `display_date` -- historical data in `YYYYMM15` format (monthly) or `YYYYMMDD` (daily)
+- `export_columns` -- specify columns like `Ph` (phrase), `Po` (position), `Nq` (volume), `Tr` (traffic), `Kd` (difficulty)
+- `display_filter` -- filter by specific columns
+
+Example prompt: *"Get the top 100 organic keywords for example.com in the US database, sorted by traffic"*
+
+---
+
+### 2. Keyword Overview and Batch Analysis
+
+Get detailed metrics for individual keywords or analyze up to 100 keywords at once.
+
+**Tools:** `SEMRUSH_KEYWORD_OVERVIEW_ONE_DATABASE`, `SEMRUSH_BATCH_KEYWORD_OVERVIEW`
+
+For single keyword:
+- `phrase` (required) -- keyword to investigate
+- `database` (required) -- regional database
+
+For batch (up to 100 keywords):
+- `phrase` (required) -- semicolon-separated keywords (max 255 chars total)
+- `database` (required) -- regional database
+- `export_columns` -- `Ph` (phrase), `Nq` (volume), `Cp` (CPC), `Co` (competition), `Kd` (difficulty), `In` (intent)
+
+Example prompt: *"Get keyword metrics for 'seo services;content marketing;link building' in the US database"*
+
+---
+
+### 3. Domain Organic Pages Report
+
+Discover which URLs on a domain drive the most organic traffic and visibility.
+
+**Tool:** `SEMRUSH_DOMAIN_ORGANIC_PAGES`
+
+Key parameters:
+- `domain` (required) -- target domain
+- `database` (required) -- regional database
+- `display_sort` -- e.g., `pc_desc` for traffic share descending
+- `display_limit` and `display_offset` -- pagination
+- `export_columns` -- `Ur` (URL), `Pc` (traffic %), `Tg` (traffic), `Tr` (traffic cost)
+
+Example prompt: *"Show the top 50 organic pages for example.com ranked by traffic share"*
+
+---
+
+### 4. Backlink Profile Overview
+
+Get a summary of backlinks for a domain including Authority Score, link types, and referring domain counts.
+
+**Tool:** `SEMRUSH_BACKLINKS_OVERVIEW`
+
+Key parameters:
+- `target` (required) -- domain, subdomain, or full URL
+- `target_type` (required) -- `root_domain`, `domain`, or `url`
+- `export_columns` -- `ascore` (Authority Score), `total` (total backlinks), `domains_num` (referring domains), `follows_num`, `nofollows_num`, etc.
+
+Example prompt: *"Get the backlink overview for example.com including Authority Score and referring domain count"*
+
+---
+
+### 5. Keyword Difficulty Assessment
+
+Score how hard it is to rank in the top 10 for specific keywords (0-100 scale).
+
+**Tool:** `SEMRUSH_KEYWORD_DIFFICULTY`
+
+Key parameters:
+- `phrase` (required) -- keyword to analyze
+- `database` (required) -- regional database
+- `export_columns` -- `Ph` (phrase), `Kd` (difficulty score)
+
+Example prompt: *"What is the keyword difficulty for 'best project management software' in the US?"*
+
+---
+
+### 6. Discover Related Keywords
+
+Find synonyms, variations, and related terms for a seed keyword to expand your content strategy.
+
+**Tool:** `SEMRUSH_RELATED_KEYWORDS`
+
+Key parameters:
+- `phrase` (required) -- seed keyword
+- `database` (required) -- regional database
+- `display_limit` (default 10000) -- max results
+- `display_sort` -- e.g., `nq_desc` for volume descending, `kd_asc` for easiest first
+- `export_columns` -- `Ph`, `Nq`, `Kd`, `Cp`, `Co`, `Rr` (relatedness score)
+
+Example prompt: *"Find related keywords for 'project management' in the US, sorted by search volume"*
+
+---
+
+## Known Pitfalls
+
+- **Pagination is essential:** `SEMRUSH_DOMAIN_ORGANIC_SEARCH_KEYWORDS` and `SEMRUSH_DOMAIN_ORGANIC_PAGES` can return very large datasets. Always use `display_limit` and `display_offset` instead of assuming a single page is complete.
+- **CSV-style responses:** Many SEMrush tools return data as CSV-style text in a single field (e.g., `data/keyword_data`). You must parse rows and columns before analysis or joining reports.
+- **"ERROR 50 :: NOTHING FOUND":** This literal string means the domain or keyword has no data in that database. Treat it as a valid zero-result response, not a transport error.
+- **Batch keyword limits:** `SEMRUSH_BATCH_KEYWORD_OVERVIEW` may return HTTP 400 for problematic or oversized batches (max 255 chars total for the `phrase` field). Shrink batches or fall back to `SEMRUSH_KEYWORD_OVERVIEW_ONE_DATABASE` for individual lookups.
+- **Date format:** Historical dates must use `YYYYMM15` format for monthly data (e.g., `20231015`). Using an incorrect format will return unexpected results.
+- **Regional database matters:** Always use the correct regional database for your target audience. Results for `us` vs `uk` can differ dramatically in volume, CPC, and rankings.
+- **Column codes:** Export columns use short codes (`Ph`, `Nq`, `Kd`, etc.). Avoid over-narrowing `export_columns` so key metrics like traffic, CPC, position, and difficulty are retained.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `SEMRUSH_DOMAIN_ORGANIC_SEARCH_KEYWORDS` | Organic keywords for a domain with positions and traffic |
+| `SEMRUSH_KEYWORD_OVERVIEW_ONE_DATABASE` | Single keyword metrics (volume, CPC, difficulty) |
+| `SEMRUSH_BATCH_KEYWORD_OVERVIEW` | Batch metrics for up to 100 keywords |
+| `SEMRUSH_DOMAIN_ORGANIC_PAGES` | Top organic pages for a domain by traffic |
+| `SEMRUSH_BACKLINKS_OVERVIEW` | Backlink profile summary with Authority Score |
+| `SEMRUSH_BACKLINKS` | Detailed backlinks list for a target |
+| `SEMRUSH_KEYWORD_DIFFICULTY` | Keyword difficulty score (0-100) |
+| `SEMRUSH_RELATED_KEYWORDS` | Related/similar keywords for a seed phrase |
+| `SEMRUSH_CATEGORIES` | Domain categories with confidence ratings |
+| `SEMRUSH_DOMAIN_ORGANIC_SUBDOMAINS` | Subdomain-level organic rankings breakdown |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/sendbird-ai-chabot-automation/SKILL.md b/plugins/awesome-claude-skills/sendbird-ai-chabot-automation/SKILL.md
new file mode 100644
index 0000000..bbc0bf0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sendbird-automation/SKILL.md b/plugins/awesome-claude-skills/sendbird-automation/SKILL.md
new file mode 100644
index 0000000..dfa3857
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sendfox-automation/SKILL.md b/plugins/awesome-claude-skills/sendfox-automation/SKILL.md
new file mode 100644
index 0000000..d2faee3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sendgrid-automation/SKILL.md b/plugins/awesome-claude-skills/sendgrid-automation/SKILL.md
new file mode 100644
index 0000000..37f1cdc
--- /dev/null
+++ b/plugins/awesome-claude-skills/sendgrid-automation/SKILL.md
@@ -0,0 +1,233 @@
+---
+name: sendgrid-automation
+description: Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# SendGrid Automation via Rube MCP
+
+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)
+- Active SendGrid connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendgrid`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sendgrid`
+3. If connection is not ACTIVE, follow the returned auth link to complete SendGrid API key authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Send Marketing Campaigns (Single Sends)
+
+**When to use**: User wants to create and send a marketing email campaign to a contact list or segment.
+
+**Tool sequence**:
+1. `SENDGRID_RETRIEVE_ALL_LISTS` - List available marketing lists to target [Prerequisite]
+2. `SENDGRID_CREATE_A_LIST` - Create a new list if needed [Optional]
+3. `SENDGRID_ADD_OR_UPDATE_A_CONTACT` - Add contacts to the list [Optional]
+4. `SENDGRID_GET_ALL_SENDER_IDENTITIES` - Get verified sender ID [Prerequisite]
+5. `SENDGRID_CREATE_SINGLE_SEND` - Create the campaign with content, sender, and recipients [Required]
+
+**Key parameters for SENDGRID_CREATE_SINGLE_SEND**:
+- `name`: Campaign name (required)
+- `email__config__subject`: Email subject line
+- `email__config__html__content`: HTML body content
+- `email__config__plain__content`: Plain text version
+- `email__config__sender__id`: Verified sender identity ID
+- `email__config__design__id`: Use instead of html_content for pre-built designs
+- `send__to__list__ids`: Array of list UUIDs to send to
+- `send__to__segment__ids`: Array of segment UUIDs
+- `send__to__all`: true to send to all contacts
+- `email__config__suppression__group__id` or `email__config__custom__unsubscribe__url`: One required for compliance
+
+**Pitfalls**:
+- Setting `send_at` on CREATE does NOT schedule the send; it only prepopulates the UI date; use the Schedule endpoint separately
+- `send_at: "now"` is only valid with the Schedule endpoint, not CREATE
+- Must provide either `suppression_group_id` or `custom_unsubscribe_url` for unsubscribe compliance
+- Sender must be verified before use; check with `SENDGRID_GET_ALL_SENDER_IDENTITIES`
+- Nested params use double-underscore notation (e.g., `email__config__subject`)
+
+### 2. Manage Contacts and Lists
+
+**When to use**: User wants to create contact lists, add/update contacts, search for contacts, or remove contacts from lists.
+
+**Tool sequence**:
+1. `SENDGRID_RETRIEVE_ALL_LISTS` - List all marketing lists [Required]
+2. `SENDGRID_CREATE_A_LIST` - Create a new contact list [Optional]
+3. `SENDGRID_GET_A_LIST_BY_ID` - Get list details and sample contacts [Optional]
+4. `SENDGRID_ADD_OR_UPDATE_A_CONTACT` - Upsert contacts with list association [Required]
+5. `SENDGRID_GET_CONTACTS_BY_EMAILS` - Look up contacts by email [Optional]
+6. `SENDGRID_GET_CONTACTS_BY_IDENTIFIERS` - Look up contacts by email, phone, or external ID [Optional]
+7. `SENDGRID_GET_LIST_CONTACT_COUNT` - Verify contact count after operations [Optional]
+8. `SENDGRID_REMOVE_CONTACTS_FROM_A_LIST` - Remove contacts from a list without deleting [Optional]
+9. `SENDGRID_REMOVE_LIST_AND_OPTIONAL_CONTACTS` - Delete an entire list [Optional]
+10. `SENDGRID_IMPORT_CONTACTS` - Bulk import from CSV [Optional]
+
+**Key parameters for SENDGRID_ADD_OR_UPDATE_A_CONTACT**:
+- `contacts`: Array of contact objects (max 30,000 or 6MB), each with at least one identifier: `email`, `phone_number_id`, `external_id`, or `anonymous_id` (required)
+- `list_ids`: Array of list UUID strings to associate contacts with
+
+**Pitfalls**:
+- `SENDGRID_ADD_OR_UPDATE_A_CONTACT` is asynchronous; returns 202 with `job_id`; contacts may take 10-30 seconds to appear
+- List IDs are UUIDs (e.g., "ca7a3796-e8a8-4029-9ccb-df8937940562"), not integers
+- List names must be unique; duplicate names cause 400 errors
+- `SENDGRID_ADD_A_SINGLE_RECIPIENT_TO_A_LIST` uses the legacy API; prefer `SENDGRID_ADD_OR_UPDATE_A_CONTACT` with `list_ids`
+- `SENDGRID_REMOVE_LIST_AND_OPTIONAL_CONTACTS` is irreversible; require explicit user confirmation
+- Email addresses are automatically lowercased by SendGrid
+
+### 3. Manage Sender Identities
+
+**When to use**: User wants to set up or view sender identities (From addresses) for sending emails.
+
+**Tool sequence**:
+1. `SENDGRID_GET_ALL_SENDER_IDENTITIES` - List all existing sender identities [Required]
+2. `SENDGRID_CREATE_A_SENDER_IDENTITY` - Create a new sender identity [Optional]
+3. `SENDGRID_VIEW_A_SENDER_IDENTITY` - View details for a specific sender [Optional]
+4. `SENDGRID_UPDATE_A_SENDER_IDENTITY` - Update sender details [Optional]
+5. `SENDGRID_CREATE_VERIFIED_SENDER_REQUEST` - Create and verify a new sender [Optional]
+6. `SENDGRID_AUTHENTICATE_A_DOMAIN` - Set up domain authentication for auto-verification [Optional]
+
+**Key parameters for SENDGRID_CREATE_A_SENDER_IDENTITY**:
+- `from__email`: From email address (required)
+- `from__name`: Display name (required)
+- `reply__to__email`: Reply-to address (required)
+- `nickname`: Internal identifier (required)
+- `address`, `city`, `country`: Physical address for CAN-SPAM compliance (required)
+
+**Pitfalls**:
+- New senders must be verified before use; if domain is not authenticated, a verification email is sent
+- Up to 100 unique sender identities per account
+- Avoid using domains with strict DMARC policies (gmail.com, yahoo.com) as from addresses
+- `SENDGRID_CREATE_VERIFIED_SENDER_REQUEST` sends a verification email; sender is unusable until verified
+
+### 4. View Email Statistics and Activity
+
+**When to use**: User wants to review email delivery stats, bounce rates, open/click metrics, or message activity.
+
+**Tool sequence**:
+1. `SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS` - Get account-wide delivery metrics [Required]
+2. `SENDGRID_GET_ALL_CATEGORIES` - Discover available categories for filtering [Optional]
+3. `SENDGRID_RETRIEVE_EMAIL_STATISTICS_FOR_CATEGORIES` - Get stats broken down by category [Optional]
+4. `SENDGRID_FILTER_ALL_MESSAGES` - Search email activity feed by recipient, status, or date [Optional]
+5. `SENDGRID_FILTER_MESSAGES_BY_MESSAGE_ID` - Get detailed events for a specific message [Optional]
+6. `SENDGRID_REQUEST_CSV` - Export activity data as CSV for large datasets [Optional]
+7. `SENDGRID_DOWNLOAD_CSV` - Download the exported CSV file [Optional]
+
+**Key parameters for SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS**:
+- `start_date`: Start date YYYY-MM-DD (required)
+- `end_date`: End date YYYY-MM-DD
+- `aggregated_by`: "day", "week", or "month"
+- `limit` / `offset`: Pagination (default 500)
+
+**Key parameters for SENDGRID_FILTER_ALL_MESSAGES**:
+- `query`: SQL-like query string, e.g., `status="delivered"`, `to_email="user@example.com"`, date ranges with `BETWEEN TIMESTAMP`
+- `limit`: 1-1000 (default 10)
+
+**Pitfalls**:
+- `SENDGRID_FILTER_ALL_MESSAGES` requires the "30 Days Additional Email Activity History" paid add-on; returns 403 without it
+- Global statistics are nested under `details[].stats[0].metrics`, not a flat structure
+- Category statistics are only available for the previous 13 months
+- Maximum 10 categories per request in `SENDGRID_RETRIEVE_EMAIL_STATISTICS_FOR_CATEGORIES`
+- CSV export is limited to one request per 12 hours; link expires after 3 days
+
+### 5. Manage Suppressions
+
+**When to use**: User wants to check or manage unsubscribe groups for email compliance.
+
+**Tool sequence**:
+1. `SENDGRID_GET_SUPPRESSION_GROUPS` - List all suppression groups [Required]
+2. `SENDGRID_RETRIEVE_ALL_SUPPRESSION_GROUPS_FOR_AN_EMAIL_ADDRESS` - Check suppression status for a specific email [Optional]
+
+**Pitfalls**:
+- Suppressed addresses remain undeliverable even if present on marketing lists
+- Campaign send counts may be lower than list counts due to suppressions
+
+## Common Patterns
+
+### ID Resolution
+Always resolve names to IDs before operations:
+- **List name -> list_id**: `SENDGRID_RETRIEVE_ALL_LISTS` and match by name
+- **Sender name -> sender_id**: `SENDGRID_GET_ALL_SENDER_IDENTITIES` and match
+- **Contact email -> contact_id**: `SENDGRID_GET_CONTACTS_BY_EMAILS` with email array
+- **Template name -> template_id**: Use the SendGrid UI or template endpoints
+
+### Pagination
+- `SENDGRID_RETRIEVE_ALL_LISTS`: Token-based with `page_token` and `page_size` (max 1000)
+- `SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS`: Offset-based with `limit` (max 500) and `offset`
+- Always paginate list retrieval to avoid missing existing lists
+
+### Async Operations
+Contact operations (`ADD_OR_UPDATE_A_CONTACT`, `IMPORT_CONTACTS`) are asynchronous:
+- Returns 202 with a `job_id`
+- Wait 10-30 seconds before verifying with `GET_CONTACTS_BY_EMAILS`
+- Use `GET_LIST_CONTACT_COUNT` to confirm list growth
+
+## Known Pitfalls
+
+### ID Formats
+- Marketing list IDs are UUIDs (e.g., "ca7a3796-e8a8-4029-9ccb-df8937940562")
+- Legacy list IDs are integers; do not mix with Marketing API endpoints
+- Sender identity IDs are integers
+- Template IDs: Dynamic templates start with "d-", legacy templates are UUIDs
+- Contact IDs are UUIDs
+
+### Rate Limits
+- SendGrid may return HTTP 429; respect `Retry-After` headers
+- CSV export limited to one request per 12 hours
+- Bulk contact upsert max: 30,000 contacts or 6MB per request
+
+### Parameter Quirks
+- Nested params use double-underscore: `email__config__subject`, `from__email`
+- `send_at` on CREATE_SINGLE_SEND only sets a UI default, does NOT schedule
+- `SENDGRID_ADD_A_SINGLE_RECIPIENT_TO_A_LIST` uses legacy API; `recipient_id` is Base64-encoded lowercase email
+- `SENDGRID_RETRIEVE_ALL_LISTS` and `SENDGRID_GET_ALL_LISTS` both exist; prefer RETRIEVE_ALL_LISTS for Marketing API
+- Contact adds are async (202); always verify after a delay
+
+### Legacy vs Marketing API
+- Some tools use the legacy Contact Database API (`/v3/contactdb/`) which may return 403 on newer accounts
+- Prefer Marketing API tools: `SENDGRID_ADD_OR_UPDATE_A_CONTACT`, `SENDGRID_RETRIEVE_ALL_LISTS`, `SENDGRID_CREATE_SINGLE_SEND`
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List marketing lists | `SENDGRID_RETRIEVE_ALL_LISTS` | `page_size`, `page_token` |
+| Create list | `SENDGRID_CREATE_A_LIST` | `name` |
+| Get list by ID | `SENDGRID_GET_A_LIST_BY_ID` | `id` |
+| Get list count | `SENDGRID_GET_LIST_CONTACT_COUNT` | `id` |
+| Add/update contacts | `SENDGRID_ADD_OR_UPDATE_A_CONTACT` | `contacts`, `list_ids` |
+| Search contacts by email | `SENDGRID_GET_CONTACTS_BY_EMAILS` | `emails` |
+| Search by identifiers | `SENDGRID_GET_CONTACTS_BY_IDENTIFIERS` | `identifier_type`, `identifiers` |
+| Remove from list | `SENDGRID_REMOVE_CONTACTS_FROM_A_LIST` | `id`, `contact_ids` |
+| Delete list | `SENDGRID_REMOVE_LIST_AND_OPTIONAL_CONTACTS` | `id`, `delete_contacts` |
+| Import contacts CSV | `SENDGRID_IMPORT_CONTACTS` | field mappings |
+| Create Single Send | `SENDGRID_CREATE_SINGLE_SEND` | `name`, `email__config__*`, `send__to__list__ids` |
+| List sender identities | `SENDGRID_GET_ALL_SENDER_IDENTITIES` | (none) |
+| Create sender | `SENDGRID_CREATE_A_SENDER_IDENTITY` | `from__email`, `from__name`, `address` |
+| Verify sender | `SENDGRID_CREATE_VERIFIED_SENDER_REQUEST` | `from_email`, `nickname`, `address` |
+| Authenticate domain | `SENDGRID_AUTHENTICATE_A_DOMAIN` | `domain` |
+| Global email stats | `SENDGRID_RETRIEVE_GLOBAL_EMAIL_STATISTICS` | `start_date`, `aggregated_by` |
+| Category stats | `SENDGRID_RETRIEVE_EMAIL_STATISTICS_FOR_CATEGORIES` | `start_date`, `categories` |
+| Filter email activity | `SENDGRID_FILTER_ALL_MESSAGES` | `query`, `limit` |
+| Message details | `SENDGRID_FILTER_MESSAGES_BY_MESSAGE_ID` | `msg_id` |
+| Export CSV | `SENDGRID_REQUEST_CSV` | `query` |
+| Download CSV | `SENDGRID_DOWNLOAD_CSV` | `download_uuid` |
+| List categories | `SENDGRID_GET_ALL_CATEGORIES` | (none) |
+| 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/plugins/awesome-claude-skills/sendlane-automation/SKILL.md b/plugins/awesome-claude-skills/sendlane-automation/SKILL.md
new file mode 100644
index 0000000..2948a01
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sendloop-automation/SKILL.md b/plugins/awesome-claude-skills/sendloop-automation/SKILL.md
new file mode 100644
index 0000000..6dc607e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sendspark-automation/SKILL.md b/plugins/awesome-claude-skills/sendspark-automation/SKILL.md
new file mode 100644
index 0000000..6235ae5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sensibo-automation/SKILL.md b/plugins/awesome-claude-skills/sensibo-automation/SKILL.md
new file mode 100644
index 0000000..245dac6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sentry-automation/SKILL.md b/plugins/awesome-claude-skills/sentry-automation/SKILL.md
new file mode 100644
index 0000000..0f5da0e
--- /dev/null
+++ b/plugins/awesome-claude-skills/sentry-automation/SKILL.md
@@ -0,0 +1,237 @@
+---
+name: sentry-automation
+description: "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Sentry Automation via Rube MCP
+
+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)
+- Active Sentry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`
+3. If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Investigate Issues
+
+**When to use**: User wants to find, inspect, or triage error issues
+
+**Tool sequence**:
+1. `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` - List issues across the organization [Required]
+2. `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` - Get detailed info on a specific issue [Optional]
+3. `SENTRY_LIST_AN_ISSUES_EVENTS` - View individual error events for an issue [Optional]
+4. `SENTRY_RETRIEVE_AN_ISSUE_EVENT` - Get full event details with stack trace [Optional]
+5. `SENTRY_RETRIEVE_ISSUE_TAG_DETAILS` - Inspect tag distribution for an issue [Optional]
+
+**Key parameters**:
+- `organization_id_or_slug`: Organization identifier
+- `issue_id`: Numeric issue ID
+- `query`: Search query (e.g., `is:unresolved`, `assigned:me`, `browser:Chrome`)
+- `sort`: Sort order (`date`, `new`, `freq`, `priority`)
+- `statsPeriod`: Time window for stats (`24h`, `14d`, etc.)
+
+**Pitfalls**:
+- `organization_id_or_slug` is the org slug (e.g., 'my-org'), not the display name
+- Issue IDs are numeric; do not confuse with event IDs which are UUIDs
+- Query syntax uses Sentry's search format: `is:unresolved`, `assigned:me`, `!has:release`
+- Events within an issue can have different stack traces; inspect individual events for details
+
+### 2. Manage Project Issues
+
+**When to use**: User wants to view issues scoped to a specific project
+
+**Tool sequence**:
+1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - List projects to find project slug [Prerequisite]
+2. `SENTRY_RETRIEVE_PROJECT_ISSUES_LIST` - List issues for a specific project [Required]
+3. `SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID` - Get events for a specific issue [Optional]
+
+**Key parameters**:
+- `organization_id_or_slug`: Organization identifier
+- `project_id_or_slug`: Project identifier
+- `query`: Search filter string
+- `statsPeriod`: Stats time window
+
+**Pitfalls**:
+- Project slugs are different from project display names
+- Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first
+- Project-scoped issue lists may have different pagination than org-scoped lists
+
+### 3. Configure Alert Rules
+
+**When to use**: User wants to create or manage alert rules for a project
+
+**Tool sequence**:
+1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - Find project for the alert [Prerequisite]
+2. `SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID` - List existing rules [Optional]
+3. `SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS` - Create a new alert rule [Required]
+4. `SENTRY_CREATE_ORGANIZATION_ALERT_RULE` - Create org-level metric alert [Alternative]
+5. `SENTRY_UPDATE_ORGANIZATION_ALERT_RULES` - Update existing alert rules [Optional]
+6. `SENTRY_RETRIEVE_ALERT_RULE_DETAILS` - Inspect specific alert rule [Optional]
+7. `SENTRY_GET_PROJECT_RULE_DETAILS` - Get project-level rule details [Optional]
+
+**Key parameters**:
+- `name`: Alert rule name
+- `conditions`: Array of trigger conditions
+- `actions`: Array of actions to perform when triggered
+- `filters`: Array of event filters
+- `frequency`: How often to trigger (in minutes)
+- `actionMatch`: 'all', 'any', or 'none' for condition matching
+
+**Pitfalls**:
+- Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different
+- Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types
+- `frequency` is in minutes; setting too low causes alert fatigue
+- `actionMatch` defaults may vary; explicitly set to avoid unexpected behavior
+
+### 4. Manage Releases
+
+**When to use**: User wants to create, track, or manage release versions
+
+**Tool sequence**:
+1. `SENTRY_LIST_ORGANIZATION_RELEASES` - List existing releases [Optional]
+2. `SENTRY_CREATE_RELEASE_FOR_ORGANIZATION` - Create a new release [Required]
+3. `SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION` - Update release metadata [Optional]
+4. `SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG` - Record a deployment for a release [Optional]
+5. `SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION` - Upload source maps or files [Optional]
+
+**Key parameters**:
+- `version`: Release version string (e.g., '1.0.0', commit SHA)
+- `projects`: Array of project slugs this release belongs to
+- `dateReleased`: Release timestamp (ISO 8601)
+- `environment`: Deployment environment name (e.g., 'production', 'staging')
+
+**Pitfalls**:
+- Release versions must be unique within an organization
+- Releases can span multiple projects; use the `projects` array
+- Deploying a release is separate from creating it; use CREATE_RELEASE_DEPLOY
+- Source map uploads require the release to exist first
+
+### 5. Monitor Organization and Teams
+
+**When to use**: User wants to view org structure, teams, or member lists
+
+**Tool sequence**:
+1. `SENTRY_GET_ORGANIZATION_DETAILS` or `SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG` - Get org info [Required]
+2. `SENTRY_LIST_TEAMS_IN_ORGANIZATION` - List all teams [Optional]
+3. `SENTRY_LIST_ORGANIZATION_MEMBERS` - List org members [Optional]
+4. `SENTRY_GET_PROJECT_LIST` - List all accessible projects [Optional]
+
+**Key parameters**:
+- `organization_id_or_slug`: Organization identifier
+- `cursor`: Pagination cursor for large result sets
+
+**Pitfalls**:
+- Organization slugs are URL-safe identifiers, not display names
+- Member lists may be paginated; follow cursor pagination
+- Team and member visibility depends on the authenticated user's permissions
+
+### 6. Manage Monitors (Cron Monitoring)
+
+**When to use**: User wants to update cron job monitoring configuration
+
+**Tool sequence**:
+1. `SENTRY_UPDATE_A_MONITOR` - Update monitor configuration [Required]
+
+**Key parameters**:
+- `organization_id_or_slug`: Organization identifier
+- `monitor_id_or_slug`: Monitor identifier
+- `name`: Monitor display name
+- `schedule`: Cron schedule expression or interval
+- `checkin_margin`: Grace period in minutes for late check-ins
+- `max_runtime`: Maximum expected runtime in minutes
+
+**Pitfalls**:
+- Monitor slugs are auto-generated from the name; use slug for API calls
+- Schedule changes take effect immediately
+- Missing check-ins trigger alerts after the margin period
+
+## Common Patterns
+
+### ID Resolution
+
+**Organization name -> Slug**:
+```
+1. Call SENTRY_GET_ORGANIZATION_DETAILS
+2. Extract slug field from response
+```
+
+**Project name -> Slug**:
+```
+1. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
+2. Find project by name, extract slug
+```
+
+### Pagination
+
+- Sentry uses cursor-based pagination with `Link` headers
+- Check response for cursor values
+- Pass cursor in next request until no more pages
+
+### Search Query Syntax
+
+- `is:unresolved` - Unresolved issues
+- `is:resolved` - Resolved issues
+- `assigned:me` - Assigned to current user
+- `assigned:team-slug` - Assigned to a team
+- `!has:release` - Issues without a release
+- `first-release:1.0.0` - Issues first seen in release
+- `times-seen:>100` - Seen more than 100 times
+- `browser:Chrome` - Filter by browser tag
+
+## Known Pitfalls
+
+**ID Formats**:
+- Organization: use slug (e.g., 'my-org'), not display name
+- Project: use slug (e.g., 'my-project'), not display name
+- Issue IDs: numeric integers
+- Event IDs: UUIDs (32-char hex strings)
+
+**Permissions**:
+- API token scopes must match the operations being performed
+- Organization-level operations require org-level permissions
+- Project-level operations require project access
+
+**Rate Limits**:
+- Sentry enforces per-organization rate limits
+- Implement backoff on 429 responses
+- Bulk operations should be staggered
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List org issues | SENTRY_LIST_AN_ORGANIZATIONS_ISSUES | organization_id_or_slug, query |
+| Get issue details | SENTRY_GET_ORGANIZATION_ISSUE_DETAILS | organization_id_or_slug, issue_id |
+| List issue events | SENTRY_LIST_AN_ISSUES_EVENTS | issue_id |
+| Get event details | SENTRY_RETRIEVE_AN_ISSUE_EVENT | organization_id_or_slug, event_id |
+| List project issues | SENTRY_RETRIEVE_PROJECT_ISSUES_LIST | organization_id_or_slug, project_id_or_slug |
+| List projects | SENTRY_RETRIEVE_ORGANIZATION_PROJECTS | organization_id_or_slug |
+| Get org details | SENTRY_GET_ORGANIZATION_DETAILS | organization_id_or_slug |
+| List teams | SENTRY_LIST_TEAMS_IN_ORGANIZATION | organization_id_or_slug |
+| List members | SENTRY_LIST_ORGANIZATION_MEMBERS | organization_id_or_slug |
+| Create alert rule | SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS | organization_id_or_slug, project_id_or_slug |
+| Create metric alert | SENTRY_CREATE_ORGANIZATION_ALERT_RULE | organization_id_or_slug |
+| Create release | SENTRY_CREATE_RELEASE_FOR_ORGANIZATION | organization_id_or_slug, version |
+| 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/plugins/awesome-claude-skills/seqera-automation/SKILL.md b/plugins/awesome-claude-skills/seqera-automation/SKILL.md
new file mode 100644
index 0000000..017c00e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/serpapi-automation/SKILL.md b/plugins/awesome-claude-skills/serpapi-automation/SKILL.md
new file mode 100644
index 0000000..42ca790
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/serpdog-automation/SKILL.md b/plugins/awesome-claude-skills/serpdog-automation/SKILL.md
new file mode 100644
index 0000000..25ad2b1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/serply-automation/SKILL.md b/plugins/awesome-claude-skills/serply-automation/SKILL.md
new file mode 100644
index 0000000..c5b4cd4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/servicem8-automation/SKILL.md b/plugins/awesome-claude-skills/servicem8-automation/SKILL.md
new file mode 100644
index 0000000..6175ee0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sevdesk-automation/SKILL.md b/plugins/awesome-claude-skills/sevdesk-automation/SKILL.md
new file mode 100644
index 0000000..d322199
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/share-point-automation/SKILL.md b/plugins/awesome-claude-skills/share-point-automation/SKILL.md
new file mode 100644
index 0000000..c28358d
--- /dev/null
+++ b/plugins/awesome-claude-skills/share-point-automation/SKILL.md
@@ -0,0 +1,197 @@
+---
+name: SharePoint Automation
+description: "SharePoint Automation: manage sites, lists, documents, folders, pages, and search content across SharePoint and OneDrive"
+requires:
+ mcp: [rube]
+---
+
+# SharePoint Automation
+
+Automate SharePoint operations including managing sites, lists, documents, folders, and pages. Integrates with both SharePoint REST API and Microsoft Graph via OneDrive.
+
+**Toolkit docs:** [composio.dev/toolkits/share_point](https://composio.dev/toolkits/share_point)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure active connections exist for the `share_point` and `one_drive` toolkits. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+> **Note:** Many OneDrive/SharePoint tools only work with organizational Microsoft 365 accounts (Azure AD/Entra ID). Personal Microsoft accounts are NOT supported.
+
+---
+
+## Core Workflows
+
+### 1. List and Browse Sites
+
+Retrieve site details and enumerate subsites to discover the SharePoint topology.
+
+**Tools:**
+- `ONE_DRIVE_GET_SITE_DETAILS` -- Get metadata for a specific site by ID
+- `ONE_DRIVE_LIST_SITE_SUBSITES` -- List all subsites of a parent site
+
+**Key Parameters:**
+- `site_id` (required) -- Composite format: `hostname,site-collection-guid,web-guid` (e.g., `"contoso.sharepoint.com,da60e844-...,712a596e-..."`)
+
+**Example:**
+```
+Tool: ONE_DRIVE_GET_SITE_DETAILS
+Arguments:
+ site_id: "contoso.sharepoint.com,2C712604-1370-44E7-A1F5-426573FDA80A,2D2244C3-251A-49EA-93A8-39E1C3A060FE"
+```
+
+---
+
+### 2. Manage Lists
+
+Create lists, enumerate existing lists, and retrieve list items.
+
+**Tools:**
+- `SHARE_POINT_LIST_ALL_LISTS` -- Retrieve all lists on a site (supports OData filter, select, orderby, top)
+- `SHARE_POINT_SHAREPOINT_CREATE_LIST` -- Create a new list with a specified template
+- `ONE_DRIVE_LIST_SITE_LISTS` -- List all lists under a site via Microsoft Graph
+- `ONE_DRIVE_GET_SHAREPOINT_LIST_ITEMS` -- Retrieve items from a specific list
+
+**Key Parameters for `SHARE_POINT_SHAREPOINT_CREATE_LIST`:**
+- `name` (required) -- List name
+- `template` (required) -- Template type: `"genericList"`, `"documentLibrary"`, `"tasks"`, etc.
+- `description` -- Optional description
+
+**Key Parameters for `SHARE_POINT_LIST_ALL_LISTS`:**
+- `filter` -- OData filter, e.g., `"Hidden eq false"`
+- `select` -- Properties to return, e.g., `"Title,Id"`
+- `orderby` -- Sort expression, e.g., `"Title desc"`
+- `top` -- Limit results count
+
+**Example:**
+```
+Tool: SHARE_POINT_SHAREPOINT_CREATE_LIST
+Arguments:
+ name: "Project Tasks"
+ template: "tasks"
+ description: "Task tracking for Q1 deliverables"
+```
+
+---
+
+### 3. Manage Folders and Files
+
+Create folders, list files within folders, and navigate the document library.
+
+**Tools:**
+- `SHARE_POINT_SHAREPOINT_CREATE_FOLDER` -- Create a new folder in a document library
+- `SHARE_POINT_LIST_FILES_IN_FOLDER` -- List files within a folder by server-relative URL
+- `SHARE_POINT_GET_FOLDER_BY_SERVER_RELATIVE_URL` -- Get folder metadata by path
+
+**Key Parameters for `SHARE_POINT_SHAREPOINT_CREATE_FOLDER`:**
+- `folder_name` (required) -- Name of the folder to create
+- `document_library` -- Target library (default: `"Shared Documents"`)
+- `relative_path` -- Additional path within the library
+
+**Key Parameters for `SHARE_POINT_LIST_FILES_IN_FOLDER`:**
+- `folder_name` (required) -- Server-relative URL, e.g., `"/Shared Documents"`
+- `select` -- Comma-separated properties, e.g., `"Name,ServerRelativeUrl,Length"`
+- `top` -- Limit results count
+- `orderby` -- Sort expression, e.g., `"Name desc"`
+
+**Example:**
+```
+Tool: SHARE_POINT_LIST_FILES_IN_FOLDER
+Arguments:
+ folder_name: "/Shared Documents/Reports"
+ select: "Name,ServerRelativeUrl,Length"
+ top: 50
+```
+
+---
+
+### 4. Search SharePoint Content
+
+Use Keyword Query Language (KQL) to search documents, list items, and other content across the site.
+
+**Tool:** `SHARE_POINT_SEARCH_QUERY`
+
+**Key Parameters:**
+- `querytext` (required) -- KQL query, e.g., `"project report"`, `"FileType:docx"`, `"Author:\"John Doe\""`
+- `rowlimit` -- Max results per request (default ~50, max 500)
+- `startrow` -- Zero-based offset for pagination
+- `selectproperties` -- Properties to return, e.g., `"Title,Author,Path"`
+- `refinementfilters` -- Narrow results, e.g., `"FileType:equals(\"docx\")"`
+
+**Example:**
+```
+Tool: SHARE_POINT_SEARCH_QUERY
+Arguments:
+ querytext: "IsDocument:1 FileType:pdf"
+ rowlimit: 25
+ selectproperties: "Title,Author,Path,LastModifiedTime"
+```
+
+---
+
+### 5. Track List Changes (Delta Query)
+
+Use delta queries to get incremental changes (created, updated, deleted items) without reading the entire list.
+
+**Tool:** `ONE_DRIVE_LIST_SHAREPOINT_LIST_ITEMS_DELTA`
+
+**Key Parameters:**
+- `site_id` (required) -- Composite site ID
+- `list_id` (required) -- List GUID
+- `token` -- Omit for initial sync; pass `"latest"` for empty response with token; pass previous token for changes since
+- `expand` -- e.g., `"fields($select=ColumnA,ColumnB)"`
+- `top` -- Max items per response
+
+---
+
+### 6. Retrieve Site Page Content
+
+Read modern SharePoint Site Pages content including canvas web parts.
+
+**Tool:** `SHARE_POINT_GET_SITE_PAGE_CONTENT`
+
+**Key Parameters:**
+- `page_file_name` -- File name with `.aspx` extension, e.g., `"Home.aspx"`
+- `item_id` -- Alternative: list item ID of the page
+- `render_as` -- `"raw"` (default), `"text"`, or `"html"`
+- `site` -- Optional site name scope
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **Site ID format** | Must be composite: `hostname,site-collection-guid,web-guid`. Incorrect format causes 400 errors. |
+| **Personal accounts unsupported** | `ONE_DRIVE_LIST_SITE_LISTS` and Graph-based tools only work with organizational M365 accounts, not personal MSA/Outlook.com accounts. |
+| **OData filter syntax** | SharePoint OData filters use specific syntax. Test filters incrementally; unsupported expressions may silently return empty results. |
+| **Pagination** | Use `skiptoken` for server-side paging in list operations. Incomplete pagination settings can miss results. |
+| **Folder paths** | Must use server-relative URLs (e.g., `/Shared Documents`) not absolute URLs. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `ONE_DRIVE_GET_SITE_DETAILS` | Get metadata for a SharePoint site |
+| `ONE_DRIVE_LIST_SITE_SUBSITES` | List subsites of a parent site |
+| `ONE_DRIVE_LIST_SITE_LISTS` | List all lists under a site (Graph API) |
+| `ONE_DRIVE_LIST_SHAREPOINT_LIST_ITEMS_DELTA` | Track incremental list changes |
+| `ONE_DRIVE_GET_SHAREPOINT_LIST_ITEMS` | Retrieve items from a list |
+| `ONE_DRIVE_LIST_DRIVES` | List available drives for a user/site/group |
+| `ONE_DRIVE_LIST_SITE_COLUMNS` | List column definitions for a site |
+| `SHARE_POINT_LIST_ALL_LISTS` | Retrieve all lists on a site (REST API) |
+| `SHARE_POINT_SHAREPOINT_CREATE_LIST` | Create a new SharePoint list |
+| `SHARE_POINT_SHAREPOINT_CREATE_FOLDER` | Create a folder in a document library |
+| `SHARE_POINT_LIST_FILES_IN_FOLDER` | List files in a folder |
+| `SHARE_POINT_SEARCH_QUERY` | Search content using KQL |
+| `SHARE_POINT_GET_SITE_PAGE_CONTENT` | Retrieve Site Page content |
+| `SHARE_POINT_GET_FOLDER_BY_SERVER_RELATIVE_URL` | Get folder metadata by path |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/share_point-automation/SKILL.md b/plugins/awesome-claude-skills/share_point-automation/SKILL.md
new file mode 100644
index 0000000..8bdfaf0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/shipengine-automation/SKILL.md b/plugins/awesome-claude-skills/shipengine-automation/SKILL.md
new file mode 100644
index 0000000..83023d6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/shopify-automation/SKILL.md b/plugins/awesome-claude-skills/shopify-automation/SKILL.md
new file mode 100644
index 0000000..1f4f0be
--- /dev/null
+++ b/plugins/awesome-claude-skills/shopify-automation/SKILL.md
@@ -0,0 +1,173 @@
+---
+name: shopify-automation
+description: "Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Shopify Automation via Rube MCP
+
+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)
+- Active Shopify connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `shopify`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `shopify`
+3. If connection is not ACTIVE, follow the returned auth link to complete Shopify OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Products
+
+**When to use**: User wants to list, search, create, or manage products
+
+**Tool sequence**:
+1. `SHOPIFY_GET_PRODUCTS` / `SHOPIFY_GET_PRODUCTS_PAGINATED` - List products [Optional]
+2. `SHOPIFY_GET_PRODUCT` - Get single product details [Optional]
+3. `SHOPIFY_BULK_CREATE_PRODUCTS` - Create products in bulk [Optional]
+4. `SHOPIFY_GET_PRODUCTS_COUNT` - Get product count [Optional]
+
+**Key parameters**:
+- `product_id`: Product ID for single retrieval
+- `title`: Product title
+- `vendor`: Product vendor
+- `status`: 'active', 'draft', or 'archived'
+
+**Pitfalls**:
+- Paginated results require cursor-based pagination for large catalogs
+- Product variants are nested within the product object
+
+### 2. Manage Orders
+
+**When to use**: User wants to list, search, or inspect orders
+
+**Tool sequence**:
+1. `SHOPIFY_GET_ORDERS_WITH_FILTERS` - List orders with filters [Required]
+2. `SHOPIFY_GET_ORDER` - Get single order details [Optional]
+3. `SHOPIFY_GET_FULFILLMENT` - Get fulfillment details [Optional]
+4. `SHOPIFY_GET_FULFILLMENT_EVENTS` - Track fulfillment events [Optional]
+
+**Key parameters**:
+- `status`: Order status filter ('any', 'open', 'closed', 'cancelled')
+- `financial_status`: Payment status filter
+- `fulfillment_status`: Fulfillment status filter
+- `order_id`: Order ID for single retrieval
+- `created_at_min`/`created_at_max`: Date range filters
+
+**Pitfalls**:
+- Order IDs are numeric; use string format for API calls
+- Default order listing may not include all statuses; specify 'any' for all
+
+### 3. Manage Customers
+
+**When to use**: User wants to list or search customers
+
+**Tool sequence**:
+1. `SHOPIFY_GET_ALL_CUSTOMERS` - List all customers [Required]
+
+**Key parameters**:
+- `limit`: Number of customers per page
+- `since_id`: Pagination cursor
+
+**Pitfalls**:
+- Customer data includes order count and total spent
+- Large customer lists require pagination
+
+### 4. Manage Collections
+
+**When to use**: User wants to manage product collections
+
+**Tool sequence**:
+1. `SHOPIFY_GET_SMART_COLLECTIONS` - List smart collections [Optional]
+2. `SHOPIFY_GET_SMART_COLLECTION_BY_ID` - Get collection details [Optional]
+3. `SHOPIFY_CREATE_SMART_COLLECTIONS` - Create a smart collection [Optional]
+4. `SHOPIFY_ADD_PRODUCT_TO_COLLECTION` - Add product to collection [Optional]
+5. `SHOPIFY_GET_PRODUCTS_IN_COLLECTION` - List products in collection [Optional]
+
+**Key parameters**:
+- `collection_id`: Collection ID
+- `product_id`: Product ID for adding to collection
+- `rules`: Smart collection rules for automatic inclusion
+
+**Pitfalls**:
+- Smart collections auto-populate based on rules; manual collections use custom collections API
+- Collection count endpoints provide approximate counts
+
+### 5. Manage Inventory
+
+**When to use**: User wants to check or manage inventory levels
+
+**Tool sequence**:
+1. `SHOPIFY_GET_INVENTORY_LEVELS` / `SHOPIFY_RETRIEVES_A_LIST_OF_INVENTORY_LEVELS` - Check stock [Required]
+2. `SHOPIFY_LIST_LOCATION` - List store locations [Optional]
+
+**Key parameters**:
+- `inventory_item_ids`: Inventory item IDs to check
+- `location_ids`: Location IDs to filter by
+
+**Pitfalls**:
+- Inventory is tracked per variant per location
+- Location IDs are required for multi-location stores
+
+## Common Patterns
+
+### Pagination
+
+- Use `limit` and `page_info` cursor for paginated results
+- Check response for `next` link header
+- Continue until no more pages available
+
+### GraphQL Queries
+
+For advanced operations:
+```
+1. Call SHOPIFY_GRAPH_QL_QUERY with custom query
+2. Parse response from data object
+```
+
+## Known Pitfalls
+
+**API Versioning**:
+- Shopify REST API has versioned endpoints
+- Some features require specific API versions
+
+**Rate Limits**:
+- REST API: 2 requests/second for standard plans
+- GraphQL: 1000 cost points per second
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List products | SHOPIFY_GET_PRODUCTS | (filters) |
+| Get product | SHOPIFY_GET_PRODUCT | product_id |
+| Products paginated | SHOPIFY_GET_PRODUCTS_PAGINATED | limit, page_info |
+| Bulk create | SHOPIFY_BULK_CREATE_PRODUCTS | products |
+| Product count | SHOPIFY_GET_PRODUCTS_COUNT | (none) |
+| List orders | SHOPIFY_GET_ORDERS_WITH_FILTERS | status, financial_status |
+| Get order | SHOPIFY_GET_ORDER | order_id |
+| List customers | SHOPIFY_GET_ALL_CUSTOMERS | limit |
+| Shop details | SHOPIFY_GET_SHOP_DETAILS | (none) |
+| Validate access | SHOPIFY_VALIDATE_ACCESS | (none) |
+| Smart collections | SHOPIFY_GET_SMART_COLLECTIONS | (none) |
+| Products in collection | SHOPIFY_GET_PRODUCTS_IN_COLLECTION | collection_id |
+| Inventory levels | SHOPIFY_GET_INVENTORY_LEVELS | inventory_item_ids |
+| Locations | SHOPIFY_LIST_LOCATION | (none) |
+| 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/plugins/awesome-claude-skills/short-io-automation/SKILL.md b/plugins/awesome-claude-skills/short-io-automation/SKILL.md
new file mode 100644
index 0000000..e68178f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/short-menu-automation/SKILL.md b/plugins/awesome-claude-skills/short-menu-automation/SKILL.md
new file mode 100644
index 0000000..dfe4db6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/shortcut-automation/SKILL.md b/plugins/awesome-claude-skills/shortcut-automation/SKILL.md
new file mode 100644
index 0000000..a76f328
--- /dev/null
+++ b/plugins/awesome-claude-skills/shortcut-automation/SKILL.md
@@ -0,0 +1,158 @@
+---
+name: Shortcut Automation
+description: "Automate project management workflows in Shortcut -- create stories, manage tasks, track epics, and organize workflows through natural language commands."
+requires:
+ mcp:
+ - rube
+---
+
+# Shortcut Automation
+
+Automate your Shortcut project management operations directly from Claude Code. Create and list stories, add tasks and comments, batch-create stories, and navigate workflows -- all without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/shortcut](https://composio.dev/toolkits/shortcut)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your Claude Code config with URL: `https://rube.app/mcp`
+2. When prompted, authenticate your Shortcut account through the connection link provided
+3. Start automating your project management workflows with natural language
+
+---
+
+## Core Workflows
+
+### 1. Create Stories
+
+Add new stories to your Shortcut workspace with full configuration.
+
+**Tool:** `SHORTCUT_CREATE_STORY`
+
+```
+Create a feature story called "Add dark mode support" in workflow state 500000001 with estimate 5 and label "frontend"
+```
+
+Key parameters for `SHORTCUT_CREATE_STORY`:
+- `name` (required) -- the story title
+- `workflow_state_id` -- the workflow state to place the story in (recommended over `project_id`)
+- `story_type` -- `"feature"`, `"bug"`, or `"chore"`
+- `description` -- story body/description
+- `estimate` -- numeric point estimate (or null for unestimated)
+- `epic_id` -- associate with an epic
+- `iteration_id` -- associate with an iteration
+- `labels` -- array of label objects with `name` (and optional `color`, `description`)
+- `owner_ids` -- array of member UUIDs to assign
+- `deadline` -- due date in ISO 8601 format
+- `tasks` -- inline task array with `description` and optional `complete`, `owner_ids`
+- `comments` -- inline comment array with `text`
+- `story_links` -- link stories with `verb` (`"blocks"`, `"duplicates"`, `"relates to"`)
+
+**Important:** Either `workflow_state_id` or `project_id` must be provided, but not both. `workflow_state_id` is recommended as Projects are being sunset in Shortcut.
+
+### 2. Batch Create Stories
+
+Create multiple stories in a single API call.
+
+**Tool:** `SHORTCUT_CREATE_MULTIPLE_STORIES`
+
+```
+Create 3 bug stories: "Login page 500 error", "Cart total rounding issue", and "Search results empty state broken"
+```
+
+- Requires `stories` array where each element follows the same schema as `SHORTCUT_CREATE_STORY`
+- Each story in the array requires `name`
+- Efficient for bulk imports, sprint planning, or template-based story creation
+
+### 3. List Stories in a Project
+
+Retrieve all stories within a specific project.
+
+**Tool:** `SHORTCUT_LIST_STORIES`
+
+```
+List all stories in project 42 with their descriptions
+```
+
+- Requires `project__public__id` (integer project ID)
+- Optional `includes_description: true` to include story descriptions in the response
+- Returns all stories with their attributes (status, type, estimate, etc.)
+
+### 4. Manage Story Tasks
+
+Create tasks (checklists) within stories for tracking sub-work.
+
+**Tool:** `SHORTCUT_CREATE_TASK`
+
+```
+Add a task "Write unit tests for dark mode toggle" to story 12345
+```
+
+Key parameters:
+- `story__public__id` (required) -- the parent story ID
+- `description` (required) -- the task description
+- `complete` -- boolean, defaults to false
+- `owner_ids` -- array of member UUIDs to assign the task
+- `external_id` -- ID from an external tool if imported
+
+### 5. Add Story Comments
+
+Post comments on stories for discussion and documentation.
+
+**Tool:** `SHORTCUT_CREATE_STORY_COMMENT`
+
+```
+Add a comment to story 12345: "Reviewed the implementation -- looks good, but needs accessibility testing"
+```
+
+Key parameters:
+- `story__public__id` (required) -- the story ID
+- `text` (required) -- the comment body
+- `author_id` -- member UUID (defaults to API token owner)
+- `parent_id` -- ID of parent comment for threaded replies
+
+### 6. Workflow and Project Discovery
+
+List workflows and projects to resolve IDs for story creation.
+
+**Tools:** `SHORTCUT_LIST_WORKFLOWS`, `SHORTCUT_LIST_PROJECTS`
+
+```
+Show me all workflows in our Shortcut workspace so I can find the right workflow state ID
+```
+
+- `SHORTCUT_LIST_WORKFLOWS` returns all workflows with their states (IDs, names, types)
+- `SHORTCUT_LIST_PROJECTS` returns all projects with their attributes
+- Use these to discover valid `workflow_state_id` and `project_id` values before creating stories
+
+---
+
+## Known Pitfalls
+
+- **`workflow_state_id` vs `project_id`:** `SHORTCUT_CREATE_STORY` requires exactly one of these. Providing both or neither causes a rejection. Prefer `workflow_state_id` since Projects are being sunset.
+- **Projects are being sunset:** Shortcut is deprecating Projects in favor of workflow-based organization. Use `workflow_state_id` for new stories.
+- **Label creation is inline:** Labels in the `labels` array are created on-the-fly if they do not exist. The `name` field is required for each label object.
+- **Story type defaults:** If `story_type` is omitted, it defaults to `"feature"`. Always set it explicitly for bugs and chores.
+- **Batch limits:** `SHORTCUT_CREATE_MULTIPLE_STORIES` processes all stories in a single request. Very large batches may time out -- keep batches under 25 stories.
+- **Integer IDs for stories/projects:** Story and project IDs are integers, not UUIDs. Member and group IDs are UUIDs. Mixing these formats causes errors.
+- **`move_to` positioning:** The `move_to` field (`"first"` or `"last"`) moves the story within its workflow state, not across states.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `SHORTCUT_CREATE_STORY` | Create a single story (requires `name` + `workflow_state_id` or `project_id`) |
+| `SHORTCUT_CREATE_MULTIPLE_STORIES` | Batch-create multiple stories (requires `stories` array) |
+| `SHORTCUT_LIST_STORIES` | List stories in a project (requires `project__public__id`) |
+| `SHORTCUT_CREATE_TASK` | Create a task in a story (requires `story__public__id`, `description`) |
+| `SHORTCUT_CREATE_STORY_COMMENT` | Add a comment to a story (requires `story__public__id`, `text`) |
+| `SHORTCUT_CREATE_STORY_FROM_TEMPLATE` | Create a story from a template |
+| `SHORTCUT_LIST_WORKFLOWS` | List all workflows and their states |
+| `SHORTCUT_LIST_PROJECTS` | List all projects |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/shorten-rest-automation/SKILL.md b/plugins/awesome-claude-skills/shorten-rest-automation/SKILL.md
new file mode 100644
index 0000000..7e8704a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/shortpixel-automation/SKILL.md b/plugins/awesome-claude-skills/shortpixel-automation/SKILL.md
new file mode 100644
index 0000000..c412ed0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/shotstack-automation/SKILL.md b/plugins/awesome-claude-skills/shotstack-automation/SKILL.md
new file mode 100644
index 0000000..1a97425
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sidetracker-automation/SKILL.md b/plugins/awesome-claude-skills/sidetracker-automation/SKILL.md
new file mode 100644
index 0000000..b67fd47
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/signaturely-automation/SKILL.md b/plugins/awesome-claude-skills/signaturely-automation/SKILL.md
new file mode 100644
index 0000000..c7fa834
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/signpath-automation/SKILL.md b/plugins/awesome-claude-skills/signpath-automation/SKILL.md
new file mode 100644
index 0000000..f604fa2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/signwell-automation/SKILL.md b/plugins/awesome-claude-skills/signwell-automation/SKILL.md
new file mode 100644
index 0000000..6047758
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/similarweb-digitalrank-api-automation/SKILL.md b/plugins/awesome-claude-skills/similarweb-digitalrank-api-automation/SKILL.md
new file mode 100644
index 0000000..b24516d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/similarweb_digitalrank_api-automation/SKILL.md b/plugins/awesome-claude-skills/similarweb_digitalrank_api-automation/SKILL.md
new file mode 100644
index 0000000..2b18766
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/simla-com-automation/SKILL.md b/plugins/awesome-claude-skills/simla-com-automation/SKILL.md
new file mode 100644
index 0000000..de200b4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/simple-analytics-automation/SKILL.md b/plugins/awesome-claude-skills/simple-analytics-automation/SKILL.md
new file mode 100644
index 0000000..4fc29ba
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/simplesat-automation/SKILL.md b/plugins/awesome-claude-skills/simplesat-automation/SKILL.md
new file mode 100644
index 0000000..ea3fa21
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sitespeakai-automation/SKILL.md b/plugins/awesome-claude-skills/sitespeakai-automation/SKILL.md
new file mode 100644
index 0000000..4469cf5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/skyfire-automation/SKILL.md b/plugins/awesome-claude-skills/skyfire-automation/SKILL.md
new file mode 100644
index 0000000..00f5f37
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/slack-automation/SKILL.md b/plugins/awesome-claude-skills/slack-automation/SKILL.md
new file mode 100644
index 0000000..b88c8fa
--- /dev/null
+++ b/plugins/awesome-claude-skills/slack-automation/SKILL.md
@@ -0,0 +1,194 @@
+---
+name: slack-automation
+description: Automate Slack messaging, channel management, search, reactions, and threads via Rube MCP (Composio). Send messages, search conversations, manage channels/users, and react to messages programmatically.
+requires:
+ mcp: [rube]
+---
+
+# Slack Automation via Rube MCP
+
+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)
+- Active Slack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `slack`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `slack`
+3. If connection is not ACTIVE, follow the returned auth link to complete Slack OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Messages to Channels
+
+**When to use**: User wants to post a message to a Slack channel or DM
+
+**Tool sequence**:
+1. `SLACK_FIND_CHANNELS` - Resolve channel name to channel ID [Prerequisite]
+2. `SLACK_LIST_ALL_CHANNELS` - Fallback if FIND_CHANNELS returns empty/ambiguous results [Fallback]
+3. `SLACK_FIND_USERS` - Resolve user for DMs or @mentions [Optional]
+4. `SLACK_OPEN_DM` - Open/reuse a DM channel if messaging a user directly [Optional]
+5. `SLACK_SEND_MESSAGE` - Post the message with resolved channel ID [Required]
+6. `SLACK_UPDATES_A_SLACK_MESSAGE` - Edit the posted message if corrections needed [Optional]
+
+**Key parameters**:
+- `channel`: Channel ID or name (without '#' prefix)
+- `markdown_text`: Preferred field for formatted messages (supports headers, bold, italic, code blocks)
+- `text`: Raw text fallback (deprecated in favor of markdown_text)
+- `thread_ts`: Timestamp of parent message to reply in a thread
+- `blocks`: Block Kit layout blocks (deprecated, use markdown_text)
+
+**Pitfalls**:
+- `SLACK_FIND_CHANNELS` requires `query` param; missing it errors with "Invalid request data provided"
+- `SLACK_SEND_MESSAGE` requires valid channel plus one of markdown_text/text/blocks/attachments
+- Invalid block payloads return error=invalid_blocks (max 50 blocks)
+- Replies become top-level posts if `thread_ts` is omitted
+- Persist `response.data.channel` and `response.data.message.ts` from SEND_MESSAGE for edit/thread operations
+
+### 2. Search Messages and Conversations
+
+**When to use**: User wants to find specific messages across the workspace
+
+**Tool sequence**:
+1. `SLACK_FIND_CHANNELS` - Resolve channel for scoped search with `in:#channel` [Optional]
+2. `SLACK_FIND_USERS` - Resolve user for author filter with `from:@user` [Optional]
+3. `SLACK_SEARCH_MESSAGES` - Run keyword search across accessible conversations [Required]
+4. `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` - Expand threads for relevant hits [Required]
+
+**Key parameters**:
+- `query`: Search string supporting modifiers (`in:#channel`, `from:@user`, `before:YYYY-MM-DD`, `after:YYYY-MM-DD`, `has:link`, `has:file`)
+- `count`: Results per page (max 100), or total with auto_paginate=true
+- `sort`: 'score' (relevance) or 'timestamp' (chronological)
+- `sort_dir`: 'asc' or 'desc'
+
+**Pitfalls**:
+- Validation fails if `query` is missing/empty
+- `ok=true` can still mean no hits (`response.data.messages.total=0`)
+- Matches are under `response.data.messages.matches` (sometimes also `response.data_preview.messages.matches`)
+- `match.text` may be empty/truncated; key info can appear in `matches[].attachments[]`
+- Thread expansion via FETCH_MESSAGE_THREAD can truncate when `response.data.has_more=true`; paginate via `response_metadata.next_cursor`
+
+### 3. Manage Channels and Users
+
+**When to use**: User wants to list channels, users, or workspace info
+
+**Tool sequence**:
+1. `SLACK_FETCH_TEAM_INFO` - Validate connectivity and get workspace identity [Required]
+2. `SLACK_LIST_ALL_CHANNELS` - Enumerate public channels [Required]
+3. `SLACK_LIST_CONVERSATIONS` - Include private channels and DMs [Optional]
+4. `SLACK_LIST_ALL_USERS` - List workspace members [Required]
+5. `SLACK_RETRIEVE_CONVERSATION_INFORMATION` - Get detailed channel metadata [Optional]
+6. `SLACK_LIST_USER_GROUPS_FOR_TEAM_WITH_OPTIONS` - List user groups [Optional]
+
+**Key parameters**:
+- `cursor`: Pagination cursor from `response_metadata.next_cursor`
+- `limit`: Results per page (default varies; set explicitly for large workspaces)
+- `types`: Channel types filter ('public_channel', 'private_channel', 'im', 'mpim')
+
+**Pitfalls**:
+- Workspace metadata is nested under `response.data.team`, not top-level
+- `SLACK_LIST_ALL_CHANNELS` returns public channels only; use `SLACK_LIST_CONVERSATIONS` for private/IM coverage
+- `SLACK_LIST_ALL_USERS` can hit HTTP 429 rate limits; honor Retry-After header
+- Always paginate via `response_metadata.next_cursor` until empty; de-duplicate by `id`
+
+### 4. React to and Thread Messages
+
+**When to use**: User wants to add reactions or manage threaded conversations
+
+**Tool sequence**:
+1. `SLACK_SEARCH_MESSAGES` or `SLACK_FETCH_CONVERSATION_HISTORY` - Find the target message [Prerequisite]
+2. `SLACK_ADD_REACTION_TO_AN_ITEM` - Add an emoji reaction [Required]
+3. `SLACK_FETCH_ITEM_REACTIONS` - List reactions on a message [Optional]
+4. `SLACK_REMOVE_REACTION_FROM_ITEM` - Remove a reaction [Optional]
+5. `SLACK_SEND_MESSAGE` - Reply in thread using `thread_ts` [Optional]
+6. `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` - Read full thread [Optional]
+
+**Key parameters**:
+- `channel`: Channel ID where the message lives
+- `timestamp` / `ts`: Message timestamp (unique identifier like '1234567890.123456')
+- `name`: Emoji name without colons (e.g., 'thumbsup', 'wave::skin-tone-3')
+- `thread_ts`: Parent message timestamp for threaded replies
+
+**Pitfalls**:
+- Reactions require exact channel ID + message timestamp pair
+- Emoji names use Slack's naming convention without colons
+- `SLACK_FETCH_CONVERSATION_HISTORY` only returns main channel timeline, NOT threaded replies
+- Use `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` with parent's `thread_ts` to get thread replies
+
+### 5. Schedule Messages
+
+**When to use**: User wants to schedule a message for future delivery
+
+**Tool sequence**:
+1. `SLACK_FIND_CHANNELS` - Resolve channel ID [Prerequisite]
+2. `SLACK_SCHEDULE_MESSAGE` - Schedule the message with `post_at` timestamp [Required]
+
+**Key parameters**:
+- `channel`: Resolved channel ID
+- `post_at`: Unix timestamp for delivery (up to 120 days in advance)
+- `text` / `blocks`: Message content
+
+**Pitfalls**:
+- Scheduling is limited to 120 days in advance
+- `post_at` must be a Unix timestamp, not ISO 8601
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to IDs before operations:
+- **Channel name -> Channel ID**: `SLACK_FIND_CHANNELS` with `query` param
+- **User name -> User ID**: `SLACK_FIND_USERS` with `search_query` or `email`
+- **DM channel**: `SLACK_OPEN_DM` with resolved user IDs
+
+### Pagination
+Most list endpoints use cursor-based pagination:
+- Follow `response_metadata.next_cursor` until empty
+- Set explicit `limit` values (e.g., 100-200) for reliable paging
+- De-duplicate results by `id` across pages
+
+### Message Formatting
+- Prefer `markdown_text` over `text` or `blocks` for formatted messages
+- Use `<@USER_ID>` format to mention users (not @username)
+- Use `\n` for line breaks in markdown_text
+
+## Known Pitfalls
+
+- **Channel resolution**: `SLACK_FIND_CHANNELS` can return empty results if channel is private and bot hasn't been invited
+- **Rate limits**: `SLACK_LIST_ALL_USERS` and other list endpoints can hit HTTP 429; honor Retry-After header
+- **Nested responses**: Results may be nested under `response.data.results[0].response.data` in wrapped executions
+- **Thread vs channel**: `SLACK_FETCH_CONVERSATION_HISTORY` returns main timeline only; use `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` for thread replies
+- **Message editing**: Requires both `channel` and original message `ts`; persist these from SEND_MESSAGE response
+- **Search delays**: Recently posted messages may not appear in search results immediately
+- **Scope limitations**: Missing OAuth scopes can cause 403 errors; check with `SLACK_GET_APP_PERMISSION_SCOPES`
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Find channels | `SLACK_FIND_CHANNELS` | `query` |
+| List all channels | `SLACK_LIST_ALL_CHANNELS` | `limit`, `cursor`, `types` |
+| Send message | `SLACK_SEND_MESSAGE` | `channel`, `markdown_text` |
+| Edit message | `SLACK_UPDATES_A_SLACK_MESSAGE` | `channel`, `ts`, `markdown_text` |
+| Search messages | `SLACK_SEARCH_MESSAGES` | `query`, `count`, `sort` |
+| Get thread | `SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` | `channel`, `ts` |
+| Add reaction | `SLACK_ADD_REACTION_TO_AN_ITEM` | `channel`, `name`, `timestamp` |
+| Find users | `SLACK_FIND_USERS` | `search_query` or `email` |
+| List users | `SLACK_LIST_ALL_USERS` | `limit`, `cursor` |
+| Open DM | `SLACK_OPEN_DM` | user IDs |
+| Schedule message | `SLACK_SCHEDULE_MESSAGE` | `channel`, `post_at`, `text` |
+| 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/plugins/awesome-claude-skills/slackbot-automation/SKILL.md b/plugins/awesome-claude-skills/slackbot-automation/SKILL.md
new file mode 100644
index 0000000..9d46236
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/smartproxy-automation/SKILL.md b/plugins/awesome-claude-skills/smartproxy-automation/SKILL.md
new file mode 100644
index 0000000..286cf10
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/smartrecruiters-automation/SKILL.md b/plugins/awesome-claude-skills/smartrecruiters-automation/SKILL.md
new file mode 100644
index 0000000..0c190d2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sms-alert-automation/SKILL.md b/plugins/awesome-claude-skills/sms-alert-automation/SKILL.md
new file mode 100644
index 0000000..4ef728d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/smtp2go-automation/SKILL.md b/plugins/awesome-claude-skills/smtp2go-automation/SKILL.md
new file mode 100644
index 0000000..42f4790
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/smugmug-automation/SKILL.md b/plugins/awesome-claude-skills/smugmug-automation/SKILL.md
new file mode 100644
index 0000000..565367e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/snowflake-automation/SKILL.md b/plugins/awesome-claude-skills/snowflake-automation/SKILL.md
new file mode 100644
index 0000000..7e4ed6f
--- /dev/null
+++ b/plugins/awesome-claude-skills/snowflake-automation/SKILL.md
@@ -0,0 +1,127 @@
+---
+name: Snowflake Automation
+description: "Automate Snowflake data warehouse operations -- list databases, schemas, and tables, execute SQL statements, and manage data workflows via the Composio MCP integration."
+requires:
+ mcp:
+ - rube
+---
+
+# Snowflake Automation
+
+Automate your Snowflake data warehouse workflows -- discover databases, browse schemas and tables, execute arbitrary SQL (SELECT, DDL, DML), and integrate Snowflake data operations into cross-app pipelines.
+
+**Toolkit docs:** [composio.dev/toolkits/snowflake](https://composio.dev/toolkits/snowflake)
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client: `https://rube.app/mcp`
+2. Connect your Snowflake account when prompted (account credentials or key-pair authentication)
+3. Start using the workflows below
+
+---
+
+## Core Workflows
+
+### 1. List Databases
+
+Use `SNOWFLAKE_SHOW_DATABASES` to discover available databases with optional filtering and Time Travel support.
+
+```
+Tool: SNOWFLAKE_SHOW_DATABASES
+Inputs:
+ - like_pattern: string (SQL wildcard, e.g., "%test%") -- case-insensitive
+ - starts_with: string (e.g., "PROD") -- case-sensitive
+ - limit: integer (max 10000)
+ - history: boolean (include dropped databases within Time Travel retention)
+ - terse: boolean (return subset of columns: created_on, name, kind, database_name, schema_name)
+ - role: string (role to use for execution)
+ - warehouse: string (optional, not required for SHOW DATABASES)
+ - timeout: integer (seconds)
+```
+
+### 2. Browse Schemas
+
+Use `SNOWFLAKE_SHOW_SCHEMAS` to list schemas within a database or across the account.
+
+```
+Tool: SNOWFLAKE_SHOW_SCHEMAS
+Inputs:
+ - database: string (database context)
+ - in_scope: "ACCOUNT" | "DATABASE" | ""
+ - like_pattern: string (SQL wildcard filter)
+ - starts_with: string (case-sensitive prefix)
+ - limit: integer (max 10000)
+ - history: boolean (include dropped schemas)
+ - terse: boolean (subset columns only)
+ - role, warehouse, timeout: string/integer (optional)
+```
+
+### 3. List Tables
+
+Use `SNOWFLAKE_SHOW_TABLES` to discover tables with metadata including row counts, sizes, and clustering keys.
+
+```
+Tool: SNOWFLAKE_SHOW_TABLES
+Inputs:
+ - database: string (database context)
+ - schema: string (schema context)
+ - in_scope: "ACCOUNT" | "DATABASE" | "SCHEMA" | ""
+ - like_pattern: string (e.g., "%customer%")
+ - starts_with: string (e.g., "FACT", "DIM", "TEMP")
+ - limit: integer (max 10000)
+ - history: boolean (include dropped tables)
+ - terse: boolean (subset columns only)
+ - role, warehouse, timeout: string/integer (optional)
+```
+
+### 4. Execute SQL Statements
+
+Use `SNOWFLAKE_EXECUTE_SQL` for SELECT queries, DDL (CREATE/ALTER/DROP), and DML (INSERT/UPDATE/DELETE) with parameterized bindings.
+
+```
+Tool: SNOWFLAKE_EXECUTE_SQL
+Inputs:
+ - statement: string (required) -- SQL statement(s), semicolon-separated for multi-statement
+ - database: string (case-sensitive, falls back to DEFAULT_NAMESPACE)
+ - schema_name: string (case-sensitive)
+ - warehouse: string (case-sensitive, required for compute-bound queries)
+ - role: string (case-sensitive, falls back to DEFAULT_ROLE)
+ - bindings: object (parameterized query values to prevent SQL injection)
+ - parameters: object (Snowflake session-level parameters)
+ - timeout: integer (seconds; 0 = max 604800s)
+```
+
+**Examples:**
+- `"SELECT * FROM my_table LIMIT 100;"`
+- `"CREATE TABLE test (id INT, name STRING);"`
+- `"ALTER SESSION SET QUERY_TAG='mytag'; SELECT COUNT(*) FROM my_table;"`
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| Case sensitivity | Database, schema, warehouse, and role names are case-sensitive in `SNOWFLAKE_EXECUTE_SQL`. |
+| Warehouse required for compute | SELECT and DML queries require a running warehouse. SHOW commands do not. |
+| Multi-statement execution | Multiple statements separated by semicolons execute in sequence automatically. |
+| SQL injection prevention | Always use the `bindings` parameter for user-supplied values to prevent injection attacks. |
+| Pagination with LIMIT | `SHOW` commands support `limit` (max 10000) and `from_name` for cursor-based pagination. |
+| Time Travel | Set `history: true` to include dropped objects still within the retention period. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `SNOWFLAKE_SHOW_DATABASES` | List databases with filtering and Time Travel support |
+| `SNOWFLAKE_SHOW_SCHEMAS` | List schemas within a database or account-wide |
+| `SNOWFLAKE_SHOW_TABLES` | List tables with metadata (row count, size, clustering) |
+| `SNOWFLAKE_EXECUTE_SQL` | Execute SQL: SELECT, DDL, DML with parameterized bindings |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/sourcegraph-automation/SKILL.md b/plugins/awesome-claude-skills/sourcegraph-automation/SKILL.md
new file mode 100644
index 0000000..759531a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/splitwise-automation/SKILL.md b/plugins/awesome-claude-skills/splitwise-automation/SKILL.md
new file mode 100644
index 0000000..aa2864d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/spoki-automation/SKILL.md b/plugins/awesome-claude-skills/spoki-automation/SKILL.md
new file mode 100644
index 0000000..775d800
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/spondyr-automation/SKILL.md b/plugins/awesome-claude-skills/spondyr-automation/SKILL.md
new file mode 100644
index 0000000..d658d7c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/spotify-automation/SKILL.md b/plugins/awesome-claude-skills/spotify-automation/SKILL.md
new file mode 100644
index 0000000..e350efc
--- /dev/null
+++ b/plugins/awesome-claude-skills/spotify-automation/SKILL.md
@@ -0,0 +1,186 @@
+---
+name: Spotify Automation
+description: "Automate Spotify workflows including playlist management, music search, playback control, and user profile access via Composio"
+requires:
+ mcp:
+ - rube
+---
+
+# Spotify Automation
+
+Automate Spotify operations -- manage playlists, search the music catalog, control playback, browse albums and tracks, and access user profiles -- all orchestrated through the Composio MCP integration.
+
+**Toolkit docs:** [composio.dev/toolkits/spotify](https://composio.dev/toolkits/spotify)
+
+---
+
+## Setup
+
+1. Connect your Spotify account through the Composio MCP server at `https://rube.app/mcp`
+2. The agent will prompt you with an authentication link if no active connection exists
+3. Once connected, all `SPOTIFY_*` tools become available for execution
+4. **Note:** Some features (playback control) require a Spotify Premium subscription
+
+---
+
+## Core Workflows
+
+### 1. Get Current User Profile
+Retrieve comprehensive profile information for the authenticated Spotify user.
+
+**Tool:** `SPOTIFY_GET_CURRENT_USER_S_PROFILE`
+
+```
+No parameters required.
+Returns: display name, email, country, subscription level (premium/free),
+explicit content settings, profile images, follower count, and Spotify URIs.
+Required scopes: user-read-private, user-read-email.
+```
+
+---
+
+### 2. Search the Spotify Catalog
+Find albums, artists, playlists, tracks, shows, episodes, or audiobooks by keyword.
+
+**Tool:** `SPOTIFY_SEARCH_FOR_ITEM`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `q` | string | Yes | Search query keywords |
+| `type` | array | Yes | Item types: `album`, `artist`, `playlist`, `track`, `show`, `episode`, `audiobook` |
+| `limit` | integer | No | Results to return (default: 20) |
+| `offset` | integer | No | Offset for pagination (default: 0) |
+| `market` | string | No | ISO 3166-1 alpha-2 country code |
+| `include_external` | string | No | Set to `audio` to include external content |
+
+**Note:** Audiobooks are only available in US, UK, Canada, Ireland, New Zealand, and Australia.
+
+---
+
+### 3. Manage Playlists
+Browse, create, modify, and populate playlists.
+
+**Get a user's playlists:**
+
+**Tool:** `SPOTIFY_GET_USER_S_PLAYLISTS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `user_id` | string | Yes | Spotify user ID |
+| `limit` | integer | No | Max playlists, 1-50 (default: 20) |
+| `offset` | integer | No | Pagination offset, 0-100000 (default: 0) |
+
+**Get current user's playlists:**
+
+**Tool:** `SPOTIFY_GET_CURRENT_USER_S_PLAYLISTS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `limit` | integer | No | Max playlists, 1-50 (default: 20) |
+| `offset` | integer | No | Pagination offset, 0-100000 (default: 0) |
+
+**Get playlist details:**
+
+**Tool:** `SPOTIFY_GET_PLAYLIST`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `playlist_id` | string | Yes | Spotify playlist ID (e.g., `3cEYpjA9oz9GiPac4AsH4n`) |
+| `fields` | string | No | Comma-separated field filter to reduce response size |
+| `market` | string | No | ISO country code for market-specific content |
+| `additional_types` | string | No | `track,episode` to include podcast episodes |
+
+**Update playlist details:**
+
+**Tool:** `SPOTIFY_CHANGE_PLAYLIST_DETAILS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `playlist_id` | string | Yes | Playlist ID (must be owned by current user) |
+| `name` | string | No | New playlist name |
+| `description` | string | No | New playlist description |
+| `public` | boolean | No | Public/private toggle |
+| `collaborative` | boolean | No | Collaborative mode (only on non-public playlists) |
+
+---
+
+### 4. Browse Playlist Items & Add Tracks
+View tracks in a playlist and add new items.
+
+**Tool:** `SPOTIFY_GET_PLAYLIST_ITEMS`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `playlist_id` | string | Yes | Spotify playlist ID |
+| `limit` | integer | No | Items per page, 1-50 (default: 20) |
+| `offset` | integer | No | Pagination offset (default: 0) |
+| `fields` | string | No | Field filter (e.g., `items(track(name,id))`) |
+| `market` | string | No | ISO country code |
+| `additional_types` | string | No | `track,episode` for podcast episodes |
+
+**Tool:** `SPOTIFY_ADD_ITEMS_TO_PLAYLIST`
+
+Add tracks or episodes to a playlist using Spotify URIs.
+
+---
+
+### 5. Get Track & Album Details
+Retrieve catalog information for individual tracks and albums.
+
+**Tool:** `SPOTIFY_GET_TRACK` -- Get details for a single track by Spotify ID.
+
+**Tool:** `SPOTIFY_GET_ALBUM` -- Get comprehensive album data including track listing, artist info, cover art, and popularity.
+
+---
+
+### 6. Control Playback
+Start, resume, or change playback on the user's active device.
+
+**Tool:** `SPOTIFY_START_RESUME_PLAYBACK`
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| `context_uri` | string | No | Spotify URI of album, artist, or playlist (cannot combine with `uris`) |
+| `uris` | array | No | List of track URIs to play (cannot combine with `context_uri`) |
+| `offset` | object | No | Starting position: `{position: 5}` or `{uri: 'spotify:track:...'}` |
+| `position_ms` | integer | No | Start position in milliseconds |
+| `device_id` | string | No | Target device ID (defaults to active device) |
+
+**Requirements:** Spotify Premium subscription and at least one active device.
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| **Premium required for playback** | `SPOTIFY_START_RESUME_PLAYBACK` returns 403 if the user does not have Spotify Premium |
+| **Active device required** | Playback control returns 404 if no Spotify device (mobile, desktop, web, speaker) is active |
+| **context_uri vs uris are exclusive** | Cannot use both `context_uri` and `uris` in the same playback call |
+| **Collaborative playlists** | `collaborative` can only be set to `true` on non-public playlists (`public` must be `false`) |
+| **Playlist ownership** | `SPOTIFY_CHANGE_PLAYLIST_DETAILS` only works on playlists owned by the authenticated user |
+| **Audiobook market restrictions** | Audiobooks via search are only available in US, UK, Canada, Ireland, New Zealand, and Australia |
+| **Max 11000 playlists** | Users are limited to approximately 11,000 playlists via `SPOTIFY_CREATE_PLAYLIST` |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Purpose |
+|-----------|---------|
+| `SPOTIFY_GET_CURRENT_USER_S_PROFILE` | Get authenticated user's profile |
+| `SPOTIFY_SEARCH_FOR_ITEM` | Search catalog for tracks, albums, artists, etc. |
+| `SPOTIFY_GET_USER_S_PLAYLISTS` | Get playlists for any user |
+| `SPOTIFY_GET_CURRENT_USER_S_PLAYLISTS` | Get current user's playlists |
+| `SPOTIFY_GET_PLAYLIST` | Get detailed playlist info |
+| `SPOTIFY_GET_PLAYLIST_ITEMS` | List tracks/episodes in a playlist |
+| `SPOTIFY_CHANGE_PLAYLIST_DETAILS` | Update playlist name, description, visibility |
+| `SPOTIFY_CREATE_PLAYLIST` | Create a new playlist |
+| `SPOTIFY_ADD_ITEMS_TO_PLAYLIST` | Add tracks/episodes to a playlist |
+| `SPOTIFY_GET_TRACK` | Get track details by ID |
+| `SPOTIFY_GET_ALBUM` | Get album details by ID |
+| `SPOTIFY_START_RESUME_PLAYBACK` | Start or resume playback on a device |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/spotlightr-automation/SKILL.md b/plugins/awesome-claude-skills/spotlightr-automation/SKILL.md
new file mode 100644
index 0000000..aa3493c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/square-automation/SKILL.md b/plugins/awesome-claude-skills/square-automation/SKILL.md
new file mode 100644
index 0000000..d50b36b
--- /dev/null
+++ b/plugins/awesome-claude-skills/square-automation/SKILL.md
@@ -0,0 +1,181 @@
+---
+name: square-automation
+description: "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Square Automation via Rube MCP
+
+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)
+- Active Square connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `square`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `square`
+3. If connection is not ACTIVE, follow the returned auth link to complete Square OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Monitor Payments
+
+**When to use**: User wants to view payment history or check payment status
+
+**Tool sequence**:
+1. `SQUARE_LIST_PAYMENTS` - Retrieve payments with optional filters [Required]
+2. `SQUARE_CANCEL_PAYMENT` - Cancel a pending payment if needed [Optional]
+
+**Key parameters**:
+- `begin_time` / `end_time`: RFC 3339 timestamps for date range filtering
+- `sort_order`: 'ASC' or 'DESC' for chronological ordering
+- `cursor`: Pagination cursor from previous response
+- `location_id`: Filter payments by specific location
+
+**Pitfalls**:
+- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')
+- Pagination required for large result sets; follow `cursor` until absent
+- Only pending payments can be cancelled; completed payments require refunds
+- `SQUARE_CANCEL_PAYMENT` requires exact `payment_id` from list results
+
+### 2. Search and Manage Orders
+
+**When to use**: User wants to find orders by criteria or update order details
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - Get location IDs for filtering [Prerequisite]
+2. `SQUARE_SEARCH_ORDERS` - Search orders with filters [Required]
+3. `SQUARE_RETRIEVE_ORDER` - Get full details of a specific order [Optional]
+4. `SQUARE_UPDATE_ORDER` - Modify order state or details [Optional]
+
+**Key parameters**:
+- `location_ids`: Array of location IDs to search within (required for search)
+- `query`: Search filter object with date ranges, states, fulfillment types
+- `order_id`: Specific order ID for retrieve/update operations
+- `cursor`: Pagination cursor for search results
+
+**Pitfalls**:
+- `location_ids` is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS first
+- Order states include: OPEN, COMPLETED, CANCELED, DRAFT
+- UPDATE_ORDER requires the current `version` field to prevent conflicts
+- Search results are paginated; follow `cursor` until absent
+
+### 3. Manage Locations
+
+**When to use**: User wants to view business locations or get location details
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - List all business locations [Required]
+
+**Key parameters**:
+- No required parameters; returns all accessible locations
+- Response includes `id`, `name`, `address`, `status`, `timezone`
+
+**Pitfalls**:
+- Location IDs are required for most other Square operations (orders, payments)
+- Always cache location IDs after first retrieval to avoid redundant calls
+- Inactive locations may still appear in results; check `status` field
+
+### 4. Invoice Management
+
+**When to use**: User wants to list, view, or cancel invoices
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - Get location ID for filtering [Prerequisite]
+2. `SQUARE_LIST_INVOICES` - List invoices for a location [Required]
+3. `SQUARE_GET_INVOICE` - Get detailed invoice information [Optional]
+4. `SQUARE_CANCEL_INVOICE` - Cancel a scheduled or unpaid invoice [Optional]
+
+**Key parameters**:
+- `location_id`: Required for listing invoices
+- `invoice_id`: Required for get/cancel operations
+- `cursor`: Pagination cursor for list results
+- `limit`: Number of results per page
+
+**Pitfalls**:
+- `location_id` is required for LIST_INVOICES; resolve via LIST_LOCATIONS first
+- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled
+- CANCEL_INVOICE requires the invoice `version` to prevent race conditions
+- Cancelled invoices cannot be uncancelled
+
+## Common Patterns
+
+### ID Resolution
+
+**Location name -> Location ID**:
+```
+1. Call SQUARE_LIST_LOCATIONS
+2. Find location by name in response
+3. Extract id field (e.g., 'L1234ABCD')
+```
+
+**Order lookup**:
+```
+1. Call SQUARE_SEARCH_ORDERS with location_ids and query filters
+2. Extract order_id from results
+3. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER
+```
+
+### Pagination
+
+- Check response for `cursor` field
+- Pass cursor value in next request's `cursor` parameter
+- Continue until `cursor` is absent or empty
+- Use `limit` to control page size
+
+### Date Range Filtering
+
+- Use RFC 3339 format: `2024-01-01T00:00:00Z`
+- For payments: `begin_time` and `end_time` parameters
+- For orders: Use query filter with date_time_filter
+- All timestamps are in UTC
+
+## Known Pitfalls
+
+**ID Formats**:
+- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')
+- Payment IDs and Order IDs are longer alphanumeric strings
+- Always resolve location names to IDs before other operations
+
+**Versioning**:
+- UPDATE_ORDER and CANCEL_INVOICE require current `version` field
+- Fetch the resource first to get its current version
+- Version mismatch returns a 409 Conflict error
+
+**Rate Limits**:
+- Square API has per-endpoint rate limits
+- Implement backoff for bulk operations
+- Pagination should include brief delays for large datasets
+
+**Response Parsing**:
+- Responses may nest data under `data` key
+- Money amounts are in smallest currency unit (cents for USD)
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List payments | SQUARE_LIST_PAYMENTS | begin_time, end_time, location_id, cursor |
+| Cancel payment | SQUARE_CANCEL_PAYMENT | payment_id |
+| Search orders | SQUARE_SEARCH_ORDERS | location_ids, query, cursor |
+| Get order | SQUARE_RETRIEVE_ORDER | order_id |
+| Update order | SQUARE_UPDATE_ORDER | order_id, version |
+| List locations | SQUARE_LIST_LOCATIONS | (none) |
+| 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/plugins/awesome-claude-skills/sslmate-cert-spotter-api-automation/SKILL.md b/plugins/awesome-claude-skills/sslmate-cert-spotter-api-automation/SKILL.md
new file mode 100644
index 0000000..1d6c548
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/stack-exchange-automation/SKILL.md b/plugins/awesome-claude-skills/stack-exchange-automation/SKILL.md
new file mode 100644
index 0000000..2b6ff3b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/stannp-automation/SKILL.md b/plugins/awesome-claude-skills/stannp-automation/SKILL.md
new file mode 100644
index 0000000..0f3bb69
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/starton-automation/SKILL.md b/plugins/awesome-claude-skills/starton-automation/SKILL.md
new file mode 100644
index 0000000..2661f6e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/statuscake-automation/SKILL.md b/plugins/awesome-claude-skills/statuscake-automation/SKILL.md
new file mode 100644
index 0000000..c22aca1
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/storeganise-automation/SKILL.md b/plugins/awesome-claude-skills/storeganise-automation/SKILL.md
new file mode 100644
index 0000000..a4a09aa
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/storerocket-automation/SKILL.md b/plugins/awesome-claude-skills/storerocket-automation/SKILL.md
new file mode 100644
index 0000000..b0b7238
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/stormglass-io-automation/SKILL.md b/plugins/awesome-claude-skills/stormglass-io-automation/SKILL.md
new file mode 100644
index 0000000..66dbe43
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/strava-automation/SKILL.md b/plugins/awesome-claude-skills/strava-automation/SKILL.md
new file mode 100644
index 0000000..777656b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/streamtime-automation/SKILL.md b/plugins/awesome-claude-skills/streamtime-automation/SKILL.md
new file mode 100644
index 0000000..b33ede3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/stripe-automation/SKILL.md b/plugins/awesome-claude-skills/stripe-automation/SKILL.md
new file mode 100644
index 0000000..bed6392
--- /dev/null
+++ b/plugins/awesome-claude-skills/stripe-automation/SKILL.md
@@ -0,0 +1,203 @@
+---
+name: stripe-automation
+description: "Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Stripe Automation via Rube MCP
+
+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)
+- Active Stripe connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `stripe`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `stripe`
+3. If connection is not ACTIVE, follow the returned auth link to complete Stripe connection
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Customers
+
+**When to use**: User wants to create, update, search, or list Stripe customers
+
+**Tool sequence**:
+1. `STRIPE_SEARCH_CUSTOMERS` - Search customers by email/name [Optional]
+2. `STRIPE_LIST_CUSTOMERS` - List all customers [Optional]
+3. `STRIPE_CREATE_CUSTOMER` - Create a new customer [Optional]
+4. `STRIPE_POST_CUSTOMERS_CUSTOMER` - Update a customer [Optional]
+
+**Key parameters**:
+- `email`: Customer email
+- `name`: Customer name
+- `description`: Customer description
+- `metadata`: Key-value metadata pairs
+- `customer`: Customer ID for updates (e.g., 'cus_xxx')
+
+**Pitfalls**:
+- Stripe allows duplicate customers with the same email; search first to avoid duplicates
+- Customer IDs start with 'cus_'
+
+### 2. Manage Charges and Payments
+
+**When to use**: User wants to create charges, payment intents, or view charge history
+
+**Tool sequence**:
+1. `STRIPE_LIST_CHARGES` - List charges with filters [Optional]
+2. `STRIPE_CREATE_PAYMENT_INTENT` - Create a payment intent [Optional]
+3. `STRIPE_CONFIRM_PAYMENT_INTENT` - Confirm a payment intent [Optional]
+4. `STRIPE_POST_CHARGES` - Create a direct charge [Optional]
+5. `STRIPE_CAPTURE_CHARGE` - Capture an authorized charge [Optional]
+
+**Key parameters**:
+- `amount`: Amount in smallest currency unit (e.g., cents for USD)
+- `currency`: Three-letter ISO currency code (e.g., 'usd')
+- `customer`: Customer ID
+- `payment_method`: Payment method ID
+- `description`: Charge description
+
+**Pitfalls**:
+- Amounts are in smallest currency unit (100 = $1.00 for USD)
+- Currency codes must be lowercase (e.g., 'usd' not 'USD')
+- Payment intents are the recommended flow over direct charges
+
+### 3. Manage Subscriptions
+
+**When to use**: User wants to create, list, update, or cancel subscriptions
+
+**Tool sequence**:
+1. `STRIPE_LIST_SUBSCRIPTIONS` - List subscriptions [Optional]
+2. `STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS` - Create subscription [Optional]
+3. `STRIPE_RETRIEVE_SUBSCRIPTION` - Get subscription details [Optional]
+4. `STRIPE_UPDATE_SUBSCRIPTION` - Modify subscription [Optional]
+
+**Key parameters**:
+- `customer`: Customer ID
+- `items`: Array of price items (price_id and quantity)
+- `subscription`: Subscription ID for retrieval/update (e.g., 'sub_xxx')
+
+**Pitfalls**:
+- Subscriptions require a valid customer with a payment method
+- Price IDs (not product IDs) are used for subscription items
+- Cancellation can be immediate or at period end
+
+### 4. Manage Invoices
+
+**When to use**: User wants to create, list, or search invoices
+
+**Tool sequence**:
+1. `STRIPE_LIST_INVOICES` - List invoices [Optional]
+2. `STRIPE_SEARCH_INVOICES` - Search invoices [Optional]
+3. `STRIPE_CREATE_INVOICE` - Create an invoice [Optional]
+
+**Key parameters**:
+- `customer`: Customer ID for invoice
+- `collection_method`: 'charge_automatically' or 'send_invoice'
+- `days_until_due`: Days until invoice is due
+
+**Pitfalls**:
+- Invoices auto-finalize by default; use `auto_advance: false` for draft invoices
+
+### 5. Manage Products and Prices
+
+**When to use**: User wants to list or search products and their pricing
+
+**Tool sequence**:
+1. `STRIPE_LIST_PRODUCTS` - List products [Optional]
+2. `STRIPE_SEARCH_PRODUCTS` - Search products [Optional]
+3. `STRIPE_LIST_PRICES` - List prices [Optional]
+4. `STRIPE_GET_PRICES_SEARCH` - Search prices [Optional]
+
+**Key parameters**:
+- `active`: Filter by active/inactive status
+- `query`: Search query for search endpoints
+
+**Pitfalls**:
+- Products and prices are separate objects; a product can have multiple prices
+- Price IDs (e.g., 'price_xxx') are used for subscriptions and checkout
+
+### 6. Handle Refunds
+
+**When to use**: User wants to issue refunds on charges
+
+**Tool sequence**:
+1. `STRIPE_LIST_REFUNDS` - List refunds [Optional]
+2. `STRIPE_POST_CHARGES_CHARGE_REFUNDS` - Create a refund [Optional]
+3. `STRIPE_CREATE_REFUND` - Create refund via payment intent [Optional]
+
+**Key parameters**:
+- `charge`: Charge ID for refund
+- `amount`: Partial refund amount (omit for full refund)
+- `reason`: Refund reason ('duplicate', 'fraudulent', 'requested_by_customer')
+
+**Pitfalls**:
+- Refunds can take 5-10 business days to appear on customer statements
+- Amount is in smallest currency unit
+
+## Common Patterns
+
+### Amount Formatting
+
+Stripe uses smallest currency unit:
+- USD: $10.50 = 1050 cents
+- EUR: 10.50 = 1050 cents
+- JPY: 1000 = 1000 (no decimals)
+
+### Pagination
+
+- Use `limit` parameter (max 100)
+- Check `has_more` in response
+- Pass `starting_after` with last object ID for next page
+- Continue until `has_more` is false
+
+## Known Pitfalls
+
+**Amount Units**:
+- Always use smallest currency unit (cents for USD/EUR)
+- Zero-decimal currencies (JPY, KRW) use the amount directly
+
+**ID Prefixes**:
+- Customers: `cus_`, Charges: `ch_`, Subscriptions: `sub_`
+- Invoices: `in_`, Products: `prod_`, Prices: `price_`
+- Payment Intents: `pi_`, Refunds: `re_`
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create customer | STRIPE_CREATE_CUSTOMER | email, name |
+| Search customers | STRIPE_SEARCH_CUSTOMERS | query |
+| Update customer | STRIPE_POST_CUSTOMERS_CUSTOMER | customer, fields |
+| List charges | STRIPE_LIST_CHARGES | customer, limit |
+| Create payment intent | STRIPE_CREATE_PAYMENT_INTENT | amount, currency |
+| Confirm payment | STRIPE_CONFIRM_PAYMENT_INTENT | payment_intent |
+| List subscriptions | STRIPE_LIST_SUBSCRIPTIONS | customer |
+| Create subscription | STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS | customer, items |
+| Update subscription | STRIPE_UPDATE_SUBSCRIPTION | subscription, fields |
+| List invoices | STRIPE_LIST_INVOICES | customer |
+| Create invoice | STRIPE_CREATE_INVOICE | customer |
+| Search invoices | STRIPE_SEARCH_INVOICES | query |
+| List products | STRIPE_LIST_PRODUCTS | active |
+| Search products | STRIPE_SEARCH_PRODUCTS | query |
+| List prices | STRIPE_LIST_PRICES | product |
+| Search prices | STRIPE_GET_PRICES_SEARCH | query |
+| List refunds | STRIPE_LIST_REFUNDS | charge |
+| Create refund | STRIPE_CREATE_REFUND | charge, amount |
+| 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/plugins/awesome-claude-skills/supabase-automation/SKILL.md b/plugins/awesome-claude-skills/supabase-automation/SKILL.md
new file mode 100644
index 0000000..1934423
--- /dev/null
+++ b/plugins/awesome-claude-skills/supabase-automation/SKILL.md
@@ -0,0 +1,241 @@
+---
+name: supabase-automation
+description: Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Supabase Automation via Rube MCP
+
+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)
+- Active Supabase connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `supabase`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `supabase`
+3. If connection is not ACTIVE, follow the returned auth link to complete Supabase authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Query and Manage Database Tables
+
+**When to use**: User wants to read data from tables, inspect schemas, or perform CRUD operations
+
+**Tool sequence**:
+1. `SUPABASE_LIST_ALL_PROJECTS` - List projects to find the target project_ref [Prerequisite]
+2. `SUPABASE_LIST_TABLES` - List all tables and views in the database [Prerequisite]
+3. `SUPABASE_GET_TABLE_SCHEMAS` - Get detailed column types, constraints, and relationships [Prerequisite for writes]
+4. `SUPABASE_SELECT_FROM_TABLE` - Query rows with filtering, sorting, and pagination [Required for reads]
+5. `SUPABASE_BETA_RUN_SQL_QUERY` - Execute arbitrary SQL for complex queries, inserts, updates, or deletes [Required for writes]
+
+**Key parameters for SELECT_FROM_TABLE**:
+- `project_ref`: 20-character lowercase project reference
+- `table`: Table or view name to query
+- `select`: Comma-separated column list (supports nested selections and JSON paths like `profile->avatar_url`)
+- `filters`: Array of filter objects with `column`, `operator`, `value`
+- `order`: Sort expression like `created_at.desc`
+- `limit`: Max rows to return (minimum 1)
+- `offset`: Rows to skip for pagination
+
+**PostgREST filter operators**:
+- `eq`, `neq`: Equal / not equal
+- `gt`, `gte`, `lt`, `lte`: Comparison operators
+- `like`, `ilike`: Pattern matching (case-sensitive / insensitive)
+- `is`: IS check (for null, true, false)
+- `in`: In a list of values
+- `cs`, `cd`: Contains / contained by (arrays)
+- `fts`, `plfts`, `phfts`, `wfts`: Full-text search variants
+
+**Key parameters for RUN_SQL_QUERY**:
+- `ref`: Project reference (20 lowercase letters, pattern `^[a-z]{20}$`)
+- `query`: Valid PostgreSQL SQL statement
+- `read_only`: Boolean to force read-only transaction (safer for SELECTs)
+
+**Pitfalls**:
+- `project_ref` must be exactly 20 lowercase letters (a-z only, no numbers or hyphens)
+- `SELECT_FROM_TABLE` is read-only; use `RUN_SQL_QUERY` for INSERT, UPDATE, DELETE operations
+- For PostgreSQL array columns (text[], integer[]), use `ARRAY['item1', 'item2']` or `'{"item1", "item2"}'` syntax, NOT JSON array syntax `'["item1", "item2"]'`
+- SQL identifiers that are case-sensitive must be double-quoted in queries
+- Complex DDL operations may timeout (~60 second limit); break into smaller queries
+- ERROR 42P01 "relation does not exist" usually means unquoted case-sensitive identifiers
+- ERROR 42883 "function does not exist" means you are calling non-standard helpers; prefer information_schema queries
+
+### 2. Manage Projects and Organizations
+
+**When to use**: User wants to list projects, inspect configurations, or manage organizations
+
+**Tool sequence**:
+1. `SUPABASE_LIST_ALL_ORGANIZATIONS` - List all organizations (IDs and names) [Required]
+2. `SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION` - Get detailed org info by slug [Optional]
+3. `SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION` - List org members with roles and MFA status [Optional]
+4. `SUPABASE_LIST_ALL_PROJECTS` - List all projects with metadata [Required]
+5. `SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG` - Get database configuration [Optional]
+6. `SUPABASE_GETS_PROJECT_S_AUTH_CONFIG` - Get authentication configuration [Optional]
+7. `SUPABASE_GET_PROJECT_API_KEYS` - Get API keys (sensitive -- handle carefully) [Optional]
+8. `SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUS` - Check service health [Optional]
+
+**Key parameters**:
+- `ref`: Project reference for project-specific tools
+- `slug`: Organization slug (URL-friendly identifier) for org tools
+- `services`: Array of services for health check: `auth`, `db`, `db_postgres_user`, `pg_bouncer`, `pooler`, `realtime`, `rest`, `storage`
+
+**Pitfalls**:
+- `LIST_ALL_ORGANIZATIONS` returns both `id` and `slug`; `LIST_MEMBERS_OF_AN_ORGANIZATION` expects `slug`, not `id`
+- `GET_PROJECT_API_KEYS` returns live secrets -- NEVER log, display, or persist full key values
+- `GETS_PROJECT_S_SERVICE_HEALTH_STATUS` requires a non-empty `services` array; empty array causes invalid_request error
+- Config tools may return 401/403 if token lacks required scope; handle gracefully rather than failing the whole workflow
+
+### 3. Inspect Database Schema
+
+**When to use**: User wants to understand table structure, columns, constraints, or generate types
+
+**Tool sequence**:
+1. `SUPABASE_LIST_ALL_PROJECTS` - Find the target project [Prerequisite]
+2. `SUPABASE_LIST_TABLES` - Enumerate all tables and views with metadata [Required]
+3. `SUPABASE_GET_TABLE_SCHEMAS` - Get detailed schema for specific tables [Required]
+4. `SUPABASE_GENERATE_TYPE_SCRIPT_TYPES` - Generate TypeScript types from schema [Optional]
+
+**Key parameters for LIST_TABLES**:
+- `project_ref`: Project reference
+- `schemas`: Array of schema names to search (e.g., `["public"]`); omit for all non-system schemas
+- `include_views`: Include views alongside tables (default true)
+- `include_metadata`: Include row count estimates and sizes (default true)
+- `include_system_schemas`: Include pg_catalog, information_schema, etc. (default false)
+
+**Key parameters for GET_TABLE_SCHEMAS**:
+- `project_ref`: Project reference
+- `table_names`: Array of table names (max 20 per request); supports schema prefix like `public.users`, `auth.users`
+- `include_relationships`: Include foreign key info (default true)
+- `include_indexes`: Include index info (default true)
+- `exclude_null_values`: Cleaner output by hiding null fields (default true)
+
+**Key parameters for GENERATE_TYPE_SCRIPT_TYPES**:
+- `ref`: Project reference
+- `included_schemas`: Comma-separated schema names (default `"public"`)
+
+**Pitfalls**:
+- Table names without schema prefix assume `public` schema
+- `row_count` and `size_bytes` from LIST_TABLES may be null for views or recently created tables; treat as unknown, not zero
+- GET_TABLE_SCHEMAS has a max of 20 tables per request; batch if needed
+- TypeScript types include all tables in specified schemas; cannot filter individual tables
+
+### 4. Manage Edge Functions
+
+**When to use**: User wants to list, inspect, or work with Supabase Edge Functions
+
+**Tool sequence**:
+1. `SUPABASE_LIST_ALL_PROJECTS` - Find the project reference [Prerequisite]
+2. `SUPABASE_LIST_ALL_FUNCTIONS` - List all edge functions with metadata [Required]
+3. `SUPABASE_RETRIEVE_A_FUNCTION` - Get detailed info for a specific function [Optional]
+
+**Key parameters**:
+- `ref`: Project reference
+- Function slug for RETRIEVE_A_FUNCTION
+
+**Pitfalls**:
+- `LIST_ALL_FUNCTIONS` returns metadata only, not function code or logs
+- `created_at` and `updated_at` may be epoch milliseconds; convert to human-readable timestamps
+- These tools cannot create or deploy edge functions; they are read-only inspection tools
+- Permission errors may occur without org/project admin rights
+
+### 5. Manage Storage Buckets
+
+**When to use**: User wants to list storage buckets or manage file storage
+
+**Tool sequence**:
+1. `SUPABASE_LIST_ALL_PROJECTS` - Find the project reference [Prerequisite]
+2. `SUPABASE_LISTS_ALL_BUCKETS` - List all storage buckets [Required]
+
+**Key parameters**:
+- `ref`: Project reference
+
+**Pitfalls**:
+- `LISTS_ALL_BUCKETS` returns bucket list only, not bucket contents or access policies
+- For file uploads, `SUPABASE_RESUMABLE_UPLOAD_SIGN_OPTIONS_WITH_ID` handles CORS preflight for TUS resumable uploads only
+- Direct file operations may require using `proxy_execute` with the Supabase storage API
+
+## Common Patterns
+
+### ID Resolution
+- **Project reference**: `SUPABASE_LIST_ALL_PROJECTS` -- extract `ref` field (20 lowercase letters)
+- **Organization slug**: `SUPABASE_LIST_ALL_ORGANIZATIONS` -- use `slug` (not `id`) for downstream org tools
+- **Table names**: `SUPABASE_LIST_TABLES` -- enumerate available tables before querying
+- **Schema discovery**: `SUPABASE_GET_TABLE_SCHEMAS` -- inspect columns and constraints before writes
+
+### Pagination
+- `SUPABASE_SELECT_FROM_TABLE`: Uses `offset` + `limit` pagination. Increment offset by limit until fewer rows than limit are returned.
+- `SUPABASE_LIST_ALL_PROJECTS`: May paginate for large accounts; follow cursors/pages until exhausted.
+- `SUPABASE_LIST_TABLES`: May paginate for large databases.
+
+### SQL Best Practices
+- Always use `SUPABASE_GET_TABLE_SCHEMAS` or `SUPABASE_LIST_TABLES` before writing SQL
+- Use `read_only: true` for SELECT queries to prevent accidental mutations
+- Quote case-sensitive identifiers: `SELECT * FROM "MyTable"` not `SELECT * FROM MyTable`
+- Use PostgreSQL array syntax for array columns: `ARRAY['a', 'b']` not `['a', 'b']`
+- Break complex DDL into smaller statements to avoid timeouts
+
+## Known Pitfalls
+
+### ID Formats
+- Project references are exactly 20 lowercase letters (a-z): pattern `^[a-z]{20}$`
+- Organization identifiers come as both `id` (UUID) and `slug` (URL-friendly string); tools vary in which they accept
+- `LIST_MEMBERS_OF_AN_ORGANIZATION` requires `slug`, not `id`
+
+### SQL Execution
+- `BETA_RUN_SQL_QUERY` has ~60 second timeout for complex operations
+- PostgreSQL array syntax required: `ARRAY['item']` or `'{"item"}'`, NOT JSON syntax `'["item"]'`
+- Case-sensitive identifiers must be double-quoted in SQL
+- ERROR 42P01: relation does not exist (check quoting and schema prefix)
+- ERROR 42883: function does not exist (use information_schema instead of custom helpers)
+
+### Sensitive Data
+- `GET_PROJECT_API_KEYS` returns service-role keys -- NEVER expose full values
+- Auth config tools exclude secrets but may still contain sensitive configuration
+- Always mask or truncate API keys in output
+
+### Schema Metadata
+- `row_count` and `size_bytes` from `LIST_TABLES` can be null; do not treat as zero
+- System schemas are excluded by default; set `include_system_schemas: true` to see them
+- Views appear alongside tables unless `include_views: false`
+
+### Rate Limits and Permissions
+- Enrichment tools (API keys, configs) may return 401/403 without proper scopes; skip gracefully
+- Large table listings may require pagination
+- `GETS_PROJECT_S_SERVICE_HEALTH_STATUS` fails with empty `services` array -- always specify at least one
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List organizations | `SUPABASE_LIST_ALL_ORGANIZATIONS` | (none) |
+| Get org info | `SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION` | `slug` |
+| List org members | `SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION` | `slug` |
+| List projects | `SUPABASE_LIST_ALL_PROJECTS` | (none) |
+| List tables | `SUPABASE_LIST_TABLES` | `project_ref`, `schemas` |
+| Get table schemas | `SUPABASE_GET_TABLE_SCHEMAS` | `project_ref`, `table_names` |
+| Query table | `SUPABASE_SELECT_FROM_TABLE` | `project_ref`, `table`, `select`, `filters` |
+| Run SQL | `SUPABASE_BETA_RUN_SQL_QUERY` | `ref`, `query`, `read_only` |
+| Generate TS types | `SUPABASE_GENERATE_TYPE_SCRIPT_TYPES` | `ref`, `included_schemas` |
+| Postgres config | `SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG` | `ref` |
+| Auth config | `SUPABASE_GETS_PROJECT_S_AUTH_CONFIG` | `ref` |
+| Get API keys | `SUPABASE_GET_PROJECT_API_KEYS` | `ref` |
+| Service health | `SUPABASE_GETS_PROJECT_S_SERVICE_HEALTH_STATUS` | `ref`, `services` |
+| List edge functions | `SUPABASE_LIST_ALL_FUNCTIONS` | `ref` |
+| 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/plugins/awesome-claude-skills/supadata-automation/SKILL.md b/plugins/awesome-claude-skills/supadata-automation/SKILL.md
new file mode 100644
index 0000000..4a626f5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/superchat-automation/SKILL.md b/plugins/awesome-claude-skills/superchat-automation/SKILL.md
new file mode 100644
index 0000000..fbc208f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/supportbee-automation/SKILL.md b/plugins/awesome-claude-skills/supportbee-automation/SKILL.md
new file mode 100644
index 0000000..08c6983
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/supportivekoala-automation/SKILL.md b/plugins/awesome-claude-skills/supportivekoala-automation/SKILL.md
new file mode 100644
index 0000000..a3dcf9a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/survey-monkey-automation/SKILL.md b/plugins/awesome-claude-skills/survey-monkey-automation/SKILL.md
new file mode 100644
index 0000000..68d0079
--- /dev/null
+++ b/plugins/awesome-claude-skills/survey-monkey-automation/SKILL.md
@@ -0,0 +1,166 @@
+---
+name: SurveyMonkey Automation
+description: "Automate SurveyMonkey survey creation, response collection, collector management, and survey discovery through natural language commands"
+requires:
+ mcp:
+ - rube
+---
+
+# SurveyMonkey Automation
+
+Automate SurveyMonkey survey workflows -- create surveys, list and search existing surveys, manage collectors and distribution links, retrieve responses, and inspect survey details -- all through natural language.
+
+**Toolkit docs:** [composio.dev/toolkits/survey_monkey](https://composio.dev/toolkits/survey_monkey)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Connect your SurveyMonkey account when prompted (OAuth flow via Composio)
+3. Start issuing natural language commands for SurveyMonkey automation
+
+---
+
+## Core Workflows
+
+### 1. Create a New Survey
+
+Create a new empty survey that can be further configured with questions and pages.
+
+**Tool:** `SURVEY_MONKEY_CREATE_SURVEY`
+
+Key parameters:
+- `title` -- survey title displayed to respondents (required)
+- `nickname` -- optional internal name for organizing surveys (not shown to respondents)
+- `language` -- ISO 639-1 language code (default `en`); examples: `es`, `fr`, `de`
+- `footer` -- whether to display SurveyMonkey branding footer (default `true`)
+
+> The created survey starts with one empty page and no questions. Use the returned `survey_id` with other actions to add content and configure collectors.
+
+Example prompt:
+> "Create a new survey titled 'Customer Satisfaction Q1 2026'"
+
+---
+
+### 2. List and Search Surveys
+
+Enumerate all surveys in your account with filtering, sorting, and pagination.
+
+**Tool:** `SURVEY_MONKEY_GET_SURVEYS`
+
+Key parameters:
+- `title` -- search by survey title (partial match)
+- `sort_by` -- sort by `title`, `date_modified`, or `num_responses`
+- `sort_order` -- `ASC` or `DESC`
+- `page` / `per_page` -- pagination controls (default 50 per page, max 100)
+- `include` -- additional fields: `response_count`, `date_modified`, `date_created`, `question_count`, `page_count`, `category`, `language`, `folder_id`
+- `folder_id` -- filter to surveys in a specific folder
+- `start_modified_at` / `end_modified_at` -- date range filter (format: `YYYY-MM-DDTHH:MM:SS`)
+
+Example prompt:
+> "List all my surveys sorted by most recent modification, include response counts"
+
+---
+
+### 3. Get Survey Details
+
+Retrieve comprehensive metadata for a specific survey including configuration, question/page counts, response counts, and all relevant URLs.
+
+**Tool:** `SURVEY_MONKEY_GET_SURVEY_DETAILS`
+
+Key parameters:
+- `survey_id` -- the unique survey identifier (required)
+
+Returns: title, language, question_count, page_count, response_count, URLs for preview/edit/analyze/collect, button text, and timestamps.
+
+Example prompt:
+> "Show me the full details and response count for survey 123456789"
+
+---
+
+### 4. Manage Collectors and Distribution Links
+
+Retrieve collectors (distribution channels) for a survey to get shareable links and monitor response progress.
+
+**Tool:** `SURVEY_MONKEY_GET_COLLECTORS`
+
+Key parameters:
+- `survey_id` -- the survey to get collectors for (required)
+- `include` -- additional fields: `type`, `status`, `response_count`, `date_created`, `date_modified`, `url`
+- `name` -- partial match filter on collector name
+- `sort_by` -- sort by `id`, `date_modified`, `type`, `status`, or `name`
+- `sort_order` -- `ASC` or `DESC`
+- `page` / `per_page` -- pagination (default 50, max 1000)
+- `start_date` / `end_date` -- filter by creation date (format: `YYYY-MM-DDTHH:MM:SS`)
+
+Example prompt:
+> "Get all collectors for survey 123456789, include URLs and response counts"
+
+---
+
+### 5. Retrieve Survey Responses
+
+Fetch response data for a specific survey with comprehensive filtering options.
+
+**Tool:** `SURVEY_MONKEY_GET_RESPONSES`
+
+Key parameters:
+- `survey_id` -- the survey to retrieve responses from (required)
+- `status` -- filter by `completed`, `partial`, `overquota`, or `disqualified`
+- `page` / `per_page` -- pagination (default 50, max 1000)
+- `sort_order` -- `ASC` or `DESC` (sorted by `date_modified`)
+- `start_created_at` / `end_created_at` -- filter by creation date range (ISO 8601)
+- `start_modified_at` / `end_modified_at` -- filter by modification date range
+- `email` -- filter by respondent email
+- `first_name` / `last_name` -- filter by respondent name
+- `ip` -- filter by IP address
+- `total_time_min` / `total_time_max` / `total_time_units` -- filter by completion time
+
+Example prompt:
+> "Get all completed responses for survey 123456789 from the last 30 days"
+
+---
+
+### 6. Full Survey Lifecycle Workflow
+
+Combine tools for end-to-end survey management:
+
+1. **Create**: `SURVEY_MONKEY_CREATE_SURVEY` -- create the survey, store the `survey_id`
+2. **Distribute**: `SURVEY_MONKEY_GET_COLLECTORS` -- retrieve the collector link to share with respondents
+3. **Monitor**: `SURVEY_MONKEY_GET_SURVEY_DETAILS` -- check response counts and survey status
+4. **Collect**: `SURVEY_MONKEY_GET_RESPONSES` -- retrieve completed responses, filter by `status=completed`
+5. **Audit**: `SURVEY_MONKEY_GET_SURVEYS` -- browse and find surveys if `survey_id` is lost
+
+Example prompt:
+> "Create a survey called 'Event Feedback', then show me how to distribute it"
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| Pagination required | `SURVEY_MONKEY_GET_COLLECTORS` and `SURVEY_MONKEY_GET_RESPONSES` require managing `page`/`per_page` for large surveys to avoid missing data |
+| Status filtering critical | `SURVEY_MONKEY_GET_RESPONSES` returns partial, overquota, and disqualified entries unless filtered -- use `status=completed` for reliable data |
+| No shareable link on create | `SURVEY_MONKEY_CREATE_SURVEY` does not create a distribution link -- use `SURVEY_MONKEY_GET_COLLECTORS` to get shareable URLs |
+| Survey ID storage | Losing track of `survey_id` forces reliance on `SURVEY_MONKEY_GET_SURVEYS` which is slower -- store IDs immediately after creation |
+| Question ID mapping | Question IDs and answer formats from responses must be carefully mapped; use `SURVEY_MONKEY_GET_SURVEY_DETAILS` to understand the structure |
+| Date format | Date filters use `YYYY-MM-DDTHH:MM:SS` format, not ISO 8601 with timezone |
+| Empty survey on create | New surveys start with one empty page and no questions -- further configuration is needed |
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Key Params |
+|--------|-----------|------------|
+| Create survey | `SURVEY_MONKEY_CREATE_SURVEY` | `title`, `language`, `nickname` |
+| List surveys | `SURVEY_MONKEY_GET_SURVEYS` | `title`, `sort_by`, `include`, `page` |
+| Get survey details | `SURVEY_MONKEY_GET_SURVEY_DETAILS` | `survey_id` |
+| List collectors | `SURVEY_MONKEY_GET_COLLECTORS` | `survey_id`, `include`, `sort_by` |
+| Get responses | `SURVEY_MONKEY_GET_RESPONSES` | `survey_id`, `status`, `start_created_at` |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/survey_monkey-automation/SKILL.md b/plugins/awesome-claude-skills/survey_monkey-automation/SKILL.md
new file mode 100644
index 0000000..b83a9d3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/svix-automation/SKILL.md b/plugins/awesome-claude-skills/svix-automation/SKILL.md
new file mode 100644
index 0000000..e177615
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/sympla-automation/SKILL.md b/plugins/awesome-claude-skills/sympla-automation/SKILL.md
new file mode 100644
index 0000000..ab1675b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/synthflow-ai-automation/SKILL.md b/plugins/awesome-claude-skills/synthflow-ai-automation/SKILL.md
new file mode 100644
index 0000000..28c20fa
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/taggun-automation/SKILL.md b/plugins/awesome-claude-skills/taggun-automation/SKILL.md
new file mode 100644
index 0000000..ffaaf7a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tailored-resume-generator/SKILL.md b/plugins/awesome-claude-skills/tailored-resume-generator/SKILL.md
new file mode 100644
index 0000000..0dac846
--- /dev/null
+++ b/plugins/awesome-claude-skills/tailored-resume-generator/SKILL.md
@@ -0,0 +1,345 @@
+---
+name: tailored-resume-generator
+description: Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
+---
+
+# Tailored Resume Generator
+
+## When to Use This Skill
+
+- Applying for a specific job position
+- Customizing your resume for different industries or roles
+- Highlighting relevant experience for career transitions
+- Optimizing your resume for ATS (Applicant Tracking Systems)
+- Creating multiple resume versions for different job applications
+- Emphasizing specific skills mentioned in job postings
+
+## What This Skill Does
+
+1. **Analyzes Job Descriptions**: Extracts key requirements, skills, qualifications, and keywords from job postings
+2. **Identifies Priorities**: Determines what employers value most based on the job description language and structure
+3. **Tailors Content**: Reorganizes and emphasizes relevant experience, skills, and achievements
+4. **Optimizes Keywords**: Incorporates ATS-friendly keywords naturally throughout the resume
+5. **Formats Professionally**: Creates clean, professional resume layouts suitable for various formats
+6. **Provides Recommendations**: Suggests improvements and highlights gaps to address
+
+## How to Use
+
+### Basic Usage
+Provide a job description and your background information:
+
+```
+I'm applying for this job:
+
+[paste job description]
+
+Here's my background:
+- 5 years as software engineer at TechCorp
+- Led team of 3 developers on mobile app project
+- Expert in Python, JavaScript, React
+- Computer Science degree from State University
+```
+
+### With Existing Resume
+Upload or paste your current resume along with the job description:
+
+```
+Please tailor my resume for this position:
+
+Job Description:
+[paste job description]
+
+My Current Resume:
+[paste resume content]
+```
+
+### Career Transition
+When changing industries or roles:
+
+```
+I'm transitioning from marketing to product management.
+Here's the job I'm applying for:
+
+[paste job description]
+
+My transferable experience:
+- 7 years in digital marketing
+- Led cross-functional teams
+- Managed product launches
+- Data analysis and A/B testing
+```
+
+## Example
+
+**User Request:**
+```
+I need a tailored resume for this job:
+
+Senior Data Analyst Position
+
+Requirements:
+- 5+ years experience in data analysis
+- Expert in SQL, Python, and data visualization tools
+- Experience with A/B testing and statistical analysis
+- Strong communication skills to present findings
+- Healthcare industry experience preferred
+
+My background:
+- Data Analyst at RetailCo (2019-2024)
+- Created dashboards using Tableau and Power BI
+- Built Python scripts for data automation
+- Worked with marketing team on campaign analysis
+- Business Analytics degree
+- Also did 1 year internship at HealthPlus clinic
+```
+
+**Generated Output:**
+
+```markdown
+# JOHN DOE
+Email: john.doe@email.com | Phone: (555) 123-4567 | LinkedIn: linkedin.com/in/johndoe
+
+## PROFESSIONAL SUMMARY
+Results-driven Data Analyst with 5+ years of experience leveraging SQL, Python, and advanced
+visualization tools to deliver actionable insights. Proven track record in statistical analysis,
+A/B testing, and cross-functional collaboration. Healthcare industry experience with strong
+ability to communicate complex data findings to stakeholders.
+
+## TECHNICAL SKILLS
+- **Data Analysis & Programming**: SQL, Python, Statistical Analysis, A/B Testing
+- **Visualization Tools**: Tableau, Power BI, Advanced Dashboard Development
+- **Data Management**: Data Automation, ETL Processes, Database Optimization
+- **Business Intelligence**: Campaign Analytics, Performance Metrics, KPI Tracking
+
+## PROFESSIONAL EXPERIENCE
+
+**Data Analyst** | RetailCo | 2019 - 2024
+- Designed and implemented 50+ SQL queries and Python automation scripts, reducing manual
+ data processing time by 60%
+- Conducted rigorous A/B testing and statistical analysis for marketing campaigns,
+ improving campaign ROI by 35%
+- Built interactive Tableau and Power BI dashboards for executive team, enabling
+ data-driven decision making
+- Presented analytical findings to cross-functional stakeholders including marketing,
+ operations, and executive leadership
+- Collaborated with marketing team to analyze customer behavior patterns and optimize
+ targeting strategies
+
+**Data Analysis Intern** | HealthPlus Clinic | 2018 - 2019
+- Supported healthcare analytics initiatives by analyzing patient data and operational metrics
+- Gained exposure to healthcare industry data management and HIPAA compliance requirements
+- Assisted in creating reports for clinical staff to improve patient care workflows
+
+## EDUCATION
+
+**Bachelor of Science in Business Analytics**
+State University | Graduated 2018
+
+## KEY ACHIEVEMENTS
+- Reduced data processing time by 60% through Python automation
+- Improved marketing campaign ROI by 35% through A/B testing and optimization
+- Created data visualization system now used across entire organization
+```
+
+**Additional Recommendations:**
+- Consider adding any specific healthcare projects or certifications
+- Quantify more achievements with metrics when possible
+- If you have experience with R or advanced statistical methods, add them
+- Consider mentioning any familiarity with healthcare regulations (HIPAA, etc.)
+
+---
+
+## Instructions
+
+When a user requests resume tailoring:
+
+### 1. Gather Information
+
+**Job Description Analysis**:
+- Request the full job description if not provided
+- Ask for the company name and job title
+
+**Candidate Background**:
+- If user provides existing resume, use it as the foundation
+- If not, request:
+ - Work history (job titles, companies, dates, responsibilities)
+ - Education background
+ - Key skills and technical proficiencies
+ - Notable achievements and metrics
+ - Certifications or awards
+ - Any other relevant information
+
+### 2. Analyze Job Requirements
+
+Extract and prioritize:
+- **Must-have qualifications**: Years of experience, required skills, education
+- **Key skills**: Technical tools, methodologies, competencies
+- **Soft skills**: Communication, leadership, teamwork
+- **Industry knowledge**: Domain-specific experience
+- **Keywords**: Repeated terms, phrases, and buzzwords for ATS optimization
+- **Company values**: Cultural fit indicators from job description
+
+Create a mental map of:
+- Priority 1: Critical requirements (deal-breakers)
+- Priority 2: Important qualifications (strongly desired)
+- Priority 3: Nice-to-have skills (bonus points)
+
+### 3. Map Candidate Experience to Requirements
+
+For each job requirement:
+- Identify matching experience from candidate's background
+- Find transferable skills if no direct match
+- Note gaps that need to be addressed or de-emphasized
+- Identify unique strengths to highlight
+
+### 4. Structure the Tailored Resume
+
+**Professional Summary** (3-4 lines):
+- Lead with years of experience in the target role/field
+- Include top 3-4 required skills from job description
+- Mention industry experience if relevant
+- Highlight unique value proposition
+
+**Technical/Core Skills Section**:
+- Group skills by category matching job requirements
+- List required tools and technologies first
+- Use exact terminology from job description
+- Only include skills you can substantiate with experience
+
+**Professional Experience**:
+- For each role, emphasize responsibilities and achievements aligned with job requirements
+- Use action verbs: Led, Developed, Implemented, Optimized, Managed, Created, Analyzed
+- **Quantify achievements**: Include numbers, percentages, timeframes, scale
+- Reorder bullet points to prioritize most relevant experience
+- Use keywords naturally from job description
+- Format: **[Action Verb] + [What] + [How/Why] + [Result/Impact]**
+
+**Education**:
+- List degrees, certifications relevant to position
+- Include relevant coursework if early career
+- Add certifications that match job requirements
+
+**Optional Sections** (if applicable):
+- Certifications & Licenses
+- Publications or Speaking Engagements
+- Awards & Recognition
+- Volunteer Work (if relevant to role)
+- Projects (especially for technical roles)
+
+### 5. Optimize for ATS (Applicant Tracking Systems)
+
+- Use standard section headings (Professional Experience, Education, Skills)
+- Incorporate exact keywords from job description naturally
+- Avoid tables, graphics, headers/footers, or complex formatting
+- Use standard fonts and bullet points
+- Include both acronyms and full terms (e.g., "SQL (Structured Query Language)")
+- Match job title terminology where truthful
+
+### 6. Format and Present
+
+**Format Options**:
+- **Markdown**: Clean, readable, easy to copy
+- **Plain Text**: ATS-optimized, safe for all systems
+- **Tips for Word/PDF**: Provide formatting guidance
+
+**Resume Structure Guidelines**:
+- Keep to 1 page for <10 years experience, 2 pages for 10+ years
+- Use consistent formatting and spacing
+- Ensure contact information is prominent
+- Use reverse chronological order (most recent first)
+- Maintain clean, scannable layout with white space
+
+### 7. Provide Strategic Recommendations
+
+After presenting the tailored resume, offer:
+
+**Strengths Analysis**:
+- What makes this candidate competitive
+- Unique qualifications to emphasize in cover letter or interview
+
+**Gap Analysis**:
+- Requirements not fully met
+- Suggestions for addressing gaps (courses, projects, reframing experience)
+
+**Interview Preparation Tips**:
+- Key talking points aligned with resume
+- Stories to prepare based on job requirements
+- Questions to ask that demonstrate fit
+
+**Cover Letter Hooks**:
+- Suggest 2-3 opening lines for cover letter
+- Key achievements to expand upon
+
+### 8. Iterate and Refine
+
+Ask if user wants to:
+- Adjust emphasis or tone
+- Add or remove sections
+- Generate alternative versions for different roles
+- Create format variations (traditional vs. modern)
+- Develop role-specific versions (if applying to multiple similar positions)
+
+### 9. Best Practices to Follow
+
+**Do**:
+- Be truthful and accurate - never fabricate experience
+- Use industry-standard terminology
+- Quantify achievements with specific metrics
+- Tailor each resume to specific job
+- Proofread for grammar and consistency
+- Keep language concise and impactful
+
+**Don't**:
+- Include personal information (age, marital status, photo unless requested)
+- Use first-person pronouns (I, me, my)
+- Include references ("available upon request" is outdated)
+- List every job if career is 20+ years (focus on relevant, recent experience)
+- Use generic templates without customization
+- Exceed 2 pages unless very senior role
+
+### 10. Special Considerations
+
+**Career Changers**:
+- Use functional or hybrid resume format
+- Emphasize transferable skills
+- Create compelling narrative in summary
+- Focus on relevant projects and coursework
+
+**Recent Graduates**:
+- Lead with education
+- Include relevant coursework, projects, internships
+- Emphasize leadership in student organizations
+- Include GPA if 3.5+
+
+**Senior Executives**:
+- Lead with executive summary
+- Focus on leadership and strategic impact
+- Include board memberships, speaking engagements
+- Emphasize revenue growth, team building, vision
+
+**Technical Roles**:
+- Include technical skills section prominently
+- List programming languages, frameworks, tools
+- Include GitHub, portfolio, or project links
+- Mention methodologies (Agile, Scrum, etc.)
+
+**Creative Roles**:
+- Include link to portfolio
+- Highlight creative achievements and campaigns
+- Mention tools and software proficiencies
+- Consider more creative formatting (while maintaining ATS compatibility)
+
+---
+
+## Tips for Best Results
+
+- **Be specific**: Provide complete job descriptions and detailed background information
+- **Share metrics**: Include numbers, percentages, and quantifiable achievements when describing your experience
+- **Indicate format preference**: Let the skill know if you need ATS-optimized, creative, or traditional format
+- **Mention constraints**: Share any specific requirements (page limits, sections to include/exclude)
+- **Iterate**: Don't hesitate to ask for revisions or alternative approaches
+- **Multiple applications**: Generate separate tailored versions for different roles
+
+## Privacy Note
+
+This skill processes your personal and professional information to generate tailored resumes. Always review the output before submitting to ensure accuracy and appropriateness. Remove or modify any information you prefer not to share with potential employers.
diff --git a/plugins/awesome-claude-skills/talenthr-automation/SKILL.md b/plugins/awesome-claude-skills/talenthr-automation/SKILL.md
new file mode 100644
index 0000000..936d503
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tally-automation/SKILL.md b/plugins/awesome-claude-skills/tally-automation/SKILL.md
new file mode 100644
index 0000000..900fd62
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tapfiliate-automation/SKILL.md b/plugins/awesome-claude-skills/tapfiliate-automation/SKILL.md
new file mode 100644
index 0000000..20f38db
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tapform-automation/SKILL.md b/plugins/awesome-claude-skills/tapform-automation/SKILL.md
new file mode 100644
index 0000000..fade454
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tavily-automation/SKILL.md b/plugins/awesome-claude-skills/tavily-automation/SKILL.md
new file mode 100644
index 0000000..0f8a214
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/taxjar-automation/SKILL.md b/plugins/awesome-claude-skills/taxjar-automation/SKILL.md
new file mode 100644
index 0000000..43d145b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/teamcamp-automation/SKILL.md b/plugins/awesome-claude-skills/teamcamp-automation/SKILL.md
new file mode 100644
index 0000000..576cab9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/telegram-automation/SKILL.md b/plugins/awesome-claude-skills/telegram-automation/SKILL.md
new file mode 100644
index 0000000..ef24a6e
--- /dev/null
+++ b/plugins/awesome-claude-skills/telegram-automation/SKILL.md
@@ -0,0 +1,224 @@
+---
+name: telegram-automation
+description: "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Telegram Automation via Rube MCP
+
+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)
+- Active Telegram connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `telegram`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+- Telegram Bot Token required (created via @BotFather)
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `telegram`
+3. If connection is not ACTIVE, follow the returned auth link to configure the Telegram bot
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Messages
+
+**When to use**: User wants to send text messages to a Telegram chat
+
+**Tool sequence**:
+1. `TELEGRAM_GET_ME` - Verify bot identity and connection [Prerequisite]
+2. `TELEGRAM_GET_CHAT` - Get chat details and verify access [Optional]
+3. `TELEGRAM_SEND_MESSAGE` - Send a text message [Required]
+
+**Key parameters**:
+- `chat_id`: Numeric chat ID or channel username (e.g., '@channelname')
+- `text`: Message text content
+- `parse_mode`: 'HTML' or 'MarkdownV2' for formatting
+- `disable_notification`: Send silently without notification sound
+- `reply_to_message_id`: Message ID to reply to
+
+**Pitfalls**:
+- Bot must be a member of the chat/group to send messages
+- MarkdownV2 requires escaping special characters: `_*[]()~>#+-=|{}.!`
+- HTML mode supports limited tags: ``, ``, ``, ``, ``
+- Messages have a 4096 character limit; split longer content
+
+### 2. Send Photos and Documents
+
+**When to use**: User wants to share images or files in a Telegram chat
+
+**Tool sequence**:
+1. `TELEGRAM_SEND_PHOTO` - Send an image [Optional]
+2. `TELEGRAM_SEND_DOCUMENT` - Send a file/document [Optional]
+
+**Key parameters**:
+- `chat_id`: Target chat ID
+- `photo`: Photo URL or file_id (for SEND_PHOTO)
+- `document`: Document URL or file_id (for SEND_DOCUMENT)
+- `caption`: Optional caption for the media
+
+**Pitfalls**:
+- Photo captions have a 1024 character limit
+- Document captions also have a 1024 character limit
+- Files up to 50MB can be sent via bot API
+- Photos are compressed by Telegram; use SEND_DOCUMENT for uncompressed images
+
+### 3. Manage Chats
+
+**When to use**: User wants to get chat information or manage chat settings
+
+**Tool sequence**:
+1. `TELEGRAM_GET_CHAT` - Get detailed chat information [Required]
+2. `TELEGRAM_GET_CHAT_ADMINISTRATORS` - List chat admins [Optional]
+3. `TELEGRAM_GET_CHAT_MEMBERS_COUNT` - Get member count [Optional]
+4. `TELEGRAM_EXPORT_CHAT_INVITE_LINK` - Generate invite link [Optional]
+
+**Key parameters**:
+- `chat_id`: Target chat ID or username
+
+**Pitfalls**:
+- Bot must be an administrator to export invite links
+- GET_CHAT returns different fields for private chats vs groups vs channels
+- Member count may be approximate for very large groups
+- Admin list does not include regular members
+
+### 4. Edit and Delete Messages
+
+**When to use**: User wants to modify or remove previously sent messages
+
+**Tool sequence**:
+1. `TELEGRAM_EDIT_MESSAGE` - Edit a sent message [Optional]
+2. `TELEGRAM_DELETE_MESSAGE` - Delete a message [Optional]
+
+**Key parameters**:
+- `chat_id`: Chat where the message is located
+- `message_id`: ID of the message to edit or delete
+- `text`: New text content (for edit)
+
+**Pitfalls**:
+- Bots can only edit their own messages
+- Messages can only be deleted within 48 hours of sending
+- In groups, bots with delete permissions can delete any message
+- Editing a message removes its 'edited' timestamp history
+
+### 5. Forward Messages and Get Updates
+
+**When to use**: User wants to forward messages or retrieve recent updates
+
+**Tool sequence**:
+1. `TELEGRAM_FORWARD_MESSAGE` - Forward a message to another chat [Optional]
+2. `TELEGRAM_GET_UPDATES` - Get recent bot updates/messages [Optional]
+3. `TELEGRAM_GET_CHAT_HISTORY` - Get chat message history [Optional]
+
+**Key parameters**:
+- `from_chat_id`: Source chat for forwarding
+- `chat_id`: Destination chat for forwarding
+- `message_id`: Message to forward
+- `offset`: Update offset for GET_UPDATES
+- `limit`: Number of updates to retrieve
+
+**Pitfalls**:
+- Forwarded messages show the original sender attribution
+- GET_UPDATES returns a limited window of recent updates
+- Chat history access may be limited by bot permissions and chat type
+- Use offset to avoid processing the same update twice
+
+### 6. Manage Bot Commands
+
+**When to use**: User wants to set or update bot command menu
+
+**Tool sequence**:
+1. `TELEGRAM_SET_MY_COMMANDS` - Set the bot's command list [Required]
+2. `TELEGRAM_ANSWER_CALLBACK_QUERY` - Respond to inline button presses [Optional]
+
+**Key parameters**:
+- `commands`: Array of command objects with `command` and `description`
+- `callback_query_id`: ID of the callback query to answer
+
+**Pitfalls**:
+- Commands must start with '/' and be lowercase
+- Command descriptions have a 256 character limit
+- Callback queries must be answered within 10 seconds or they expire
+- Setting commands replaces the entire command list
+
+## Common Patterns
+
+### Chat ID Resolution
+
+**From username**:
+```
+1. Use '@username' format as chat_id (for public channels/groups)
+2. For private chats, numeric chat_id is required
+3. Call GET_CHAT with username to retrieve numeric ID
+```
+
+**From GET_UPDATES**:
+```
+1. Call TELEGRAM_GET_UPDATES
+2. Extract chat.id from message objects
+3. Use numeric chat_id in subsequent calls
+```
+
+### Message Formatting
+
+- Use `parse_mode: 'HTML'` for `bold`, `italic`, `code`
+- Use `parse_mode: 'MarkdownV2'` for `*bold*`, `_italic_`, `` `code` ``
+- Escape special chars in MarkdownV2: `_ * [ ] ( ) ~ > # + - = | { } . !`
+- Omit parse_mode for plain text without formatting
+
+## Known Pitfalls
+
+**Bot Permissions**:
+- Bots must be added to groups/channels to interact
+- Admin permissions needed for: deleting messages, exporting invite links, managing members
+- Bots cannot initiate conversations; users must start them first
+
+**Rate Limits**:
+- 30 messages per second to the same group
+- 20 messages per minute to the same user in groups
+- Bulk operations should implement delays between calls
+- API returns 429 Too Many Requests when limits are hit
+
+**Chat Types**:
+- Private chat: One-on-one with the bot
+- Group: Multi-user chat (bot must be added)
+- Supergroup: Enhanced group with admin features
+- Channel: Broadcast-only (bot must be admin to post)
+
+**Message Limits**:
+- Text messages: 4096 characters max
+- Captions: 1024 characters max
+- File uploads: 50MB max via bot API
+- Inline keyboard buttons: 8 per row
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Verify bot | TELEGRAM_GET_ME | (none) |
+| Send message | TELEGRAM_SEND_MESSAGE | chat_id, text, parse_mode |
+| Send photo | TELEGRAM_SEND_PHOTO | chat_id, photo, caption |
+| Send document | TELEGRAM_SEND_DOCUMENT | chat_id, document, caption |
+| Edit message | TELEGRAM_EDIT_MESSAGE | chat_id, message_id, text |
+| Delete message | TELEGRAM_DELETE_MESSAGE | chat_id, message_id |
+| Forward message | TELEGRAM_FORWARD_MESSAGE | chat_id, from_chat_id, message_id |
+| Get chat info | TELEGRAM_GET_CHAT | chat_id |
+| Get chat admins | TELEGRAM_GET_CHAT_ADMINISTRATORS | chat_id |
+| Get member count | TELEGRAM_GET_CHAT_MEMBERS_COUNT | chat_id |
+| Export invite link | TELEGRAM_EXPORT_CHAT_INVITE_LINK | chat_id |
+| Get updates | TELEGRAM_GET_UPDATES | offset, limit |
+| 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/plugins/awesome-claude-skills/telnyx-automation/SKILL.md b/plugins/awesome-claude-skills/telnyx-automation/SKILL.md
new file mode 100644
index 0000000..8d417ef
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/teltel-automation/SKILL.md b/plugins/awesome-claude-skills/teltel-automation/SKILL.md
new file mode 100644
index 0000000..12229f7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/templated-automation/SKILL.md b/plugins/awesome-claude-skills/templated-automation/SKILL.md
new file mode 100644
index 0000000..69ef6de
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/test-app-automation/SKILL.md b/plugins/awesome-claude-skills/test-app-automation/SKILL.md
new file mode 100644
index 0000000..cc9423d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/text-to-pdf-automation/SKILL.md b/plugins/awesome-claude-skills/text-to-pdf-automation/SKILL.md
new file mode 100644
index 0000000..9d23e33
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/textcortex-automation/SKILL.md b/plugins/awesome-claude-skills/textcortex-automation/SKILL.md
new file mode 100644
index 0000000..871b91e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/textit-automation/SKILL.md b/plugins/awesome-claude-skills/textit-automation/SKILL.md
new file mode 100644
index 0000000..370842c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/textrazor-automation/SKILL.md b/plugins/awesome-claude-skills/textrazor-automation/SKILL.md
new file mode 100644
index 0000000..dcdcbf7
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/thanks-io-automation/SKILL.md b/plugins/awesome-claude-skills/thanks-io-automation/SKILL.md
new file mode 100644
index 0000000..1797bc2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/the-odds-api-automation/SKILL.md b/plugins/awesome-claude-skills/the-odds-api-automation/SKILL.md
new file mode 100644
index 0000000..b2401eb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ticketmaster-automation/SKILL.md b/plugins/awesome-claude-skills/ticketmaster-automation/SKILL.md
new file mode 100644
index 0000000..55ac578
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ticktick-automation/SKILL.md b/plugins/awesome-claude-skills/ticktick-automation/SKILL.md
new file mode 100644
index 0000000..9f66e0b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tiktok-automation/SKILL.md b/plugins/awesome-claude-skills/tiktok-automation/SKILL.md
new file mode 100644
index 0000000..29512b6
--- /dev/null
+++ b/plugins/awesome-claude-skills/tiktok-automation/SKILL.md
@@ -0,0 +1,183 @@
+---
+name: tiktok-automation
+description: "Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# TikTok Automation via Rube MCP
+
+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)
+- Active TikTok connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `tiktok`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tiktok`
+3. If connection is not ACTIVE, follow the returned auth link to complete TikTok OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Upload and Publish a Video
+
+**When to use**: User wants to upload a video and publish it to TikTok
+
+**Tool sequence**:
+1. `TIKTOK_UPLOAD_VIDEO` or `TIKTOK_UPLOAD_VIDEOS` - Upload video file(s) [Required]
+2. `TIKTOK_FETCH_PUBLISH_STATUS` - Check upload/processing status [Required]
+3. `TIKTOK_PUBLISH_VIDEO` - Publish the uploaded video [Required]
+
+**Key parameters for upload**:
+- `video`: Video file object with `s3key`, `mimetype`, `name`
+- `title`: Video title/caption
+
+**Key parameters for publish**:
+- `publish_id`: ID returned from upload step
+- `title`: Video caption text
+- `privacy_level`: 'PUBLIC_TO_EVERYONE', 'MUTUAL_FOLLOW_FRIENDS', 'FOLLOWER_OF_CREATOR', 'SELF_ONLY'
+- `disable_duet`: Disable duet feature
+- `disable_stitch`: Disable stitch feature
+- `disable_comment`: Disable comments
+
+**Pitfalls**:
+- Video upload and publish are TWO separate steps; upload first, then publish
+- After upload, poll FETCH_PUBLISH_STATUS until processing is complete before publishing
+- Video must meet TikTok requirements: MP4/WebM format, max 10 minutes, max 4GB
+- Caption/title has character limits; check current TikTok guidelines
+- Privacy level strings are case-sensitive and must match exactly
+- Processing may take 30-120 seconds depending on video size
+
+### 2. Post a Photo
+
+**When to use**: User wants to post a photo to TikTok
+
+**Tool sequence**:
+1. `TIKTOK_POST_PHOTO` - Upload and post a photo [Required]
+2. `TIKTOK_FETCH_PUBLISH_STATUS` - Check processing status [Optional]
+
+**Key parameters**:
+- `photo`: Photo file object with `s3key`, `mimetype`, `name`
+- `title`: Photo caption text
+- `privacy_level`: Privacy setting for the post
+
+**Pitfalls**:
+- Photo posts are a newer TikTok feature; availability may vary by account type
+- Supported formats: JPEG, PNG, WebP
+- Image size and dimension limits apply; check current TikTok guidelines
+
+### 3. List and Manage Videos
+
+**When to use**: User wants to view their published videos
+
+**Tool sequence**:
+1. `TIKTOK_LIST_VIDEOS` - List user's published videos [Required]
+
+**Key parameters**:
+- `max_count`: Number of videos to return per page
+- `cursor`: Pagination cursor for next page
+
+**Pitfalls**:
+- Only returns the authenticated user's own videos
+- Response includes video metadata: id, title, create_time, share_url, duration, etc.
+- Pagination uses cursor-based approach; check for `has_more` and `cursor` in response
+- Recently published videos may not appear immediately in the list
+
+### 4. View User Profile and Stats
+
+**When to use**: User wants to check their TikTok profile info or account statistics
+
+**Tool sequence**:
+1. `TIKTOK_GET_USER_PROFILE` - Get full profile information [Required]
+2. `TIKTOK_GET_USER_STATS` - Get account statistics [Optional]
+3. `TIKTOK_GET_USER_BASIC_INFO` - Get basic user info [Alternative]
+
+**Key parameters**: (no required parameters; returns data for authenticated user)
+
+**Pitfalls**:
+- Profile data is for the authenticated user only; cannot view other users' profiles
+- Stats include follower count, following count, video count, likes received
+- `GET_USER_PROFILE` returns more details than `GET_USER_BASIC_INFO`
+- Stats may have slight delays; not real-time
+
+### 5. Check Publish Status
+
+**When to use**: User wants to check the status of a content upload or publish operation
+
+**Tool sequence**:
+1. `TIKTOK_FETCH_PUBLISH_STATUS` - Poll for status updates [Required]
+
+**Key parameters**:
+- `publish_id`: The publish ID from a previous upload/publish operation
+
+**Pitfalls**:
+- Status values include processing, success, and failure states
+- Poll at reasonable intervals (5-10 seconds) to avoid rate limits
+- Failed publishes include error details in the response
+- Content moderation may cause delays or rejections after processing
+
+## Common Patterns
+
+### Video Publish Flow
+
+```
+1. Upload video via TIKTOK_UPLOAD_VIDEO -> get publish_id
+2. Poll TIKTOK_FETCH_PUBLISH_STATUS with publish_id until complete
+3. If status is ready, call TIKTOK_PUBLISH_VIDEO with final settings
+4. Optionally poll status again to confirm publication
+```
+
+### Pagination
+
+- Use `cursor` from previous response for next page
+- Check `has_more` boolean to determine if more results exist
+- `max_count` controls page size
+
+## Known Pitfalls
+
+**Content Requirements**:
+- Videos: MP4/WebM, max 4GB, max 10 minutes
+- Photos: JPEG/PNG/WebP
+- Captions: Character limits vary by region
+- Content must comply with TikTok community guidelines
+
+**Authentication**:
+- OAuth tokens have scopes; ensure video.upload and video.publish are authorized
+- Tokens expire; re-authenticate if operations fail with 401
+
+**Rate Limits**:
+- TikTok API has strict rate limits per application
+- Implement exponential backoff on 429 responses
+- Upload operations have daily limits
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Publish IDs are strings; use exactly as returned
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Upload video | TIKTOK_UPLOAD_VIDEO | video, title |
+| Upload multiple videos | TIKTOK_UPLOAD_VIDEOS | videos |
+| Publish video | TIKTOK_PUBLISH_VIDEO | publish_id, title, privacy_level |
+| Post photo | TIKTOK_POST_PHOTO | photo, title, privacy_level |
+| List videos | TIKTOK_LIST_VIDEOS | max_count, cursor |
+| Get profile | TIKTOK_GET_USER_PROFILE | (none) |
+| 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/plugins/awesome-claude-skills/timecamp-automation/SKILL.md b/plugins/awesome-claude-skills/timecamp-automation/SKILL.md
new file mode 100644
index 0000000..c311982
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/timekit-automation/SKILL.md b/plugins/awesome-claude-skills/timekit-automation/SKILL.md
new file mode 100644
index 0000000..3765b8a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/timelinesai-automation/SKILL.md b/plugins/awesome-claude-skills/timelinesai-automation/SKILL.md
new file mode 100644
index 0000000..25a0a84
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/timelink-automation/SKILL.md b/plugins/awesome-claude-skills/timelink-automation/SKILL.md
new file mode 100644
index 0000000..6edaa5c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/timely-automation/SKILL.md b/plugins/awesome-claude-skills/timely-automation/SKILL.md
new file mode 100644
index 0000000..c66eca2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tinyurl-automation/SKILL.md b/plugins/awesome-claude-skills/tinyurl-automation/SKILL.md
new file mode 100644
index 0000000..ba8f18f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tisane-automation/SKILL.md b/plugins/awesome-claude-skills/tisane-automation/SKILL.md
new file mode 100644
index 0000000..4da0732
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/todoist-automation/SKILL.md b/plugins/awesome-claude-skills/todoist-automation/SKILL.md
new file mode 100644
index 0000000..7fd2ff1
--- /dev/null
+++ b/plugins/awesome-claude-skills/todoist-automation/SKILL.md
@@ -0,0 +1,236 @@
+---
+name: todoist-automation
+description: Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Todoist Automation via Rube MCP
+
+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)
+- Active Todoist connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `todoist`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `todoist`
+3. If connection is not ACTIVE, follow the returned auth link to complete Todoist OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Tasks
+
+**When to use**: User wants to create, update, complete, reopen, or delete tasks
+
+**Tool sequence**:
+1. `TODOIST_GET_ALL_PROJECTS` - List projects to find the target project ID [Prerequisite]
+2. `TODOIST_GET_ALL_SECTIONS` - List sections within a project for task placement [Optional]
+3. `TODOIST_CREATE_TASK` - Create a single task with content, due date, priority, labels [Required]
+4. `TODOIST_BULK_CREATE_TASKS` - Create multiple tasks in one request [Alternative]
+5. `TODOIST_UPDATE_TASK` - Modify task properties (content, due date, priority, labels) [Optional]
+6. `TODOIST_CLOSE_TASK` - Mark a task as completed [Optional]
+7. `TODOIST_REOPEN_TASK` - Restore a previously completed task [Optional]
+8. `TODOIST_DELETE_TASK` - Permanently remove a task [Optional]
+
+**Key parameters for CREATE_TASK**:
+- `content`: Task title (supports markdown and hyperlinks)
+- `description`: Additional notes (do NOT put due dates here)
+- `project_id`: Alphanumeric project ID; omit to add to Inbox
+- `section_id`: Alphanumeric section ID for placement within a project
+- `parent_id`: Task ID for creating subtasks
+- `priority`: 1 (normal) to 4 (urgent) -- note: Todoist UI shows p1=urgent, API p4=urgent
+- `due_string`: Natural language date like `"tomorrow at 3pm"`, `"every Friday at 9am"`
+- `due_date`: Specific date `YYYY-MM-DD` format
+- `due_datetime`: Specific date+time in RFC3339 `YYYY-MM-DDTHH:mm:ssZ`
+- `labels`: Array of label name strings
+- `duration` + `duration_unit`: Task duration (e.g., `30` + `"minute"`)
+
+**Pitfalls**:
+- Only one `due_*` field can be used at a time (except `due_lang` which can accompany any)
+- Do NOT embed due dates in `content` or `description` -- use `due_string` field
+- Do NOT embed duration phrases like "for 30 minutes" in `due_string` -- use `duration` + `duration_unit`
+- `priority` in API: 1=normal, 4=urgent (opposite of Todoist UI display where p1=urgent)
+- Task IDs can be numeric or alphanumeric; use the format returned by the API
+- `CLOSE_TASK` marks complete; `DELETE_TASK` permanently removes -- they are different operations
+
+### 2. Manage Projects
+
+**When to use**: User wants to list, create, update, or inspect projects
+
+**Tool sequence**:
+1. `TODOIST_GET_ALL_PROJECTS` - List all projects with metadata [Required]
+2. `TODOIST_GET_PROJECT` - Get details for a specific project by ID [Optional]
+3. `TODOIST_CREATE_PROJECT` - Create a new project with name, color, view style [Optional]
+4. `TODOIST_UPDATE_PROJECT` - Modify project properties [Optional]
+
+**Key parameters**:
+- `name`: Project name (required for creation)
+- `color`: Todoist palette color (e.g., `"blue"`, `"red"`, `"green"`, `"charcoal"`)
+- `view_style`: `"list"` or `"board"` layout
+- `parent_id`: Parent project ID for creating sub-projects
+- `is_favorite` / `favorite`: Boolean to mark as favorite
+- `project_id`: Required for update and get operations
+
+**Pitfalls**:
+- Projects with similar names can lead to selecting the wrong project_id; always verify
+- `CREATE_PROJECT` uses `favorite` while `UPDATE_PROJECT` uses `is_favorite` -- different field names
+- Use the project `id` returned by API, not the `v2_id`, for downstream operations
+- Alphanumeric/URL-style project IDs may cause HTTP 400 in some tools; use numeric ID if available
+
+### 3. Manage Sections
+
+**When to use**: User wants to organize tasks within projects using sections
+
+**Tool sequence**:
+1. `TODOIST_GET_ALL_PROJECTS` - Find the target project ID [Prerequisite]
+2. `TODOIST_GET_ALL_SECTIONS` - List existing sections to avoid duplicates [Prerequisite]
+3. `TODOIST_CREATE_SECTION` - Create a new section in a project [Required]
+4. `TODOIST_UPDATE_SECTION` - Rename an existing section [Optional]
+5. `TODOIST_DELETE_SECTION` - Permanently remove a section [Optional]
+
+**Key parameters**:
+- `project_id`: Required -- the project to create the section in
+- `name`: Section name (required for creation)
+- `order`: Integer position within the project (lower values appear first)
+- `section_id`: Required for update and delete operations
+
+**Pitfalls**:
+- `CREATE_SECTION` requires `project_id` and `name` -- omitting project_id causes a 400 error
+- HTTP 400 "project_id is invalid" can occur if alphanumeric ID is used; prefer numeric ID
+- Deleting a section may move or regroup its tasks in non-obvious ways
+- Response may include both `id` and `v2_id`; store and reuse the correct identifier consistently
+- Always check existing sections first to avoid creating duplicates
+
+### 4. Search and Filter Tasks
+
+**When to use**: User wants to find tasks by criteria, view today's tasks, or get completed task history
+
+**Tool sequence**:
+1. `TODOIST_GET_ALL_TASKS` - Fetch incomplete tasks with optional filter query [Required]
+2. `TODOIST_GET_TASK` - Get full details of a specific task by ID [Optional]
+3. `TODOIST_GET_COMPLETED_TASKS_BY_COMPLETION_DATE` - Retrieve completed tasks within a date range [Optional]
+4. `TODOIST_LIST_FILTERS` - List user's custom saved filters [Optional]
+
+**Key parameters for GET_ALL_TASKS**:
+- `filter`: Todoist filter syntax string
+ - Keywords: `today`, `tomorrow`, `overdue`, `no date`, `recurring`, `subtask`
+ - Priority: `p1` (urgent), `p2`, `p3`, `p4` (normal)
+ - Projects: `#ProjectName` (must exist in account)
+ - Labels: `@LabelName` (must exist in account)
+ - Date ranges: `7 days`, `-7 days`, `due before: YYYY-MM-DD`, `due after: YYYY-MM-DD`
+ - Search: `search: keyword` for content text search
+ - Operators: `&` (AND), `|` (OR), `!` (NOT)
+- `ids`: List of specific task IDs to retrieve
+
+**Key parameters for GET_COMPLETED_TASKS_BY_COMPLETION_DATE**:
+- `since`: Start date in RFC3339 format (e.g., `2024-01-01T00:00:00Z`)
+- `until`: End date in RFC3339 format
+- `project_id`, `section_id`, `parent_id`: Optional filters
+- `cursor`: Pagination cursor from previous response
+- `limit`: Max results per page (default 50)
+
+**Pitfalls**:
+- `GET_ALL_TASKS` returns ONLY incomplete tasks; use `GET_COMPLETED_TASKS_BY_COMPLETION_DATE` for completed ones
+- Filter terms must reference ACTUAL EXISTING entities; arbitrary text causes HTTP 400 errors
+- Do NOT use `completed`, `!completed`, or `completed after` in GET_ALL_TASKS filter -- causes 400 error
+- `GET_COMPLETED_TASKS_BY_COMPLETION_DATE` limits date range to approximately 3 months between `since` and `until`
+- Search uses `search: keyword` syntax within the filter, not a separate parameter
+
+### 5. Bulk Task Creation
+
+**When to use**: User wants to scaffold a project with multiple tasks at once
+
+**Tool sequence**:
+1. `TODOIST_GET_ALL_PROJECTS` - Find target project ID [Prerequisite]
+2. `TODOIST_GET_ALL_SECTIONS` - Find section IDs for task placement [Optional]
+3. `TODOIST_BULK_CREATE_TASKS` - Create multiple tasks in a single request [Required]
+
+**Key parameters**:
+- `tasks`: Array of task objects, each requiring at minimum `content`
+- Each task object supports: `content`, `description`, `project_id`, `section_id`, `parent_id`, `priority`, `labels`, `due` (object with `string`, `date`, or `datetime`), `duration`, `order`
+
+**Pitfalls**:
+- Each task in the array must have at least the `content` field
+- The `due` field in bulk create is an object with nested fields (`string`, `date`, `datetime`, `lang`) -- different structure from CREATE_TASK's flat fields
+- All tasks can target different projects/sections within the same batch
+
+## Common Patterns
+
+### ID Resolution
+Always resolve human-readable names to IDs before operations:
+- **Project name -> Project ID**: `TODOIST_GET_ALL_PROJECTS`, match by `name` field
+- **Section name -> Section ID**: `TODOIST_GET_ALL_SECTIONS` with `project_id`
+- **Task content -> Task ID**: `TODOIST_GET_ALL_TASKS` with `filter` or `search: keyword`
+
+### Pagination
+- `TODOIST_GET_ALL_TASKS`: Returns all matching incomplete tasks (no pagination needed)
+- `TODOIST_GET_COMPLETED_TASKS_BY_COMPLETION_DATE`: Uses cursor-based pagination; follow `cursor` from response until no more results
+- `TODOIST_GET_ALL_PROJECTS` and `TODOIST_GET_ALL_SECTIONS`: Return all results (no pagination)
+
+### Due Date Handling
+- Natural language: Use `due_string` (e.g., `"tomorrow at 3pm"`, `"every Monday"`)
+- Specific date: Use `due_date` in `YYYY-MM-DD` format
+- Specific datetime: Use `due_datetime` in RFC3339 format (`YYYY-MM-DDTHH:mm:ssZ`)
+- Only use ONE due field at a time (except `due_lang` which can accompany any)
+- Recurring tasks: Use natural language in `due_string` (e.g., `"every Friday at 9am"`)
+
+## Known Pitfalls
+
+### ID Formats
+- Task IDs can be numeric (`"2995104339"`) or alphanumeric (`"6X4Vw2Hfmg73Q2XR"`)
+- Project IDs similarly vary; prefer the format returned by the API
+- Some tools accept only numeric IDs; if 400 error occurs, try fetching the numeric `id` via GET_PROJECT
+- Response objects may contain both `id` and `v2_id`; use `id` for API operations
+
+### Priority Inversion
+- API priority: 1 = normal, 4 = urgent
+- Todoist UI display: p1 = urgent, p4 = normal
+- This is inverted; always clarify with the user which convention they mean
+
+### Filter Syntax
+- Filter terms must reference real entities in the user's account
+- `#NonExistentProject` or `@NonExistentLabel` will cause HTTP 400
+- Use `search: keyword` for text search, not bare keywords
+- Combine with `&` (AND), `|` (OR), `!` (NOT)
+- `completed` filters do NOT work on GET_ALL_TASKS endpoint
+
+### Rate Limits
+- Todoist API has rate limits; batch operations should use `BULK_CREATE_TASKS` where possible
+- Space out rapid sequential requests to avoid throttling
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List all projects | `TODOIST_GET_ALL_PROJECTS` | (none) |
+| Get project | `TODOIST_GET_PROJECT` | `project_id` |
+| Create project | `TODOIST_CREATE_PROJECT` | `name`, `color`, `view_style` |
+| Update project | `TODOIST_UPDATE_PROJECT` | `project_id`, `name`, `color` |
+| List sections | `TODOIST_GET_ALL_SECTIONS` | `project_id` |
+| Create section | `TODOIST_CREATE_SECTION` | `project_id`, `name`, `order` |
+| Update section | `TODOIST_UPDATE_SECTION` | `section_id`, `name` |
+| Delete section | `TODOIST_DELETE_SECTION` | `section_id` |
+| Get all tasks | `TODOIST_GET_ALL_TASKS` | `filter`, `ids` |
+| Get task | `TODOIST_GET_TASK` | `task_id` |
+| Create task | `TODOIST_CREATE_TASK` | `content`, `project_id`, `due_string`, `priority` |
+| Bulk create tasks | `TODOIST_BULK_CREATE_TASKS` | `tasks` (array) |
+| Update task | `TODOIST_UPDATE_TASK` | `task_id`, `content`, `due_string` |
+| Complete task | `TODOIST_CLOSE_TASK` | `task_id` |
+| Reopen task | `TODOIST_REOPEN_TASK` | `task_id` |
+| 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/plugins/awesome-claude-skills/toggl-automation/SKILL.md b/plugins/awesome-claude-skills/toggl-automation/SKILL.md
new file mode 100644
index 0000000..dfc4b25
--- /dev/null
+++ b/plugins/awesome-claude-skills/toggl-automation/SKILL.md
@@ -0,0 +1,157 @@
+---
+name: Toggl Automation
+description: "Automate time tracking workflows in Toggl Track -- create time entries, manage projects, clients, tags, and workspaces through natural language commands."
+requires:
+ mcp:
+ - rube
+---
+
+# Toggl Automation
+
+Automate your Toggl Track time tracking operations directly from Claude Code. Log time, manage projects and clients, organize with tags, and control workspaces -- all without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/toggl](https://composio.dev/toolkits/toggl)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your Claude Code config with URL: `https://rube.app/mcp`
+2. When prompted, authenticate your Toggl Track account through the connection link provided
+3. Start automating your time tracking workflows with natural language
+
+---
+
+## Core Workflows
+
+### 1. Create and Stop Time Entries
+
+Log time with project, task, and tag associations, or start/stop timers.
+
+**Tools:** `TOGGL_CREATE_TIME_ENTRY`, `TOGGL_PATCH_STOP_TIME_ENTRY`
+
+```
+Start a time entry in workspace 123456 for project 78910 tagged "meeting" and "design" with description "Design review session"
+```
+
+Key parameters for `TOGGL_CREATE_TIME_ENTRY`:
+- `workspace_id` (required) -- target workspace
+- `created_with` (required) -- client application name (e.g., `"api_client"`)
+- `start` (required) -- ISO 8601 timestamp
+- `stop` -- ISO 8601 end time; omit to leave the entry running
+- `duration` -- duration in seconds; omit for running entries
+- `project_id` -- associate with a project
+- `task_id` -- associate with a task
+- `tags` -- array of tag name strings (not IDs)
+- `description` -- description of the work
+- `billable` -- billable status
+
+Key parameters for `TOGGL_PATCH_STOP_TIME_ENTRY`:
+- `workspace_id` (required) and `time_entry_id` (required)
+
+### 2. Manage Projects
+
+Create new projects and list existing ones with client details and pagination.
+
+**Tools:** `TOGGL_CREATE_PROJECT`, `TOGGL_GET_PROJECTS`, `TOGGL_GET_PROJECT_DETAILS`
+
+```
+Create a private billable project called "Q1 Marketing Campaign" in workspace 123456 for client 78910
+```
+
+Key parameters for `TOGGL_CREATE_PROJECT`:
+- `workspace_id` (required) and `name` (required)
+- `client_id`, `billable`, `is_private`, `active`, `color`
+- `estimated_hours`, `rate`, `fixed_fee`, `currency` (premium features)
+
+Key parameters for `TOGGL_GET_PROJECTS`:
+- `workspace_id` (required)
+- `page` / `page_size` (1-200) for pagination
+- `since` / `until` -- Unix timestamps for modification filtering (last 3 months only)
+- `clients: true` to include full client details
+
+### 3. Manage Clients
+
+Create and list clients within a workspace.
+
+**Tools:** `TOGGL_CREATE_CLIENT`, `TOGGL_GET_LIST_CLIENTS`
+
+```
+List all active clients in workspace 123456, then create a new client called "Acme Corp"
+```
+
+- `TOGGL_CREATE_CLIENT` requires `workspace_id` and `name`; accepts `notes`, `external_reference`
+- `TOGGL_GET_LIST_CLIENTS` requires `workspace_id`; supports `status` (`"active"`, `"archived"`, `"both"`) and `name` (case-insensitive search)
+
+### 4. Tags and Workspace Preferences
+
+Retrieve tags for categorization and check workspace settings.
+
+**Tools:** `TOGGL_GET_TAGS`, `TOGGL_GET_WORKSPACE_PREFERENCES`
+
+```
+Show me all tags in workspace 123456 and the workspace preferences
+```
+
+- `TOGGL_GET_TAGS` requires `workspace_id`; returns tag IDs and names
+- `TOGGL_GET_WORKSPACE_PREFERENCES` requires `workspace_id`; returns pricing plan and display settings
+
+### 5. Workspace Discovery
+
+List all workspaces the authenticated user belongs to.
+
+**Tool:** `TOGGL_GET_USER_WORKSPACES`
+
+```
+What Toggl workspaces do I have access to?
+```
+
+- No parameters required
+- Returns all workspaces with IDs, names, and metadata
+- Use this first to discover workspace IDs for other operations
+
+### 6. User Project Visibility
+
+List projects visible to the authenticated user.
+
+**Tool:** `TOGGL_GET_USER_PROJECTS`
+
+```
+Show me all projects I can see across my workspaces
+```
+
+- Returns projects the authenticated user has access to
+- Use alongside `TOGGL_GET_PROJECTS` for workspace-scoped views
+
+---
+
+## Known Pitfalls
+
+- **Tags use names, not IDs:** `TOGGL_CREATE_TIME_ENTRY` accepts tag names as strings in the `tags` array, unlike many APIs that use IDs. Use `TOGGL_GET_TAGS` to verify available tag names.
+- **`created_with` is required:** Every time entry must include `created_with` (e.g., `"api_client"`). Missing this field causes silent failures.
+- **Duration is in seconds:** The `duration` parameter on time entries is in seconds, not hours. 1 hour = 3600 seconds.
+- **`since` timestamp restriction:** The `since` filter on `TOGGL_GET_PROJECTS` only allows timestamps within the last 3 months. Older queries will be rejected.
+- **Premium features gated:** Custom colors, templates, fixed fees, and hourly rates on projects require a premium Toggl plan. Non-premium accounts will get errors when using these fields.
+- **Workspace ID required everywhere:** Nearly all Toggl tools require `workspace_id`. Always call `TOGGL_GET_USER_WORKSPACES` first to resolve it.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `TOGGL_CREATE_TIME_ENTRY` | Create a time entry or running timer (requires `workspace_id`, `created_with`, `start`) |
+| `TOGGL_PATCH_STOP_TIME_ENTRY` | Stop a running time entry (requires `workspace_id`, `time_entry_id`) |
+| `TOGGL_GET_PROJECTS` | List projects in a workspace with pagination |
+| `TOGGL_GET_PROJECT_DETAILS` | Get details for a specific project |
+| `TOGGL_CREATE_PROJECT` | Create a new project (requires `workspace_id`, `name`) |
+| `TOGGL_GET_LIST_CLIENTS` | List clients with status/name filters (requires `workspace_id`) |
+| `TOGGL_CREATE_CLIENT` | Create a new client (requires `workspace_id`, `name`) |
+| `TOGGL_GET_TAGS` | List all tags in a workspace (requires `workspace_id`) |
+| `TOGGL_GET_WORKSPACE_PREFERENCES` | Get workspace settings (requires `workspace_id`) |
+| `TOGGL_GET_USER_WORKSPACES` | List all workspaces for the authenticated user |
+| `TOGGL_GET_USER_PROJECTS` | List projects visible to the authenticated user |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/token-metrics-automation/SKILL.md b/plugins/awesome-claude-skills/token-metrics-automation/SKILL.md
new file mode 100644
index 0000000..aa37de3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tomba-automation/SKILL.md b/plugins/awesome-claude-skills/tomba-automation/SKILL.md
new file mode 100644
index 0000000..d33258b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tomtom-automation/SKILL.md b/plugins/awesome-claude-skills/tomtom-automation/SKILL.md
new file mode 100644
index 0000000..3ff1249
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/toneden-automation/SKILL.md b/plugins/awesome-claude-skills/toneden-automation/SKILL.md
new file mode 100644
index 0000000..15327f2
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tpscheck-automation/SKILL.md b/plugins/awesome-claude-skills/tpscheck-automation/SKILL.md
new file mode 100644
index 0000000..474b713
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/trello-automation/SKILL.md b/plugins/awesome-claude-skills/trello-automation/SKILL.md
new file mode 100644
index 0000000..61251ba
--- /dev/null
+++ b/plugins/awesome-claude-skills/trello-automation/SKILL.md
@@ -0,0 +1,185 @@
+---
+name: trello-automation
+description: Automate Trello boards, cards, and workflows via Rube MCP (Composio). Create cards, manage lists, assign members, and search across boards programmatically.
+requires:
+ mcp: [rube]
+---
+
+# Trello Automation via Rube MCP
+
+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)
+- Active Trello connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `trello`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `trello`
+3. If connection is not ACTIVE, follow the returned auth link to complete Trello auth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create a Card on a Board
+
+**When to use**: User wants to add a new card/task to a Trello board
+
+**Tool sequence**:
+1. `TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER` - List boards to find target board ID [Prerequisite]
+2. `TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD` - Get lists on board to find target list ID [Prerequisite]
+3. `TRELLO_ADD_CARDS` - Create the card on the resolved list [Required]
+4. `TRELLO_ADD_CARDS_CHECKLISTS_BY_ID_CARD` - Add a checklist to the card [Optional]
+5. `TRELLO_ADD_CARDS_CHECKLIST_CHECK_ITEM_BY_ID_CARD_BY_ID_CHECKLIST` - Add items to the checklist [Optional]
+
+**Key parameters**:
+- `idList`: 24-char hex ID (NOT list name)
+- `name`: Card title
+- `desc`: Card description (supports Markdown)
+- `pos`: Position ('top'/'bottom')
+- `due`: Due date (ISO 8601 format)
+
+**Pitfalls**:
+- Store returned id (idCard) immediately; downstream checklist operations fail without it
+- Checklist payload may be nested (data.data); extract idChecklist from inner object
+- One API call per checklist item; large checklists can trigger rate limits
+
+### 2. Manage Boards and Lists
+
+**When to use**: User wants to view, browse, or restructure board layout
+
+**Tool sequence**:
+1. `TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER` - List all boards for the user [Required]
+2. `TRELLO_GET_BOARDS_BY_ID_BOARD` - Get detailed board info [Required]
+3. `TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD` - Get lists (columns) on the board [Optional]
+4. `TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD` - Get board members [Optional]
+5. `TRELLO_GET_BOARDS_LABELS_BY_ID_BOARD` - Get labels on the board [Optional]
+
+**Key parameters**:
+- `idMember`: Use 'me' for authenticated user
+- `filter`: 'open', 'starred', or 'all'
+- `idBoard`: 24-char hex or 8-char shortLink (NOT board name)
+
+**Pitfalls**:
+- Some runs return boards under response.data.details[]—don't assume flat top-level array
+- Lists may be nested under results[0].response.data.details—parse defensively
+- ISO 8601 timestamps with trailing 'Z' must be parsed as timezone-aware
+
+### 3. Move Cards Between Lists
+
+**When to use**: User wants to change a card's status by moving it to another list
+
+**Tool sequence**:
+1. `TRELLO_GET_SEARCH` - Find the card by name or keyword [Prerequisite]
+2. `TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD` - Get destination list ID [Prerequisite]
+3. `TRELLO_UPDATE_CARDS_BY_ID_CARD` - Update card's idList to move it [Required]
+
+**Key parameters**:
+- `idCard`: Card ID from search
+- `idList`: Destination list ID
+- `pos`: Optional ordering within new list
+
+**Pitfalls**:
+- Search returns partial matches; verify card name before updating
+- Moving doesn't update position within new list; set pos if ordering matters
+
+### 4. Assign Members to Cards
+
+**When to use**: User wants to assign team members to cards
+
+**Tool sequence**:
+1. `TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD` - Get member IDs from the board [Prerequisite]
+2. `TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD` - Add a member to the card [Required]
+
+**Key parameters**:
+- `idCard`: Target card ID
+- `value`: Member ID to assign
+
+**Pitfalls**:
+- UPDATE_CARDS_ID_MEMBERS replaces entire member list; use ADD_CARDS_ID_MEMBERS to append
+- Member must have board permissions
+
+### 5. Search and Filter Cards
+
+**When to use**: User wants to find specific cards across boards
+
+**Tool sequence**:
+1. `TRELLO_GET_SEARCH` - Search by query string [Required]
+
+**Key parameters**:
+- `query`: Search string (supports board:, list:, label:, is:open/archived operators)
+- `modelTypes`: Set to 'cards'
+- `partial`: Set to 'true' for prefix matching
+
+**Pitfalls**:
+- Search indexing has delay; newly created cards may not appear for several minutes
+- For exact name matching, use TRELLO_GET_BOARDS_CARDS_BY_ID_BOARD and filter locally
+- Query uses word tokenization; common words may be ignored as stop words
+
+### 6. Add Comments and Attachments
+
+**When to use**: User wants to add context to an existing card
+
+**Tool sequence**:
+1. `TRELLO_ADD_CARDS_ACTIONS_COMMENTS_BY_ID_CARD` - Post a comment on the card [Required]
+2. `TRELLO_ADD_CARDS_ATTACHMENTS_BY_ID_CARD` - Attach a file or URL [Optional]
+
+**Key parameters**:
+- `text`: Comment text (1-16384 chars, supports Markdown and @mentions)
+- `url` OR `file`: Attachment source (not both)
+- `name`: Attachment display name
+- `mimeType`: File MIME type
+
+**Pitfalls**:
+- Comments don't support file attachments; use the attachment tool separately
+- Attachment deletion is irreversible
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to IDs before operations:
+- **Board name → Board ID**: `TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER` with idMember='me'
+- **List name → List ID**: `TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD` with resolved board ID
+- **Card name → Card ID**: `TRELLO_GET_SEARCH` with query string
+- **Member name → Member ID**: `TRELLO_GET_BOARDS_MEMBERS_BY_ID_BOARD`
+
+### Pagination
+Most list endpoints return all items. For boards with 1000+ cards, use `limit` and `before` parameters on card listing endpoints.
+
+### Rate Limits
+300 requests per 10 seconds per token. Use `TRELLO_GET_BATCH` for bulk read operations to stay within limits.
+
+## Known Pitfalls
+
+- **ID Requirements**: Nearly every tool requires IDs, not display names. Always resolve names to IDs first.
+- **Board ID Format**: Board IDs must be 24-char hex or 8-char shortLink. URL slugs like 'my-board' are NOT valid.
+- **Search Delays**: Search indexing has delays; newly created/updated cards may not appear immediately.
+- **Nested Responses**: Response data is often nested (data.data or data.details[]); parse defensively.
+- **Rate Limiting**: 300 req/10s per token. Batch reads with TRELLO_GET_BATCH.
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List user's boards | TRELLO_GET_MEMBERS_BOARDS_BY_ID_MEMBER | idMember='me', filter='open' |
+| Get board details | TRELLO_GET_BOARDS_BY_ID_BOARD | idBoard (24-char hex) |
+| List board lists | TRELLO_GET_BOARDS_LISTS_BY_ID_BOARD | idBoard |
+| Create card | TRELLO_ADD_CARDS | idList, name, desc, pos, due |
+| Update card | TRELLO_UPDATE_CARDS_BY_ID_CARD | idCard, idList (to move) |
+| Search cards | TRELLO_GET_SEARCH | query, modelTypes='cards' |
+| Add checklist | TRELLO_ADD_CARDS_CHECKLISTS_BY_ID_CARD | idCard, name |
+| Add comment | TRELLO_ADD_CARDS_ACTIONS_COMMENTS_BY_ID_CARD | idCard, text |
+| 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) |
+---
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/triggercmd-automation/SKILL.md b/plugins/awesome-claude-skills/triggercmd-automation/SKILL.md
new file mode 100644
index 0000000..284c068
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/tripadvisor-content-api-automation/SKILL.md b/plugins/awesome-claude-skills/tripadvisor-content-api-automation/SKILL.md
new file mode 100644
index 0000000..097a141
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/turbot-pipes-automation/SKILL.md b/plugins/awesome-claude-skills/turbot-pipes-automation/SKILL.md
new file mode 100644
index 0000000..f587903
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/turso-automation/SKILL.md b/plugins/awesome-claude-skills/turso-automation/SKILL.md
new file mode 100644
index 0000000..57f5a3d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/twelve-data-automation/SKILL.md b/plugins/awesome-claude-skills/twelve-data-automation/SKILL.md
new file mode 100644
index 0000000..7e5fe2d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/twitch-automation/SKILL.md b/plugins/awesome-claude-skills/twitch-automation/SKILL.md
new file mode 100644
index 0000000..be80494
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/twitter-algorithm-optimizer/SKILL.md b/plugins/awesome-claude-skills/twitter-algorithm-optimizer/SKILL.md
new file mode 100644
index 0000000..b3c69d9
--- /dev/null
+++ b/plugins/awesome-claude-skills/twitter-algorithm-optimizer/SKILL.md
@@ -0,0 +1,327 @@
+---
+name: twitter-algorithm-optimizer
+description: Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.
+license: AGPL-3.0 (referencing Twitter's algorithm source)
+---
+
+# Twitter Algorithm Optimizer
+
+## When to Use This Skill
+
+Use this skill when you need to:
+- **Optimize tweet drafts** for maximum reach and engagement
+- **Understand why** a tweet might not perform well algorithmically
+- **Rewrite tweets** to align with Twitter's ranking mechanisms
+- **Improve content strategy** based on the actual ranking algorithms
+- **Debug underperforming content** and increase visibility
+- **Maximize engagement signals** that Twitter's algorithms track
+
+## What This Skill Does
+
+1. **Analyzes tweets** against Twitter's core recommendation algorithms
+2. **Identifies optimization opportunities** based on engagement signals
+3. **Rewrites and edits tweets** to improve algorithmic ranking
+4. **Explains the "why"** behind recommendations using algorithm insights
+5. **Applies Real-graph, SimClusters, and TwHIN principles** to content strategy
+6. **Provides engagement-boosting tactics** grounded in Twitter's actual systems
+
+## How It Works: Twitter's Algorithm Architecture
+
+Twitter's recommendation system uses multiple interconnected models:
+
+### Core Ranking Models
+
+**Real-graph**: Predicts interaction likelihood between users
+- Determines if your followers will engage with your content
+- Affects how widely Twitter shows your tweet to others
+- Key signal: Will followers like, reply, or retweet this?
+
+**SimClusters**: Community detection with sparse embeddings
+- Identifies communities of users with similar interests
+- Determines if your tweet resonates within specific communities
+- Key strategy: Make content that appeals to tight communities who will engage
+
+**TwHIN**: Knowledge graph embeddings for users and posts
+- Maps relationships between users and content topics
+- Helps Twitter understand if your tweet fits your follower interests
+- Key strategy: Stay in your niche or clearly signal topic shifts
+
+**Tweepcred**: User reputation/authority scoring
+- Higher-credibility users get more distribution
+- Your past engagement history affects current tweet reach
+- Key strategy: Build reputation through consistent engagement
+
+### Engagement Signals Tracked
+
+Twitter's **Unified User Actions** service tracks both explicit and implicit signals:
+
+**Explicit Signals** (high weight):
+- Likes (direct positive signal)
+- Replies (indicates valuable content worth discussing)
+- Retweets (strongest signal - users want to share it)
+- Quote tweets (engaged discussion)
+
+**Implicit Signals** (also weighted):
+- Profile visits (curiosity about the author)
+- Clicks/link clicks (content deemed useful enough to explore)
+- Time spent (users reading/considering your tweet)
+- Saves/bookmarks (plan to return later)
+
+**Negative Signals**:
+- Block/report (Twitter penalizes this heavily)
+- Mute/unfollow (person doesn't want your content)
+- Skip/scroll past quickly (low engagement)
+
+### The Feed Generation Process
+
+Your tweet reaches users through this pipeline:
+
+1. **Candidate Retrieval** - Multiple sources find candidate tweets:
+ - Search Index (relevant keyword matches)
+ - UTEG (timeline engagement graph - following relationships)
+ - Tweet-mixer (trending/viral content)
+
+2. **Ranking** - ML models rank candidates by predicted engagement:
+ - Will THIS user engage with THIS tweet?
+ - How quickly will engagement happen?
+ - Will it spread to non-followers?
+
+3. **Filtering** - Remove blocked content, apply preferences
+
+4. **Delivery** - Show ranked feed to user
+
+## Optimization Strategies Based on Algorithm Insights
+
+### 1. Maximize Real-graph (Follower Engagement)
+
+**Strategy**: Make content your followers WILL engage with
+
+- **Know your audience**: Reference topics they care about
+- **Ask questions**: Direct questions get more replies than statements
+- **Create controversy (safely)**: Debate attracts engagement (but avoid blocks/reports)
+- **Tag related creators**: Increases visibility through networks
+- **Post when followers are active**: Better early engagement means better ranking
+
+**Example Optimization**:
+- ❌ "I think climate policy is important"
+- ✅ "Hot take: Current climate policy ignores nuclear energy. Thoughts?" (triggers replies)
+
+### 2. Leverage SimClusters (Community Resonance)
+
+**Strategy**: Find and serve tight communities deeply interested in your topic
+
+- **Pick ONE clear topic**: Don't confuse the algorithm with mixed messages
+- **Use community language**: Reference shared memes, inside jokes, terminology
+- **Provide value to the niche**: Be genuinely useful to that specific community
+- **Encourage community-to-community sharing**: Quotes that spark discussion
+- **Build in your lane**: Consistency helps algorithm understand your topic
+
+**Example Optimization**:
+- ❌ "I use many programming languages"
+- ✅ "Rust's ownership system is the most underrated feature. Here's why..." (targets specific dev community)
+
+### 3. Improve TwHIN Mapping (Content-User Fit)
+
+**Strategy**: Make your content clearly relevant to your established identity
+
+- **Signal your expertise**: Lead with domain knowledge
+- **Consistency matters**: Stay in your lanes (or clearly announce a new direction)
+- **Use specific terminology**: Helps algorithm categorize you correctly
+- **Reference your past wins**: "Following up on my tweet about X..."
+- **Build topical authority**: Multiple tweets on same topic strengthen the connection
+
+**Example Optimization**:
+- ❌ "I like lots of things" (vague, confuses algorithm)
+- ✅ "My 3rd consecutive framework review as a full-stack engineer" (establishes authority)
+
+### 4. Boost Tweepcred (Authority/Credibility)
+
+**Strategy**: Build reputation through engagement consistency
+
+- **Reply to top creators**: Interaction with high-credibility accounts boosts visibility
+- **Quote interesting tweets**: Adds value and signals engagement
+- **Avoid engagement bait**: Doesn't build real credibility
+- **Be consistent**: Regular quality posting beats sporadic viral attempts
+- **Engage deeply**: Quality replies and discussions matter more than volume
+
+**Example Optimization**:
+- ❌ "RETWEET IF..." (engagement bait, damages credibility over time)
+- ✅ "Thoughtful critique of the approach in [linked tweet]" (builds authority)
+
+### 5. Maximize Engagement Signals
+
+**Explicit Signal Triggers**:
+
+**For Likes**:
+- Novel insights or memorable phrasing
+- Validation of audience beliefs
+- Useful/actionable information
+- Strong opinions with supporting evidence
+
+**For Replies**:
+- Ask a direct question
+- Create a debate
+- Request opinions
+- Share incomplete thoughts (invites completion)
+
+**For Retweets**:
+- Useful information people want to share
+- Representational value (tweet speaks for them)
+- Entertainment that entertains their followers
+- Information advantage (breaking news first)
+
+**For Bookmarks/Saves**:
+- Tutorials or how-tos
+- Data/statistics they'll reference later
+- Inspiration or motivation
+- Jokes/entertainment they'll want to see again
+
+**Example Optimization**:
+- ❌ "Check out this tool" (passive)
+- ✅ "This tool saved me 5 hours this week. Here's how to set it up..." (actionable, retweet-worthy)
+
+### 6. Prevent Negative Signals
+
+**Avoid**:
+- Inflammatory content likely to be reported
+- Targeted harassment (gets algorithmic penalty)
+- Misleading/false claims (damages credibility)
+- Off-brand pivots (confuses the algorithm)
+- Reply-guy syndrome (too many low-value replies)
+
+## How to Optimize Your Tweets
+
+### Step 1: Identify the Core Message
+- What's the single most important thing this tweet communicates?
+- Who should care about this?
+- What action/engagement do you want?
+
+### Step 2: Map to Algorithm Strategy
+- Which Real-graph follower segment will engage? (Followers who care about X)
+- Which SimCluster community? (Niche interested in Y)
+- How does this fit your TwHIN identity? (Your established expertise)
+- Does this boost or hurt Tweepcred?
+
+### Step 3: Optimize for Signals
+- Does it trigger replies? (Ask a question, create debate)
+- Is it retweet-worthy? (Usefulness, entertainment, representational value)
+- Will followers like it? (Novel, validating, actionable)
+- Could it go viral? (Community resonance + network effects)
+
+### Step 4: Check Against Negatives
+- Any blocks/reports risk?
+- Any confusion about your identity?
+- Any engagement bait that damages credibility?
+- Any inflammatory language that hurts Tweepcred?
+
+## Example Optimizations
+
+### Example 1: Developer Tweet
+
+**Original**:
+> "I fixed a bug today"
+
+**Algorithm Analysis**:
+- No clear audience - too generic
+- No engagement signals - statements don't trigger replies
+- No Real-graph trigger - followers won't engage strongly
+- No SimCluster resonance - could apply to any developer
+
+**Optimized**:
+> "Spent 2 hours debugging, turned out I was missing one semicolon. The best part? The linter didn't catch it.
+>
+> What's your most embarrassing bug? Drop it in replies 👇"
+
+**Why It Works**:
+- SimCluster trigger: Specific developer community
+- Real-graph trigger: Direct question invites replies
+- Tweepcred: Relatable vulnerability builds connection
+- Engagement: Likely replies (others share embarrassing bugs)
+
+### Example 2: Product Launch Tweet
+
+**Original**:
+> "We launched a new feature today. Check it out."
+
+**Algorithm Analysis**:
+- Passive voice - doesn't indicate impact
+- No specific benefit - followers don't know why to care
+- No community resonance - generic
+- Engagement bait risk if it feels like self-promotion
+
+**Optimized**:
+> "Spent 6 months on the one feature our users asked for most: export to PDF.
+>
+> 10x improvement in report generation time. Already live.
+>
+> What export format do you want next?"
+
+**Why It Works**:
+- Real-graph: Followers in your product space will engage
+- Specificity: "PDF export" + "10x improvement" triggers bookmarks (useful info)
+- Question: Ends with engagement trigger
+- Authority: You spent 6 months (shows credibility)
+- SimCluster: Product management/SaaS community resonates
+
+### Example 3: Opinion Tweet
+
+**Original**:
+> "I think remote work is better than office work"
+
+**Algorithm Analysis**:
+- Vague opinion - doesn't invite engagement
+- Could be debated either way - no clear position
+- No Real-graph hooks - followers unclear if they should care
+- Generic topic - dilutes your personal brand
+
+**Optimized**:
+> "Hot take: remote work works great for async tasks but kills creative collaboration.
+>
+> We're now hybrid: deep focus days remote, collab days in office.
+>
+> What's your team's balance? Genuinely curious what works."
+
+**Why It Works**:
+- Clear position: Not absolutes, nuanced stance
+- Debate trigger: "Hot take" signals discussion opportunity
+- Question: Direct engagement request
+- Real-graph: Followers in your industry will have opinions
+- SimCluster: CTOs, team leads, engineering managers will relate
+- Tweepcred: Nuanced thinking builds authority
+
+## Best Practices for Algorithm Optimization
+
+1. **Quality Over Virality**: Consistent engagement from your community beats occasional viral moments
+2. **Community First**: Deep resonance with 100 engaged followers beats shallow reach to 10,000
+3. **Authenticity Matters**: The algorithm rewards genuine engagement, not manipulation
+4. **Timing Helps**: Engage early when tweet is fresh (first hour critical)
+5. **Build Threads**: Threaded tweets often get more engagement than single tweets
+6. **Follow Up**: Reply to replies quickly - Twitter's algorithm favors active conversation
+7. **Avoid Spam**: Engagement pods and bots hurt long-term credibility
+8. **Track Your Performance**: Notice what YOUR audience engages with and iterate
+
+## Common Pitfalls to Avoid
+
+- **Generic statements**: Doesn't trigger algorithm (too vague)
+- **Pure engagement bait**: "Like if you agree" - hurts credibility long-term
+- **Unclear audience**: Who should care? If unclear, algorithm won't push it far
+- **Off-brand pivots**: Confuses algorithm about your identity
+- **Over-frequency**: Spamming hurts engagement rate metrics
+- **Toxicity**: Blocks/reports heavily penalize future reach
+- **No calls to action**: Passive tweets underperform
+
+## When to Ask for Algorithm Optimization
+
+Use this skill when:
+- You've drafted a tweet and want to maximize reach
+- A tweet underperformed and you want to understand why
+- You're launching important content and want algorithm advantage
+- You're building audience in a specific niche
+- You want to become known for something specific
+- You're debugging inconsistent engagement rates
+
+Use Claude without this skill for:
+- General writing and grammar fixes
+- Tone adjustments not related to algorithm
+- Off-Twitter content (LinkedIn, Medium, blogs, etc.)
+- Personal conversations and casual tweets
\ No newline at end of file
diff --git a/plugins/awesome-claude-skills/twitter-automation/SKILL.md b/plugins/awesome-claude-skills/twitter-automation/SKILL.md
new file mode 100644
index 0000000..f2aef18
--- /dev/null
+++ b/plugins/awesome-claude-skills/twitter-automation/SKILL.md
@@ -0,0 +1,236 @@
+---
+name: twitter-automation
+description: "Automate Twitter/X tasks via Rube MCP (Composio): posts, search, users, bookmarks, lists, media. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Twitter/X Automation via Rube MCP
+
+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)
+- Active Twitter connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `twitter`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `twitter`
+3. If connection is not ACTIVE, follow the returned auth link to complete Twitter OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Posts
+
+**When to use**: User wants to create, delete, or look up tweets/posts
+
+**Tool sequence**:
+1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user info [Prerequisite]
+2. `TWITTER_UPLOAD_MEDIA` / `TWITTER_UPLOAD_LARGE_MEDIA` - Upload media [Optional]
+3. `TWITTER_CREATION_OF_A_POST` - Create a new post [Required]
+4. `TWITTER_POST_LOOKUP_BY_POST_ID` - Look up a specific post [Optional]
+5. `TWITTER_POST_DELETE_BY_POST_ID` - Delete a post [Optional]
+
+**Key parameters**:
+- `text`: Post text content (max 280 weighted characters)
+- `media__media_ids`: Array of media ID strings for attachments
+- `reply__in_reply_to_tweet_id`: Tweet ID to reply to
+- `quote_tweet_id`: Tweet ID to quote
+- `id`: Post ID for lookup/delete
+
+**Pitfalls**:
+- Post text is limited to 280 weighted characters; some characters count as more than one
+- Posting is NOT idempotent; retrying on timeout will create duplicate posts
+- Media IDs must be numeric strings, not integers
+- UPLOAD_LARGE_MEDIA is for videos/GIFs; UPLOAD_MEDIA for images
+- Always call USER_LOOKUP_ME first to get the authenticated user's ID
+
+### 2. Search Posts
+
+**When to use**: User wants to find tweets matching specific criteria
+
+**Tool sequence**:
+1. `TWITTER_RECENT_SEARCH` - Search recent tweets (last 7 days) [Required]
+2. `TWITTER_FULL_ARCHIVE_SEARCH` - Search full archive (Academic access) [Optional]
+3. `TWITTER_RECENT_SEARCH_COUNTS` - Get tweet count matching query [Optional]
+
+**Key parameters**:
+- `query`: Search query using Twitter search operators
+- `max_results`: Results per page (10-100)
+- `next_token`: Pagination token
+- `start_time`/`end_time`: ISO 8601 time range
+- `tweet__fields`: Comma-separated fields to include
+- `expansions`: Related objects to expand
+
+**Pitfalls**:
+- RECENT_SEARCH covers only the last 7 days; use FULL_ARCHIVE_SEARCH for older tweets
+- FULL_ARCHIVE_SEARCH requires Academic Research or Enterprise access
+- Query operators: `from:username`, `to:username`, `is:retweet`, `has:media`, `-is:retweet`
+- Empty results return `meta.result_count: 0` with no `data` field
+- Rate limits vary by endpoint and access level; check response headers
+
+### 3. Look Up Users
+
+**When to use**: User wants to find or inspect Twitter user profiles
+
+**Tool sequence**:
+1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user [Optional]
+2. `TWITTER_USER_LOOKUP_BY_USERNAME` - Look up by username [Optional]
+3. `TWITTER_USER_LOOKUP_BY_ID` - Look up by user ID [Optional]
+4. `TWITTER_USER_LOOKUP_BY_IDS` - Batch look up multiple users [Optional]
+
+**Key parameters**:
+- `username`: Twitter handle without @ prefix
+- `id`: Numeric user ID string
+- `ids`: Comma-separated user IDs for batch lookup
+- `user__fields`: Fields to return (description, public_metrics, etc.)
+
+**Pitfalls**:
+- Usernames are case-insensitive but must not include the @ prefix
+- User IDs are numeric strings, not integers
+- Suspended or deleted accounts return errors, not empty results
+- LOOKUP_BY_IDS accepts max 100 IDs per request
+
+### 4. Manage Bookmarks
+
+**When to use**: User wants to save, view, or remove bookmarked tweets
+
+**Tool sequence**:
+1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user ID [Prerequisite]
+2. `TWITTER_BOOKMARKS_BY_USER` - List bookmarked posts [Required]
+3. `TWITTER_ADD_POST_TO_BOOKMARKS` - Bookmark a post [Optional]
+4. `TWITTER_REMOVE_A_BOOKMARKED_POST` - Remove bookmark [Optional]
+
+**Key parameters**:
+- `id`: User ID (from USER_LOOKUP_ME) for listing bookmarks
+- `tweet_id`: Tweet ID to bookmark or unbookmark
+- `max_results`: Results per page
+- `pagination_token`: Token for next page
+
+**Pitfalls**:
+- Bookmarks require the authenticated user's ID, not username
+- Bookmarks are private; only the authenticated user can see their own
+- Pagination uses `pagination_token`, not `next_token`
+
+### 5. Manage Lists
+
+**When to use**: User wants to view or manage Twitter lists
+
+**Tool sequence**:
+1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user ID [Prerequisite]
+2. `TWITTER_GET_A_USER_S_OWNED_LISTS` - List owned lists [Optional]
+3. `TWITTER_GET_A_USER_S_LIST_MEMBERSHIPS` - List memberships [Optional]
+4. `TWITTER_GET_A_USER_S_PINNED_LISTS` - Get pinned lists [Optional]
+5. `TWITTER_GET_USER_S_FOLLOWED_LISTS` - Get followed lists [Optional]
+6. `TWITTER_LIST_LOOKUP_BY_LIST_ID` - Get list details [Optional]
+
+**Key parameters**:
+- `id`: User ID for listing owned/member/followed lists
+- `list_id`: List ID for specific list lookup
+- `max_results`: Results per page (1-100)
+
+**Pitfalls**:
+- List IDs and User IDs are numeric strings
+- Lists endpoints require the user's numeric ID, not username
+
+### 6. Interact with Posts
+
+**When to use**: User wants to like, unlike, or view liked posts
+
+**Tool sequence**:
+1. `TWITTER_USER_LOOKUP_ME` - Get authenticated user ID [Prerequisite]
+2. `TWITTER_RETURNS_POST_OBJECTS_LIKED_BY_THE_PROVIDED_USER_ID` - Get liked posts [Optional]
+3. `TWITTER_UNLIKE_POST` - Unlike a post [Optional]
+
+**Key parameters**:
+- `id`: User ID for listing liked posts
+- `tweet_id`: Tweet ID to unlike
+
+**Pitfalls**:
+- Like/unlike endpoints require user ID from USER_LOOKUP_ME
+- Liked posts pagination may be slow for users with many likes
+
+## Common Patterns
+
+### Search Query Syntax
+
+**Operators**:
+- `from:username` - Posts by user
+- `to:username` - Replies to user
+- `@username` - Mentions user
+- `#hashtag` - Contains hashtag
+- `"exact phrase"` - Exact match
+- `has:media` - Contains media
+- `has:links` - Contains links
+- `is:retweet` / `-is:retweet` - Include/exclude retweets
+- `is:reply` / `-is:reply` - Include/exclude replies
+- `lang:en` - Language filter
+
+**Combinators**:
+- Space for AND
+- `OR` for either condition
+- `-` prefix for NOT
+- Parentheses for grouping
+
+### Media Upload Flow
+
+```
+1. Upload media with TWITTER_UPLOAD_MEDIA (images) or TWITTER_UPLOAD_LARGE_MEDIA (video/GIF)
+2. Get media_id from response
+3. Pass media_id as string in media__media_ids array to TWITTER_CREATION_OF_A_POST
+```
+
+## Known Pitfalls
+
+**Character Limits**:
+- Standard posts: 280 weighted characters
+- Some Unicode characters count as more than 1
+- URLs are shortened and count as fixed length (23 characters)
+
+**Rate Limits**:
+- Vary significantly by access tier (Free, Basic, Pro, Enterprise)
+- Free tier: very limited (e.g., 1,500 posts/month)
+- Check `x-rate-limit-remaining` header in responses
+
+**Idempotency**:
+- Post creation is NOT idempotent; duplicate posts will be created on retry
+- Implement deduplication logic for automated posting
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create post | TWITTER_CREATION_OF_A_POST | text |
+| Delete post | TWITTER_POST_DELETE_BY_POST_ID | id |
+| Look up post | TWITTER_POST_LOOKUP_BY_POST_ID | id |
+| Recent search | TWITTER_RECENT_SEARCH | query |
+| Archive search | TWITTER_FULL_ARCHIVE_SEARCH | query |
+| Search counts | TWITTER_RECENT_SEARCH_COUNTS | query |
+| My profile | TWITTER_USER_LOOKUP_ME | (none) |
+| User by name | TWITTER_USER_LOOKUP_BY_USERNAME | username |
+| User by ID | TWITTER_USER_LOOKUP_BY_ID | id |
+| Users by IDs | TWITTER_USER_LOOKUP_BY_IDS | ids |
+| Upload media | TWITTER_UPLOAD_MEDIA | media |
+| Upload video | TWITTER_UPLOAD_LARGE_MEDIA | media |
+| List bookmarks | TWITTER_BOOKMARKS_BY_USER | id |
+| Add bookmark | TWITTER_ADD_POST_TO_BOOKMARKS | tweet_id |
+| Remove bookmark | TWITTER_REMOVE_A_BOOKMARKED_POST | tweet_id |
+| Unlike post | TWITTER_UNLIKE_POST | tweet_id |
+| Liked posts | TWITTER_RETURNS_POST_OBJECTS_LIKED_BY_THE_PROVIDED_USER_ID | id |
+| Owned lists | TWITTER_GET_A_USER_S_OWNED_LISTS | id |
+| List memberships | TWITTER_GET_A_USER_S_LIST_MEMBERSHIPS | id |
+| 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/plugins/awesome-claude-skills/twocaptcha-automation/SKILL.md b/plugins/awesome-claude-skills/twocaptcha-automation/SKILL.md
new file mode 100644
index 0000000..5970ab6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/typefully-automation/SKILL.md b/plugins/awesome-claude-skills/typefully-automation/SKILL.md
new file mode 100644
index 0000000..3a8c22e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/typless-automation/SKILL.md b/plugins/awesome-claude-skills/typless-automation/SKILL.md
new file mode 100644
index 0000000..cfb339a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/u301-automation/SKILL.md b/plugins/awesome-claude-skills/u301-automation/SKILL.md
new file mode 100644
index 0000000..97b5130
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/unione-automation/SKILL.md b/plugins/awesome-claude-skills/unione-automation/SKILL.md
new file mode 100644
index 0000000..0917476
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/updown-io-automation/SKILL.md b/plugins/awesome-claude-skills/updown-io-automation/SKILL.md
new file mode 100644
index 0000000..7f50b5d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/uploadcare-automation/SKILL.md b/plugins/awesome-claude-skills/uploadcare-automation/SKILL.md
new file mode 100644
index 0000000..7d0ec88
--- /dev/null
+++ b/plugins/awesome-claude-skills/uploadcare-automation/SKILL.md
@@ -0,0 +1,153 @@
+---
+name: Uploadcare Automation
+description: "Automate Uploadcare file management including listing, storing, inspecting, downloading, and organizing file groups through natural language commands"
+requires:
+ mcp:
+ - rube
+---
+
+# Uploadcare Automation
+
+Automate Uploadcare file handling workflows -- list project files, permanently store uploads, retrieve file metadata, get download URLs, and manage file groups -- all through natural language.
+
+**Toolkit docs:** [composio.dev/toolkits/uploadcare](https://composio.dev/toolkits/uploadcare)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Connect your Uploadcare account when prompted (API key auth via Composio)
+3. Start issuing natural language commands for Uploadcare automation
+
+---
+
+## Core Workflows
+
+### 1. List Project Files
+
+Browse uploaded files in your Uploadcare project with filtering, sorting, and pagination.
+
+**Tool:** `UPLOADCARE_LIST_FILES`
+
+Key parameters:
+- `stored` -- filter by storage status: `"true"` for stored, `"false"` for unstored
+- `removed` -- filter by removal status: `"true"` for removed, `"false"` for active
+- `ordering` -- sort by `datetime_uploaded` (ascending) or `-datetime_uploaded` (descending)
+- `limit` -- files per page, 1-1000 (default 100)
+- `offset` -- zero-based pagination offset
+- `from_date` -- ISO 8601 timestamp to filter files uploaded after this date
+- `to_date` -- ISO 8601 timestamp to filter files uploaded before this date
+- `include` -- set to `"total"` to include total file count in response
+
+Example prompt:
+> "List the 50 most recently uploaded stored files in my Uploadcare project"
+
+---
+
+### 2. Store a File Permanently
+
+Mark an uploaded file as permanently stored. By default, Uploadcare files are temporary and will be deleted after 24 hours unless stored.
+
+**Tool:** `UPLOADCARE_STORE_FILE`
+
+Key parameters:
+- `uuid` -- UUID of the file to store (required); must be in `8-4-4-4-12` hex format (e.g., `3e55317b-23d1-4f35-9b4c-b9accb7b53f4`)
+
+> Always store files after upload to prevent automatic deletion.
+
+Example prompt:
+> "Permanently store the file with UUID 3e55317b-23d1-4f35-9b4c-b9accb7b53f4"
+
+---
+
+### 3. Get File Metadata
+
+Retrieve detailed information about a specific file including size, MIME type, CDN URL, image dimensions, and more.
+
+**Tool:** `UPLOADCARE_GET_FILE_INFO`
+
+Key parameters:
+- `uuid` -- the UUID of the file to inspect (required); format: `8-4-4-4-12` hex
+
+Returns: filename, size, MIME type, CDN URL, upload date, storage status, image info (dimensions, color mode), and more.
+
+Example prompt:
+> "Get the metadata and dimensions for file 3e0923f2-e05a-4b37-9f0d-343b981c9d70"
+
+---
+
+### 4. Get a Temporary Download URL
+
+Retrieve a temporary direct download link for a specific file.
+
+**Tool:** `UPLOADCARE_GET_FILE_DOWNLOAD_URL`
+
+Key parameters:
+- `file_id` -- the unique file identifier (required)
+
+Returns a time-limited URL that can be used for direct file download.
+
+Example prompt:
+> "Get a download link for file 3e0923f2-e05a-4b37-9f0d-343b981c9d70"
+
+---
+
+### 5. Browse File Groups
+
+List file groups in your project. Groups are collections of files uploaded together.
+
+**Tool:** `UPLOADCARE_LIST_GROUPS`
+
+Key parameters:
+- `limit` -- groups per page, 1-1000 (default 20)
+- `offset` -- zero-based pagination offset (default 0)
+- `ordering` -- sort by `datetime_created` (ascending) or `-datetime_created` (descending)
+
+Example prompt:
+> "List my 10 most recent file groups"
+
+---
+
+### 6. File Lifecycle Workflow
+
+Combine tools for end-to-end file management:
+
+1. **Upload**: Files are uploaded via Uploadcare's upload API or widget (outside this toolkit)
+2. **Store**: `UPLOADCARE_STORE_FILE` -- mark files as permanent to prevent auto-deletion
+3. **Inspect**: `UPLOADCARE_GET_FILE_INFO` -- verify metadata, check dimensions and MIME type
+4. **Share**: `UPLOADCARE_GET_FILE_DOWNLOAD_URL` -- generate a temporary download link
+5. **Browse**: `UPLOADCARE_LIST_FILES` -- audit all files with status and date filters
+6. **Groups**: `UPLOADCARE_LIST_GROUPS` -- review batch uploads
+
+Example prompt:
+> "Store file abc-123, then get its metadata and a download link"
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| Auto-deletion of unstored files | Uploaded files are temporary by default and deleted after 24 hours -- always call `UPLOADCARE_STORE_FILE` to persist them |
+| UUID format strict | File UUIDs must be in exact `8-4-4-4-12` hex format (e.g., `3e55317b-23d1-4f35-9b4c-b9accb7b53f4`); invalid formats will be rejected |
+| Filter values are strings | The `stored` and `removed` parameters accept string values `"true"` or `"false"`, not booleans |
+| Temporary download URLs | URLs from `UPLOADCARE_GET_FILE_DOWNLOAD_URL` are time-limited and will expire |
+| Pagination is offset-based | Use `offset` + `limit` for pagination; there are no cursor-based pagination tokens |
+| No upload tool | File uploads happen through Uploadcare's upload API or widget, not through this toolkit -- these tools manage already-uploaded files |
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Key Params |
+|--------|-----------|------------|
+| List files | `UPLOADCARE_LIST_FILES` | `stored`, `ordering`, `limit`, `offset` |
+| Store file | `UPLOADCARE_STORE_FILE` | `uuid` |
+| Get file info | `UPLOADCARE_GET_FILE_INFO` | `uuid` |
+| Get download URL | `UPLOADCARE_GET_FILE_DOWNLOAD_URL` | `file_id` |
+| List groups | `UPLOADCARE_LIST_GROUPS` | `limit`, `offset`, `ordering` |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/uptimerobot-automation/SKILL.md b/plugins/awesome-claude-skills/uptimerobot-automation/SKILL.md
new file mode 100644
index 0000000..2c63be3
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/userlist-automation/SKILL.md b/plugins/awesome-claude-skills/userlist-automation/SKILL.md
new file mode 100644
index 0000000..98774d0
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/v0-automation/SKILL.md b/plugins/awesome-claude-skills/v0-automation/SKILL.md
new file mode 100644
index 0000000..4bf6e9b
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/venly-automation/SKILL.md b/plugins/awesome-claude-skills/venly-automation/SKILL.md
new file mode 100644
index 0000000..e1056c6
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/veo-automation/SKILL.md b/plugins/awesome-claude-skills/veo-automation/SKILL.md
new file mode 100644
index 0000000..80d3872
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/vercel-automation/SKILL.md b/plugins/awesome-claude-skills/vercel-automation/SKILL.md
new file mode 100644
index 0000000..08badbb
--- /dev/null
+++ b/plugins/awesome-claude-skills/vercel-automation/SKILL.md
@@ -0,0 +1,231 @@
+---
+name: vercel-automation
+description: "Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Vercel Automation via Rube MCP
+
+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)
+- Active Vercel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`
+3. If connection is not ACTIVE, follow the returned auth link to complete Vercel OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Monitor and Inspect Deployments
+
+**When to use**: User wants to list, inspect, or debug deployments
+
+**Tool sequence**:
+1. `VERCEL_LIST_ALL_DEPLOYMENTS` or `VERCEL_GET_DEPLOYMENTS` - List deployments with filters [Required]
+2. `VERCEL_GET_DEPLOYMENT` or `VERCEL_GET_DEPLOYMENT_DETAILS` - Get specific deployment info [Optional]
+3. `VERCEL_GET_DEPLOYMENT_LOGS` or `VERCEL_GET_RUNTIME_LOGS` - View build/runtime logs [Optional]
+4. `VERCEL_GET_DEPLOYMENT_EVENTS` - Get deployment event timeline [Optional]
+5. `VERCEL_LIST_DEPLOYMENT_CHECKS` - View deployment check results [Optional]
+
+**Key parameters**:
+- `projectId`: Filter deployments by project
+- `state`: Filter by deployment state (e.g., 'READY', 'ERROR', 'BUILDING')
+- `limit`: Number of deployments to return
+- `target`: Filter by environment ('production', 'preview')
+- `deploymentId` or `idOrUrl`: Specific deployment identifier
+
+**Pitfalls**:
+- Deployment IDs and URLs are both accepted as identifiers in most endpoints
+- Build logs and runtime logs are separate; use the appropriate tool
+- `VERCEL_GET_DEPLOYMENT_LOGS` returns build logs; `VERCEL_GET_RUNTIME_LOGS` returns serverless function logs
+- Deployment events include status transitions and are useful for debugging timing issues
+
+### 2. Create and Manage Deployments
+
+**When to use**: User wants to trigger a new deployment
+
+**Tool sequence**:
+1. `VERCEL_LIST_PROJECTS` - Find the target project [Prerequisite]
+2. `VERCEL_CREATE_NEW_DEPLOYMENT` - Trigger a new deployment [Required]
+3. `VERCEL_GET_DEPLOYMENT` - Monitor deployment progress [Optional]
+
+**Key parameters**:
+- `name`: Project name for the deployment
+- `target`: Deployment target ('production' or 'preview')
+- `gitSource`: Git repository source with ref/branch info
+- `files`: Array of file objects for file-based deployments
+
+**Pitfalls**:
+- Either `gitSource` or `files` must be provided, not both
+- Git-based deployments require proper repository integration
+- Production deployments update the production domain alias automatically
+- Deployment creation is asynchronous; poll with GET_DEPLOYMENT for status
+
+### 3. Manage Environment Variables
+
+**When to use**: User wants to add, list, or remove environment variables for a project
+
+**Tool sequence**:
+1. `VERCEL_LIST_PROJECTS` - Find the project ID [Prerequisite]
+2. `VERCEL_LIST_ENV_VARIABLES` - List existing env vars [Required]
+3. `VERCEL_ADD_ENVIRONMENT_VARIABLE` - Add a new env var [Optional]
+4. `VERCEL_DELETE_ENVIRONMENT_VARIABLE` - Remove an env var [Optional]
+
+**Key parameters**:
+- `projectId`: Target project identifier
+- `key`: Environment variable name
+- `value`: Environment variable value
+- `target`: Array of environments ('production', 'preview', 'development')
+- `type`: Variable type ('plain', 'secret', 'encrypted', 'sensitive')
+
+**Pitfalls**:
+- Environment variable names must be unique per target environment
+- `type: 'secret'` variables cannot be read back after creation; only the ID is returned
+- Deleting an env var requires both `projectId` and the env var `id` (not the key name)
+- Changes require a new deployment to take effect
+
+### 4. Manage Domains and DNS
+
+**When to use**: User wants to configure custom domains or manage DNS records
+
+**Tool sequence**:
+1. `VERCEL_GET_DOMAIN` - Check domain status and configuration [Required]
+2. `VERCEL_GET_DOMAIN_CONFIG` - Get DNS/SSL configuration details [Optional]
+3. `VERCEL_LIST_PROJECT_DOMAINS` - List domains attached to a project [Optional]
+4. `VERCEL_GET_DNS_RECORDS` - List DNS records for a domain [Optional]
+5. `VERCEL_CREATE_DNS_RECORD` - Add a new DNS record [Optional]
+6. `VERCEL_UPDATE_DNS_RECORD` - Modify an existing DNS record [Optional]
+
+**Key parameters**:
+- `domain`: Domain name (e.g., 'example.com')
+- `name`: DNS record name/subdomain
+- `type`: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV')
+- `value`: DNS record value
+- `ttl`: Time-to-live in seconds
+
+**Pitfalls**:
+- Domain must be added to the Vercel account before DNS management
+- SSL certificates are auto-provisioned but may take time for new domains
+- CNAME records at the apex domain are not supported; use A records instead
+- MX records require priority values
+
+### 5. Manage Projects
+
+**When to use**: User wants to list, inspect, or update project settings
+
+**Tool sequence**:
+1. `VERCEL_LIST_PROJECTS` - List all projects [Required]
+2. `VERCEL_GET_PROJECT` - Get detailed project information [Optional]
+3. `VERCEL_UPDATE_PROJECT` - Modify project settings [Optional]
+
+**Key parameters**:
+- `idOrName`: Project ID or name for lookup
+- `name`: Project name for updates
+- `framework`: Framework preset (e.g., 'nextjs', 'vite', 'remix')
+- `buildCommand`: Custom build command override
+- `rootDirectory`: Root directory if not repo root
+
+**Pitfalls**:
+- Project names are globally unique within a team/account
+- Changing framework settings affects subsequent deployments
+- `rootDirectory` is relative to the repository root
+
+### 6. Team Management
+
+**When to use**: User wants to view team info or list team members
+
+**Tool sequence**:
+1. `VERCEL_LIST_TEAMS` - List all teams the user belongs to [Required]
+2. `VERCEL_GET_TEAM` - Get detailed team information [Optional]
+3. `VERCEL_GET_TEAM_MEMBERS` - List members of a specific team [Optional]
+
+**Key parameters**:
+- `teamId`: Team identifier
+- `limit`: Number of results per page
+- `role`: Filter members by role
+
+**Pitfalls**:
+- Team operations require appropriate team-level permissions
+- Personal accounts have no teams; team endpoints return empty results
+- Member roles include 'OWNER', 'MEMBER', 'DEVELOPER', 'VIEWER'
+
+## Common Patterns
+
+### ID Resolution
+
+**Project name -> Project ID**:
+```
+1. Call VERCEL_LIST_PROJECTS
+2. Find project by name in response
+3. Extract id field for subsequent operations
+```
+
+**Domain -> DNS Records**:
+```
+1. Call VERCEL_GET_DNS_RECORDS with domain name
+2. Extract record IDs for update/delete operations
+```
+
+### Pagination
+
+- Use `limit` parameter to control page size
+- Check response for pagination tokens or `next` fields
+- Continue fetching until no more pages are indicated
+
+## Known Pitfalls
+
+**Deployment States**:
+- States include: INITIALIZING, ANALYZING, BUILDING, DEPLOYING, READY, ERROR, CANCELED, QUEUED
+- Only READY deployments are live and serving traffic
+- ERROR deployments should be inspected via logs for failure details
+
+**Environment Variables**:
+- Secret type vars are write-only; values cannot be retrieved after creation
+- Env vars are scoped to environments (production, preview, development)
+- A redeployment is needed for env var changes to take effect
+
+**Rate Limits**:
+- Vercel API has rate limits per endpoint
+- Implement backoff on 429 responses
+- Batch operations where possible to reduce API calls
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List projects | VERCEL_LIST_PROJECTS | limit |
+| Get project details | VERCEL_GET_PROJECT | idOrName |
+| Update project | VERCEL_UPDATE_PROJECT | idOrName, name, framework |
+| List deployments | VERCEL_LIST_ALL_DEPLOYMENTS | projectId, state, limit |
+| Get deployment | VERCEL_GET_DEPLOYMENT | idOrUrl |
+| Create deployment | VERCEL_CREATE_NEW_DEPLOYMENT | name, target, gitSource |
+| Deployment logs | VERCEL_GET_DEPLOYMENT_LOGS | deploymentId |
+| Runtime logs | VERCEL_GET_RUNTIME_LOGS | deploymentId |
+| List env vars | VERCEL_LIST_ENV_VARIABLES | projectId |
+| Add env var | VERCEL_ADD_ENVIRONMENT_VARIABLE | projectId, key, value, target |
+| Delete env var | VERCEL_DELETE_ENVIRONMENT_VARIABLE | projectId, id |
+| Get domain | VERCEL_GET_DOMAIN | domain |
+| Get domain config | VERCEL_GET_DOMAIN_CONFIG | domain |
+| List DNS records | VERCEL_GET_DNS_RECORDS | domain |
+| Create DNS record | VERCEL_CREATE_DNS_RECORD | domain, name, type, value |
+| Update DNS record | VERCEL_UPDATE_DNS_RECORD | domain, recordId |
+| List project domains | VERCEL_LIST_PROJECT_DOMAINS | projectId |
+| 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/plugins/awesome-claude-skills/verifiedemail-automation/SKILL.md b/plugins/awesome-claude-skills/verifiedemail-automation/SKILL.md
new file mode 100644
index 0000000..162cabb
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/veriphone-automation/SKILL.md b/plugins/awesome-claude-skills/veriphone-automation/SKILL.md
new file mode 100644
index 0000000..ea73d3e
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/vero-automation/SKILL.md b/plugins/awesome-claude-skills/vero-automation/SKILL.md
new file mode 100644
index 0000000..44ce557
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/vestaboard-automation/SKILL.md b/plugins/awesome-claude-skills/vestaboard-automation/SKILL.md
new file mode 100644
index 0000000..73420df
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/virustotal-automation/SKILL.md b/plugins/awesome-claude-skills/virustotal-automation/SKILL.md
new file mode 100644
index 0000000..81925fe
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/visme-automation/SKILL.md b/plugins/awesome-claude-skills/visme-automation/SKILL.md
new file mode 100644
index 0000000..de6646a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/waboxapp-automation/SKILL.md b/plugins/awesome-claude-skills/waboxapp-automation/SKILL.md
new file mode 100644
index 0000000..a925050
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wachete-automation/SKILL.md b/plugins/awesome-claude-skills/wachete-automation/SKILL.md
new file mode 100644
index 0000000..2e5842a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/waiverfile-automation/SKILL.md b/plugins/awesome-claude-skills/waiverfile-automation/SKILL.md
new file mode 100644
index 0000000..666647c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wakatime-automation/SKILL.md b/plugins/awesome-claude-skills/wakatime-automation/SKILL.md
new file mode 100644
index 0000000..f8dfb5a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wati-automation/SKILL.md b/plugins/awesome-claude-skills/wati-automation/SKILL.md
new file mode 100644
index 0000000..d3ea9da
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wave-accounting-automation/SKILL.md b/plugins/awesome-claude-skills/wave-accounting-automation/SKILL.md
new file mode 100644
index 0000000..b332f10
--- /dev/null
+++ b/plugins/awesome-claude-skills/wave-accounting-automation/SKILL.md
@@ -0,0 +1,40 @@
+---
+name: Wave Accounting Automation
+description: "Wave Accounting toolkit is not currently available as a native integration. No Wave-specific tools were found in the Composio platform. This skill is a placeholder pending future integration."
+category: accounting
+requires:
+ mcp:
+ - rube
+---
+
+# Wave Accounting Automation
+
+> **Note:** The Wave Accounting toolkit (`wave_accounting`) does not currently have native tools available in the Composio platform. Searches for Wave Accounting-specific tools return results from other accounting/invoicing platforms (Stripe, Zoho Invoice) instead.
+
+**Toolkit docs:** [composio.dev/toolkits/wave_accounting](https://composio.dev/toolkits/wave_accounting)
+
+---
+
+## Status
+
+This integration is **not yet available** with native Wave Accounting tools. When Wave Accounting tools become available in Composio, this skill file will be updated with real tool slugs, workflows, and pitfalls.
+
+For accounting and invoicing automation needs, consider these alternatives that are available today:
+- **Stripe** -- Payment processing, invoicing, and subscription management
+- **Zoho Invoice** -- Invoice creation, payment tracking, and contact management
+- **QuickBooks** -- Full accounting suite with invoicing and expense tracking
+- **FreshBooks** -- Cloud accounting with time tracking and invoicing
+
+---
+
+## Setup
+
+1. Add the Composio MCP server to your client configuration:
+ ```
+ https://rube.app/mcp
+ ```
+2. Check back for Wave Accounting integration availability.
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/wave_accounting-automation/SKILL.md b/plugins/awesome-claude-skills/wave_accounting-automation/SKILL.md
new file mode 100644
index 0000000..89cc739
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/weathermap-automation/SKILL.md b/plugins/awesome-claude-skills/weathermap-automation/SKILL.md
new file mode 100644
index 0000000..4d286b9
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/webex-automation/SKILL.md b/plugins/awesome-claude-skills/webex-automation/SKILL.md
new file mode 100644
index 0000000..d098ae7
--- /dev/null
+++ b/plugins/awesome-claude-skills/webex-automation/SKILL.md
@@ -0,0 +1,176 @@
+---
+name: Webex Automation
+description: "Automate Cisco Webex messaging, rooms, teams, webhooks, and people management through natural language commands"
+requires:
+ mcp:
+ - rube
+---
+
+# Webex Automation
+
+Automate Cisco Webex collaboration workflows -- send messages, manage rooms and teams, configure webhooks, and look up people -- all through natural language.
+
+**Toolkit docs:** [composio.dev/toolkits/webex](https://composio.dev/toolkits/webex)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Connect your Webex account when prompted (OAuth flow via Composio)
+3. Start issuing natural language commands for Webex automation
+
+---
+
+## Core Workflows
+
+### 1. Send a Message to a Room or Person
+
+Post plain text, markdown, file attachments, or Adaptive Cards to any Webex room or directly to a person.
+
+**Tool:** `WEBEX_MESSAGING_CREATE_MESSAGE`
+
+Key parameters:
+- `roomId` -- target room ID (use `WEBEX_MESSAGING_LIST_ROOMS` to find it)
+- `toPersonEmail` -- send a private 1:1 message instead (mutually exclusive with `roomId`)
+- `text` -- plain text content (max 7439 bytes)
+- `markdown` -- markdown-formatted content (takes precedence over `text`)
+- `files` -- list of public URLs for file attachments (one file per message)
+- `attachments` -- Adaptive Card JSON (one card per message)
+- `parentId` -- reply to a specific message as a threaded response
+
+Example prompt:
+> "Send a markdown message to room Y2lz... saying **Deploy completed** with a link to the release notes"
+
+---
+
+### 2. List and Discover Rooms
+
+Browse all rooms you belong to, filtered by type, team, or sorted by activity.
+
+**Tool:** `WEBEX_MESSAGING_LIST_ROOMS`
+
+Key parameters:
+- `type` -- filter by `direct` (1:1) or `group`
+- `teamId` -- limit to rooms in a specific team
+- `sortBy` -- sort by `id`, `lastactivity`, or `created`
+- `max` -- limit results (1-1000, default 100)
+
+Follow-up with `WEBEX_MESSAGING_GET_ROOM_DETAILS` to get full metadata for a specific room including title, type, lock status, creator, and timestamps.
+
+Example prompt:
+> "List my 10 most recently active group rooms in Webex"
+
+---
+
+### 3. Manage Webhooks for Event-Driven Automation
+
+Create webhooks to receive real-time HTTP POST notifications when Webex resources change.
+
+**Tool:** `WEBEX_WEBHOOKS_CREATE_WEBHOOK`
+
+Key parameters:
+- `name` -- human-friendly webhook name (required)
+- `targetUrl` -- URL that receives POST notifications (required)
+- `resource` -- what to monitor: `messages`, `rooms`, `memberships`, `meetings`, `recordings`, `meetingParticipants`, `telephony_calls`, etc. (required)
+- `event` -- trigger type: `created`, `updated`, `deleted`, `started`, `ended`, `joined`, `left` (required)
+- `filter` -- scope notifications (e.g., `roomId=` or `hostEmail=`)
+- `secret` -- optional HMAC secret for payload signature verification
+- `ownedBy` -- `creator` for personal or `org` for organization-wide webhooks
+
+Supporting tools:
+- `WEBEX_LIST_WEBHOOKS` -- list all registered webhooks with optional `max` and `ownedBy` filters
+- `WEBEX_WEBHOOKS_GET_WEBHOOK` -- inspect a specific webhook by `webhookId`
+
+Example prompt:
+> "Create a webhook called 'New Messages' that POSTs to https://my-app.com/hook whenever a message is created in room Y2lz..."
+
+---
+
+### 4. Manage Team Memberships
+
+Add people to Webex teams and optionally grant moderator privileges.
+
+**Tool:** `WEBEX_MESSAGING_CREATE_TEAM_MEMBERSHIP`
+
+Key parameters:
+- `teamId` -- the team to add the person to (required)
+- `personEmail` -- email of the person to add
+- `personId` -- Webex person ID (alternative to email)
+- `isModerator` -- set to `true` for moderator access (default `false`)
+
+Use `WEBEX_LIST_TEAMS` to discover available teams first.
+
+Example prompt:
+> "Add alice@example.com as a moderator to team Y2lz..."
+
+---
+
+### 5. Audit Room Memberships
+
+Check who is in a room, verify a specific person's membership, or list memberships across teams.
+
+**Tool:** `WEBEX_MESSAGING_LIST_MEMBERSHIPS`
+
+Key parameters:
+- `roomId` -- list all members of a specific room
+- `personEmail` -- check if a person is a member (requires `roomId`)
+- `personId` -- check by Webex person ID (requires `roomId`)
+- `teamId` -- filter by team association
+- `max` -- limit results
+
+Example prompt:
+> "List all members of room Y2lz... and tell me who the moderators are"
+
+---
+
+### 6. Search and Look Up People
+
+Look up people in your Webex organization by email, display name, or ID.
+
+**Tool:** `WEBEX_PEOPLE_LIST_PEOPLE`
+
+Use to resolve names to person IDs before sending direct messages or adding team members.
+
+Example prompt:
+> "Find the Webex person ID for bob@company.com"
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| Webhook auto-disable | Target URL must respond with HTTP 2xx; 100 failures in 5 minutes disables the webhook automatically |
+| Message size limit | Both `text` and `markdown` have a 7439-byte maximum |
+| One file per message | The `files` array accepts a list but only one attachment is actually supported per message |
+| One card per message | Only one Adaptive Card attachment is supported per message |
+| Mutually exclusive targets | `roomId` and `toPersonEmail`/`toPersonId` cannot be used together when sending messages |
+| Room update requires title | `WEBEX_UPDATE_ROOM` always requires the `title` parameter, even when only changing lock status or team |
+| orgPublicSpaces conflicts | Cannot combine `orgPublicSpaces` with `teamId`, `type`, or `sortBy` when listing rooms |
+| Webhook read scope | Creating a webhook requires `read` scope on the monitored resource type |
+| Membership filter requires roomId | `personEmail` and `personId` filters in list memberships require `roomId` unless you are a Compliance Officer |
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Key Params |
+|--------|-----------|------------|
+| Send message | `WEBEX_MESSAGING_CREATE_MESSAGE` | `roomId`, `text`/`markdown`, `toPersonEmail` |
+| List rooms | `WEBEX_MESSAGING_LIST_ROOMS` | `type`, `sortBy`, `max` |
+| Get room details | `WEBEX_MESSAGING_GET_ROOM_DETAILS` | `roomId` |
+| Update room | `WEBEX_UPDATE_ROOM` | `roomId`, `title` |
+| Delete message | `WEBEX_MESSAGING_DELETE_MESSAGE` | `messageId` |
+| Get message details | `WEBEX_MESSAGING_GET_MESSAGE_DETAILS` | `messageId` |
+| Create webhook | `WEBEX_WEBHOOKS_CREATE_WEBHOOK` | `name`, `targetUrl`, `resource`, `event` |
+| List webhooks | `WEBEX_LIST_WEBHOOKS` | `max`, `ownedBy` |
+| Get webhook | `WEBEX_WEBHOOKS_GET_WEBHOOK` | `webhookId` |
+| Add team member | `WEBEX_MESSAGING_CREATE_TEAM_MEMBERSHIP` | `teamId`, `personEmail`, `isModerator` |
+| List memberships | `WEBEX_MESSAGING_LIST_MEMBERSHIPS` | `roomId`, `personEmail`, `max` |
+| List people | `WEBEX_PEOPLE_LIST_PEOPLE` | email, displayName, ID filters |
+| List teams | `WEBEX_LIST_TEAMS` | `max` |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/webflow-automation/SKILL.md b/plugins/awesome-claude-skills/webflow-automation/SKILL.md
new file mode 100644
index 0000000..e319e31
--- /dev/null
+++ b/plugins/awesome-claude-skills/webflow-automation/SKILL.md
@@ -0,0 +1,241 @@
+---
+name: webflow-automation
+description: Automate Webflow CMS collections, site publishing, page management, asset uploads, and ecommerce orders via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Webflow Automation via Rube MCP
+
+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)
+- Active Webflow connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `webflow`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `webflow`
+3. If connection is not ACTIVE, follow the returned auth link to complete Webflow OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage CMS Collection Items
+
+**When to use**: User wants to create, update, list, or delete items in Webflow CMS collections (blog posts, products, team members, etc.)
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - List sites to find the target site_id [Prerequisite]
+2. `WEBFLOW_LIST_COLLECTIONS` - List all collections for the site [Prerequisite]
+3. `WEBFLOW_GET_COLLECTION` - Get collection schema to find valid field slugs [Prerequisite for create/update]
+4. `WEBFLOW_LIST_COLLECTION_ITEMS` - List existing items with filtering and pagination [Optional]
+5. `WEBFLOW_GET_COLLECTION_ITEM` - Get a specific item's full details [Optional]
+6. `WEBFLOW_CREATE_COLLECTION_ITEM` - Create a new item with field data [Required for creation]
+7. `WEBFLOW_UPDATE_COLLECTION_ITEM` - Update an existing item's fields [Required for updates]
+8. `WEBFLOW_DELETE_COLLECTION_ITEM` - Permanently remove an item [Optional]
+9. `WEBFLOW_PUBLISH_SITE` - Publish changes to make them live [Optional]
+
+**Key parameters for CREATE_COLLECTION_ITEM**:
+- `collection_id`: 24-character hex string from LIST_COLLECTIONS
+- `field_data`: Object with field slug keys (NOT display names); must include `name` and `slug`
+- `field_data.name`: Display name for the item
+- `field_data.slug`: URL-friendly identifier (lowercase, hyphens, no spaces)
+- `is_draft`: Boolean to create as draft (default false)
+
+**Key parameters for UPDATE_COLLECTION_ITEM**:
+- `collection_id`: Collection identifier
+- `item_id`: 24-character hex MongoDB ObjectId of the existing item
+- `fields`: Object with field slug keys and new values
+- `live`: Boolean to publish changes immediately (default false)
+
+**Field value types**:
+- Text/Email/Link/Date: string
+- Number: integer or float
+- Boolean: true/false
+- Image: `{"url": "...", "alt": "...", "fileId": "..."}`
+- Multi-reference: array of reference ID strings
+- Multi-image: array of image objects
+- Option: option ID string
+
+**Pitfalls**:
+- Field keys must use the exact field `slug` from the collection schema, NOT display names
+- Always call `GET_COLLECTION` first to retrieve the schema and identify correct field slugs
+- `CREATE_COLLECTION_ITEM` requires `name` and `slug` in `field_data`
+- `UPDATE_COLLECTION_ITEM` cannot create new items; it requires a valid existing `item_id`
+- `item_id` must be a 24-character hexadecimal MongoDB ObjectId
+- Slug must be lowercase alphanumeric with hyphens: `^[a-z0-9]+(?:-[a-z0-9]+)*$`
+- CMS items are staged; use `PUBLISH_SITE` or set `live: true` to push to production
+
+### 2. Manage Sites and Publishing
+
+**When to use**: User wants to list sites, inspect site configuration, or publish staged changes
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - List all accessible sites [Required]
+2. `WEBFLOW_GET_SITE_INFO` - Get detailed site metadata including domains and settings [Optional]
+3. `WEBFLOW_PUBLISH_SITE` - Deploy all staged changes to live site [Required for publishing]
+
+**Key parameters for PUBLISH_SITE**:
+- `site_id`: Site identifier from LIST_WEBFLOW_SITES
+- `custom_domains`: Array of custom domain ID strings (from GET_SITE_INFO)
+- `publish_to_webflow_subdomain`: Boolean to publish to `{shortName}.webflow.io`
+- At least one of `custom_domains` or `publish_to_webflow_subdomain` must be specified
+
+**Pitfalls**:
+- `PUBLISH_SITE` republishes ALL staged changes for selected domains -- verify no unintended drafts are pending
+- Rate limit: 1 successful publish per minute
+- For sites without custom domains, must set `publish_to_webflow_subdomain: true`
+- `custom_domains` expects domain IDs (hex strings), not domain names
+- Publishing is a production action -- always confirm with the user first
+
+### 3. Manage Pages
+
+**When to use**: User wants to list pages, inspect page metadata, or examine page DOM structure
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - Find the target site_id [Prerequisite]
+2. `WEBFLOW_LIST_PAGES` - List all pages for a site with pagination [Required]
+3. `WEBFLOW_GET_PAGE` - Get detailed metadata for a specific page [Optional]
+4. `WEBFLOW_GET_PAGE_DOM` - Get the DOM/content node structure of a static page [Optional]
+
+**Key parameters**:
+- `site_id`: Site identifier (required for list pages)
+- `page_id`: 24-character hex page identifier
+- `locale_id`: Optional locale filter for multi-language sites
+- `limit`: Max results per page (max 100)
+- `offset`: Pagination offset
+
+**Pitfalls**:
+- `LIST_PAGES` paginates via offset/limit; iterate when sites have many pages
+- Page IDs are 24-character hex strings matching pattern `^[0-9a-fA-F]{24}$`
+- `GET_PAGE_DOM` returns the node structure, not rendered HTML
+- Pages include both static and CMS-driven pages
+
+### 4. Upload Assets
+
+**When to use**: User wants to upload images, files, or other assets to a Webflow site
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - Find the target site_id [Prerequisite]
+2. `WEBFLOW_UPLOAD_ASSET` - Upload a file with base64-encoded content [Required]
+
+**Key parameters**:
+- `site_id`: Site identifier
+- `file_name`: Name of the file (e.g., `"logo.png"`)
+- `file_content`: Base64-encoded binary content of the file (NOT a placeholder or URL)
+- `content_type`: MIME type (e.g., `"image/png"`, `"image/jpeg"`, `"application/pdf"`)
+- `md5`: MD5 hash of the raw file bytes (32-character hex string)
+- `asset_folder_id`: Optional folder placement
+
+**Pitfalls**:
+- `file_content` must be actual base64-encoded data, NOT a variable reference or placeholder
+- `md5` must be computed from the raw bytes, not from the base64 string
+- This is a two-step process internally: generates an S3 pre-signed URL, then uploads
+- Large files may encounter timeouts; keep uploads reasonable in size
+
+### 5. Manage Ecommerce Orders
+
+**When to use**: User wants to view ecommerce orders from a Webflow site
+
+**Tool sequence**:
+1. `WEBFLOW_LIST_WEBFLOW_SITES` - Find the site with ecommerce enabled [Prerequisite]
+2. `WEBFLOW_LIST_ORDERS` - List all orders with optional status filtering [Required]
+3. `WEBFLOW_GET_ORDER` - Get detailed information for a specific order [Optional]
+
+**Key parameters**:
+- `site_id`: Site identifier (must have ecommerce enabled)
+- `order_id`: Specific order identifier for detailed retrieval
+- `status`: Filter orders by status
+
+**Pitfalls**:
+- Ecommerce must be enabled on the Webflow site for order endpoints to work
+- Order endpoints are read-only; no create/update/delete for orders through these tools
+
+## Common Patterns
+
+### ID Resolution
+Webflow uses 24-character hexadecimal IDs throughout:
+- **Site ID**: `WEBFLOW_LIST_WEBFLOW_SITES` -- find by name, capture `id`
+- **Collection ID**: `WEBFLOW_LIST_COLLECTIONS` with `site_id`
+- **Item ID**: `WEBFLOW_LIST_COLLECTION_ITEMS` with `collection_id`
+- **Page ID**: `WEBFLOW_LIST_PAGES` with `site_id`
+- **Domain IDs**: `WEBFLOW_GET_SITE_INFO` -- found in `customDomains` array
+- **Field slugs**: `WEBFLOW_GET_COLLECTION` -- found in collection `fields` array
+
+### Pagination
+Webflow uses offset-based pagination:
+- `offset`: Starting index (0-based)
+- `limit`: Items per page (max 100)
+- Increment offset by limit until fewer results than limit are returned
+- Available on: LIST_COLLECTION_ITEMS, LIST_PAGES
+
+### CMS Workflow
+Typical CMS content creation flow:
+1. Get site_id from LIST_WEBFLOW_SITES
+2. Get collection_id from LIST_COLLECTIONS
+3. Get field schema from GET_COLLECTION (to learn field slugs)
+4. Create/update items using correct field slugs
+5. Publish site to make changes live
+
+## Known Pitfalls
+
+### ID Formats
+- All Webflow IDs are 24-character hexadecimal strings (MongoDB ObjectIds)
+- Example: `580e63fc8c9a982ac9b8b745`
+- Pattern: `^[0-9a-fA-F]{24}$`
+- Invalid IDs return 404 errors
+
+### Field Slugs vs Display Names
+- CMS operations require field `slug` values, NOT display names
+- A field with displayName "Author Name" might have slug `author-name`
+- Always call `GET_COLLECTION` to discover correct field slugs
+- Using wrong field names silently ignores the data or causes validation errors
+
+### Publishing
+- `PUBLISH_SITE` deploys ALL staged changes, not just specific items
+- Rate limited to 1 publish per minute
+- Must specify at least one domain target (custom or webflow subdomain)
+- This is a production-affecting action; always confirm intent
+
+### Authentication Scopes
+- Different operations require different OAuth scopes: `sites:read`, `cms:read`, `cms:write`, `pages:read`
+- A 403 error typically means missing OAuth scopes
+- Check connection permissions if operations fail with authorization errors
+
+### Destructive Operations
+- `DELETE_COLLECTION_ITEM` permanently removes CMS items
+- `PUBLISH_SITE` makes all staged changes live immediately
+- Always confirm with the user before executing these actions
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List sites | `WEBFLOW_LIST_WEBFLOW_SITES` | (none) |
+| Get site info | `WEBFLOW_GET_SITE_INFO` | `site_id` |
+| Publish site | `WEBFLOW_PUBLISH_SITE` | `site_id`, `custom_domains` or `publish_to_webflow_subdomain` |
+| List collections | `WEBFLOW_LIST_COLLECTIONS` | `site_id` |
+| Get collection schema | `WEBFLOW_GET_COLLECTION` | `collection_id` |
+| List collection items | `WEBFLOW_LIST_COLLECTION_ITEMS` | `collection_id`, `limit`, `offset` |
+| Get collection item | `WEBFLOW_GET_COLLECTION_ITEM` | `collection_id`, `item_id` |
+| Create collection item | `WEBFLOW_CREATE_COLLECTION_ITEM` | `collection_id`, `field_data` |
+| Update collection item | `WEBFLOW_UPDATE_COLLECTION_ITEM` | `collection_id`, `item_id`, `fields` |
+| Delete collection item | `WEBFLOW_DELETE_COLLECTION_ITEM` | `collection_id`, `item_id` |
+| List pages | `WEBFLOW_LIST_PAGES` | `site_id`, `limit`, `offset` |
+| Get page | `WEBFLOW_GET_PAGE` | `page_id` |
+| Get page DOM | `WEBFLOW_GET_PAGE_DOM` | `page_id` |
+| 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/plugins/awesome-claude-skills/webscraping-ai-automation/SKILL.md b/plugins/awesome-claude-skills/webscraping-ai-automation/SKILL.md
new file mode 100644
index 0000000..11f406c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/webvizio-automation/SKILL.md b/plugins/awesome-claude-skills/webvizio-automation/SKILL.md
new file mode 100644
index 0000000..58d8c12
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/whatsapp-automation/SKILL.md b/plugins/awesome-claude-skills/whatsapp-automation/SKILL.md
new file mode 100644
index 0000000..95ef137
--- /dev/null
+++ b/plugins/awesome-claude-skills/whatsapp-automation/SKILL.md
@@ -0,0 +1,219 @@
+---
+name: whatsapp-automation
+description: "Automate WhatsApp Business tasks via Rube MCP (Composio): send messages, manage templates, upload media, and handle contacts. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# WhatsApp Business Automation via Rube MCP
+
+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)
+- Active WhatsApp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `whatsapp`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+- WhatsApp Business API account required (not regular WhatsApp)
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `whatsapp`
+3. If connection is not ACTIVE, follow the returned auth link to complete WhatsApp Business setup
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send a Text Message
+
+**When to use**: User wants to send a text message to a WhatsApp contact
+
+**Tool sequence**:
+1. `WHATSAPP_GET_PHONE_NUMBERS` - List available business phone numbers [Prerequisite]
+2. `WHATSAPP_SEND_MESSAGE` - Send a text message [Required]
+
+**Key parameters**:
+- `to`: Recipient phone number in international format (e.g., '+14155551234')
+- `body`: Message text content
+- `phone_number_id`: Business phone number ID to send from
+
+**Pitfalls**:
+- Phone numbers must be in international E.164 format with country code
+- Messages outside the 24-hour window require approved templates
+- The 24-hour window starts when the customer last messaged you
+- Business-initiated conversations require template messages first
+
+### 2. Send Template Messages
+
+**When to use**: User wants to send pre-approved template messages for outbound communication
+
+**Tool sequence**:
+1. `WHATSAPP_GET_MESSAGE_TEMPLATES` - List available templates [Prerequisite]
+2. `WHATSAPP_GET_TEMPLATE_STATUS` - Check template approval status [Optional]
+3. `WHATSAPP_SEND_TEMPLATE_MESSAGE` - Send the template message [Required]
+
+**Key parameters**:
+- `template_name`: Name of the approved template
+- `language_code`: Template language (e.g., 'en_US')
+- `to`: Recipient phone number
+- `components`: Template variable values and parameters
+
+**Pitfalls**:
+- Templates must be approved by Meta before use
+- Template variables must match the expected count and format
+- Sending unapproved or rejected templates returns errors
+- Language code must match an approved translation of the template
+
+### 3. Send Media Messages
+
+**When to use**: User wants to send images, documents, or other media
+
+**Tool sequence**:
+1. `WHATSAPP_UPLOAD_MEDIA` - Upload media to WhatsApp servers [Required]
+2. `WHATSAPP_SEND_MEDIA_BY_ID` - Send media using the uploaded media ID [Required]
+ OR
+3. `WHATSAPP_SEND_MEDIA` - Send media using a public URL [Alternative]
+
+**Key parameters**:
+- `media_url`: Public URL of the media (for SEND_MEDIA)
+- `media_id`: ID from upload response (for SEND_MEDIA_BY_ID)
+- `type`: Media type ('image', 'document', 'audio', 'video', 'sticker')
+- `caption`: Optional caption for the media
+
+**Pitfalls**:
+- Uploaded media IDs are temporary and expire after a period
+- Media size limits vary by type (images: 5MB, videos: 16MB, documents: 100MB)
+- Supported formats: images (JPEG, PNG), videos (MP4, 3GPP), documents (PDF, etc.)
+- SEND_MEDIA requires a publicly accessible HTTPS URL
+
+### 4. Reply to Messages
+
+**When to use**: User wants to reply to an incoming WhatsApp message
+
+**Tool sequence**:
+1. `WHATSAPP_SEND_REPLY` - Send a reply to a specific message [Required]
+
+**Key parameters**:
+- `message_id`: ID of the message being replied to
+- `to`: Recipient phone number
+- `body`: Reply text content
+
+**Pitfalls**:
+- message_id must be from a message received within the 24-hour window
+- Replies appear as quoted messages in the conversation
+- The original message must still exist (not deleted) for the quote to display
+
+### 5. Manage Business Profile and Templates
+
+**When to use**: User wants to view or manage their WhatsApp Business profile
+
+**Tool sequence**:
+1. `WHATSAPP_GET_BUSINESS_PROFILE` - Get business profile details [Optional]
+2. `WHATSAPP_GET_PHONE_NUMBERS` - List registered phone numbers [Optional]
+3. `WHATSAPP_GET_PHONE_NUMBER` - Get details for a specific number [Optional]
+4. `WHATSAPP_CREATE_MESSAGE_TEMPLATE` - Create a new template [Optional]
+5. `WHATSAPP_GET_MESSAGE_TEMPLATES` - List all templates [Optional]
+
+**Key parameters**:
+- `phone_number_id`: Business phone number ID
+- `template_name`: Name for the new template
+- `category`: Template category (MARKETING, UTILITY, AUTHENTICATION)
+- `language`: Template language code
+
+**Pitfalls**:
+- New templates require Meta review before they can be used
+- Template names must be lowercase with underscores (no spaces)
+- Category affects pricing and approval criteria
+- Templates have specific formatting requirements for headers, body, and buttons
+
+### 6. Share Contacts
+
+**When to use**: User wants to send contact information via WhatsApp
+
+**Tool sequence**:
+1. `WHATSAPP_SEND_CONTACTS` - Send contact cards [Required]
+
+**Key parameters**:
+- `to`: Recipient phone number
+- `contacts`: Array of contact objects with name, phone, email details
+
+**Pitfalls**:
+- Contact objects must follow the WhatsApp Business API contact schema
+- At least a name field is required for each contact
+- Phone numbers in contacts should include country codes
+
+## Common Patterns
+
+### 24-Hour Messaging Window
+
+- Customers must message you first to open a conversation window
+- Within 24 hours of their last message, you can send free-form messages
+- After 24 hours, only approved template messages can be sent
+- Template messages can re-open the conversation window
+
+### Phone Number Resolution
+
+```
+1. Call WHATSAPP_GET_PHONE_NUMBERS
+2. Extract phone_number_id for your business number
+3. Use phone_number_id in all send operations
+```
+
+### Media Upload Flow
+
+```
+1. Call WHATSAPP_UPLOAD_MEDIA with the file
+2. Extract media_id from response
+3. Call WHATSAPP_SEND_MEDIA_BY_ID with media_id
+4. OR use WHATSAPP_SEND_MEDIA with a public URL directly
+```
+
+## Known Pitfalls
+
+**Phone Number Format**:
+- Always use E.164 format: +[country code][number] (e.g., '+14155551234')
+- Do not include dashes, spaces, or parentheses
+- Country code is required; local numbers without it will fail
+
+**Messaging Restrictions**:
+- Business-initiated messages require templates outside the 24-hour window
+- Template messages cost money per conversation
+- Rate limits apply per phone number and per account
+
+**Media Handling**:
+- Uploaded media expires; use promptly after upload
+- Media URLs must be publicly accessible HTTPS
+- Stickers have specific requirements (WebP format, 512x512 pixels)
+
+**Template Management**:
+- Template review can take up to 24 hours
+- Rejected templates need to be fixed and resubmitted
+- Template variables use double curly braces: {{1}}, {{2}}, etc.
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Send message | WHATSAPP_SEND_MESSAGE | to, body |
+| Send template | WHATSAPP_SEND_TEMPLATE_MESSAGE | template_name, to, language_code |
+| Upload media | WHATSAPP_UPLOAD_MEDIA | (file params) |
+| Send media by ID | WHATSAPP_SEND_MEDIA_BY_ID | media_id, to, type |
+| Send media by URL | WHATSAPP_SEND_MEDIA | media_url, to, type |
+| Reply to message | WHATSAPP_SEND_REPLY | message_id, to, body |
+| Send contacts | WHATSAPP_SEND_CONTACTS | to, contacts |
+| Get media | WHATSAPP_GET_MEDIA | media_id |
+| List phone numbers | WHATSAPP_GET_PHONE_NUMBERS | (none) |
+| Get phone number | WHATSAPP_GET_PHONE_NUMBER | phone_number_id |
+| Get business profile | WHATSAPP_GET_BUSINESS_PROFILE | phone_number_id |
+| 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/plugins/awesome-claude-skills/whautomate-automation/SKILL.md b/plugins/awesome-claude-skills/whautomate-automation/SKILL.md
new file mode 100644
index 0000000..7f21d80
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/winston-ai-automation/SKILL.md b/plugins/awesome-claude-skills/winston-ai-automation/SKILL.md
new file mode 100644
index 0000000..6274741
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wit-ai-automation/SKILL.md b/plugins/awesome-claude-skills/wit-ai-automation/SKILL.md
new file mode 100644
index 0000000..d1a1d39
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wiz-automation/SKILL.md b/plugins/awesome-claude-skills/wiz-automation/SKILL.md
new file mode 100644
index 0000000..394be4d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wolfram-alpha-api-automation/SKILL.md b/plugins/awesome-claude-skills/wolfram-alpha-api-automation/SKILL.md
new file mode 100644
index 0000000..88a1b98
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/woodpecker-co-automation/SKILL.md b/plugins/awesome-claude-skills/woodpecker-co-automation/SKILL.md
new file mode 100644
index 0000000..eb41151
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/workable-automation/SKILL.md b/plugins/awesome-claude-skills/workable-automation/SKILL.md
new file mode 100644
index 0000000..b9d9e56
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/workday-automation/SKILL.md b/plugins/awesome-claude-skills/workday-automation/SKILL.md
new file mode 100644
index 0000000..fbbe00f
--- /dev/null
+++ b/plugins/awesome-claude-skills/workday-automation/SKILL.md
@@ -0,0 +1,145 @@
+---
+name: Workday Automation
+description: "Automate HR operations in Workday -- manage workers, time off requests, absence balances, and employee data through natural language commands."
+requires:
+ mcp:
+ - rube
+---
+
+# Workday Automation
+
+Automate your Workday HR operations directly from Claude Code. Look up workers, create time off requests, check absence balances, and validate time off eligibility -- all without leaving your terminal.
+
+**Toolkit docs:** [composio.dev/toolkits/workday](https://composio.dev/toolkits/workday)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your Claude Code config with URL: `https://rube.app/mcp`
+2. When prompted, authenticate your Workday account through the connection link provided
+3. Start automating your HR workflows with natural language
+
+---
+
+## Core Workflows
+
+### 1. Search and List Workers
+
+Retrieve worker information with search and pagination.
+
+**Tool:** `WORKDAY_LIST_WORKERS`
+
+```
+Search for workers named "Sarah" and include terminated employees
+```
+
+Key parameters:
+- `search` -- search by name or worker ID (case-insensitive, space-delimited for OR search)
+- `includeTerminatedWorkers` -- include terminated workers in results
+- `limit` (default 20, max 100) / `offset` -- pagination controls
+
+### 2. Create Time Off Requests
+
+Submit time off requests for workers with full business process support.
+
+**Tool:** `WORKDAY_CREATE_TIME_OFF_REQUEST`
+
+```
+Create a vacation request for worker abc123 for March 15-17, 2026 (8 hours each day)
+```
+
+Key parameters:
+- `ID` (required) -- Workday worker ID
+- `businessProcessParameters` (required) -- must include `action` with `id` field (use `"d9e4223e446c11de98360015c5e6daf6"` for submit action)
+- `days` (required) -- array of time off entries, each with:
+ - `date` (required) -- date in `yyyy-mm-dd` format
+ - `timeOffType` (required) -- object with `id` of the eligible absence type
+ - `dailyQuantity` -- hours or days quantity
+ - `comment`, `start`, `end`, `position`, `reason` -- optional fields
+- `businessProcessParameters.comment` -- optional business process comment
+
+### 3. Check Time Off Eligibility
+
+Validate which dates a worker can take off before submitting a request.
+
+**Tool:** `WORKDAY_GET_WORKER_VALID_TIME_OFF_DATES`
+
+```
+Check if worker abc123 is eligible to take time off on March 15, 2026
+```
+
+Key parameters:
+- `ID` (required) -- Workday worker ID
+- `date` -- specific date to validate (`yyyy-mm-dd`)
+- `position` -- filter by specific position ID
+- `timeOff` -- filter by specific time off plan/type ID
+- `limit` (max 100) / `offset` -- pagination
+
+### 4. View Absence Balances
+
+Check remaining time off balances for workers across all plans.
+
+**Tool:** `WORKDAY_LIST_ABSENCE_BALANCES`
+
+```
+Show me absence balances for all workers in the organization
+```
+
+- Retrieves balances for time off plans and leave of absence types
+- Can be filtered by worker ID, category, and effective date
+
+### 5. Get Current User Profile
+
+Retrieve the authenticated worker's profile information.
+
+**Tool:** `WORKDAY_GET_CURRENT_USER`
+
+```
+Show me my Workday profile information
+```
+
+- No parameters required
+- Returns the authenticated worker's profile
+- Use this first to get the worker ID for subsequent operations
+
+### 6. View Time Off History
+
+Retrieve time off details and history for a specific worker.
+
+**Tool:** `WORKDAY_GET_WORKER_TIME_OFF_DETAILS`
+
+```
+Show me the time off history for worker abc123
+```
+
+- Retrieves a collection of time off details for the specified worker
+- Useful for auditing time off usage and remaining balances
+
+---
+
+## Known Pitfalls
+
+- **Worker ID resolution:** Always call `WORKDAY_GET_CURRENT_USER` or `WORKDAY_LIST_WORKERS` first to resolve Workday worker IDs. Worker IDs are Workday-specific UUIDs, not employee numbers.
+- **Time off type IDs must be valid:** The `timeOffType.id` in `WORKDAY_CREATE_TIME_OFF_REQUEST` must reference a valid eligible absence type for that worker. Use the "Get Worker Eligible Absence Types" flow to discover valid type IDs.
+- **Submit action ID:** The `businessProcessParameters.action.id` should be `"d9e4223e446c11de98360015c5e6daf6"` for the submit action. Using an incorrect ID will cause the business process to fail.
+- **Date format:** All date fields use `yyyy-mm-dd` format. ISO 8601 with timestamps is not accepted for date-only fields.
+- **Pagination limits:** The maximum `limit` is 100 across all Workday endpoints. Default is 20. Always paginate for complete datasets.
+- **Business process approval:** Creating a time off request initiates the business process but does not guarantee approval. The request enters the normal approval workflow.
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|---|---|
+| `WORKDAY_LIST_WORKERS` | Search and list workers with staffing info |
+| `WORKDAY_GET_CURRENT_USER` | Get the authenticated worker's profile |
+| `WORKDAY_CREATE_TIME_OFF_REQUEST` | Submit a time off request (requires `ID`, `businessProcessParameters`, `days`) |
+| `WORKDAY_GET_WORKER_VALID_TIME_OFF_DATES` | Check time off date eligibility (requires `ID`) |
+| `WORKDAY_LIST_ABSENCE_BALANCES` | Retrieve absence balances across time off plans |
+| `WORKDAY_GET_WORKER_TIME_OFF_DETAILS` | Get time off history for a worker |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/workiom-automation/SKILL.md b/plugins/awesome-claude-skills/workiom-automation/SKILL.md
new file mode 100644
index 0000000..d681d9a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/worksnaps-automation/SKILL.md b/plugins/awesome-claude-skills/worksnaps-automation/SKILL.md
new file mode 100644
index 0000000..d570899
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/wrike-automation/SKILL.md b/plugins/awesome-claude-skills/wrike-automation/SKILL.md
new file mode 100644
index 0000000..7680960
--- /dev/null
+++ b/plugins/awesome-claude-skills/wrike-automation/SKILL.md
@@ -0,0 +1,238 @@
+---
+name: wrike-automation
+description: "Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Wrike Automation via Rube MCP
+
+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)
+- Active Wrike connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `wrike`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `wrike`
+3. If connection is not ACTIVE, follow the returned auth link to complete Wrike OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Tasks
+
+**When to use**: User wants to create, assign, or update tasks in Wrike
+
+**Tool sequence**:
+1. `WRIKE_GET_FOLDERS` - Find the target folder/project [Prerequisite]
+2. `WRIKE_GET_ALL_CUSTOM_FIELDS` - Get custom field IDs if needed [Optional]
+3. `WRIKE_CREATE_TASK` - Create a new task [Required]
+4. `WRIKE_MODIFY_TASK` - Update task properties [Optional]
+
+**Key parameters**:
+- `folderId`: Parent folder ID where the task will be created
+- `title`: Task title
+- `description`: Task description (supports HTML)
+- `responsibles`: Array of user IDs to assign
+- `status`: 'Active', 'Completed', 'Deferred', 'Cancelled'
+- `importance`: 'High', 'Normal', 'Low'
+- `customFields`: Array of {id, value} objects
+- `dates`: Object with type, start, due, duration
+
+**Pitfalls**:
+- folderId is required; tasks must belong to a folder
+- responsibles requires Wrike user IDs, not emails or names
+- Custom field IDs must be obtained from GET_ALL_CUSTOM_FIELDS
+- priorityBefore and priorityAfter are mutually exclusive
+- Status field may not be available on Team plan
+- dates.start and dates.due use 'YYYY-MM-DD' format
+
+### 2. Manage Folders and Projects
+
+**When to use**: User wants to create, modify, or organize folders and projects
+
+**Tool sequence**:
+1. `WRIKE_GET_FOLDERS` - List existing folders [Required]
+2. `WRIKE_CREATE_FOLDER` - Create a new folder/project [Optional]
+3. `WRIKE_MODIFY_FOLDER` - Update folder properties [Optional]
+4. `WRIKE_LIST_SUBFOLDERS_BY_FOLDER_ID` - List subfolders [Optional]
+5. `WRIKE_DELETE_FOLDER` - Delete a folder permanently [Optional]
+
+**Key parameters**:
+- `folderId`: Parent folder ID for creation; target folder ID for modification
+- `title`: Folder name
+- `description`: Folder description
+- `customItemTypeId`: Set to create as a project instead of a folder
+- `shareds`: Array of user IDs or emails to share with
+- `project`: Filter for projects (true) or folders (false) in GET_FOLDERS
+
+**Pitfalls**:
+- DELETE_FOLDER is permanent and removes ALL contents (tasks, subfolders, documents)
+- Cannot modify rootFolderId or recycleBinId as parents
+- Folder creation auto-shares with the creator
+- customItemTypeId converts a folder into a project
+- GET_FOLDERS with descendants=true returns folder tree (may be large)
+
+### 3. Retrieve and Track Tasks
+
+**When to use**: User wants to find tasks, check status, or monitor progress
+
+**Tool sequence**:
+1. `WRIKE_FETCH_ALL_TASKS` - List tasks with optional filters [Required]
+2. `WRIKE_GET_TASK_BY_ID` - Get detailed info for a specific task [Optional]
+
+**Key parameters**:
+- `status`: Filter by task status ('Active', 'Completed', etc.)
+- `dueDate`: Filter by due date range (start/end/equal)
+- `fields`: Additional response fields to include
+- `page_size`: Results per page (1-100)
+- `taskId`: Specific task ID for detailed retrieval
+- `resolve_user_names`: Auto-resolve user IDs to names (default true)
+
+**Pitfalls**:
+- FETCH_ALL_TASKS paginates at max 100 items per page
+- dueDate filter supports 'equal', 'start', and 'end' fields
+- Date format: 'yyyy-MM-dd' or 'yyyy-MM-ddTHH:mm:ss'
+- GET_TASK_BY_ID returns read-only detailed information
+- customFields are returned by default for single task queries
+
+### 4. Launch Task Blueprints
+
+**When to use**: User wants to create tasks from predefined templates
+
+**Tool sequence**:
+1. `WRIKE_LIST_TASK_BLUEPRINTS` - List available blueprints [Prerequisite]
+2. `WRIKE_LIST_SPACE_TASK_BLUEPRINTS` - List blueprints in a specific space [Alternative]
+3. `WRIKE_LAUNCH_TASK_BLUEPRINT_ASYNC` - Launch a blueprint [Required]
+
+**Key parameters**:
+- `task_blueprint_id`: ID of the blueprint to launch
+- `title`: Title for the root task
+- `parent_id`: Parent folder/project ID (OR super_task_id)
+- `super_task_id`: Parent task ID (OR parent_id)
+- `reschedule_date`: Target date for task rescheduling
+- `reschedule_mode`: 'RescheduleStartDate' or 'RescheduleFinishDate'
+- `entry_limit`: Max tasks to copy (1-250)
+
+**Pitfalls**:
+- Either parent_id or super_task_id is required, not both
+- Blueprint launch is asynchronous; tasks may take time to appear
+- reschedule_date requires reschedule_mode to be set
+- entry_limit caps at 250 tasks/folders per blueprint launch
+- copy_descriptions defaults to false; set true to include task descriptions
+
+### 5. Manage Workspace and Members
+
+**When to use**: User wants to manage spaces, members, or invitations
+
+**Tool sequence**:
+1. `WRIKE_GET_SPACE` - Get space details [Optional]
+2. `WRIKE_GET_CONTACTS` - List workspace contacts/members [Optional]
+3. `WRIKE_CREATE_INVITATION` - Invite a user to the workspace [Optional]
+4. `WRIKE_DELETE_SPACE` - Delete a space permanently [Optional]
+
+**Key parameters**:
+- `spaceId`: Space identifier
+- `email`: Email for invitation
+- `role`: User role ('Admin', 'Regular User', 'External User')
+- `firstName`/`lastName`: Invitee name
+
+**Pitfalls**:
+- DELETE_SPACE is irreversible and removes all space contents
+- userTypeId and role/external are mutually exclusive in invitations
+- Custom email subjects/messages require a paid Wrike plan
+- GET_CONTACTS returns workspace-level contacts, not task-specific assignments
+
+## Common Patterns
+
+### Folder ID Resolution
+
+```
+1. Call WRIKE_GET_FOLDERS (optionally with project=true for projects only)
+2. Navigate folder tree to find target
+3. Extract folder id (e.g., 'IEAGKVLFK4IHGQOI')
+4. Use as folderId in task/folder creation
+```
+
+### Custom Field Setup
+
+```
+1. Call WRIKE_GET_ALL_CUSTOM_FIELDS to get definitions
+2. Find field by name, extract id and type
+3. Format value according to type (text, dropdown, number, date)
+4. Include as {id: 'FIELD_ID', value: 'VALUE'} in customFields array
+```
+
+### Task Assignment
+
+```
+1. Call WRIKE_GET_CONTACTS to find user IDs
+2. Use user IDs in responsibles array when creating tasks
+3. Or use addResponsibles/removeResponsibles when modifying tasks
+```
+
+### Pagination
+
+- FETCH_ALL_TASKS: Use page_size (max 100) and check for more results
+- GET_FOLDERS: Use nextPageToken when descendants=false and pageSize is set
+- LIST_TASK_BLUEPRINTS: Use next_page_token and page_size (default 100)
+
+## Known Pitfalls
+
+**ID Formats**:
+- Wrike IDs are opaque alphanumeric strings (e.g., 'IEAGTXR7I4IHGABC')
+- Task IDs, folder IDs, space IDs, and user IDs all use this format
+- Custom field IDs follow the same pattern
+- Never guess IDs; always resolve from list/search operations
+
+**Permissions**:
+- Operations depend on user role and sharing settings
+- Shared folders/tasks are visible only to shared users
+- Admin operations require appropriate role
+- Some features (custom statuses, billing types) are plan-dependent
+
+**Deletion Safety**:
+- DELETE_FOLDER removes ALL contents permanently
+- DELETE_SPACE removes the entire space and contents
+- Consider using MODIFY_FOLDER to move to recycle bin instead
+- Restore from recycle bin is possible via MODIFY_FOLDER with restore=true
+
+**Date Handling**:
+- Dates use 'yyyy-MM-dd' format
+- DateTime uses 'yyyy-MM-ddTHH:mm:ssZ' or with timezone offset
+- Task dates include type ('Planned', 'Actual'), start, due, duration
+- Duration is in minutes
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create task | WRIKE_CREATE_TASK | folderId, title, responsibles, status |
+| Modify task | WRIKE_MODIFY_TASK | taskId, title, status, addResponsibles |
+| Get task by ID | WRIKE_GET_TASK_BY_ID | taskId |
+| Fetch all tasks | WRIKE_FETCH_ALL_TASKS | status, dueDate, page_size |
+| Get folders | WRIKE_GET_FOLDERS | project, descendants |
+| Create folder | WRIKE_CREATE_FOLDER | folderId, title |
+| Modify folder | WRIKE_MODIFY_FOLDER | folderId, title, addShareds |
+| Delete folder | WRIKE_DELETE_FOLDER | folderId |
+| List subfolders | WRIKE_LIST_SUBFOLDERS_BY_FOLDER_ID | folderId |
+| Get custom fields | WRIKE_GET_ALL_CUSTOM_FIELDS | (none) |
+| List blueprints | WRIKE_LIST_TASK_BLUEPRINTS | limit, page_size |
+| Launch blueprint | WRIKE_LAUNCH_TASK_BLUEPRINT_ASYNC | task_blueprint_id, title, parent_id |
+| Get space | WRIKE_GET_SPACE | spaceId |
+| 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/plugins/awesome-claude-skills/writer-automation/SKILL.md b/plugins/awesome-claude-skills/writer-automation/SKILL.md
new file mode 100644
index 0000000..cd24b5c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/xero-automation/SKILL.md b/plugins/awesome-claude-skills/xero-automation/SKILL.md
new file mode 100644
index 0000000..7cc3765
--- /dev/null
+++ b/plugins/awesome-claude-skills/xero-automation/SKILL.md
@@ -0,0 +1,208 @@
+---
+name: Xero Automation
+description: "Xero Automation: manage invoices, contacts, payments, bank transactions, and accounts in Xero for cloud-based bookkeeping"
+requires:
+ mcp: [rube]
+---
+
+# Xero Automation
+
+Automate Xero accounting operations including managing invoices, contacts, payments, bank transactions, and chart of accounts for small business bookkeeping.
+
+**Toolkit docs:** [composio.dev/toolkits/xero](https://composio.dev/toolkits/xero)
+
+---
+
+## Setup
+
+This skill requires the **Rube MCP server** connected at `https://rube.app/mcp`.
+
+Before executing any tools, ensure an active connection exists for the `xero` toolkit. If no connection is active, initiate one via `RUBE_MANAGE_CONNECTIONS`.
+
+**Multi-tenant:** If you manage multiple Xero organizations, first call `XERO_GET_CONNECTIONS` to list active tenants and obtain the correct `tenant_id` for subsequent calls.
+
+---
+
+## Core Workflows
+
+### 1. List and Filter Invoices
+
+Retrieve invoices with filtering by status, contact, date range, and pagination.
+
+**Tool:** `XERO_LIST_INVOICES`
+
+**Key Parameters:**
+- `Statuses` -- Comma-separated status filter: `"DRAFT"`, `"SUBMITTED"`, `"AUTHORISED"`, `"PAID"`
+- `ContactIDs` -- Comma-separated Contact IDs to filter by
+- `InvoiceIDs` -- Comma-separated Invoice IDs to filter by
+- `where` -- OData-style filter, e.g., `"Status==\"AUTHORISED\" AND Total>100"`
+- `order` -- Sort expression, e.g., `"Date DESC"`, `"InvoiceNumber ASC"`
+- `page` -- Page number for pagination
+- `If-Modified-Since` -- UTC timestamp; returns only invoices modified since this date
+- `tenant_id` -- Xero organization ID (uses first tenant if omitted)
+
+**Example:**
+```
+Tool: XERO_LIST_INVOICES
+Arguments:
+ Statuses: "AUTHORISED,PAID"
+ order: "Date DESC"
+ page: 1
+```
+
+---
+
+### 2. Manage Contacts
+
+Retrieve and search contacts for use in invoices and transactions.
+
+**Tool:** `XERO_GET_CONTACTS`
+
+**Key Parameters:**
+- `searchTerm` -- Case-insensitive search across Name, FirstName, LastName, Email, ContactNumber
+- `ContactID` -- Fetch a single contact by ID
+- `where` -- OData filter, e.g., `"ContactStatus==\"ACTIVE\""`
+- `page`, `pageSize` -- Pagination controls
+- `order` -- Sort, e.g., `"UpdatedDateUTC DESC"`
+- `includeArchived` -- Include archived contacts when `true`
+- `summaryOnly` -- Lightweight response when `true`
+
+**Example:**
+```
+Tool: XERO_GET_CONTACTS
+Arguments:
+ searchTerm: "acme"
+ page: 1
+ pageSize: 25
+```
+
+> **Note:** On high-volume accounts, some `where` filters (e.g., `IsCustomer`, `IsSupplier`) may be rejected by Xero. Fall back to `searchTerm` or pagination.
+
+---
+
+### 3. Create Payments
+
+Link an invoice to a bank account by creating a payment record.
+
+**Tool:** `XERO_CREATE_PAYMENT`
+
+**Key Parameters:**
+- `InvoiceID` (required) -- Xero Invoice ID the payment applies to
+- `AccountID` (required) -- Bank account ID for the payment
+- `Amount` (required) -- Payment amount (number)
+- `Date` -- Payment date in `YYYY-MM-DD` format
+- `Reference` -- Payment reference or description
+- `CurrencyRate` -- Exchange rate for foreign currency payments
+
+**Example:**
+```
+Tool: XERO_CREATE_PAYMENT
+Arguments:
+ InvoiceID: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
+ AccountID: "b2c3d4e5-f6a7-8901-bcde-f12345678901"
+ Amount: 1500.00
+ Date: "2026-02-11"
+ Reference: "Payment for INV-0042"
+```
+
+---
+
+### 4. Create Bank Transactions
+
+Record spend (payments out) or receive (money in) bank transactions.
+
+**Tool:** `XERO_CREATE_BANK_TRANSACTION`
+
+**Key Parameters:**
+- `Type` (required) -- `"SPEND"` (payment out) or `"RECEIVE"` (money in)
+- `ContactID` (required) -- Xero Contact ID
+- `BankAccountCode` (required) -- Bank account code from chart of accounts
+- `LineItems` (required) -- Array of line items, each with:
+ - `Description` (required) -- Line item description
+ - `UnitAmount` (required) -- Unit price
+ - `AccountCode` (required) -- Account code for categorization
+ - `Quantity` -- Quantity (default 1)
+ - `TaxType` -- Tax type: `"OUTPUT"`, `"INPUT"`, `"NONE"`
+- `Date` -- Transaction date in `YYYY-MM-DD` format
+- `Reference` -- Transaction reference
+- `Status` -- `"AUTHORISED"` or `"DELETED"`
+- `CurrencyCode` -- e.g., `"USD"`, `"EUR"`
+
+**Example:**
+```
+Tool: XERO_CREATE_BANK_TRANSACTION
+Arguments:
+ Type: "SPEND"
+ ContactID: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
+ BankAccountCode: "090"
+ LineItems: [
+ {
+ "Description": "Office supplies",
+ "UnitAmount": 75.00,
+ "AccountCode": "429",
+ "Quantity": 1,
+ "TaxType": "INPUT"
+ }
+ ]
+ Date: "2026-02-11"
+ Reference: "Feb office supplies"
+```
+
+---
+
+### 5. List Payments and Bank Transactions
+
+Review existing payments and bank transaction history.
+
+**Tools:**
+- `XERO_LIST_PAYMENTS` -- List payments linking invoices to bank transactions
+- `XERO_LIST_BANK_TRANSACTIONS` -- List spend/receive bank transactions
+
+**Common Parameters:**
+- `where` -- OData filter, e.g., `"Status==\"AUTHORISED\""`
+- `order` -- Sort expression, e.g., `"Date DESC"`
+- `page` -- Page number for pagination
+- `If-Modified-Since` -- Incremental updates since timestamp
+- `tenant_id` -- Organization ID
+
+---
+
+### 6. View Chart of Accounts and Connections
+
+**Tools:**
+- `XERO_LIST_ACCOUNTS` -- Retrieve all account codes for categorizing transactions
+- `XERO_GET_CONNECTIONS` -- List active Xero tenant connections
+- `XERO_LIST_ATTACHMENTS` -- List attachments on an entity (invoice, contact, etc.)
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Detail |
+|---------|--------|
+| **Multi-tenant routing** | If `tenant_id` is omitted, the first connected tenant is used. Always verify the correct tenant with `XERO_GET_CONNECTIONS` when managing multiple organizations. |
+| **High-volume filter rejection** | On large accounts, some `where` filters like `IsCustomer`/`IsSupplier` may be rejected. Fall back to `searchTerm` with pagination. |
+| **OData filter syntax** | Use double-equals (`==`) in OData filters, e.g., `Status==\"AUTHORISED\"`. Single `=` causes errors. |
+| **Pagination required** | Most list endpoints paginate results. Always check for additional pages and continue fetching until complete. |
+| **Date format** | All dates must be in `YYYY-MM-DD` format. Timestamps for `If-Modified-Since` must be full ISO 8601 UTC datetime. |
+| **Bank account codes** | `BankAccountCode` in bank transactions must match a valid code from the chart of accounts. Use `XERO_LIST_ACCOUNTS` to discover valid codes. |
+
+---
+
+## Quick Reference
+
+| Tool Slug | Description |
+|-----------|-------------|
+| `XERO_LIST_INVOICES` | List invoices with filtering and pagination |
+| `XERO_GET_CONTACTS` | Retrieve and search contacts |
+| `XERO_CREATE_PAYMENT` | Create a payment linking invoice to bank account |
+| `XERO_CREATE_BANK_TRANSACTION` | Record a spend or receive bank transaction |
+| `XERO_LIST_PAYMENTS` | List payment records |
+| `XERO_LIST_BANK_TRANSACTIONS` | List bank transactions |
+| `XERO_LIST_ACCOUNTS` | Retrieve chart of accounts |
+| `XERO_GET_CONNECTIONS` | List active Xero tenant connections |
+| `XERO_LIST_ATTACHMENTS` | List attachments on an entity |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/y-gy-automation/SKILL.md b/plugins/awesome-claude-skills/y-gy-automation/SKILL.md
new file mode 100644
index 0000000..d5cccf4
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/yandex-automation/SKILL.md b/plugins/awesome-claude-skills/yandex-automation/SKILL.md
new file mode 100644
index 0000000..fcf8783
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/yelp-automation/SKILL.md b/plugins/awesome-claude-skills/yelp-automation/SKILL.md
new file mode 100644
index 0000000..091b044
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/ynab-automation/SKILL.md b/plugins/awesome-claude-skills/ynab-automation/SKILL.md
new file mode 100644
index 0000000..ddbca2c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/yousearch-automation/SKILL.md b/plugins/awesome-claude-skills/yousearch-automation/SKILL.md
new file mode 100644
index 0000000..1bbc056
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/youtube-automation/SKILL.md b/plugins/awesome-claude-skills/youtube-automation/SKILL.md
new file mode 100644
index 0000000..f30e3c6
--- /dev/null
+++ b/plugins/awesome-claude-skills/youtube-automation/SKILL.md
@@ -0,0 +1,223 @@
+---
+name: youtube-automation
+description: "Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# YouTube Automation via Rube MCP
+
+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)
+- Active YouTube connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `youtube`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `youtube`
+3. If connection is not ACTIVE, follow the returned auth link to complete Google OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Upload and Manage Videos
+
+**When to use**: User wants to upload a video or update video metadata
+
+**Tool sequence**:
+1. `YOUTUBE_UPLOAD_VIDEO` - Upload a new video [Required]
+2. `YOUTUBE_UPDATE_VIDEO` - Update title, description, tags, privacy [Optional]
+3. `YOUTUBE_UPDATE_THUMBNAIL` - Set a custom thumbnail [Optional]
+
+**Key parameters**:
+- `title`: Video title (max 100 characters)
+- `description`: Video description (max 5000 bytes)
+- `tags`: Array of keyword tags
+- `categoryId`: YouTube category ID (e.g., '22' for People & Blogs)
+- `privacyStatus`: 'public', 'private', or 'unlisted'
+- `videoFilePath`: Object with `{name, mimetype, s3key}` for the video file
+
+**Pitfalls**:
+- UPLOAD_VIDEO consumes high quota; prefer UPDATE_VIDEO for metadata-only changes
+- videoFilePath must be an object with s3key, not a raw file path or URL
+- Tags total must not exceed 500 characters including separators
+- Angle brackets `< >` in tags are automatically stripped
+- Description limit is 5000 bytes, not characters (multibyte chars count more)
+
+### 2. Search YouTube Content
+
+**When to use**: User wants to find videos, channels, or playlists
+
+**Tool sequence**:
+1. `YOUTUBE_SEARCH_YOU_TUBE` - Search for content [Required]
+2. `YOUTUBE_VIDEO_DETAILS` - Get full details for a specific video [Optional]
+3. `YOUTUBE_GET_VIDEO_DETAILS_BATCH` - Get details for multiple videos [Optional]
+
+**Key parameters**:
+- `q`: Search query (supports exact phrases, exclusions, channel handles)
+- `type`: 'video', 'channel', or 'playlist'
+- `maxResults`: Results per page (1-50)
+- `pageToken`: For pagination
+
+**Pitfalls**:
+- Search endpoint only returns 'snippet' part; use VIDEO_DETAILS for statistics
+- Search results are capped at 500 total items
+- Search has higher quota cost (100 units) vs list endpoints (1 unit)
+- BATCH video details practical limit is ~50 IDs per call; chunk larger sets
+
+### 3. Manage Playlists
+
+**When to use**: User wants to create playlists or manage playlist contents
+
+**Tool sequence**:
+1. `YOUTUBE_LIST_USER_PLAYLISTS` - List user's existing playlists [Optional]
+2. `YOUTUBE_CREATE_PLAYLIST` - Create a new playlist [Optional]
+3. `YOUTUBE_ADD_VIDEO_TO_PLAYLIST` - Add a video to a playlist [Optional]
+4. `YOUTUBE_LIST_PLAYLIST_ITEMS` - List videos in a playlist [Optional]
+
+**Key parameters**:
+- `playlistId`: Playlist ID ('PL...' for user-created, 'UU...' for uploads)
+- `part`: Resource parts to include (e.g., 'snippet,contentDetails')
+- `maxResults`: Items per page (1-50)
+- `pageToken`: Pagination token from previous response
+
+**Pitfalls**:
+- Do NOT pass channel IDs ('UC...') as playlist IDs; convert 'UC' to 'UU' for uploads
+- Large playlists require pagination via pageToken; follow nextPageToken until absent
+- items[].id is not the videoId; use items[].snippet.resourceId.videoId
+- Creating duplicate playlist names is allowed; check existing playlists first
+
+### 4. Get Channel and Video Analytics
+
+**When to use**: User wants to analyze channel performance or video metrics
+
+**Tool sequence**:
+1. `YOUTUBE_GET_CHANNEL_ID_BY_HANDLE` - Resolve a handle to channel ID [Prerequisite]
+2. `YOUTUBE_GET_CHANNEL_STATISTICS` - Get channel subscriber/view/video counts [Required]
+3. `YOUTUBE_LIST_CHANNEL_VIDEOS` - List all videos from a channel [Optional]
+4. `YOUTUBE_GET_VIDEO_DETAILS_BATCH` - Get per-video statistics [Optional]
+5. `YOUTUBE_GET_CHANNEL_ACTIVITIES` - Get recent channel activities [Optional]
+
+**Key parameters**:
+- `channelId`: Channel ID ('UC...'), handle ('@handle'), or 'me'
+- `forHandle`: Channel handle (e.g., '@Google')
+- `id`: Comma-separated video IDs for batch details
+- `parts`: Resource parts to include (e.g., 'snippet,statistics')
+
+**Pitfalls**:
+- Channel statistics are lifetime totals, not per-period
+- BATCH video details may return fewer items than requested for private/deleted videos
+- Response data may be nested under `data` or `data_preview`; parse defensively
+- contentDetails.duration uses ISO 8601 format (e.g., 'PT4M13S')
+
+### 5. Manage Subscriptions and Comments
+
+**When to use**: User wants to subscribe to channels or view video comments
+
+**Tool sequence**:
+1. `YOUTUBE_SUBSCRIBE_CHANNEL` - Subscribe to a channel [Optional]
+2. `YOUTUBE_UNSUBSCRIBE_CHANNEL` - Unsubscribe from a channel [Optional]
+3. `YOUTUBE_LIST_USER_SUBSCRIPTIONS` - List subscriptions [Optional]
+4. `YOUTUBE_LIST_COMMENT_THREADS` - List comments on a video [Optional]
+
+**Key parameters**:
+- `channelId`: Channel to subscribe/unsubscribe
+- `videoId`: Video ID for comment threads
+- `maxResults`: Results per page
+- `pageToken`: Pagination token
+
+**Pitfalls**:
+- Subscribing to an already-subscribed channel may return an error
+- Comment threads return top-level comments with up to 5 replies each
+- Comments may be disabled on some videos
+- Unsubscribe requires the subscription ID, not the channel ID
+
+## Common Patterns
+
+### Channel ID Resolution
+
+**Handle to Channel ID**:
+```
+1. Call YOUTUBE_GET_CHANNEL_ID_BY_HANDLE with '@handle'
+2. Extract channelId from response
+3. Use in subsequent channel operations
+```
+
+**Uploads Playlist**:
+```
+1. Get channel ID (starts with 'UC')
+2. Replace 'UC' prefix with 'UU' to get uploads playlist ID
+3. Use with LIST_PLAYLIST_ITEMS to enumerate all videos
+```
+
+### Pagination
+
+- Set `maxResults` (max 50 per page)
+- Check response for `nextPageToken`
+- Pass token as `pageToken` in next request
+- Continue until `nextPageToken` is absent
+
+### Batch Video Details
+
+- Collect video IDs from search or playlist listings
+- Chunk into groups of ~50 IDs
+- Call GET_VIDEO_DETAILS_BATCH per chunk
+- Merge results across chunks
+
+## Known Pitfalls
+
+**Quota Management**:
+- YouTube API has a daily quota limit (default 10,000 units)
+- Upload = 1600 units; search = 100 units; list = 1 unit
+- Prefer list endpoints over search when possible
+- Monitor quota usage to avoid hitting daily limits
+
+**ID Formats**:
+- Video IDs: 11-character alphanumeric strings
+- Channel IDs: Start with 'UC' followed by 22 characters
+- Playlist IDs: Start with 'PL' (user) or 'UU' (uploads)
+- Do not confuse channel IDs with playlist IDs
+
+**Thumbnails**:
+- Custom thumbnails require channel phone verification
+- Must be JPG, PNG, or GIF; under 2MB
+- Recommended: 1280x720 resolution (16:9 aspect ratio)
+
+**Response Parsing**:
+- Statistics values are returned as strings, not integers; cast before math
+- Duration uses ISO 8601 format (PT#H#M#S)
+- Batch responses may wrap data under different keys
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Upload video | YOUTUBE_UPLOAD_VIDEO | title, description, tags, categoryId, privacyStatus, videoFilePath |
+| Update video | YOUTUBE_UPDATE_VIDEO | video_id, title, description, tags |
+| Set thumbnail | YOUTUBE_UPDATE_THUMBNAIL | videoId, thumbnailUrl |
+| Search YouTube | YOUTUBE_SEARCH_YOU_TUBE | q, type, maxResults |
+| Video details | YOUTUBE_VIDEO_DETAILS | id, part |
+| Batch video details | YOUTUBE_GET_VIDEO_DETAILS_BATCH | id, parts |
+| List playlists | YOUTUBE_LIST_USER_PLAYLISTS | maxResults, pageToken |
+| Create playlist | YOUTUBE_CREATE_PLAYLIST | (check schema) |
+| Add to playlist | YOUTUBE_ADD_VIDEO_TO_PLAYLIST | (check schema) |
+| List playlist items | YOUTUBE_LIST_PLAYLIST_ITEMS | playlistId, maxResults |
+| Channel statistics | YOUTUBE_GET_CHANNEL_STATISTICS | id/forHandle/mine |
+| List channel videos | YOUTUBE_LIST_CHANNEL_VIDEOS | channelId, maxResults |
+| Channel ID by handle | YOUTUBE_GET_CHANNEL_ID_BY_HANDLE | channel_handle |
+| Subscribe | YOUTUBE_SUBSCRIBE_CHANNEL | channelId |
+| 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/plugins/awesome-claude-skills/zendesk-automation/SKILL.md b/plugins/awesome-claude-skills/zendesk-automation/SKILL.md
new file mode 100644
index 0000000..a9df20d
--- /dev/null
+++ b/plugins/awesome-claude-skills/zendesk-automation/SKILL.md
@@ -0,0 +1,220 @@
+---
+name: zendesk-automation
+description: "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Zendesk Automation via Rube MCP
+
+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)
+- Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`
+3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Search Tickets
+
+**When to use**: User wants to view, filter, or search support tickets
+
+**Tool sequence**:
+1. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required]
+2. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional]
+
+**Key parameters**:
+- `page`: Page number (1-based)
+- `per_page`: Results per page (max 100)
+- `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status')
+- `sort_order`: 'asc' or 'desc'
+- `ticket_id`: Ticket ID for single retrieval
+
+**Pitfalls**:
+- LIST uses `page`/`per_page` pagination, NOT offset-based; check `next_page` in response
+- Maximum 100 results per page; iterate with page numbers until `next_page` is null
+- Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'
+- Ticket comments and audits are included in GET_BY_ID but not in LIST responses
+
+### 2. Create and Update Tickets
+
+**When to use**: User wants to create new tickets or modify existing ones
+
+**Tool sequence**:
+1. `ZENDESK_SEARCH_ZENDESK_USERS` - Find requester/assignee [Prerequisite]
+2. `ZENDESK_CREATE_ZENDESK_TICKET` - Create a new ticket [Required]
+3. `ZENDESK_UPDATE_ZENDESK_TICKET` - Update ticket fields [Optional]
+4. `ZENDESK_DELETE_ZENDESK_TICKET` - Delete a ticket [Optional]
+
+**Key parameters**:
+- `subject`: Ticket subject line
+- `description`: Ticket body (for creation; becomes first comment)
+- `priority`: 'urgent', 'high', 'normal', 'low'
+- `status`: 'new', 'open', 'pending', 'hold', 'solved', 'closed'
+- `type`: 'problem', 'incident', 'question', 'task'
+- `assignee_id`: Agent user ID to assign
+- `requester_id`: Requester user ID
+- `tags`: Array of tag strings
+- `ticket_id`: Ticket ID (for update/delete)
+
+**Pitfalls**:
+- Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them
+- Use `safe_update` with `updated_stamp` to prevent concurrent modification conflicts
+- DELETE is permanent and irreversible; tickets cannot be recovered
+- `description` is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation
+- Closed tickets cannot be updated; create a follow-up ticket instead
+
+### 3. Reply to Tickets
+
+**When to use**: User wants to add comments or replies to tickets
+
+**Tool sequence**:
+1. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get current ticket state [Prerequisite]
+2. `ZENDESK_REPLY_ZENDESK_TICKET` - Add a reply/comment [Required]
+
+**Key parameters**:
+- `ticket_id`: Ticket ID to reply to
+- `body`: Reply text content
+- `public`: Boolean; true for public reply, false for internal note
+- `author_id`: Author user ID (defaults to authenticated user)
+
+**Pitfalls**:
+- Set `public: false` for internal notes visible only to agents
+- Default is public reply which sends email to requester
+- HTML is supported in body text
+- Replying can also update ticket status simultaneously
+
+### 4. Manage Users
+
+**When to use**: User wants to find or create Zendesk users (agents, end-users)
+
+**Tool sequence**:
+1. `ZENDESK_SEARCH_ZENDESK_USERS` - Search for users [Required]
+2. `ZENDESK_CREATE_ZENDESK_USER` - Create a new user [Optional]
+3. `ZENDESK_GET_ABOUT_ME` - Get authenticated user info [Optional]
+
+**Key parameters**:
+- `query`: Search string (matches name, email, phone, etc.)
+- `name`: User's full name (required for creation)
+- `email`: User's email address
+- `role`: 'end-user', 'agent', or 'admin'
+- `verified`: Whether email is verified
+
+**Pitfalls**:
+- User search is fuzzy; may return partial matches
+- Creating a user with an existing email returns the existing user (upsert behavior)
+- Agent and admin roles may require specific plan features
+
+### 5. Manage Organizations
+
+**When to use**: User wants to list, create, or manage organizations
+
+**Tool sequence**:
+1. `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` - List all organizations [Required]
+2. `ZENDESK_GET_ZENDESK_ORGANIZATION` - Get specific organization [Optional]
+3. `ZENDESK_CREATE_ZENDESK_ORGANIZATION` - Create organization [Optional]
+4. `ZENDESK_UPDATE_ZENDESK_ORGANIZATION` - Update organization [Optional]
+5. `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` - Get total count [Optional]
+
+**Key parameters**:
+- `name`: Organization name (unique, required for creation)
+- `organization_id`: Organization ID for get/update
+- `details`: Organization details text
+- `notes`: Internal notes
+- `domain_names`: Array of associated domains
+- `tags`: Array of tag strings
+
+**Pitfalls**:
+- Organization names must be unique; duplicate names cause creation errors
+- Tags on UPDATE REPLACE existing tags (same behavior as tickets)
+- Domain names can be used for automatic user association
+
+## Common Patterns
+
+### Pagination
+
+**List endpoints**:
+- Use `page` (1-based) and `per_page` (max 100)
+- Check `next_page` URL in response; null means last page
+- `count` field gives total results
+
+### Ticket Lifecycle
+
+```
+new -> open -> pending -> solved -> closed
+ | ^
+ v |
+ hold --------+
+```
+
+- `new`: Unassigned ticket
+- `open`: Assigned, being worked on
+- `pending`: Waiting for customer response
+- `hold`: Waiting for internal action
+- `solved`: Resolved, can be reopened
+- `closed`: Permanently closed, cannot be modified
+
+### User Search for Assignment
+
+```
+1. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)
+2. Extract user ID from results
+3. Use user ID as assignee_id in ticket creation/update
+```
+
+## Known Pitfalls
+
+**Tags Behavior**:
+- Tags on update REPLACE all existing tags
+- Always fetch current tags first and merge before updating
+- Tags are lowercase, no spaces (use underscores)
+
+**Safe Updates**:
+- Use `safe_update: true` with `updated_stamp` (ISO 8601) to prevent conflicts
+- Returns 409 if ticket was modified since the stamp
+
+**Deletion**:
+- Ticket deletion is permanent and irreversible
+- Consider setting status to 'closed' instead of deleting
+- Deleted tickets cannot be recovered via API
+
+**Rate Limits**:
+- Default: 400 requests per minute
+- Varies by plan tier
+- 429 responses include Retry-After header
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List tickets | ZENDESK_LIST_ZENDESK_TICKETS | page, per_page, sort_by |
+| Get ticket | ZENDESK_GET_ZENDESK_TICKET_BY_ID | ticket_id |
+| Create ticket | ZENDESK_CREATE_ZENDESK_TICKET | subject, description, priority |
+| Update ticket | ZENDESK_UPDATE_ZENDESK_TICKET | ticket_id, status, tags |
+| Reply to ticket | ZENDESK_REPLY_ZENDESK_TICKET | ticket_id, body, public |
+| Delete ticket | ZENDESK_DELETE_ZENDESK_TICKET | ticket_id |
+| Search users | ZENDESK_SEARCH_ZENDESK_USERS | query |
+| Create user | ZENDESK_CREATE_ZENDESK_USER | name, email |
+| My profile | ZENDESK_GET_ABOUT_ME | (none) |
+| List orgs | ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS | page, per_page |
+| Get org | ZENDESK_GET_ZENDESK_ORGANIZATION | organization_id |
+| 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/plugins/awesome-claude-skills/zenrows-automation/SKILL.md b/plugins/awesome-claude-skills/zenrows-automation/SKILL.md
new file mode 100644
index 0000000..0496d94
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zenserp-automation/SKILL.md b/plugins/awesome-claude-skills/zenserp-automation/SKILL.md
new file mode 100644
index 0000000..22fc8fc
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zeplin-automation/SKILL.md b/plugins/awesome-claude-skills/zeplin-automation/SKILL.md
new file mode 100644
index 0000000..d2f9250
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zerobounce-automation/SKILL.md b/plugins/awesome-claude-skills/zerobounce-automation/SKILL.md
new file mode 100644
index 0000000..a75677d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-automation/SKILL.md
new file mode 100644
index 0000000..44a70f5
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho-bigin-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-bigin-automation/SKILL.md
new file mode 100644
index 0000000..32fdb8a
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho-books-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-books-automation/SKILL.md
new file mode 100644
index 0000000..32395b1
--- /dev/null
+++ b/plugins/awesome-claude-skills/zoho-books-automation/SKILL.md
@@ -0,0 +1,200 @@
+---
+name: Zoho Books Automation
+description: "Automate Zoho Books accounting workflows including invoice creation, bill management, contact lookup, payment tracking, and multi-organization support through natural language commands"
+requires:
+ mcp:
+ - rube
+---
+
+# Zoho Books Automation
+
+Automate Zoho Books accounting workflows -- create and manage invoices, track bills and payments, look up contacts, export PDFs, and handle multi-organization setups -- all through natural language.
+
+**Toolkit docs:** [composio.dev/toolkits/zoho_books](https://composio.dev/toolkits/zoho_books)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Connect your Zoho Books account when prompted (OAuth flow via Composio)
+3. Start issuing natural language commands for Zoho Books automation
+
+---
+
+## Core Workflows
+
+### 1. Discover Organizations
+
+Retrieve all organizations for the authenticated user. This is a prerequisite since `organization_id` is required by nearly every other endpoint.
+
+**Tool:** `ZOHO_BOOKS_LIST_ORGANIZATIONS`
+
+No parameters required. Returns organization IDs, names, and metadata.
+
+> Always call this first to obtain the `organization_id` needed by all other Zoho Books tools.
+
+Example prompt:
+> "List my Zoho Books organizations"
+
+---
+
+### 2. Create and Manage Invoices
+
+Create invoices with line items, manage existing invoices, and export them as PDFs.
+
+**Create:** `ZOHO_BOOKS_CREATE_INVOICE`
+
+Key parameters:
+- `organization_id` -- target organization (required)
+- `customer_id` -- customer to bill (required)
+- `line_items` -- array of line items (required), each with:
+ - `item_id` or `name` -- reference existing item or create ad-hoc line
+ - `quantity`, `rate` -- amount details
+ - `description`, `tax_id`, `discount` -- optional details
+- `date` / `due_date` -- dates in `YYYY-MM-DD` format
+- `invoice_number` -- custom number (set `ignore_auto_number_generation=true`)
+- `discount` / `discount_type` -- invoice-level discount (`entity_level` or `item_level`)
+- `notes` / `terms` -- printed on the invoice
+- `send` -- email the invoice immediately after creation
+- `payment_terms` -- number of days for payment
+
+**List:** `ZOHO_BOOKS_LIST_INVOICES`
+
+Key parameters:
+- `organization_id` (required)
+- `status` -- `sent`, `draft`, `overdue`, `paid`, `void`, `unpaid`, `partially_paid`, `viewed`
+- `customer_id` / `customer_name` -- filter by customer
+- `date_start` / `date_end` -- date range filter (`YYYY-MM-DD`)
+- `search_text` -- search invoice number, reference, or customer name
+- `sort_column` / `sort_order` -- sort by `date`, `due_date`, `total`, `balance`, etc.
+- `page` / `per_page` -- pagination (max 200 per page)
+
+**Get details:** `ZOHO_BOOKS_GET_INVOICE` -- fetch by `invoice_id` with `accept` format: `json`, `pdf`, or `html`
+
+**Delete:** `ZOHO_BOOKS_DELETE_INVOICE` -- remove by `invoice_id`
+
+**Bulk export:** `ZOHO_BOOKS_BULK_EXPORT_INVOICES_PDF` -- merge up to 25 invoices into a single PDF
+
+**Bulk print:** `ZOHO_BOOKS_BULK_PRINT_INVOICES` -- generate a combined print-ready PDF for up to 25 invoices
+
+Example prompt:
+> "Create an invoice for customer 1234567890 with 2 line items: 10 units of Widget A at $25 each, and 5 units of Widget B at $50 each, due in 30 days"
+
+---
+
+### 3. Track and Manage Bills
+
+List, view, and update vendor bills with comprehensive filtering.
+
+**List:** `ZOHO_BOOKS_LIST_BILLS`
+
+Key parameters:
+- `organization_id` (required)
+- `status` -- `paid`, `open`, `overdue`, `void`, `partially_paid`
+- `vendor_id` / `vendor_name_contains` -- filter by vendor
+- `bill_number` / `bill_number_contains` -- filter by bill number
+- `date_start` / `date_end` -- date range filter
+- `total_greater_than` / `total_less_than` -- amount range filters
+- `sort_column` / `sort_order` -- sort by `vendor_name`, `bill_number`, `date`, `due_date`, `total`, etc.
+- `page` / `per_page` -- pagination (max 200)
+
+**Get details:** `ZOHO_BOOKS_GET_BILL` -- fetch full bill by `bill_id` and `organization_id`
+
+**Update:** `ZOHO_BOOKS_UPDATE_BILL` -- modify existing bill (requires `bill_id`, `organization_id`, `vendor_id`, `bill_number`)
+
+Example prompt:
+> "List all overdue bills for my organization, sorted by due date"
+
+---
+
+### 4. Look Up Contacts
+
+Search and filter contacts (customers and vendors) for use in invoices and bills.
+
+**Tool:** `ZOHO_BOOKS_LIST_CONTACTS`
+
+Key parameters:
+- `organization_id` (required)
+- `contact_type` -- `customer` or `vendor`
+- `contact_name_contains` / `contact_name_startswith` -- name filters
+- `email_contains` / `email_startswith` -- email filters
+- `company_name_contains` -- company name filter
+- `filter_by` -- status filter: `Status.Active`, `Status.Inactive`, `Status.Duplicate`, etc.
+- `search_text` -- search by contact name or notes (max 100 chars)
+- `sort_column` -- sort by `contact_name`, `email`, `outstanding_receivable_amount`, `created_time`, etc.
+- `page` / `per_page` -- pagination (max 200)
+
+Example prompt:
+> "Find all active customers whose company name contains 'Acme'"
+
+---
+
+### 5. Track Invoice Payments
+
+List all payments recorded against a specific invoice.
+
+**Tool:** `ZOHO_BOOKS_LIST_INVOICE_PAYMENTS`
+
+Key parameters:
+- `invoice_id` -- the invoice to check (required)
+- `organization_id` -- the organization (required)
+
+Returns all payment transactions applied to the invoice including amounts, dates, and payment methods.
+
+Example prompt:
+> "Show all payments recorded against invoice 451025000000123045"
+
+---
+
+### 6. Full Invoicing Workflow
+
+Combine tools for end-to-end invoice management:
+
+1. **Organization**: `ZOHO_BOOKS_LIST_ORGANIZATIONS` -- get `organization_id`
+2. **Contacts**: `ZOHO_BOOKS_LIST_CONTACTS` -- find or verify `customer_id`
+3. **Create**: `ZOHO_BOOKS_CREATE_INVOICE` -- create invoice with line items
+4. **Review**: `ZOHO_BOOKS_GET_INVOICE` -- fetch invoice details or PDF
+5. **Track**: `ZOHO_BOOKS_LIST_INVOICE_PAYMENTS` -- monitor payment status
+6. **Export**: `ZOHO_BOOKS_BULK_EXPORT_INVOICES_PDF` -- batch export for records
+
+Example prompt:
+> "Find the customer ID for 'Acme Corp', create an invoice for them with consulting services, and then get the PDF"
+
+---
+
+## Known Pitfalls
+
+| Pitfall | Details |
+|---------|---------|
+| Organization ID always required | Nearly every endpoint requires `organization_id` -- always call `ZOHO_BOOKS_LIST_ORGANIZATIONS` first |
+| Line items required for invoices | `ZOHO_BOOKS_CREATE_INVOICE` requires at least one line item with either `item_id` or `name` |
+| Invoice ID format | Use the numeric `invoice_id` from the invoice object (e.g., `7472322000000264123`), not the encoded ID from `invoice_url` |
+| Bulk limits | Both `ZOHO_BOOKS_BULK_EXPORT_INVOICES_PDF` and `ZOHO_BOOKS_BULK_PRINT_INVOICES` accept a maximum of 25 invoice IDs |
+| Pagination max 200 | All list endpoints cap at 200 records per page -- iterate pages for complete results |
+| Bill update requires all fields | `ZOHO_BOOKS_UPDATE_BILL` requires `bill_id`, `organization_id`, `vendor_id`, and `bill_number` even for partial updates |
+| Date format | All date parameters use `YYYY-MM-DD` format |
+| response_option undocumented | `ZOHO_BOOKS_LIST_INVOICES` has an undocumented `response_option` parameter (0=full, 1=full+totals, 2=counts only) that may change without notice |
+
+---
+
+## Quick Reference
+
+| Action | Tool Slug | Key Params |
+|--------|-----------|------------|
+| List organizations | `ZOHO_BOOKS_LIST_ORGANIZATIONS` | (none) |
+| Create invoice | `ZOHO_BOOKS_CREATE_INVOICE` | `organization_id`, `customer_id`, `line_items` |
+| List invoices | `ZOHO_BOOKS_LIST_INVOICES` | `organization_id`, `status`, `date_start` |
+| Get invoice | `ZOHO_BOOKS_GET_INVOICE` | `invoice_id`, `organization_id`, `accept` |
+| Delete invoice | `ZOHO_BOOKS_DELETE_INVOICE` | `invoice_id`, `organization_id` |
+| Bulk export PDF | `ZOHO_BOOKS_BULK_EXPORT_INVOICES_PDF` | `organization_id`, `invoice_ids` |
+| Bulk print | `ZOHO_BOOKS_BULK_PRINT_INVOICES` | `organization_id`, `invoice_ids` |
+| List bills | `ZOHO_BOOKS_LIST_BILLS` | `organization_id`, `status`, `vendor_id` |
+| Get bill | `ZOHO_BOOKS_GET_BILL` | `bill_id`, `organization_id` |
+| Update bill | `ZOHO_BOOKS_UPDATE_BILL` | `bill_id`, `organization_id`, `vendor_id` |
+| List contacts | `ZOHO_BOOKS_LIST_CONTACTS` | `organization_id`, `contact_type`, `search_text` |
+| List payments | `ZOHO_BOOKS_LIST_INVOICE_PAYMENTS` | `invoice_id`, `organization_id` |
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/zoho-crm-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-crm-automation/SKILL.md
new file mode 100644
index 0000000..4a5c06f
--- /dev/null
+++ b/plugins/awesome-claude-skills/zoho-crm-automation/SKILL.md
@@ -0,0 +1,211 @@
+---
+name: zoho-crm-automation
+description: "Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas."
+requires:
+ mcp: [rube]
+---
+
+# Zoho CRM Automation via Rube MCP
+
+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)
+- Active Zoho CRM 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 Zoho OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search and Retrieve Records
+
+**When to use**: User wants to find specific CRM records by criteria
+
+**Tool sequence**:
+1. `ZOHO_LIST_MODULES` - List available CRM modules [Prerequisite]
+2. `ZOHO_GET_MODULE_FIELDS` - Get field definitions for a module [Optional]
+3. `ZOHO_SEARCH_ZOHO_RECORDS` - Search records by criteria [Required]
+4. `ZOHO_GET_ZOHO_RECORDS` - Get records from a module [Alternative]
+
+**Key parameters**:
+- `module`: Module name (e.g., 'Leads', 'Contacts', 'Deals', 'Accounts')
+- `criteria`: Search criteria string (e.g., 'Email:equals:john@example.com')
+- `fields`: Comma-separated list of fields to return
+- `per_page`: Number of records per page
+- `page`: Page number for pagination
+
+**Pitfalls**:
+- Module names are case-sensitive (e.g., 'Leads' not 'leads')
+- Search criteria uses specific syntax: 'Field:operator:value'
+- Supported operators: equals, starts_with, contains, not_equal, greater_than, less_than
+- Complex criteria use parentheses and AND/OR: '(Email:equals:john@example.com)AND(Last_Name:equals:Doe)'
+- GET_ZOHO_RECORDS returns all records with optional filtering; SEARCH is for targeted lookups
+
+### 2. Create Records
+
+**When to use**: User wants to add new leads, contacts, deals, or other CRM records
+
+**Tool sequence**:
+1. `ZOHO_GET_MODULE_FIELDS` - Get required fields for the module [Prerequisite]
+2. `ZOHO_CREATE_ZOHO_RECORD` - Create a new record [Required]
+
+**Key parameters**:
+- `module`: Target module name (e.g., 'Leads', 'Contacts')
+- `data`: Record data object with field-value pairs
+- Required fields vary by module (e.g., Last_Name for Contacts)
+
+**Pitfalls**:
+- Each module has mandatory fields; use GET_MODULE_FIELDS to identify them
+- Field names use underscores (e.g., 'Last_Name', 'Email', 'Phone')
+- Lookup fields require the related record ID, not the name
+- Date fields must use 'yyyy-MM-dd' format
+- Creating duplicates is allowed unless duplicate check rules are configured
+
+### 3. Update Records
+
+**When to use**: User wants to modify existing CRM records
+
+**Tool sequence**:
+1. `ZOHO_SEARCH_ZOHO_RECORDS` - Find the record to update [Prerequisite]
+2. `ZOHO_UPDATE_ZOHO_RECORD` - Update the record [Required]
+
+**Key parameters**:
+- `module`: Module name
+- `record_id`: ID of the record to update
+- `data`: Object with fields to update (only changed fields needed)
+
+**Pitfalls**:
+- record_id must be the Zoho record ID (numeric string)
+- Only provide fields that need to change; other fields are preserved
+- Read-only and system fields cannot be updated
+- Lookup field updates require the related record ID
+
+### 4. Convert Leads
+
+**When to use**: User wants to convert a lead into a contact, account, and/or deal
+
+**Tool sequence**:
+1. `ZOHO_SEARCH_ZOHO_RECORDS` - Find the lead to convert [Prerequisite]
+2. `ZOHO_CONVERT_ZOHO_LEAD` - Convert the lead [Required]
+
+**Key parameters**:
+- `lead_id`: ID of the lead to convert
+- `deal`: Deal details if creating a deal during conversion
+- `account`: Account details for the conversion
+- `contact`: Contact details for the conversion
+
+**Pitfalls**:
+- Lead conversion is irreversible; the lead record is removed from the Leads module
+- Conversion can create up to three records: Contact, Account, and Deal
+- Existing account matching may occur based on company name
+- Custom field mappings between Lead and Contact/Account/Deal modules affect the outcome
+
+### 5. Manage Tags and Related Records
+
+**When to use**: User wants to tag records or manage relationships between records
+
+**Tool sequence**:
+1. `ZOHO_CREATE_ZOHO_TAG` - Create a new tag [Optional]
+2. `ZOHO_UPDATE_RELATED_RECORDS` - Update related/linked records [Optional]
+
+**Key parameters**:
+- `module`: Module for the tag
+- `tag_name`: Name of the tag
+- `record_id`: Parent record ID (for related records)
+- `related_module`: Module of the related record
+- `data`: Related record data to update
+
+**Pitfalls**:
+- Tags are module-specific; a tag created for Leads is not available in Contacts
+- Related records require both the parent record ID and the related module
+- Tag names must be unique within a module
+- Bulk tag operations may hit rate limits
+
+## Common Patterns
+
+### Module and Field Discovery
+
+```
+1. Call ZOHO_LIST_MODULES to get all available modules
+2. Call ZOHO_GET_MODULE_FIELDS with module name
+3. Identify required fields, field types, and picklist values
+4. Use field API names (not display labels) in data objects
+```
+
+### Search Criteria Syntax
+
+**Simple search**:
+```
+criteria: '(Email:equals:john@example.com)'
+```
+
+**Combined criteria**:
+```
+criteria: '((Last_Name:equals:Doe)AND(Email:contains:example.com))'
+```
+
+**Supported operators**:
+- `equals`, `not_equal`
+- `starts_with`, `contains`
+- `greater_than`, `less_than`, `greater_equal`, `less_equal`
+- `between` (for dates/numbers)
+
+### Pagination
+
+- Set `per_page` (max 200) and `page` starting at 1
+- Check response `info.more_records` flag
+- Increment page until more_records is false
+- Total count available in response info
+
+## Known Pitfalls
+
+**Field Names**:
+- Use API names, not display labels (e.g., 'Last_Name' not 'Last Name')
+- Custom fields have API names like 'Custom_Field1' or user-defined names
+- Picklist values must match exactly (case-sensitive)
+
+**Rate Limits**:
+- API call limits depend on your Zoho CRM plan
+- Free plan: 5000 API calls/day; Enterprise: 25000+/day
+- Implement delays between bulk operations
+- Monitor 429 responses and respect rate limit headers
+
+**Data Formats**:
+- Dates: 'yyyy-MM-dd' format
+- DateTime: 'yyyy-MM-ddTHH:mm:ss+HH:mm' format
+- Currency: Numeric values without formatting
+- Phone: String values (no specific format enforced)
+
+**Module Access**:
+- Access depends on user role and profile permissions
+- Some modules may be hidden or restricted in your CRM setup
+- Custom modules have custom API names
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List modules | ZOHO_LIST_MODULES | (none) |
+| Get module fields | ZOHO_GET_MODULE_FIELDS | module |
+| Search records | ZOHO_SEARCH_ZOHO_RECORDS | module, criteria |
+| Get records | ZOHO_GET_ZOHO_RECORDS | module, fields, per_page, page |
+| Create record | ZOHO_CREATE_ZOHO_RECORD | module, data |
+| Update record | ZOHO_UPDATE_ZOHO_RECORD | module, record_id, data |
+| 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/plugins/awesome-claude-skills/zoho-desk-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-desk-automation/SKILL.md
new file mode 100644
index 0000000..2e17b62
--- /dev/null
+++ b/plugins/awesome-claude-skills/zoho-desk-automation/SKILL.md
@@ -0,0 +1,57 @@
+---
+name: Zoho Desk Automation
+description: "Zoho Desk automation via Rube MCP -- toolkit not currently available in Composio; no ZOHO_DESK_ tools found"
+requires:
+ mcp:
+ - rube
+---
+
+# Zoho Desk Automation
+
+> **Status: Toolkit Not Available** -- RUBE_SEARCH_TOOLS returned no `zoho_desk`-specific tools. The Zoho Desk toolkit is not currently available in Composio's tool catalog. Searches returned tools from unrelated helpdesk and CRM toolkits instead.
+
+**Toolkit docs:** [composio.dev/toolkits/zoho_desk](https://composio.dev/toolkits/zoho_desk)
+
+---
+
+## Setup
+
+1. Add the Rube MCP server to your environment: `https://rube.app/mcp`
+2. Check availability by calling `RUBE_SEARCH_TOOLS` with Zoho Desk-related queries
+3. If `ZOHO_DESK_*` tools appear in the future, connect via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho_desk`
+
+---
+
+## Current Status
+
+As of the last tool discovery scan, no `ZOHO_DESK_*` tool slugs were returned by RUBE_SEARCH_TOOLS. Queries for Zoho Desk ticket management, contacts, agents, and departments all returned tools from other toolkits:
+
+- Ticket creation queries returned **Freshdesk** (`FRESHDESK_CREATE_TICKET`), **HubSpot** (`HUBSPOT_CREATE_TICKET`), and **Zendesk** (`ZENDESK_CREATE_ZENDESK_TICKET`) tools
+- Contact listing queries returned **Zoho Invoice** (`ZOHO_INVOICE_LIST_CONTACTS`) tools
+- Agent/department queries returned **Zoho CRM** (`ZOHO_GET_ZOHO_USERS`) tools
+
+This indicates the `zoho_desk` toolkit either has no tools registered or is not yet integrated into the Composio platform.
+
+---
+
+## Alternatives
+
+If you need helpdesk and support ticket automation, consider these available toolkits:
+
+| Need | Alternative Toolkit | Example Tools |
+|------|-------------------|---------------|
+| Ticket management | Freshdesk | `FRESHDESK_CREATE_TICKET`, `FRESHDESK_UPDATE_TICKET` |
+| Ticket management | Zendesk | `ZENDESK_CREATE_ZENDESK_TICKET` |
+| Ticket management | HubSpot | `HUBSPOT_CREATE_TICKET`, `HUBSPOT_LIST_TICKETS` |
+| CRM records | Zoho CRM | `ZOHO_CREATE_ZOHO_RECORD`, `ZOHO_GET_ZOHO_USERS` |
+| Contact management | Zoho Invoice | `ZOHO_INVOICE_LIST_CONTACTS` |
+
+---
+
+## When Tools Become Available
+
+Once Zoho Desk tools are added to Composio, this skill should be updated with real tool slugs, schemas, and pitfalls following the same pattern as other automation skills in this collection.
+
+---
+
+*Powered by [Composio](https://composio.dev)*
diff --git a/plugins/awesome-claude-skills/zoho-inventory-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-inventory-automation/SKILL.md
new file mode 100644
index 0000000..3400c51
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho-invoice-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-invoice-automation/SKILL.md
new file mode 100644
index 0000000..7e18105
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho-mail-automation/SKILL.md b/plugins/awesome-claude-skills/zoho-mail-automation/SKILL.md
new file mode 100644
index 0000000..7934668
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho_bigin-automation/SKILL.md b/plugins/awesome-claude-skills/zoho_bigin-automation/SKILL.md
new file mode 100644
index 0000000..12b2cdd
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho_books-automation/SKILL.md b/plugins/awesome-claude-skills/zoho_books-automation/SKILL.md
new file mode 100644
index 0000000..b257e28
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho_desk-automation/SKILL.md b/plugins/awesome-claude-skills/zoho_desk-automation/SKILL.md
new file mode 100644
index 0000000..53bfc03
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho_inventory-automation/SKILL.md b/plugins/awesome-claude-skills/zoho_inventory-automation/SKILL.md
new file mode 100644
index 0000000..0941d6c
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho_invoice-automation/SKILL.md b/plugins/awesome-claude-skills/zoho_invoice-automation/SKILL.md
new file mode 100644
index 0000000..d8a4875
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoho_mail-automation/SKILL.md b/plugins/awesome-claude-skills/zoho_mail-automation/SKILL.md
new file mode 100644
index 0000000..bb9b6da
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zoom-automation/SKILL.md b/plugins/awesome-claude-skills/zoom-automation/SKILL.md
new file mode 100644
index 0000000..80b12d7
--- /dev/null
+++ b/plugins/awesome-claude-skills/zoom-automation/SKILL.md
@@ -0,0 +1,222 @@
+---
+name: zoom-automation
+description: Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
+requires:
+ mcp: [rube]
+---
+
+# Zoom Automation via Rube MCP
+
+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)
+- Active Zoom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoom`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+- Most features require a paid Zoom account (Pro plan or higher)
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `zoom`
+3. If connection is not ACTIVE, follow the returned auth link to complete Zoom OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Schedule Meetings
+
+**When to use**: User wants to create a new Zoom meeting with specific time, duration, and settings
+
+**Tool sequence**:
+1. `ZOOM_GET_USER` - Verify authenticated user and check license type [Prerequisite]
+2. `ZOOM_CREATE_A_MEETING` - Create the meeting with topic, time, duration, and settings [Required]
+3. `ZOOM_GET_A_MEETING` - Retrieve full meeting details including join_url [Optional]
+4. `ZOOM_UPDATE_A_MEETING` - Modify meeting settings or reschedule [Optional]
+5. `ZOOM_ADD_A_MEETING_REGISTRANT` - Register participants for registration-enabled meetings [Optional]
+
+**Key parameters**:
+- `userId`: Always use `"me"` for user-level apps
+- `topic`: Meeting subject line
+- `type`: `1` (instant), `2` (scheduled), `3` (recurring no fixed time), `8` (recurring fixed time)
+- `start_time`: ISO 8601 format (`yyyy-MM-ddTHH:mm:ssZ` for UTC or `yyyy-MM-ddTHH:mm:ss` with timezone field)
+- `timezone`: Timezone ID (e.g., `"America/New_York"`)
+- `duration`: Duration in minutes
+- `settings__auto_recording`: `"none"`, `"local"`, or `"cloud"`
+- `settings__waiting_room`: Boolean to enable waiting room
+- `settings__join_before_host`: Boolean (disabled when waiting room is enabled)
+- `settings__meeting_invitees`: Array of invitee objects with email addresses
+
+**Pitfalls**:
+- `start_time` must be in the future; Zoom stores and returns times in UTC regardless of input timezone
+- If no `start_time` is set for type `2`, it becomes an instant meeting that expires after 30 days
+- The `join_url` for participants and `start_url` for host come from the create response - persist these
+- `start_url` expires in 2 hours (or 90 days for `custCreate` users)
+- Meeting creation is rate-limited to 100 requests/day
+- Setting names use double underscores for nesting (e.g., `settings__host_video`)
+
+### 2. List and Manage Meetings
+
+**When to use**: User wants to view upcoming, live, or past meetings
+
+**Tool sequence**:
+1. `ZOOM_LIST_MEETINGS` - List meetings by type (scheduled, live, upcoming, previous) [Required]
+2. `ZOOM_GET_A_MEETING` - Get detailed info for a specific meeting [Optional]
+3. `ZOOM_UPDATE_A_MEETING` - Modify meeting details [Optional]
+
+**Key parameters**:
+- `userId`: Use `"me"` for authenticated user
+- `type`: `"scheduled"` (default), `"live"`, `"upcoming"`, `"upcoming_meetings"`, `"previous_meetings"`
+- `page_size`: Records per page (default 30)
+- `next_page_token`: Pagination token from previous response
+- `from` / `to`: Date range filters
+
+**Pitfalls**:
+- `ZOOM_LIST_MEETINGS` excludes instant meetings and only shows unexpired scheduled meetings
+- For past meetings, use `type: "previous_meetings"`
+- Pagination: always follow `next_page_token` until empty to get complete results
+- Token expiration: `next_page_token` expires after 15 minutes
+- Meeting IDs can exceed 10 digits; store as long integers, not standard integers
+
+### 3. Manage Recordings
+
+**When to use**: User wants to list, retrieve, or delete cloud recordings
+
+**Tool sequence**:
+1. `ZOOM_LIST_ALL_RECORDINGS` - List all cloud recordings for a user within a date range [Required]
+2. `ZOOM_GET_MEETING_RECORDINGS` - Get recordings for a specific meeting [Optional]
+3. `ZOOM_DELETE_MEETING_RECORDINGS` - Move recordings to trash or permanently delete [Optional]
+4. `ZOOM_LIST_ARCHIVED_FILES` - List archived meeting/webinar files [Optional]
+
+**Key parameters**:
+- `userId`: Use `"me"` for authenticated user
+- `from` / `to`: Date range in `yyyy-mm-dd` format (max 1 month range)
+- `meetingId`: Meeting ID or UUID for specific recording retrieval
+- `action`: `"trash"` (recoverable) or `"delete"` (permanent) for deletion
+- `include_fields`: Set to `"download_access_token"` to get JWT for downloading recordings
+- `trash`: Set `true` to list recordings from trash
+
+**Pitfalls**:
+- Date range maximum is 1 month; API auto-adjusts `from` if range exceeds this
+- Cloud Recording must be enabled on the account
+- UUIDs starting with `/` or containing `//` must be double URL-encoded
+- `ZOOM_DELETE_MEETING_RECORDINGS` defaults to `"trash"` action (recoverable); `"delete"` is permanent
+- Download URLs require the OAuth token in the Authorization header for passcode-protected recordings
+- Requires Pro plan or higher
+
+### 4. Get Meeting Participants and Reports
+
+**When to use**: User wants to see who attended a past meeting or get usage statistics
+
+**Tool sequence**:
+1. `ZOOM_GET_PAST_MEETING_PARTICIPANTS` - List attendees of a completed meeting [Required]
+2. `ZOOM_GET_A_MEETING` - Get meeting details and registration info for upcoming meetings [Optional]
+3. `ZOOM_GET_DAILY_USAGE_REPORT` - Get daily usage statistics (meetings, participants, minutes) [Optional]
+4. `ZOOM_GET_A_MEETING_SUMMARY` - Get AI-generated meeting summary [Optional]
+
+**Key parameters**:
+- `meetingId`: Meeting ID (latest instance) or UUID (specific occurrence)
+- `page_size`: Records per page (default 30)
+- `next_page_token`: Pagination token for large participant lists
+
+**Pitfalls**:
+- `ZOOM_GET_PAST_MEETING_PARTICIPANTS` only works for completed meetings on paid plans
+- Solo meetings (no other participants) return empty results
+- UUID encoding: UUIDs starting with `/` or containing `//` must be double-encoded
+- Always paginate with `next_page_token` until empty to avoid dropping attendees
+- `ZOOM_GET_A_MEETING_SUMMARY` requires a paid plan with AI Companion enabled; free accounts get 400 errors
+- `ZOOM_GET_DAILY_USAGE_REPORT` has a Heavy rate limit; avoid frequent calls
+
+### 5. Manage Webinars
+
+**When to use**: User wants to list webinars or register participants for webinars
+
+**Tool sequence**:
+1. `ZOOM_LIST_WEBINARS` - List scheduled or upcoming webinars [Required]
+2. `ZOOM_GET_A_WEBINAR` - Get detailed webinar information [Optional]
+3. `ZOOM_ADD_A_WEBINAR_REGISTRANT` - Register a participant for a webinar [Optional]
+
+**Key parameters**:
+- `userId`: Use `"me"` for authenticated user
+- `type`: `"scheduled"` (default) or `"upcoming"`
+- `page_size`: Records per page (default 30)
+- `next_page_token`: Pagination token
+
+**Pitfalls**:
+- Webinar features require Pro plan or higher with Webinar add-on
+- Free/basic accounts cannot use webinar tools
+- Only shows unexpired webinars
+- Registration must be enabled on the webinar for `ZOOM_ADD_A_WEBINAR_REGISTRANT` to work
+
+## Common Patterns
+
+### ID Resolution
+- **User ID**: Always use `"me"` for user-level apps to refer to the authenticated user
+- **Meeting ID**: Numeric ID (store as long integer); use for latest instance
+- **Meeting UUID**: Use for specific occurrence of recurring meetings; double-encode if starts with `/` or contains `//`
+- **Occurrence ID**: Use with recurring meetings to target a specific occurrence
+
+### Pagination
+Most Zoom list endpoints use token-based pagination:
+- Follow `next_page_token` until it is empty or missing
+- Token expires after 15 minutes
+- Set explicit `page_size` (default 30, varies by endpoint)
+- Do not use `page_number` (deprecated on many endpoints)
+
+### Time Handling
+- Zoom stores all times in UTC internally
+- Provide `timezone` field alongside `start_time` for local time input
+- Use ISO 8601 format: `yyyy-MM-ddTHH:mm:ssZ` (UTC) or `yyyy-MM-ddTHH:mm:ss` (with timezone field)
+- Date-only fields use `yyyy-mm-dd` format
+
+## Known Pitfalls
+
+### Plan Requirements
+- Most recording and participant features require Pro plan or higher
+- Webinar features require Webinar add-on
+- AI meeting summaries require AI Companion feature enabled
+- Archived files require "Meeting and Webinar Archiving" enabled by Zoom Support
+
+### Rate Limits
+- Meeting creation: 100 requests/day, 100 updates per meeting in 24 hours
+- `ZOOM_GET_PAST_MEETING_PARTICIPANTS`: Moderate throttle; add delays for batch processing
+- `ZOOM_GET_DAILY_USAGE_REPORT`: Heavy rate limit
+- `ZOOM_GET_A_MEETING`, `ZOOM_GET_MEETING_RECORDINGS`: Light rate limit
+- `ZOOM_LIST_MEETINGS`, `ZOOM_LIST_ALL_RECORDINGS`: Medium rate limit
+
+### Parameter Quirks
+- Nested settings use double underscore notation (e.g., `settings__waiting_room`)
+- `start_url` expires in 2 hours; renew via API if needed
+- `join_before_host` is automatically disabled when `waiting_room` is `true`
+- Recurring meeting fields (`recurrence__*`) only apply to type `3` and `8`
+- `password` field has max 10 characters with alphanumeric and `@`, `-`, `_`, `*` only
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create meeting | `ZOOM_CREATE_A_MEETING` | `userId`, `topic`, `start_time`, `type` |
+| Get meeting details | `ZOOM_GET_A_MEETING` | `meetingId` |
+| Update meeting | `ZOOM_UPDATE_A_MEETING` | `meetingId`, fields to update |
+| List meetings | `ZOOM_LIST_MEETINGS` | `userId`, `type`, `page_size` |
+| Get user info | `ZOOM_GET_USER` | `userId` |
+| List recordings | `ZOOM_LIST_ALL_RECORDINGS` | `userId`, `from`, `to` |
+| Get recording | `ZOOM_GET_MEETING_RECORDINGS` | `meetingId` |
+| Delete recording | `ZOOM_DELETE_MEETING_RECORDINGS` | `meetingId`, `action` |
+| Past participants | `ZOOM_GET_PAST_MEETING_PARTICIPANTS` | `meetingId`, `page_size` |
+| Daily usage report | `ZOOM_GET_DAILY_USAGE_REPORT` | date params |
+| Meeting summary | `ZOOM_GET_A_MEETING_SUMMARY` | `meetingId` |
+| List webinars | `ZOOM_LIST_WEBINARS` | `userId`, `type` |
+| Get webinar | `ZOOM_GET_A_WEBINAR` | webinar ID |
+| 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/plugins/awesome-claude-skills/zoominfo-automation/SKILL.md b/plugins/awesome-claude-skills/zoominfo-automation/SKILL.md
new file mode 100644
index 0000000..5504e7d
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zylvie-automation/SKILL.md b/plugins/awesome-claude-skills/zylvie-automation/SKILL.md
new file mode 100644
index 0000000..5cc2f7f
--- /dev/null
+++ b/plugins/awesome-claude-skills/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/plugins/awesome-claude-skills/zyte-api-automation/SKILL.md b/plugins/awesome-claude-skills/zyte-api-automation/SKILL.md
new file mode 100644
index 0000000..a3f8e24
--- /dev/null
+++ b/plugins/awesome-claude-skills/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)*