prava CLI does the work; skills tell the agent when to call what. A skill is a small
instruction file installed into the agent’s runtime that encodes the correct flow, the pacing, and the
safety stops, so the agent invokes setup, sessions, and shop commands in the right order and
pauses for the user’s approval before spending.
The CLI works without any skill: every
prava command runs on its own. The skill adds the
guidance: which command comes next, when to stop and confirm, and how to keep the user in control.
If the matching skill is missing, the CLI nudges you (once) to install it.Why skills matter
Left to itself, an agent might chain commands or spend without checking. Skills prevent that by encoding:- One decision per turn: after
search, wait for the user to pick; afterproduct, wait for them to confirm the seller/variant; afterquote, wait for them to approve the total. - Confirmation hard-stops: the agent must present the merchant, item, and final amount and get an
explicit “yes” before
sessions create/checkout. “Buy me X” is intent, not price approval. - PII masking: the agent works with masked address summaries only; full details stay server-side.
- Move promptly: card credentials are single-use and short-lived, so mint → poll → checkout without pausing.
The skills
Install a skill
Install into the agent’s global skills directory (e.g.~/.claude/skills/<name>/SKILL.md):
--skill names: prava-pay, prava-shopping, prava-sdk-integration, swiggy-prava-skill,
zepto-prava-skill.
Keeping skills current
The CLI checks your installed skill version on every call. If it’s behind the server minimum, it prints:Platforms
Skills work across coding agents: Claude Code, Cursor, Codex, Gemini CLI, Hermes, and many more. The agent’s platform is set with--platform when you run
prava setup.
Next steps
Link an agent
Connect and approve the agent before it can pay.
Agentic shopping
The search → quote → checkout flow the shopping skill guides.