ClaudeSuperPower
SubmitLog in

third-party-integrations

Skill

Use when a val talks to an external service — Slack, Discord, Telegram, Stripe, GitHub, Gmail, Google Sheets, Postgres/Supabase/Upstash/Neon, browser automation (Playwright, Browserbase, Kernel, Steel), web scraping, PDF generation, push notifications, RSS, or any other third-party API. Covers the r

0Communication

Install

git clone https://github.com/val-town/plugins.git ~/.claude/skills/third-party-integrations

What is third-party-integrations?

Use when a val talks to an external service — Slack, Discord, Telegram, Stripe, GitHub, Gmail, Google Sheets, Postgres/Supabase/Upstash/Neon, browser automation (Playwright, Browserbase, Kernel, Steel), web scraping, PDF generation, push notifications, RSS, or any other third-party API. Covers the required workflow (fetch the Val Town guide, get credentials, test, store secrets) and the catalog of available guides.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~105 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

Third-Party Integrations

When a val uses any external service, follow this order — do not skip steps and do not write integration code from training-data memory alone. Val Town's guides have platform-specific patterns and required workarounds that won't be in your training data.

Workflow

  1. Fetch the Val Town guide first. Guides live under https://docs.val.town/guides/, but the slug isn't always just the service name — some are grouped under a category (e.g. databases/neon-postgres/, browser-automation/kernel/) or live on a sub-page (slack/agent/). Don't guess the URL: fetch the docs sitemap at https://docs.val.town/sitemap-0.xml (it lists every docs URL), find the guides/… entry that matches the service, and fetch that page before writing any integration code.
  2. Help the user get credentials. Provide direct links to create API keys or step-by-step OAuth setup instructions. Don't make the user hunt.
  3. Test the connection with a minimal script (a single fetch / SDK call that returns one record) before building features on top. This isolates auth/setup problems from feature bugs.
  4. Store secrets in env vars. Use Deno.env.get("KEY_NAME") to read them, and document the required env vars in the README so the user (or anyone remixing the val) knows what to set. Whenever you reference an env var the user needs to set, show the raw, full URL to the prefilled Val Town env var editor on its own line, in this exact format: 👉 Add KEY_NAME here: https://www.val.town/x/HANDLE/VAL_NAME/environment-variables?key=KEY_NAME. Keep the URL visible (not hidden behind link text) — it's the call-to-action.

Available guides

Services with dedicated guides today — not exhaustive, so use the sitemap from step 1 as the current source of truth:

  • Messaging / chat: Slack, Discord, Telegram

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.