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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- third-party-integrations
- triggers
- [ "integration", "third-party", "external", "service", "api", "slack", "discord", "telegram", "stripe", "github", "gmail", "sheets", "google", "neon", "postgres", "supabase", "upstash", "database", "playwright", "browser", "browserbase", "kernel", "steel", "browserless", "scraping", "scrape", "pdf", "rss", "push", "notification", "webhook" ]
- description
- 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.
03 SKILL.md 正文
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
- 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 athttps://docs.val.town/sitemap-0.xml(it lists every docs URL), find theguides/…entry that matches the service, and fetch that page before writing any integration code. - 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.
- 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.
- 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
- Payments: Stripe
- Email: Gmail (for sending via a user's account; for built-in mail use
std/emailinstead — see theemailskill) - Google: Google Sheets
- External databases: Neon Postgres, Supabase, Upstash (for SQLite use built-in
std/sqliteinstead — see thesqlite-storageskill) - Browser automation: Kernel (recommended for Playwright), Browserbase, Steel, Browserless
- Source control / webhooks: GitHub (including webhooks)
- Content / output: RSS feeds, PDF generation, web scraping
- Notifications: push notifications
- Auth: OAuth providers (for logging in with a Val Town account use
std/oauthinstead)
Why this matters
Integration code is the most common place models hallucinate. APIs change, auth flows get reworked, and platform constraints (no filesystem, no subprocess) break naive approaches. The Val Town guide is the source of truth for what currently works on the platform.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.