@ngxtm/devkit 3.14.0 → 3.16.0

package/skills/brevo-automation/SKILL.md

@@ -0,0 +1,202 @@
+---
+name: brevo-automation
+description: "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche..."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Brevo Automation via Rube MCP
+
+Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Brevo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brevo`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brevo`
+3. If connection is not ACTIVE, follow the returned auth link to complete Brevo authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Email Campaigns
+
+**When to use**: User wants to list, review, or update email campaigns
+
+**Tool sequence**:
+1. `BREVO_LIST_EMAIL_CAMPAIGNS` - List all campaigns with filters [Required]
+2. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Update campaign content or settings [Optional]
+
+**Key parameters for listing**:
+- `type`: Campaign type ('classic' or 'trigger')
+- `status`: Campaign status ('suspended', 'archive', 'sent', 'queued', 'draft', 'inProcess', 'inReview')
+- `startDate`/`endDate`: Date range filter (YYYY-MM-DDTHH:mm:ss.SSSZ format)
+- `statistics`: Stats type to include ('globalStats', 'linksStats', 'statsByDomain')
+- `limit`: Results per page (max 100, default 50)
+- `offset`: Pagination offset
+- `sort`: Sort order ('asc' or 'desc')
+- `excludeHtmlContent`: Set `true` to reduce response size
+
+**Key parameters for update**:
+- `campaign_id`: Numeric campaign ID (required)
+- `name`: Campaign name
+- `subject`: Email subject line
+- `htmlContent`: HTML email body (mutually exclusive with `htmlUrl`)
+- `htmlUrl`: URL to HTML content
+- `sender`: Sender object with `name`, `email`, or `id`
+- `recipients`: Object with `listIds` and `exclusionListIds`
+- `scheduledAt`: Scheduled send time (YYYY-MM-DDTHH:mm:ss.SSSZ)
+
+**Pitfalls**:
+- `startDate` and `endDate` are mutually required; provide both or neither
+- Date filters only work when `status` is not passed or set to 'sent'
+- `htmlContent` and `htmlUrl` are mutually exclusive
+- Campaign `sender` email must be a verified sender in Brevo
+- A/B testing fields (`subjectA`, `subjectB`, `splitRule`, `winnerCriteria`) require `abTesting: true`
+- `scheduledAt` uses full ISO 8601 format with timezone
+
+### 2. Create and Manage Email Templates
+
+**When to use**: User wants to create, edit, list, or delete email templates
+
+**Tool sequence**:
+1. `BREVO_GET_ALL_EMAIL_TEMPLATES` - List all templates [Required]
+2. `BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE` - Create a new template or update existing [Required]
+3. `BREVO_DELETE_EMAIL_TEMPLATE` - Delete an inactive template [Optional]
+
+**Key parameters for listing**:
+- `templateStatus`: Filter active (`true`) or inactive (`false`) templates
+- `limit`: Results per page (max 1000, default 50)
+- `offset`: Pagination offset
+- `sort`: Sort order ('asc' or 'desc')
+
+**Key parameters for create/update**:
+- `templateId`: Include to update; omit to create new
+- `templateName`: Template display name (required for creation)
+- `subject`: Email subject line (required for creation)
+- `htmlContent`: HTML template body (min 10 characters; use this or `htmlUrl`)
+- `sender`: Sender object with `name` and `email`, or `id` (required for creation)
+- `replyTo`: Reply-to email address
+- `isActive`: Activate or deactivate the template
+- `tag`: Category tag for the template
+
+**Pitfalls**:
+- When `templateId` is provided, the tool updates; when omitted, it creates
+- For creation, `templateName`, `subject`, and `sender` are required
+- `htmlContent` must be at least 10 characters
+- Template personalization uses `{{contact.ATTRIBUTE}}` syntax
+- Only inactive templates can be deleted
+- `htmlContent` and `htmlUrl` are mutually exclusive
+
+### 3. Manage Senders
+
+**When to use**: User wants to view authorized sender identities
+
+**Tool sequence**:
+1. `BREVO_GET_ALL_SENDERS` - List all verified senders [Required]
+
+**Key parameters**: (none required)
+
+**Pitfalls**:
+- Senders must be verified before they can be used in campaigns or templates
+- Sender verification is done through the Brevo web interface, not via API
+- Sender IDs can be used in `sender.id` fields for campaigns and templates
+
+### 4. Configure A/B Testing Campaigns
+
+**When to use**: User wants to set up or modify A/B test settings on a campaign
+
+**Tool sequence**:
+1. `BREVO_LIST_EMAIL_CAMPAIGNS` - Find the target campaign [Prerequisite]
+2. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Configure A/B test settings [Required]
+
+**Key parameters**:
+- `campaign_id`: Campaign to configure
+- `abTesting`: Set to `true` to enable A/B testing
+- `subjectA`: Subject line for variant A
+- `subjectB`: Subject line for variant B
+- `splitRule`: Percentage split for the test (1-99)
+- `winnerCriteria`: 'open' or 'click' for determining the winner
+- `winnerDelay`: Hours to wait before selecting winner (1-168)
+
+**Pitfalls**:
+- A/B testing must be enabled (`abTesting: true`) before setting variant fields
+- `splitRule` is the percentage of contacts that receive variant A
+- `winnerDelay` defines how long to test before sending the winner to remaining contacts
+- Only works with 'classic' campaign type
+
+## Common Patterns
+
+### Campaign Lifecycle
+
+```
+1. Create campaign (status: draft)
+2. Set recipients (listIds)
+3. Configure content (htmlContent or htmlUrl)
+4. Optionally schedule (scheduledAt)
+5. Send or schedule via Brevo UI (API update can set scheduledAt)
+```
+
+### Pagination
+
+- Use `limit` (page size) and `offset` (starting index)
+- Default limit is 50; max varies by endpoint (100 for campaigns, 1000 for templates)
+- Increment `offset` by `limit` each page
+- Check `count` in response to determine total available
+
+### Template Personalization
+
+```
+- First name: {{contact.FIRSTNAME}}
+- Last name: {{contact.LASTNAME}}
+- Custom attribute: {{contact.CUSTOM_ATTRIBUTE}}
+- Mirror link: {{mirror}}
+- Unsubscribe link: {{unsubscribe}}
+```
+
+## Known Pitfalls
+
+**Date Formats**:
+- All dates use ISO 8601 with milliseconds: YYYY-MM-DDTHH:mm:ss.SSSZ
+- Pass timezone in the date-time format for accurate results
+- `startDate` and `endDate` must be used together
+
+**Sender Verification**:
+- All sender emails must be verified in Brevo before use
+- Unverified senders cause campaign creation/update failures
+- Use GET_ALL_SENDERS to check available verified senders
+
+**Rate Limits**:
+- Brevo API has rate limits per account plan
+- Implement backoff on 429 responses
+- Template operations have lower limits than read operations
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Campaign and template IDs are numeric integers
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List campaigns | BREVO_LIST_EMAIL_CAMPAIGNS | type, status, limit, offset |
+| Update campaign | BREVO_UPDATE_EMAIL_CAMPAIGN | campaign_id, subject, htmlContent |
+| List templates | BREVO_GET_ALL_EMAIL_TEMPLATES | templateStatus, limit, offset |
+| Create template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateName, subject, htmlContent, sender |
+| Update template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateId, htmlContent |
+| Delete template | BREVO_DELETE_EMAIL_TEMPLATE | templateId |
+| List senders | BREVO_GET_ALL_SENDERS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/broken-authentication/SKILL.md

@@ -1,9 +1,11 @@
 ---
-name: Broken Authentication Testing
-description: This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
+name: broken-authentication
+description: "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # Broken Authentication Testing
@@ -474,3 +476,6 @@ https://target.com/reset?token=a1b2c3d4e5f6&email=admin@example.com
 | Session analysis inconclusive | Collect 1000+ tokens; use statistical tools; check for timestamps; compare accounts |
 | MFA cannot be bypassed | Document as secure; test backup/recovery mechanisms; check MFA fatigue; verify enrollment |
 | Account lockout prevents testing | Request multiple test accounts; test threshold first; use slower timing |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/browser-automation/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: browser-automation
-description: "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns.  This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 202"
+description: "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Browser Automation
@@ -68,3 +69,6 @@ Let Playwright wait automatically, never add manual waits
 ## Related Skills
 
 Works well with: `agent-tool-builder`, `workflow-automation`, `computer-use-agents`, `test-architect`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/browser-extension-builder/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: browser-extension-builder
-description: "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3."
+description: "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Browser Extension Builder
@@ -259,3 +260,6 @@ Update quickly when broken.
 ## Related Skills
 
 Works well with: `frontend`, `micro-saas-launcher`, `personal-tool-builder`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/bullmq-specialist/SKILL.md

@@ -2,6 +2,7 @@
 name: bullmq-specialist
 description: "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # BullMQ Specialist
@@ -55,3 +56,6 @@ Complex multi-step job processing with parent-child relationships
 ## Related Skills
 
 Works well with: `redis-specialist`, `backend`, `nextjs-app-router`, `email-systems`, `ai-workflow-automation`, `performance-hunter`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/bun-development/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: bun-development
-description: "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun."
+description: "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o..."
+risk: unknown
+source: community
 ---
 
 # ⚡ Bun Development

package/skills/burp-suite-testing/SKILL.md

@@ -1,9 +1,11 @@
 ---
-name: Burp Suite Web Application Testing
-description: This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.
+name: burp-suite-testing
+description: "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # Burp Suite Web Application Testing
@@ -378,3 +380,6 @@ javascript:alert(1)
 - Check intercept rules aren't filtering target
 - Ensure browser is using Burp proxy
 - Verify target isn't using unsupported protocol
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/business-analyst/SKILL.md

@@ -1,11 +1,13 @@
 ---
 name: business-analyst
-description: Master modern business analysis with AI-powered analytics,
+description: "Master modern business analysis with AI-powered analytics,"
   real-time dashboards, and data-driven insights. Build comprehensive KPI
   frameworks, predictive models, and strategic recommendations. Use PROACTIVELY
   for business intelligence or strategic analysis.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/busybox-on-windows/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: busybox-on-windows
-description: How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
+description: "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows."
 license: MIT
+risk: unknown
+source: community
 ---
 
 BusyBox is a single binary that implements many common Unix tools.
@@ -28,3 +30,6 @@ If you need to run a UNIX command under another CWD, then use the absolute path
 
 Documentation: https://frippery.org/busybox/
 Original BusyBox: https://busybox.net/
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/c-pro/SKILL.md

@@ -6,6 +6,8 @@ description: Write efficient C code with proper memory management, pointer
   or system programming.
 metadata:
   model: opus
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/c4-architecture-c4-architecture/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: c4-architecture-c4-architecture
 description: "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach."
+risk: unknown
+source: community
 ---
 
 # C4 Architecture Documentation Workflow

package/skills/c4-code/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: c4-code
-description: Expert C4 Code-level documentation specialist. Analyzes code
+description: "Expert C4 Code-level documentation specialist. Analyzes code"
   directories to create comprehensive C4 code-level documentation including
   function signatures, arguments, dependencies, and code structure. Use when
   documenting code at the lowest C4 level for individual directories and code
   modules.
 metadata:
   model: haiku
+risk: unknown
+source: community
 ---
 
 # C4 Code Level: [Directory Name]

package/skills/c4-component/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: c4-component
-description: Expert C4 Component-level documentation specialist. Synthesizes C4
+description: "Expert C4 Component-level documentation specialist. Synthesizes C4"
   Code-level documentation into Component-level architecture, defining component
   boundaries, interfaces, and relationships. Creates component diagrams and
   documentation. Use when synthesizing code-level documentation into logical
   components.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 # C4 Component Level: [Component Name]
@@ -49,8 +51,8 @@ metadata:
 
 This component contains the following code-level elements:
 
-- [c4-code-file-1.md](./c4-code-file-1.md) - [Description]
-- [c4-code-file-2.md](./c4-code-file-2.md) - [Description]
+- c4-code-file-1.md - [Description]
+- c4-code-file-2.md - [Description]
 
 ## Interfaces
 
@@ -114,12 +116,12 @@ C4Component
 ### [Component 1]
 - **Name**: [Component name]
 - **Description**: [Short description]
-- **Documentation**: [c4-component-name-1.md](./c4-component-name-1.md)
+- **Documentation**: c4-component-name-1.md
 
 ### [Component 2]
 - **Name**: [Component name]
 - **Description**: [Short description]
-- **Documentation**: [c4-component-name-2.md](./c4-component-name-2.md)
+- **Documentation**: c4-component-name-2.md
 
 ## Component Relationships
 [Mermaid diagram showing all components and their relationships]

package/skills/c4-container/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: c4-container
-description: Expert C4 Container-level documentation specialist. Synthesizes
+description: "Expert C4 Container-level documentation specialist. Synthesizes"
   Component-level documentation into Container-level architecture, mapping
   components to deployment units, documenting container interfaces as APIs, and
   creating container diagrams. Use when synthesizing components into deployment
   containers and documenting system deployment architecture.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 # C4 Container Level: System Deployment
@@ -47,7 +49,7 @@ metadata:
 This container deploys the following components:
 
 - [Component Name]: [Description]
-  - Documentation: [c4-component-name.md](./c4-component-name.md)
+  - Documentation: c4-component-name.md
 
 ## Interfaces
 

package/skills/c4-context/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: c4-context
-description: Expert C4 Context-level documentation specialist. Creates
+description: "Expert C4 Context-level documentation specialist. Creates"
   high-level system context diagrams, documents personas, user journeys, system
   features, and external dependencies. Synthesizes container and component
   documentation with system documentation to create comprehensive context-level
@@ -8,6 +8,8 @@ description: Expert C4 Context-level documentation specialist. Creates
   documentation.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 # C4 Context Level: System Context
@@ -86,8 +88,8 @@ metadata:
 
 ## Related Documentation
 
-- [Container Documentation](./c4-container.md)
-- [Component Documentation](./c4-component.md)
+- Container Documentation
+- Component Documentation
 ```
 
 ## Context Diagram Template

package/skills/cal-com-automation/SKILL.md

@@ -0,0 +1,208 @@
+---
+name: cal-com-automation
+description: "Automate Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, and handle teams. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Cal.com Automation via Rube MCP
+
+Automate Cal.com scheduling operations through Composio's Cal toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Cal.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `cal`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cal`
+3. If connection is not ACTIVE, follow the returned auth link to complete Cal.com authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Bookings
+
+**When to use**: User wants to list, create, or review bookings
+
+**Tool sequence**:
+1. `CAL_FETCH_ALL_BOOKINGS` - List all bookings with filters [Required]
+2. `CAL_POST_NEW_BOOKING_REQUEST` - Create a new booking [Optional]
+
+**Key parameters for listing**:
+- `status`: Filter by booking status ('upcoming', 'recurring', 'past', 'cancelled', 'unconfirmed')
+- `afterStart`: Filter bookings after this date (ISO 8601)
+- `beforeEnd`: Filter bookings before this date (ISO 8601)
+
+**Key parameters for creation**:
+- `eventTypeId`: Event type ID for the booking
+- `start`: Booking start time (ISO 8601)
+- `end`: Booking end time (ISO 8601)
+- `name`: Attendee name
+- `email`: Attendee email
+- `timeZone`: Attendee timezone (IANA format)
+- `language`: Attendee language code
+- `metadata`: Additional metadata object
+
+**Pitfalls**:
+- Date filters use ISO 8601 format with timezone (e.g., '2024-01-15T09:00:00Z')
+- `eventTypeId` must reference a valid, active event type
+- Booking creation requires matching an available slot; check availability first
+- Time zone must be a valid IANA timezone string (e.g., 'America/New_York')
+- Status filter values are specific strings; invalid values return empty results
+
+### 2. Check Availability
+
+**When to use**: User wants to find free/busy times or available booking slots
+
+**Tool sequence**:
+1. `CAL_RETRIEVE_CALENDAR_BUSY_TIMES` - Get busy time blocks [Required]
+2. `CAL_GET_AVAILABLE_SLOTS_INFO` - Get specific available slots [Required]
+
+**Key parameters**:
+- `dateFrom`: Start date for availability check (YYYY-MM-DD)
+- `dateTo`: End date for availability check (YYYY-MM-DD)
+- `eventTypeId`: Event type to check slots for
+- `timeZone`: Timezone for the availability response
+- `loggedInUsersTz`: Timezone of the requesting user
+
+**Pitfalls**:
+- Busy times show when the user is NOT available
+- Available slots are specific to an event type's duration and configuration
+- Date range should be reasonable (not months in advance) to get accurate results
+- Timezone affects how slots are displayed; always specify explicitly
+- Availability reflects calendar integrations (Google Calendar, Outlook, etc.)
+
+### 3. Configure Webhooks
+
+**When to use**: User wants to set up or manage webhook notifications for booking events
+
+**Tool sequence**:
+1. `CAL_RETRIEVE_WEBHOOKS_LIST` - List existing webhooks [Required]
+2. `CAL_GET_WEBHOOK_BY_ID` - Get specific webhook details [Optional]
+3. `CAL_UPDATE_WEBHOOK_BY_ID` - Update webhook configuration [Optional]
+4. `CAL_DELETE_WEBHOOK_BY_ID` - Remove a webhook [Optional]
+
+**Key parameters**:
+- `id`: Webhook ID for GET/UPDATE/DELETE operations
+- `subscriberUrl`: Webhook endpoint URL
+- `eventTriggers`: Array of event types to trigger on
+- `active`: Whether the webhook is active
+- `secret`: Webhook signing secret
+
+**Pitfalls**:
+- Webhook URLs must be publicly accessible HTTPS endpoints
+- Event triggers include: 'BOOKING_CREATED', 'BOOKING_RESCHEDULED', 'BOOKING_CANCELLED', etc.
+- Inactive webhooks do not fire; toggle `active` to enable/disable
+- Webhook secrets are used for payload signature verification
+
+### 4. Manage Teams
+
+**When to use**: User wants to create, view, or manage teams and team event types
+
+**Tool sequence**:
+1. `CAL_GET_TEAMS_LIST` - List all teams [Required]
+2. `CAL_GET_TEAM_INFORMATION_BY_TEAM_ID` - Get specific team details [Optional]
+3. `CAL_CREATE_TEAM_IN_ORGANIZATION` - Create a new team [Optional]
+4. `CAL_RETRIEVE_TEAM_EVENT_TYPES` - List event types for a team [Optional]
+
+**Key parameters**:
+- `teamId`: Team identifier
+- `name`: Team name (for creation)
+- `slug`: URL-friendly team identifier
+
+**Pitfalls**:
+- Team creation may require organization-level permissions
+- Team event types are separate from personal event types
+- Team slugs must be URL-safe and unique within the organization
+
+### 5. Organization Management
+
+**When to use**: User wants to view organization details
+
+**Tool sequence**:
+1. `CAL_GET_ORGANIZATION_ID` - Get the organization ID [Required]
+
+**Key parameters**: (none required)
+
+**Pitfalls**:
+- Organization ID is needed for team creation and org-level operations
+- Not all Cal.com accounts have organizations; personal plans may return errors
+
+## Common Patterns
+
+### Booking Creation Flow
+
+```
+1. Call CAL_GET_AVAILABLE_SLOTS_INFO to find open slots
+2. Present available times to the user
+3. Call CAL_POST_NEW_BOOKING_REQUEST with selected slot
+4. Confirm booking creation response
+```
+
+### ID Resolution
+
+**Team name -> Team ID**:
+```
+1. Call CAL_GET_TEAMS_LIST
+2. Find team by name in response
+3. Extract id field
+```
+
+### Webhook Setup
+
+```
+1. Call CAL_RETRIEVE_WEBHOOKS_LIST to check existing hooks
+2. Create or update webhook with desired triggers
+3. Verify webhook fires on test booking
+```
+
+## Known Pitfalls
+
+**Date/Time Formats**:
+- Booking times: ISO 8601 with timezone (e.g., '2024-01-15T09:00:00Z')
+- Availability dates: YYYY-MM-DD format
+- Always specify timezone explicitly to avoid confusion
+
+**Event Types**:
+- Event type IDs are numeric integers
+- Event types define duration, location, and booking rules
+- Disabled event types cannot accept new bookings
+
+**Permissions**:
+- Team operations require team membership or admin access
+- Organization operations require org-level permissions
+- Webhook management requires appropriate access level
+
+**Rate Limits**:
+- Cal.com API has rate limits per API key
+- Implement backoff on 429 responses
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List bookings | CAL_FETCH_ALL_BOOKINGS | status, afterStart, beforeEnd |
+| Create booking | CAL_POST_NEW_BOOKING_REQUEST | eventTypeId, start, end, name, email |
+| Get busy times | CAL_RETRIEVE_CALENDAR_BUSY_TIMES | dateFrom, dateTo |
+| Get available slots | CAL_GET_AVAILABLE_SLOTS_INFO | eventTypeId, dateFrom, dateTo |
+| List webhooks | CAL_RETRIEVE_WEBHOOKS_LIST | (none) |
+| Get webhook | CAL_GET_WEBHOOK_BY_ID | id |
+| Update webhook | CAL_UPDATE_WEBHOOK_BY_ID | id, subscriberUrl, eventTriggers |
+| Delete webhook | CAL_DELETE_WEBHOOK_BY_ID | id |
+| List teams | CAL_GET_TEAMS_LIST | (none) |
+| Get team | CAL_GET_TEAM_INFORMATION_BY_TEAM_ID | teamId |
+| Create team | CAL_CREATE_TEAM_IN_ORGANIZATION | name, slug |
+| Team event types | CAL_RETRIEVE_TEAM_EVENT_TYPES | teamId |
+| Get org ID | CAL_GET_ORGANIZATION_ID | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.