---
name: try-it
description: "Find a way to try your changes to a repo for real, by using what it builds, and keep what you learn for the next thread. Says what can and can't reach your sandbox, so you ask a person only for what can arrive. Use when you start on a repo you haven't run, and when a change needs more than its tests."
title: try-it
canonical_url: https://skilld.dev/gh/vercel/board/try-it
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/try-it`. 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/try-it`, 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/try-it) 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/try-it`. 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/try-it --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/try-it --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.

# Try your work for real

Tests tell you some of it. Using the thing tells you the rest: open the page, run the command,
call the endpoint. For each repo you work on, look for a way to do that yourself.

How is yours to work out from what's there. Every repo is different, and some have no way you
can reach. That's fine: say what you couldn't try, and carry on.

What the repo won't tell you:

- **What's in your sandbox** is the repo, what it installs, and what you make there: a local
  database, seed data, an account you sign up for on a server you started.
- **A service's key reaches your requests, never your sandbox** (the add-service skill). Nothing
  else comes in. A variable in this factory's Vercel project isn't in your environment, so don't
  ask for a password, a client secret, or a connection string to be put there: it would never
  arrive.
- **A person can do what happens outside your sandbox:** add a service's key, make an account
  or a test project, change a setting, try one step and say what they saw. Get as far as you
  can first, then ask once, for all of it.
- **A protected preview is closed to you.** It asks for a Vercel login, which your browser
  can't do.
- **In a thread you start yourself, your GitHub access covers every repo the board brings in
  from one org,** this factory's own. A repo in another org can't be cloned there: work on it
  from the thread of one of its pull requests or issues.

When you find a way, show it once in the thread (a screenshot, what the command printed), and
write it down in the repo's `AGENTS.md`: what to run, what it needs, and what can't be tried.
The next thread starts from there.
