From arcade
Lists connected apps, disconnects them, and guides users through one-time sign-in flows for Arcade integrations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/arcade:managing-arcade-appsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```text
Arcade_Apps(action: "list") # all apps + connected state + account
Arcade_Apps(action: "disconnect", app_id: "...") # remove one app (confirm first)
Use apps language: app, connected, not connected, permissions, sign in, disconnect. Avoid authorization, OAuth, scopes, provider, token.
Call Arcade_Apps(action: "list") and show each app, whether it's connected, and
the account it's connected as. Connected apps first, then not connected. Don't
show internal ids or raw permission strings.
Call Arcade_Apps(action: "disconnect", app_id: "<id from list>"). Confirm with
the user first — disconnecting removes Arcade's access to that app. Report the
outcome plainly.
The first time a task needs an app the user hasn't connected, a tool returns a one-time sign-in link:
npx claudepluginhub arcadeai-labs/omnimcp --plugin arcadeCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.