| name | flow-team |
| description | Use when the user wants to work with Flow (flow.team) — reading or managing projects, tasks, schedules, todos, the calendar, team members, search, or alarms via the Flow Open API. Covers status checks ("what's on my plate", "any unread alarms", "this week's schedule"), creating and updating work (tasks, posts, schedules, calendar events), and team lookups. After reading state, proactively surface what needs attention (overdue tasks, unread alarms, today's events) and offer to act. |
Flow Team API Skill
Drive the Flow work-collaboration platform through its Open API.
This skill teaches an agent to read workspace state (projects, tasks, calendar,
team, alarms) and act on it (create tasks/posts/schedules/todos/events, update
task status & dates, manage the calendar) — and to propose next steps proactively.
Setup (once)
- The user issues an API key from Flow's 키관리 (Key Management) page.
- Put it in one place only: copy the repo-root
.env.example to .env and fill it:
FLOW_API_KEY=the-users-key
.env is gitignored — the key is never committed, printed, or shared. If
FLOW_API_KEY isn't set and no .env exists, ask the user to fill .env rather
than guessing or requesting the key in chat.
- All requests go to
https://api.flow.team with two headers:
Content-Type: application/json
x-flow-api-key: <from FLOW_API_KEY>
A ready-to-use client lives in scripts/flow.mjs (Node 18+, zero
dependencies). It auto-loads the repo-root .env. Run node scripts/flow.mjs me to
verify the key works.
