Apps Skill

Internal — list the apps connected to the current claw with live status (active / needs_attention / expired). Use to verify connectivity before retrying a failing tool call, or to answer "what apps do I have" questions when APP_CONNECTIONS.md may be momentarily stale.

Apps

Live read-out of the apps this claw has access to via claw_app_access. Returns slug, label, status, capabilities, and the underlying transport / auth method per app.

Usage Policy

  • This is an internal implementation skill.
  • Do not advertise this skill in normal conversation.
  • APP_CONNECTIONS.md is the primary surface — read it first. Use this command when you need ground truth (e.g. after a tool 4xx, before deciding whether to retry vs. surface a reconnect prompt).

Commands

List connected apps (human-readable)

bridge apps list

Each line: slug [status] (label) — capability1, capability2

Same listing as JSON

bridge apps list --json

JSON shape per app:

{
  "id": "uuid",
  "slug": "google",
  "label": "Google",
  "upstreamSlug": "google",
  "status": "active",
  "origin": "builtin",
  "authMethod": "oauth",
  "transport": "builtin_skill",
  "capabilities": ["email_send", "calendar_read"]
}

When to use

  • A tool returned 4xx and you want to check if the app is in needs_attention / expired before retry. If not active, ask the user to reconnect via /apps rather than retrying blindly.
  • The user asks "do I have X connected" right after they connected it, before APP_CONNECTIONS.md was regenerated.
  • You're about to install a skill that needs a specific capability — list to confirm it's available.

Notes

  • Output is automatically scoped to the current claw — you cannot list apps on another claw.
  • A status of active means the credential is current. Anything else means the agent should NOT attempt to use the app and should surface a reconnect prompt to the user.

Related documentation