Telara-Labs

TAP Runtime — Development skill for Claude Code

Development community

Run your coding agent's repeated work as small sandboxed programs that borrow its tools and ask before changing anything.

How to install TAP Runtime

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Telara-Labs/TAP-Runtime and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What TAP Runtime does

Run your coding agent's repeated work as small sandboxed programs that borrow its tools and ask before changing anything. Includes tap discover, which finds those procedures in your own agent history, locally.

Alternatives in Development

  • Build Program — Build Solana programs (Anchor, Pinocchio, native), incl 105 ★
  • Assess Project — DEPRECATED: Use /bootstrap-project instead 60 ★
  • Crucible Write — Draft novel prose scene-by-scene from Crucible outlines 58 ★

README

TAP Runtime

TAP (Trusted Agent Primitives) lets agents build their own internal tools as reusable blocks of code. We expect agents to write most of these primitives as they work. Humans can write them too.

People ask agents to get work done across source control, ticketing, CRM, and other company systems. A different project or account often needs the same procedure. Much like engineers build software for people, agents can put those repeatable steps in code, give them a defined interface, and call them again with new inputs. The code handles the procedure and returns a result or failure; the agent decides what to do next.

Read [Why TAP](WHY-TAP.md) for the thinking behind the project.

Quick start

npm install -g @telaralabs/tap     # the tap CLI
tap setup                          # connect it to the agents installed here
tap discover                       # what you keep asking your agents to do

No account, registry or server is needed. MIT licensed.

`tap discover` looks for reusable procedures in local agent histories and proposes primitives for review. To write one yourself, start with the [authoring guide](docs/writing-a-primitive.md) and [examples](examples/). A package contains `primitive.yaml` and an entrypoint (`main.sh`, `main.py`, `main.js` or `main.ts`). The runner executes it in a WebAssembly sandbox, using the host's tool connections and approval paths. Connected-tool execution is supported in Claude Code and Codex; see [Where it runs](#where-it-runs) for the other clients.

An example: checking a release

An agent could write a primitive that takes a repository, a candidate commit, and a set of release requirements, then:

  1. Finds the changes since the previous release.
  2. Retrieves the CI results for the candidate commit.
  3. Follows references to the work items and reviews associated with those changes.
  4. Handles pagination, matches records by their IDs, and checks the requirements.
  5. Returns the checks that passed, anything m