~/.claude/skills by hand and remembering which agent got what.
Tools ▸ Skills Manager (⇧⌘M) does that for you, per agent.
The window
The left column lists every agent FlowDeck supports — Claude Code, Codex, OpenCode, Cursor, and Grok Build — with what is installed for each. An agent that has never run on this Mac has no skills folder yet and reads Not detected; run it once and re-check. Selecting an agent shows two groups.Included with FlowDeck
Two skills ship with the app and install in one click:
The FlowDeck CLI Skill is what makes an agent drive FlowDeck properly instead of reaching for
xcodebuild and simctl. If an agent keeps calling Apple’s tools directly, this is the first
thing to check.
Installed Skills
Everything else in that agent’s skills folder, with its name, description, and version when the skill declares one. These are yours: FlowDeck lists them so you can see what an agent is carrying, and removes them on request.Adding your own
Add Skill in the header takes a.md file or a .zip archive and installs it into the
selected agent’s folder. FlowDeck asks for confirmation, names the skill and the agent, and
installs only for that agent — adding a skill to Claude Code does not add it to Codex.
Removing
Every row has a remove action, and every removal is confirmed. The two FlowDeck skills say they can be reinstalled at any time; your own skills say the removal cannot be undone, because FlowDeck has no copy of them to put back.Skills live in each agent’s own home folder —
~/.claude/skills, ~/.config/opencode/skills,
and so on — not inside FlowDeck. A skill you install here is available to that agent
everywhere, including when you run it from your own terminal.