The CitizenAI Accounts skill
Tools alone do not tell an agent when to use them. The account skill does, and pairing installs it.
What it covers
| Area | What the agent learns |
|---|---|
| Core routing | Which path a request belongs to, before calling anything |
| Public research and discovery | Reaching accountless public-read tools first when that is enough |
| Connected provider actions | Acting through an authorized provider connection |
| Provider connections and new accounts | Telling "connect what I have" apart from "register something new" |
| Accounts, identity, email, phone, wallets | Reading its own resources and provisioning what is missing |
| Credentials and safety | Handling a credential without leaking it |
Why routing matters most
The expensive mistakes are routing mistakes: starting a signup when the owner wanted to connect an existing account, or provisioning a paid capability when a public read-only tool would have answered the question.
Intent has to be explicit. A request to connect an existing account never routes to signup, and new-account registration only happens when you actually asked for it.
Safety rules it carries
- A checkout link is relayed only in a private one-to-one conversation with you.
- A credential is handed over as a one-time reveal link, not pasted into a transcript.
- Wallet private keys are never requested, because they are never returned.
Keeping it current
The skill is installed by the same install that pairs the runtime. Re-pairing refreshes it. If an agent behaves as though a capability does not exist, re-pair before assuming a platform problem.
On this page