The `Connect` Claude Code Skill: 1000+ Service Integrations Without the Boilerplate

What Is the `Connect` Skill?

Connect is a Claude Code skill that gives Claude deep knowledge of integration patterns for a wide catalog of services. It ships with pre-built authentication flows, API client patterns, and data transformation schemas for services across the major categories:

Productivity: Gmail, Google Calendar, Google Drive, Notion, Airtable, Coda
Communication: Slack, Discord, Microsoft Teams, Telegram
Development: GitHub, GitLab, Linear, Jira, CircleCI, Vercel
CRM and sales: HubSpot, Salesforce, Pipedrive
Data and analytics: Snowflake, BigQuery, Mixpanel, PostHog
Payments: Stripe, PayPal, Braintree
File storage: Dropbox, Box, S3, Cloudflare R2

When you ask Claude to “create a GitHub issue whenever a Slack message is posted in #bugs,” the Connect skill means Claude already knows the GitHub Issues API, the Slack Events API, and the idiomatic way to wire them together — not as a rough sketch but as deployable code.

Why Integration Work Is Painful Without It

Integration code is notoriously tedious. The logic is usually simple — “get this, transform it, send it there” — but the implementation details are relentless: token refresh flows, webhook signature verification, pagination handling, error retries with backoff, API version differences, and SDK quirks.

Without the Connect skill, Claude can write integration code, but it writes it the way someone writes it from memory — with approximate API shapes that require multiple correction cycles. With the skill loaded, Claude has accurate, current knowledge of the APIs it is working with, and it applies the correct patterns from the start.

Installation

Install via the Claude Code Skills panel (Customize > Skills > search “connect” > toggle on), or via CLI:

claude skill add connect

Some integrations require API credentials at runtime. The skill itself has no secrets — you provide those as environment variables in your project:

export GITHUB_TOKEN=...
export SLACK_BOT_TOKEN=...
export NOTION_API_KEY=...

The skill generates code that reads from environment variables rather than hardcoding credentials, which is the correct default for any production use.

What the Skill Actually Does

Generate complete OAuth flows — Including the authorization redirect, token exchange, and token refresh logic. For services that require OAuth (Google, GitHub, Slack), this is often the hardest part to get right. The skill produces correct, production-grade OAuth implementations rather than pseudocode placeholders.

Write typed API clients — For TypeScript projects, Claude generates clients with correct types for request and response shapes, drawn from the actual API schemas of the target service.

Handle pagination correctly — Many APIs paginate results. The skill gives Claude accurate knowledge of each service’s pagination model (cursor-based, offset-based, link header) so it generates loops that actually retrieve all records.

Produce webhook handlers — Including signature verification (critical for security), idempotency patterns, and proper HTTP response codes.

Generate data transformation logic — When moving data between services with different schemas, Claude produces the correct field mappings rather than generic data.field placeholders.

Use Cases

Internal tooling — Build a Slack bot that queries your database, creates Linear tickets from support requests, or posts deployment notifications from your CI pipeline. These are two-hour tasks with Connect rather than two-day projects.

Automation pipelines — Wire together services in ways your no-code tools cannot handle: custom business logic, conditional routing, data transformations that require actual code.

Integration testing — Generate test fixtures and mock handlers for third-party APIs so your integration tests do not depend on live external services.

Migration scripts — Move data between platforms (Trello to Linear, Intercom to HubSpot) with correctly mapped field schemas and proper API rate limiting.

Reporting dashboards — Pull data from multiple sources (Stripe revenue, Mixpanel events, GitHub activity) into a unified data layer. Claude knows how to query each and how to join the results.

Example Workflow

I need a webhook handler that listens for new Stripe payments, then
creates a Notion database entry with the customer name, amount, and
payment date, and posts a summary to the #revenue Slack channel.

With Connect loaded, Claude produces:

An Express webhook handler with Stripe signature verification
Notion API client code using the correct database schema
Slack chat.postMessage call with a properly formatted Block Kit message
Environment variable scaffolding for all required secrets
Error handling for each external call

That is a complete, deployable integration — not a sketch.

Tips and Gotchas

Specify the service version when it matters. Some APIs have significant differences between versions (Notion v1 vs v2, Slack Web API vs Events API). Tell Claude which version your project uses.

Test with sandbox environments first. Stripe, PayPal, and most payment processors have sandbox modes. The skill generates code that works in both modes — just point your credentials at the sandbox.

Rate limiting is your responsibility to configure. The skill generates correct rate limit handling patterns, but you need to set the actual thresholds based on your service tier.

Webhook security is non-negotiable. Always use the signature verification the skill generates. Skipping it exposes you to replay attacks.