---
name: add-service
description: "Reach a service besides GitHub (a payment provider, a database's API, a monitor, a host) with a key from the Vercel project's env: what to ask a person for, and the pull request that adds it. Use when work needs a service you can't reach, and when someone asks what you can reach."
title: add-service
canonical_url: https://skilld.dev/gh/vercel/board/add-service
last_updated: 2026-11-19T06:15:42.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install vercel/board/add-service`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/add-service`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/vercel/board/add-service) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/add-service`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/add-service --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/add-service --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Reach a service

A service's key lives in the factory's Vercel project and never enters your sandbox: the network
policy adds it to your requests on the way out. `agent/lib/services.ts` lists the services, and
`serviceChannels` in `app/api/board/[[...path]]/channels.ts` says which channels' threads reach
each. A thread anywhere else reaches none, though its env holds the same placeholders: a 401
there means the wrong channel, so say which one to ask in.

## Add one

1. **Ask for the key,** as your instructions say: the variable to create in Vercel, with the
   least access the work takes.
2. **Open the pull request** in the factory's repo:
   - a line in `agent/lib/services.ts`: its variable, the hosts its API answers on, `headers`
     when the key isn't sent as a bearer token, and `prefixes` when its CLI checks how a key
     starts;
   - its name under the channel in `serviceChannels`;
   - its CLI in `agent/sandbox.ts` when you'd use one, pinned like `gh`.
3. **Come back to it** (the check-ins skill). The key is read when the project deploys, so it
   works after a deploy that has both the variable and the merge. From then on the variable
   holds a placeholder in your sandbox.

## What it can't do

- **Only HTTP goes through the policy.** A connection string or a password a service hands you
  stays in the sandbox: say so before you use one.
- **Everything the thread runs can use the key,** a repo's scripts included. Ask for a key that
  can do only what the work needs.
