CAPABILITY · LIBRARY

A versioned library of the skills your agents compile

Every compiled skill is stored, versioned, and reusable — browse them, run them directly, and share them across your agents.

GET /api/v1/skills
Capability

What agent & skill library does

As your agents work, they build a library of compiled skills. Twin keeps that library organized: each skill is versioned, named, and runnable on its own, so a flow one agent figured out becomes a building block every agent can call.

Versioned skills

Each skill carries a stable id and version, so you can pin, roll forward, or audit exactly what ran.

Run a skill directly

Skills are first-class — invoke one by id with typed inputs from the API or over MCP, no goal needed.

Reusable across agents

A skill compiled by one agent is available to the rest, so your fleet stops re-solving the same flows.

Browse in the dashboard

See every skill, its versions, and recent runs in one place — with the session video for each.

How it works

From a goal to deterministic action

  1. 1CompileA successful run compiles into a named, versioned skill in your library.
  2. 2OrganizeSkills are stored per tenant with versions and run history.
  3. 3ReuseAny agent — or a direct API/MCP call — can run a skill by id with typed inputs.
  4. 4IterateReal drift bumps a version; you can pin to a known-good version anytime.
In practice

See it on a real call

Compiled skills are first-class: list the library and invoke any skill by id with typed inputs.

skills.tsts
// List the library
const skills = await twin.skills.list();
// → [ book-slot@v3, export-report@v2, … ]

// Run one directly, no planner
await twin.skills.run("export-report", {
  inputs: { range: "30d", format: "csv" },
});
api.twin-browser.com
  1. Compiledone
  2. Organizerunning
  3. Reusequeued
  4. Iteratequeued
At a glance

What agent & skill library is

The facts — how it works, what it costs, and the signal you get back on every call.

PropertyTwin Browser
UnitVersioned skill
InvokeBy id, typed inputs
SurfacesAPI, MCP, dashboard
SharingReusable across agents
HistoryRuns + session video
PinningPin to a version
FAQ

Agent & skill library — common questions

Can I run a skill without giving a goal?
Yes. Skills are first-class — call one by id with typed inputs from the API or over MCP and it replays deterministically.
How do versions work?
Each skill has a stable id and version. Real page drift bumps the version; you can pin to a known-good version at any time.
Can different agents share skills?
Yes. The library is per tenant, so a skill one agent compiles becomes a building block the rest of your fleet can call.

Put your agent to work — you stay in control.

Start free. Hand your agent a goal on any site you authorize, set the guardrails, and let it do the work — repeated runs compile into skills that replay at near-zero cost.