@ngxtm/devkit 3.15.0 → 3.17.0

package/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]
+risk: unknown
+source: community
+---
+
+# Zendesk Automation via Rube MCP
+
+Automate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.
+
+## 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) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/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]
+risk: unknown
+source: community
+---
+
+# Zoho CRM Automation via Rube MCP
+
+Automate Zoho CRM operations through Composio's Zoho toolkit via Rube MCP.
+
+## 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 |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/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]
+risk: unknown
+source: community
+---
+
+# 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.
+
+## 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` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.