Loading...
Loading...
Found 250 Skills
Send messages and rich content to Slack channels via webhooks or Bot API. Use Block Kit for formatted announcements, marketing reports, and community updates. Trigger phrases: "post to slack", "slack message", "slack webhook", "slack notification", "slack announcement", "send to slack", "slack marketing", "slack update", "slack channel".
Clerk authentication integration for Convex. Use when setting up Clerk auth, configuring ConvexProviderWithClerk, implementing Clerk webhooks for user sync, or troubleshooting Clerk-specific auth issues.
Create and manage Kibana connectors for Slack, PagerDuty, Jira, webhooks, and more via REST API or Terraform. Use when configuring third-party integrations or managing connectors as code.
Send and receive emails programmatically using the AgentMail CLI. Use when agents need to manage inboxes, send/receive emails, handle threads, drafts, webhooks, and domains via command line.
Connect sales tools with webhooks, Zapier/Make, native integrations, and custom API pipelines — CRM sync, event triggers, data mapping, and error handling. Use when connecting Mailshake/Apollo/Salesloft to CRM, setting up webhook pipelines, building Zapier/Make automations for sales workflows, syncing data between tools, or troubleshooting integration issues. Do NOT use for Qwilr-specific automations (use /sales-qwilr-automation), general CRM platform config (use /sales-apollo or /sales-salesloft), or marketing automation flows (use /email-sequence).
Build automations connecting Qwilr to CRM and other tools via API, Zapier, or native integrations. Use when connecting Qwilr to HubSpot, connecting Qwilr to Salesforce, setting up Qwilr Zapier workflows, auto-generating proposals from CRM data, using the Qwilr API, automating proposal creation, syncing Qwilr with CRM, configuring Qwilr webhooks, or building Qwilr integrations.
Woodpecker.co platform help — cold email campaigns, condition-based sequences, email warmup, Bounce Shield, Adaptive Sending, email verification, inbox rotation, centralized inbox, LinkedIn automation, Lead Finder, agency panel, API & webhooks. Use when asking 'how do I do X in Woodpecker', setting up Woodpecker campaigns, configuring Woodpecker warmup or deliverability, using Woodpecker's agency panel, or troubleshooting Woodpecker sending issues. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Woodpecker to other tools via Zapier (use /sales-integration).
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kubernetes API analysis, service-account trust, RBAC edges, admission and controller behavior, cluster secrets, workload mutation, and namespace-scoped drift. Use when the user asks to inspect kube API permissions, service-account tokens, RoleBinding or ClusterRoleBinding edges, admission webhooks, controller-created pods, secret exposure, or why live workloads differ from manifests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
Clay platform help — Waterfall Enrichment (150+ data providers), Claygent (AI Research Agents), Sculptor (workflow builder), Signals (job changes, intent), Audiences, Ad Sync (LinkedIn/Meta/Google), Email Sequencer, CRM Sync (Salesforce/HubSpot/Dynamics), HTTP API actions, webhooks. Use when asking 'how do I set up Clay', 'Clay waterfall enrichment', 'Clay Claygent', 'Clay Sculptor workflows', 'Clay signals', 'Clay audiences', 'Clay ad sync', 'Clay sequencer', 'Clay CRM sync', 'Clay webhooks', 'Clay vs Apollo'. Do NOT use for enrichment strategy across tools (use /sales-enrich), cadence/sequence strategy across tools (use /sales-cadence), intent signal strategy across tools (use /sales-intent), B2B advertising strategy across tools (use /sales-b2b-advertising), or CRM data hygiene strategy across tools (use /sales-data-hygiene).
Integrate Commet billing and payments into any application. Use when working with @commet/node, @commet/next, @commet/better-auth, the Commet CLI, or building billing features like subscriptions, usage tracking, seat management, checkout, customer portal, webhooks, feature gating, or payment flows. Triggers on imports from "@commet/node", "@commet/next", "@commet/better-auth", commet SDK usage, billing integration tasks, or mentions of Commet.
Build backend APIs for Chrome extensions. NestJS + MongoDB (Mongoose) recommended stack. Auth, webhooks, license verification, CORS. Use when: backend, API, server, database, license, webhook.
Reference skill for Zoom Phone. Use after routing to a phone workflow when implementing OAuth, Phone APIs, webhooks, Smart Embed events, URI schemes, CRM or CTI dialers, or call handling automation.