> ## 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

export const Link = ({href, label, newTab = false}) => {
  const [isHovered, setIsHovered] = useState(false);
  return <a href={href} target={newTab ? '_blank' : '_self'} rel={newTab ? 'noopener noreferrer' : undefined} className="not-prose inline-block relative text-black font-semibold cursor-pointer border-b-0 no-underline" onMouseEnter={() => setIsHovered(true)} onMouseLeave={() => setIsHovered(false)}>
      {label}
      <span className={`absolute left-0 bottom-0 w-full rounded-sm bg-gradient-to-r from-orange-600 to-purple-600 transition-all duration-300 ${isHovered ? 'h-0.5' : 'h-px'}`} />
    </a>;
};

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

<Info>
  Want a command-by-command workflow for Claude or Codex? See <Link href="/v3/cli/agentic-development" label="Agentic Development with the Para CLI" />.
</Info>

## 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"*

After authentication, your agent can use `para` CLI commands for setup, API key configuration, diagnostics, and project context without manually navigating the portal.

## Safe CLI Workflow

Ask your agent to inspect first, then propose changes:

```text theme={null}
Use the Para CLI to inspect my current project.
Run para commands --json, para auth status --json, para whoami --json, and para keys config show --json.
Summarize the active organization, project, key environment, and API key configuration.
Ask before creating, rotating, archiving, or changing API keys or projects.
```

For a full setup, ask:

```text theme={null}
Use the Para CLI to finish my Para integration.
If the CLI is missing, install @getpara/cli.
Authenticate with para login, help me select the right org and project, configure the beta API key for local development, and run para doctor.
Use JSON output where the CLI supports it.
```

## 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                                     |