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

# Skills

> Give your agent knowledge on how to set up and manage Latitude autonomously with our skills.

## Overview

The fastest way to add Latitude to an app is to let your coding agent do it. Latitude publishes a set of **[Agent Skills](https://github.com/latitude-dev/skills)** that teach an agent (Claude Code, Cursor, Codex, Windsurf, OpenCode, …) how to instrument your code, drive the [CLI](/getting-started/cli), and confirm that real traces arrive — following Latitude best practices.

There are two entry points, depending on whether you already have a Latitude account.

## The skills

All skills live in the public [`latitude-dev/skills`](https://github.com/latitude-dev/skills) repo. Most agents can install them with the `skills` CLI:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
npx skills add https://github.com/latitude-dev/skills --skill latitude-setup,latitude-cli,latitude-telemetry
```

| Skill                | What it does                                                        |
| -------------------- | ------------------------------------------------------------------- |
| `latitude-setup`     | Zero-account orchestrator: bootstrap → instrument → verify → claim. |
| `latitude-telemetry` | Adds Latitude / OpenTelemetry instrumentation to your app.          |
| `latitude-cli`       | Installs and drives the [`latitude` CLI](/getting-started/cli).     |

<Info>
  `latitude-setup` builds on the other two, so install all three together for the from-scratch flow.
</Info>

## No account yet

If you don't have a Latitude account, paste this prompt into your coding agent:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
Install the `latitude-setup` skill from `github.com/latitude-dev/skills`, and use it to add Latitude tracing to this app following best practices.
```

The `latitude-setup` skill orchestrates the whole zero-account flow:

1. Installs the [`latitude` CLI](/getting-started/cli) and the Latitude skills.
2. **Bootstraps a temporary account** — no signup — with an API key and a project.
3. Instruments your app (via the `latitude-telemetry` skill) against that project.
4. Runs your real code and inspects the resulting traces, iterating until they look right.
5. Cleans up the trace noise and hands you a **claim link**.

Open the claim link in your browser to take ownership of the temporary account and keep it. Unclaimed temporary accounts expire automatically.

<Info>
  The skill presents a plan and waits for your approval before it edits any code, and it never prints your API key in the chat.
</Info>

## Already have an account

If you're already signed in, skip the temporary account and point the agent straight at your existing project:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
Install the `latitude-telemetry` skill from `github.com/latitude-dev/skills`, and use it to add Latitude tracing to this app following best practices.
```

Give the agent your `LATITUDE_API_KEY` and `LATITUDE_PROJECT_SLUG` when it asks — or connect the [MCP server](/getting-started/mcp) so it can look them up — and it will instrument your app and verify traces the same way.

***

Once traces are flowing, head to the [telemetry guides](/telemetry/start-tracing) for provider-specific details, or the [CLI](/getting-started/cli) and [MCP server](/getting-started/mcp) pages to keep driving Latitude from your terminal or agent.