limrun-access-tokens — Claude Code skill: what it does, install
A Claude Code skill for creating and revoking Limrun access tokens. It activates for temporary instance, asset, device-installation, or service access and permission or lifetime choices.
MIT 1,300 installs ★ 2 updated 2026-10-23
npx skills add limrun-inc/skills --skill limrun-access-tokens -a claude-codeWhat limrun-access-tokens does
The skill manages Limrun access tokens through the CLI or TypeScript SDK. It helps select grants for tasks such as streaming from an instance or installing an asset on a physical device. Creating a token does not create an instance or asset.
CLI use requires lim login or LIM_API_KEY; install the CLI with npm install --global lim if needed. The caller must hold accesstoken:*:all plus every permission being delegated. A token cannot grant more permissions than its creator has.
CLI and SDK tokens can have a lifetime from 1 to 14,400 seconds; the default is one hour. Revocation does not close existing connections, and instance endpoints keep accepting a token until it expires or the instance ends.
What it helps with
- grant a client temporary access to an instance
- limit a token to interactive instance streaming
- combine asset access with physical-device installation
- revoke a token using its ID or token value
Example prompts for the agent
- Create a 900-second token for streaming from instance
$INSTANCE_ID. - Give the client full control of the instance with the required permissions.
- Revoke this Limrun token using its ID.
How to install limrun-access-tokens
1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-access-tokens -a claude-code2Manually: put the files in place
~/.claude/skills/limrun-access-tokens/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/limrun-access-tokens/
1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-access-tokens -a codex2Manually: put the files in place
.agents/skills/limrun-access-tokens/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-access-tokens -a cursor2Manually: put the files in place
.cursor/skills/limrun-access-tokens/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install limrun-inc/skills skills/limrun-access-tokens2Manually: put the files in place
.github/skills/limrun-access-tokens/SKILL.md1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-access-tokens -a gemini-cli2Platform CLI
gemini skills install https://github.com/limrun-inc/skills --path skills/limrun-access-tokensManually: put the files in place
.devin/skills/limrun-access-tokens/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-access-tokens -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about limrun-access-tokens
How do I install limrun-access-tokens in Claude Code?
Run npx skills add limrun-inc/skills --skill limrun-access-tokens -a claude-code. The skill file is installed at ~/.claude/skills/limrun-access-tokens/SKILL.md.
What does limrun-access-tokens do?
It creates and revokes Limrun access tokens through the CLI or TypeScript SDK, with grants and lifetimes suited to the requested access.
What does limrun-access-tokens need to work?
CLI use needs authentication through lim login or LIM_API_KEY; install the CLI with npm install --global lim if necessary. The caller must have accesstoken:*:all and each permission being delegated.
Source text
SKILL.md · MIT
---
name: limrun-access-tokens
description: "Create and revoke Limrun access tokens through the CLI or TypeScript SDK. Use when delegating temporary instance control, interactive streaming, asset access, device installation, or service access, or choosing permissions and token lifetimes."
---
# Limrun access tokens
Mint an access token to give another client temporary access without sharing an
organization API key. Use the permission and lifetime needed for the requested
task. Creating a token does not create an instance or asset.
## Authentication
Use `lim login` or an existing `LIM_API_KEY`. Install the CLI if needed with
`npm install --global lim`. If a command or flag is unavailable, check
`lim access-token create --help` or `lim access-token revoke --help` and the
installed CLI version.
The caller needs `accesstoken:*:all` and must hold every permission it delegates.
An access token cannot expand the caller's permissions. Permission strings use
`resource:target:action`; the action wildcard is `all`, not `*`.
## Choose permissions
For an existing instance, use its returned ID exactly:
| Instance | Resource and ID prefix | Accepted actions |
| --- | --- | --- |
| iOS simulator | `ios`, `ios_` | `stream`, `all` |
| Android emulator | `android`, `android_` | `stream`, `all` |
| Xcode sandbox | `xcode`, `sandbox_` | `all` |
| Gradle sandbox | `gradle`, `gradle_` | `all` |
`stream` permits interactive streaming, including touch and typing. Give the
client the token and `status.endpointWebSocketUrl`. It cannot install or
explicitly launch apps, use the device API or ADB, or fetch the instance record.
`all` permits full control through the instance's endpoints, including streaming
where supported. Give a device or build client the token and `status.apiUrl`.
Have the trusted backend supply the endpoint URL alongside either token; access
tokens are not a replacement for an API key across all SDK methods.
Instance grants require a concrete ID. They do not grant organization-wide
listing, instance creation, deletion, or role updates. Access-token create
rejects instance `read`, `work`, and `tunnel` actions; the latter two belong to
specialized build and private-tunnel flows.
Other accepted grants include:
| Permission | Purpose |
| --- | --- |
| `asset:<target>:<action>` | Asset access. Targets can be an asset ID, `name/<name-or-pattern>`, or `*`. Actions are `read`, `create`, `upload`, `update`, `delete`, and `all`; `create` requires a name target or `*`. |
| `device:*:install` | Physical-device installation; also needs `asset:<target>:read` for the asset. |
| `applerelay:*:connect` | Apple Account authentication relay access. |
| `remotecache:*:read` or `remotecache:*:all` | Read the organization's Bazel cache, or read and write it. |
| `remoteexecution:*:all` | Execute actions through the organization's Bazel service. |
For asset pattern delegation, organization roles, or workload-role permissions,
consult [Permissions and access tokens](https://docs.limrun.com/docs/reference/permissions).
Workload roles grant asset access from inside an instance; they do not grant
another client control of it.
## Create and revoke with the CLI
```bash
lim access-token create \
--permission "ios:$INSTANCE_ID:stream" \
--ttl-seconds 900 \
--json
```
Use `all` for full instance control. Repeat `--permission` to combine grants,
for example an asset read permission and `device:*:install`.
The JSON response includes `id`, `token`, `permissions`, and `expiresAt`.
Save `id` for revocation and pass `token` to the intended client.
`--quiet` prints only the token; `--quiet --json` keeps the JSON response.
```bash
lim access-token revoke "$TOKEN_ID"
# Or pass the token itself:
lim access-token revoke "$ACCESS_TOKEN"
```
CLI revocation accepts the returned ID or the `lim_st_...` token value. It
extracts the token's JWT `jti` and sends only that ID, authenticated with your
API key or login. Tokens without a `jti`, including `status.token` and
`status.streamToken`, cannot be revoked this way. Output contains the resolved
ID, not the supplied token. Repeating a revoke call is safe. A failed request
is not confirmation of revocation.
## TypeScript SDK
```ts
import Limrun from '@limrun/api';
const lim = new Limrun(); // Reads LIM_API_KEY.
const access = await lim.accessTokens.create({
permissions: [`xcode:${instance.metadata.id}:all`],
ttlSeconds: 900,
});
// Give the build client instance.status.apiUrl and access.token.
// When the credential is no longer needed:
await lim.accessTokens.revoke(access.id);
```
The SDK revoke method takes an ID. Use `accessTokens` and `permissions` in new integrations. For REST, the matching
routes are `POST /v1/access_tokens` and `DELETE /v1/access_tokens/{id}`;
authenticate with the API key in the Authorization Bearer header.
## Lifetime and revocation
Tokens created with an API key or CLI login default to one hour.
`--ttl-seconds` and `ttlSeconds` accept integers from 1 through 14,400.
The management and registry APIs check revocation after it propagates. Instance
endpoints verify tokens offline and continue accepting them until expiry or
instance termination. Revocation does not close existing connections or
terminate the instance. Choose the lifetime with these limits in mind.
© limrun-inc · MIT · limrun-inc/skills