23 skills · category

Integrations skills for Claude Code

Skills for wiring third-party services in correctly the first time: Stripe payments and subscriptions, auth providers, transactional email with deliverability, Slack and Discord bots, GitHub automation, Shopify apps, search engines, Sentry, product analytics, Twilio, and the Notion API.

  1. 401Airtable API
  2. 402Auth Providers
  3. 403Calendar Scheduling
  4. 404Discord Bots
  5. 405Email Deliverability
  6. 406GitHub API Automation
  7. 407Google Workspace APIs
  8. 408HubSpot CRM
  9. 409Jira and Linear APIs
  10. 410Media CDN
  11. 411Merchant of Record Billing
  12. 412Microsoft Graph
  13. 413Notion API
  14. 414Plaid Banking
  15. 415Product Analytics
  16. 416Salesforce API
  17. 417Search Integration
  18. 418Sentry Error Tracking
  19. 419Shopify Apps
  20. 420Slack Apps
  21. 421Stripe Payments
  22. 422Transactional Email
  23. 423Twilio Messaging

Every integrations skill

Each card opens the full playbook, example prompts and install commands.

No. 401

Airtable API

Field IDs, 10-record batches, and verified webhooks

Claude treats Airtable as an external system with a contract: it pins table and field IDs so UI renames cannot break sync, routes every call through one limiter that respects the per-base rate limit and 30-second lockout, writes with idempotent performUpsert batches, and captures changes through MAC-verified webhook pings, persisted payload cursors, and a refresh job.

airtable-api 212 lines
No. 402

Auth Providers

Hosted login wired in, authorization kept server-side

Claude picks an auth provider from your real constraints (self-hosting, SSO, MAU, data residency), wires the current SDK for your framework version, and refuses to treat middleware as authorization: every data read re-checks the session. Users are keyed on stable provider IDs and synced through signature-verified webhooks, with a tested plan for moving between providers.

auth-providers 231 lines
No. 403

Calendar Scheduling

Bookings that survive DST, races, and Outlook

Claude models scheduling the way calendar engineers do: UTC instants with IANA zones, slots computed from working hours minus busy time and buffers, a Postgres exclusion constraint that makes double-booking impossible, Cal.com bookings with verified webhooks, and RFC 5545 invites with stable UIDs and SEQUENCE. A bundled script generates and lints .ics files.

calendar-scheduling 237 lines · 2 files
No. 404

Discord Bots

Slash-command bots that never miss the 3-second window

Claude builds discord.js v14 bots with only the intents they use, a separate deploy script for slash commands, and handlers that defer before slow work so Unknown interaction errors stop. Buttons and selects encode record IDs in customId so they survive restarts and shards, and serverless endpoints verify Ed25519 signatures before answering PING.

discord-bots 238 lines
No. 405

Email Deliverability

From p=none to p=reject without losing real mail

Claude treats deliverability as an audit, not a guess. It inventories every service sending as your domain, reads DMARC aggregate reports with a bundled parser to find unaligned senders, fixes them with custom-domain DKIM, then moves the policy to quarantine and reject over full monthly cycles. It also checks Gmail, Yahoo and Outlook bulk rules, RFC 8058 unsubscribe, stream separation and warm-up.

email-deliverability 262 lines · 2 files
No. 406

GitHub API Automation

Bulk GitHub changes with dry runs and throttling

Claude scripts GitHub the careful way: it picks the least-privileged credential (GITHUB_TOKEN, fine-grained PAT, or GitHub App), prototypes with gh api, paginates every list, throttles writes under primary and secondary limits, and runs a dry run you approve before mutating anything. App webhooks are verified against the raw body and deduped by delivery ID.

github-api-automation 215 lines · 2 files
No. 407

Google Workspace APIs

Drive, Calendar, Gmail and Sheets with minimal scopes

Claude picks the right Google auth model for who owns the data, requests the narrowest scopes so verification stays cheap, and replaces repeated full scans with sync tokens, history IDs and change feeds. Push notifications are authenticated by channel token or Pub/Sub OIDC, and quota errors get backoff instead of retry storms.

google-workspace-apis 229 lines
No. 408

HubSpot CRM

Upserts, labeled associations and loop-free CRM sync

Claude builds HubSpot integrations around a unique external ID per record, so every write is an idempotent batch upsert instead of search-then-create. It decides field ownership up front, creates v4 associations with looked-up label IDs, pulls changes incrementally within the search API's 10,000-result cap, and verifies v3 webhook signatures before handling events, merges and deletes.

hubspot-crm 224 lines
No. 409

Jira and Linear APIs

Ticket automation that never files the same bug twice

Claude automates issue trackers with production habits: an external key and mapping table so retries never create duplicate tickets, Jira's current JQL search endpoint with nextPageToken paging, Atlassian Document Format bodies, transitions looked up by ID, Linear GraphQL with complexity-aware queries, and HMAC-verified webhooks that ignore the integration's own writes.

issue-tracker-apis 227 lines · 2 files
No. 410

Media CDN

Signed uploads, signed URLs, no surprise media bills

Claude sets up image and video delivery so it is fast, private where it must be, and hard to abuse: server-signed direct uploads to Cloudinary or Mux, a URL builder limited to an allowlisted width ladder with signed or strict transformations, short-lived Mux playback tokens minted after an ownership check, and asset state updated only from signature-verified webhooks.

media-cdn 201 lines
★ No. 411

Merchant of Record Billing

Sell globally while the MoR owes the VAT and sales tax

Claude wires merchant-of-record billing so the provider carries VAT and sales tax while your app only tracks entitlements. Checkout carries your account ID in custom data, webhooks are verified over the raw body and deduplicated before an entitlement state machine applies them, and the full buy, renew, fail, cancel and refund lifecycle is replayed in sandbox before launch.

merchant-of-record-billing 280 lines · 2 files
No. 412

Microsoft Graph

Outlook, OneDrive and Teams calls with fenced permissions

Claude registers Entra ID apps with the fewest permissions of the right type, fences application access to specific mailboxes and SharePoint sites, and authenticates with certificates or federated identities. Sync runs on delta links, change notification endpoints validate tokens and clientState and handle lifecycle events, and throttled calls wait out Retry-After instead of hammering Graph.

microsoft-graph 221 lines
No. 413

Notion API

Notion sync scripts that page, pace and chunk

Gives Claude the Notion details that usually cause silent failures: pinned API versions and the newer data source model, cursor pagination on every list, property write shapes, the 100-block and 2,000-character limits, and Retry-After backoff for 429s. Sync jobs pull incrementally by last_edited_time, detect trashed pages, and test against a duplicated database before touching the real one.

notion-api 220 lines
No. 414

Plaid Banking

Bank linking with encrypted tokens and cursor-based sync

Claude wires Plaid the way fintech teams ship it: link tokens minted per session, access tokens envelope-encrypted and never exposed to clients, transaction sync applied atomically per cursor with restarts on mid-pagination mutations, ES256 webhook verification with body hashes, update mode for broken logins, and /item/remove plus deletion when a user disconnects.

plaid-banking 227 lines
No. 415

Product Analytics

One person per user, one name per event

Makes Claude implement analytics the way a careful data team would: a typed track wrapper instead of scattered strings, identify with internal IDs and reset on logout, revenue captured from verified payment webhooks with dedupe IDs, and every SDK held behind consent. Funnels are checked against raw events so dashboards can be trusted rather than argued about.

product-analytics 218 lines · 2 files
No. 416

Salesforce API

JWT auth, Bulk 2.0 loads and CDC-driven CRM sync

Claude connects backends to Salesforce through an API-only integration user and JWT bearer or client credentials auth on an External Client App, never stored passwords. It picks REST, Composite or Bulk API 2.0 by volume, upserts on external IDs, syncs incrementally with Change Data Capture or a SystemModstamp watermark, and tracks usage against the org's daily API allocation.

salesforce-api 192 lines
No. 417

Search Integration

Search that ranks right and never drifts from the DB

Has Claude treat the search engine as a rebuildable derived store: records shaped for queries, settings declared per engine, atomic reindex via replaceAllObjects, index swaps or aliases, and after-commit sync that propagates deletes. Relevance changes are judged against a golden query set, and private data is protected with server-generated scoped keys rather than client filters.

search-integration 230 lines
No. 418

Sentry Error Tracking

Readable stack traces, quiet quotas, useful alerts

Guides Claude through a Sentry setup that actually helps on-call: every event tagged with release and environment, source maps uploaded from CI with the auth token kept secret, errors kept at full rate while traces and replays are sampled, and noise filtered at the SDK before it burns quota. It finishes with alert rules for new and regressed issues and a weekly triage routine.

sentry-error-tracking 247 lines
No. 419

Shopify Apps

GraphQL-first Shopify apps that pass review

Keeps Claude on the current Shopify platform: CLI-scaffolded apps configured in shopify.app.toml, GraphQL Admin calls with pinned versions and userErrors checks, bulk operations for big syncs, and webhooks verified against raw bytes and deduped by webhook id. It treats REST calls and Shopify Scripts as migration debt and never ships an app missing the three compliance webhooks.

shopify-apps 257 lines · 2 files
No. 420

Slack Apps

Bolt apps that ack in time and ask for few scopes

Claude builds Slack integrations from a committed app manifest, acknowledges every command, action and modal submission inside the 3-second window before doing real work, and keeps scopes minimal. It knows Block Kit limits, trigger_id expiry, event retry headers and rate-limit tiers, and wires OAuth installation stores keyed by team for apps installed beyond one workspace.

slack-apps 246 lines
★ No. 421

Stripe Payments

Webhook-driven checkout that never double-charges

Claude builds Stripe flows the way payment engineers do: prices resolved on the server, one Customer per account, idempotency keys tied to the business operation, and fulfillment driven only by signature-verified webhooks that tolerate retries and out-of-order delivery. It then proves the flow with Stripe CLI triggers, decline and 3DS cards, and test clocks.

stripe-payments 253 lines · 2 files
No. 422

Transactional Email

Receipts and resets that reach the inbox

Claude sets up app email like a deliverability engineer: a dedicated sending subdomain with aligned SPF, DKIM and DMARC (checked by a bundled dig script), React Email or MJML templates with plain-text parts, one queued and idempotent send function, and signature-verified bounce and complaint webhooks that feed a suppression list before every send.

transactional-email 226 lines · 3 files
No. 423

Twilio Messaging

Texts that get delivered and stay compliant

Steers Claude toward Twilio setups that survive carrier scrutiny: sends routed through Messaging Services with status callbacks, every inbound and status webhook validated against X-Twilio-Signature, per-message delivery state stored and only moved forward, and opt-outs mirrored in your own database. It also covers 10DLC and toll-free registration, WhatsApp template rules and Verify for login codes.

twilio-messaging 222 lines · 2 files

Choosing Integrations skills

Install the skills that match requests you make every week; each costs about 100 tokens of standing context until it loads. If you are not sure where to begin, start with Merchant of Record Billing and Stripe Payments. For background, read The Best Claude Code Skills in 2026, by Use Case, How to Install Claude Code Skills (5 Ways) and Personal vs Project Skills.

By technology: Python skillsGraphQL skills

Install several

Install several at once

The installer accepts any number of skill names. Add --project to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- airtable-api auth-providers calendar-scheduling discord-bots email-deliverability github-api-automation google-workspace-apis hubspot-crm issue-tracker-apis media-cdn merchant-of-record-billing microsoft-graph notion-api plaid-banking product-analytics salesforce-api search-integration sentry-error-tracking shopify-apps slack-apps stripe-payments transactional-email twilio-messaging

Integrations skills FAQ

How do I install every Integrations skill at once?

Download the bundle at https://claudeskills.page/downloads/category/integrations.zip and unzip it into ~/.claude/skills/ (or .claude/skills/ inside a repository). To pick a few, pass several names to the installer: curl -fsSL https://claudeskills.page/install.sh | sh -s -- airtable-api auth-providers calendar-scheduling.

Will installing 23 skills slow Claude Code down?

No. Claude Code keeps only each skill's short description in context — roughly 100 tokens per skill — and loads the full instructions only when a request matches. Install the whole category if it fits your work; unused skills cost almost nothing.

Which Integrations skill should I start with?

Start with Merchant of Record Billing, Stripe Payments. They cover the most common requests in this category; add the rest as your work calls for them.

esc