Index of every page on this site: llms.txt
All skills
vercel avatar

/add-service

@86694bd
by vercelvercel/board147 stars
13
Run it yourself

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.

  • 1 file
  • 1.8 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/board/add-service

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈73 tokens for metadata: the name and description. ≈376 when used: this file.

Description uses 3.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈294 characters, or 3.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 86694bd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 12 hours ago.

Activeupdated 4 days ago

README badge

README badge for vercel/board/add-service