> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getpara.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Skill

> Give your AI coding agent full context on Para — setup, CLI, SDKs, and integration patterns

Give your AI coding agent everything it needs to set up and build with Para. Send it one message and it'll install the Para CLI, authenticate, save the skill for future sessions, and help you start building.

## Send This to Your Agent

Copy and paste this into Claude Code, Cursor, Windsurf, or any AI coding agent:

```text theme={null}
Fetch https://docs.getpara.com/skill.md and help me build with Para
```

Your agent will:

1. **Save the skill** so it remembers Para in future sessions
2. **Install the Para CLI** (`npm install -g @getpara/cli`)
3. **Authenticate** via `para login` (opens your browser)
4. **Ask what you want to build** and use `para` commands to do it

## What You Can Ask

Once your agent has the skill, try:

* *"Set up Para in my Next.js app with EVM and Solana"*
* *"Scaffold an Expo app with Para wallets"*
* *"Why isn't my Para integration working?"*
* *"Configure webhooks for user.created and wallet.created"*
* *"Rotate my production API key"*
* *"Add Google and Apple OAuth to my config"*

Your agent uses `para` CLI commands to handle everything — no portal needed.

## What's in the Skill

The skill file at [`docs.getpara.com/skill.md`](https://docs.getpara.com/skill.md) teaches your agent:

| Area                  | What the agent learns                                                                 |
| --------------------- | ------------------------------------------------------------------------------------- |
| **CLI commands**      | All `para` commands — auth, orgs, projects, keys, config, scaffolding, diagnostics    |
| **Key configuration** | Security, branding, wallet setup, webhooks, and ramp settings via `para keys config`  |
| **SDK packages**      | Which `@getpara/*` packages to install for React, Viem, Ethers, Solana, Cosmos        |
| **Integration steps** | ParaProvider setup, CSS import, env var naming per framework, "use client" directives |
| **Diagnostics**       | What `para doctor` checks and how to interpret results                                |
| **Environments**      | Beta vs prod key management and config resolution                                     |