Skip to content
Skills Library
Programming · Tool integration

privy-cli

/privy-cli

Manage Privy developer accounts and apps from the terminal with the unofficial `privy` CLI (npm package @awesamarth/privy-cli). Use when the user wants to create, configure or inspect a Privy app; enable or disable login methods (email, passkeys, wallets, Google, Apple, GitHub, Discord, X/Twitter, Telegram, custom JWT and more); manage app users, wallets, policies, key quorums, webhooks, API credentials, clients, domains, integrations or Global Wallet settings; or read dashboard members and analytics. Not for signing transactions, funding wallets or agent wallets (that is Privy's separate @pri

Repository
privy-cli ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Manage Privy developer accounts and apps from the terminal with the unofficial `privy` CLI (npm package @awesamarth/privy-cli). Use when the user wants to create, configure or inspect a Privy app; enable or disable login methods (email, passkeys, wallets, Google, Apple, GitHub, Discord, X/Twitter, Telegram, custom JWT and more); manage app users, wallets, policies, key quorums, webhooks, API credentials, clients, domains, integrations or Global Wallet settings; or read dashboard members and analytics. Not for signing transactions, funding wallets or agent wallets (that is Privy's separate @pri

Original author description

Manage Privy developer accounts and apps from the terminal with the unofficial `privy` CLI (npm package @awesamarth/privy-cli). Use when the user wants to create, configure or inspect a Privy app; enable or disable login methods (email, passkeys, wallets, Google, Apple, GitHub, Discord, X/Twitter, Telegram, custom JWT and more); manage app users, wallets, policies, key quorums, webhooks, API credentials, clients, domains, integrations or Global Wallet settings; or read dashboard members and analytics. Not for signing transactions, funding wallets or agent wallets (that is Privy's separate @pri

How it works

  1. Setup
  2. Then let the CLI guide you
  3. Rules
Original SKILL.md headings · 31 lines, 328 words
SKILL.md preview
---
name: privy-cli
description: Manage Privy developer accounts and apps from the terminal with the unofficial `privy` CLI (npm package @awesamarth/privy-cli). Use when the user wants to create, configure or inspect a Privy app; enable or disable login methods (email, passkeys, wallets, Google, Apple, GitHub, Discord, X/Twitter, Telegram, custom JWT and more); manage app users, wallets, policies, key quorums, webhooks, API credentials, clients, domains, integrations or Global Wallet settings; or read dashboard members and analytics. Not for signing transactions, funding wallets or agent wallets (that is Privy's separate @privy-io/agent-wallet-cli), and not a replacement for Privy SDK code inside an app.
license: MIT
compatibility: Requires Node.js 22.18+, the `privy` command installed globally, an OS credential store (macOS Keychain, Windows Credential Manager or Linux Secret Service), and a human for first-time dashboard login.
metadata:
  author: awesamarth
  homepage: https://github.com/awesamarth/privy-cli
---

# Privy CLI

`privy` does from the terminal what you'd otherwise click through in the Privy dashboard. It signs in as a dashboard admin, outputs JSON and makes every change explicit. The CLI documents itself, so use it rather than guessing.

## Setup

1. Check it's installed: `command -v privy`. If not, ask the user before running `npm install -g @awesamarth/privy-cli`.
2. Check login: `privy auth status --remote` (read-only). The session is in the OS keychain, not env vars, so missing `PRIVY_*` variables don't mean the user is logged out.
3. If access has expired, `privy auth login` renews a saved session without human input. If it returns `LOGIN_REQUIRED` or there is no session, **stop and ask the user to run `privy auth login` in their own terminal**: it needs a browser CAPTCHA and an email code typed into a hidden prompt. Never ask for the code in chat.
4. Get real IDs from `privy accounts list` and `privy apps list`. Don't guess, and ask if more than one could match.

## Then let the CLI guide you

```sh
privy cli search "what the user wants"   # finds the right command
privy schema <command>                   # inputs, required confirmations, how it verifies
privy docs read <topic>                  # workflow guides, offline
```

Preview with `--dry-run` (offline) or `--diff` (reads live state, writes nothing), then run with `--yes` plus whatever confirmations the schema lists.

## Rules

- Only make the changes the user asked for. Confirmation flags confirm a request; they don't widen it.
- Secrets go through stdin only (`--body -`), never command arguments, chat or files.
- If a write fails or times out, read the current state before doing anything else. Never retry blindly; see `privy docs read recovery`.
- Refusals like `ACCOUNT_APPROVAL_REQUIRED` are real gates. Report them; don't work around them.
- Don't run `auth logout` or `auth login --replace` unless the user asks.
- It never signs transactions, moves funds, exports private keys or touches billing.

Versions

The database has no other skills named privy-cli.

Database snapshot: 13.11.2026 · package version 398a4388323b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90Privy
    Use when building wallet infrastructure, authentication systems, or financial applications. Reach for Privy when you need to create embedded wallets, manage user authentication, control wallet permissions with policies, execute transactions across blockchains, or build…
  • 100privy-webhooks
    Receive and verify Privy webhooks (auth and embedded-wallet infrastructure, delivered via Svix). Use when setting up Privy webhook handlers, debugging svix-signature verification, or handling events like user.created, user.wallet_created, transaction.confirmed, and wallet.funds_deposited.
  • 100integration-privy
    Add Privy authentication to a Solana Expo Android app on top of Mobile Wallet Adapter, using Sign-In-With-Solana. Use when installing @privy-io/expo, mounting PrivyProvider, logging a user in with useLoginWithSiws, linking a wallet to an existing Privy account, reading the Privy…
  • 95sodax-wallet-sdk-react-privy
    Granular skill for @sodax/wallet-sdk-react v2 email login with Privy only — the privy field on the EVM slot of SodaxWalletConfig, built with privy() from the @sodax/wallet-sdk-react/privy sub-path, which adds an "Email (Privy)" embedded wallet next to MetaMask and WalletConnect.…
  • 100nansen-wallet-manager
    Wallet management — create (local or Privy server-side), list, show, export, send, delete. Use when creating wallets, checking balances, or sending tokens.
  • 100use-user-controlled-wallets
    Build non-custodial wallets where end users retain control of their private keys via Circle's user-controlled wallets SDK. Supports Google, Apple, Facebook social login, email OTP, and PIN authentication with MPC-based key management. Covers wallet creation, token transfers,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.