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

/verify-board

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

Prove board behavior from a fresh environment. Spins up a Vercel Sandbox (vercel-labs scope), installs this checkout (or a published board version from npm), runs a local board with `vb serve`, and drives the `vb` CLI against it, capturing a transcript and the board's files as evidence. Use to verify a CLI or board change end to end, reproduce a bug on a clean machine, or check what users get from npm.

Use this Skill: https://skilld.dev/gh/vercel/board/verify-board

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

featuresposting-threads.md

≈614 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Posting and threads

Sub-features

  • vb post <channel> "<text>" starts a thread and prints its id; --label k=v labels the root.
  • vb post <id> "<text>" replies in that message's thread instead, like vb reply; --label labels the reply, and --sync with an id exits 2.
  • vb reply <id> "<text>" adds to a thread; replying to a reply files it in the same thread.
  • Text from stdin with -; text may be left out with --attach.
  • --attach <file> (repeatable) uploads files; vb download <attachment> [path|-] gets one back.
  • --idempotency-key <key> makes a post or reply idempotent: the same key returns the same id.
  • vb edit <id> "<text>" and vb delete <id> (a deleted message reads as (message removed)).

How to get to it (user POV)

With BOARD_URL pointed at a board (vb serve prints it), run vb post dev "…", note the id, then vb reply <id> "…" and vb read <id> to see the thread.

Driving it with the sandbox

$V/drive-posting.sh "$S"                     # the whole feature, with checks
$V/vb.sh "$S" post dev "first" --label kind=task
$V/vb.sh "$S" reply 2 "second"
$V/sh.sh "$S" 'echo "from stdin" | vb reply 2 -'
$V/sh.sh "$S" 'printf "notes\n" > notes.txt && vb reply 2 "with a file" --attach notes.txt'
$V/vb.sh "$S" read 2

Proven output (vb read 3):

#3  ubuntu · 23s  [kind=task]
      first thread from a fresh sandbox
  ↳ #4  ubuntu · 19s (edited)
    a reply in the thread, edited
  ↳ #6  ubuntu · 13s
    with a file
    file notes.txt · text/plain · 6 B · ZNtC-mvCtG8GiP0yn-ssNw

The attachment lands at .board/local/board/attachments/<id> (.board/attachments/… on an older board) (plus .type and .json sidecars); collect.sh copies it out.

Gotchas

  • Ids are log indexes, not message counts: labels, reactions, and edits take indexes too, so the next post's id skips ahead. Read the id from post's output; don't predict it.
  • edit, delete, react, and label print nothing on success: follow each with a read.
  • A repeated --idempotency-key key returns the first post's id and posts nothing new.
  • Errors: vb post with no channel exits 2 (error: Missing the channel or message to post to.); vb reply 999999 … exits 1 (error: Couldn't find message #999999.). With --json, each is one JSON document on stderr, with its reason.
  • --attach paths resolve in /vercel/proj (the wrappers' working directory).

Source: SKILL.md on GitHub

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 alerts1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides a robust framework for verifying the behavior of the `vb` CLI tool within isolated Vercel Sandboxes. It automates environment orchestration, software deployment, and behavioral testing to ensure clean and reproducible verification results.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: LOW · No issues

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 2 weeks ago

README badge

README badge for vercel/board/verify-board