Qonto Crew Onboard

Every new hire triggers the same manual ritual: invite them on Qonto, create their card with the right caps, prepare their first day. This skill turns it into one sentence. Read-heavy, a few explicit writes: every write is individually confirmed, and anything sensitive stays behind the user's own SCA in the Qonto app.

Prerequisites

1. get_organization FIRST → organization, accounts, country. Then get_authenticated_membership → the requester's role. Inviting members and requesting cards require an Admin/Owner role: if the authenticated membership is weaker, say so honestly and degrade to a read-only preview of what would be done.
2. Country-agnostic: memberships, teams and cards work the same on every Qonto country (FR, DE, ES, IT, AT, NL, BE, PT). No fiscal logic here — nothing to degrade.
3. A per-role policy decided by the user — card type, monthly cap, online-only or not, team, e.g. "developer → virtual card, €200/month, online-only, team Tech". Defined once in conversation (or pasted from the user's notes). A role without a policy triggers questions, never a guess.

Workflow

1. Snapshot & permissions

get_organization → get_authenticated_membership (role check, honest warning if not Admin/Owner) → list_memberships (paginate per_page ≤ 50; count members, verify the email isn't already invited) → list_teams → list_cards.

2. Load the policy — never invent it

Ask for (or recall) the per-role policy: card type (virtual/physical), monthly spending cap, per-transaction cap if any, online-only flag, target team. Show it back as a table. Plan limits: ask the user which plan they're on, compare with the member count from list_memberships, and warn before inviting if the invitation could exceed the plan or carry a per-seat cost. Never state a price you didn't verify (get_qonto_public_pricing can help for public plan info).

3. Parse the sentence, then recap everything

"Alex starts Monday as a developer" → first name, role, start date. Ask for what's missing (at minimum the email address — required for the invitation, never guessed). Map role → policy. Then show ONE full recap table before any write: invitation (email, role granted on Qonto), team (existing or to create), card request (type, caps, online-only), welcome pack items. The user approves the plan as a whole, then each write is still confirmed individually.