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

# Skills for AI Agents

> Agent Skills that teach AI coding assistants (Claude Code, Cursor, etc.) how to use Sixtyfour — people and company intelligence at scale.

## What are Agent Skills?

The [sixtyfour-ai/skills](https://github.com/sixtyfour-ai/skills) repo packages Sixtyfour as an Agent Skill — a single directory of instructions that teaches an AI coding assistant how to use the Sixtyfour API correctly.

## Prerequisites

1. Have an AI coding assistant installed (Claude Code, Cursor, etc.).
2. Sign up at [app.sixtyfour.ai](https://app.sixtyfour.ai).
3. Generate a key by following [Get an API Key](/get-api-key).
4. Set `SIXTYFOUR_API_KEY` in your agent's shell.

```bash theme={null}
export SIXTYFOUR_API_KEY=YOUR_API_KEY
```

## Install

You can install the Sixtyfour skills from [Smithery](https://smithery.ai/skills/sixtyfour/sixtyfour-intelligence), from the [Cursor Plugin Directory](https://cursor.directory/plugins/sixtyfour), or manually from the [sixtyfour-ai/skills](https://github.com/sixtyfour-ai/skills) repo.

### Smithery

Install via the [Sixtyfour Intelligence skill on Smithery](https://smithery.ai/skills/sixtyfour/sixtyfour-intelligence). Pick your client on the Smithery page and follow the one-line install command it generates — Smithery handles registering the skill with Claude Code, Cursor, and other supported clients.

### Cursor Plugin Directory

The skill is also listed in the [Cursor Plugin Directory](https://cursor.directory/plugins/sixtyfour). Open the listing and use the install button to add it to Cursor directly.

### Manual install

<Note>
  The Sixtyfour Agent Skills are not yet available in the Claude Code marketplace. For now, follow the instructions below to install manually.
</Note>

<CodeGroup>
  ```bash Claude Code theme={null}
  npx skills add sixtyfour-ai/skills --skill "sixtyfour"
  ```

  ```bash Cursor theme={null}
  mkdir -p ~/.cursor/plugins/local
  git clone https://github.com/sixtyfour-ai/skills.git \
    ~/.cursor/plugins/local/sixtyfour
  ```

  ```bash Manual theme={null}
  git clone https://github.com/sixtyfour-ai/skills.git
  cp -r skills/skills/sixtyfour <your-agent-skills-dir>/sixtyfour
  ```
</CodeGroup>

After cloning into Cursor, open the Command Palette (`Cmd+Shift+P` on macOS, `Ctrl+Shift+P` on Windows/Linux) and run `Developer: Reload Window`. Then open **Cursor Settings → Plugins** and confirm Sixtyfour appears with a **Local** badge and 1 skill.

## Usage

Once installed, your agent can:

* **Investigate people** — "Tell me everything about Jane Doe at Acme Corp — title, background, LinkedIn, career trajectory"
* **Research companies** — "Research Ramp — revenue, headcount, funding, engineering leadership"
* **Search at scale** — "Find 500 VPs of Sales at Series B SaaS startups in NYC"
* **Build pipelines** — "Search for AI startups, find their CTOs, get contact info, and export to CSV"
* **Due diligence** — "Deep investigation on this person for compliance review" (medium/high tier)

## Troubleshooting

### API key not set

Check that the variable is exported in the same shell your agent runs in:

```bash theme={null}
[ -n "$SIXTYFOUR_API_KEY" ] && echo "set" || echo "not set"
```

If it's not set, generate a key at [app.sixtyfour.ai/keys](https://app.sixtyfour.ai/keys) and export it in the terminal that your agent runs in:

```bash theme={null}
export SIXTYFOUR_API_KEY=YOUR_API_KEY
```

Setting the variable in a different terminal window does not carry over.

### Environment variables don't persist in Cursor or VS Code

Cursor and VS Code don't always inherit shell environment variables — especially on macOS when launched from the Dock or Spotlight. Fix it one of three ways:

* Launch from a terminal that already has the variable set: `cursor .`
* Add the export to `~/.zshrc` or `~/.bashrc` so it's always available
* Add it to `.claude/settings.json` under `env`

### Locating `poll_job.py`

The polling script ships inside the skill's plugin cache. The agent knows where to find it, but if you need to run it manually:

```bash theme={null}
~/.claude/plugins/cache/sixtyfour-skills/sixtyfour/<version>/skills/sixtyfour/scripts/poll_job.py
```

Run it from that directory or pass the full path. It requires Python 3 and uses only the standard library.

### 429: too many concurrent searches

Deep search allows a maximum of 5 concurrent searches per org. If you hit a 429, wait for running searches to finish before starting new ones. Check the status of previous tasks with `GET /search/status/{task_id}`.

### 403 on high or xhigh tier requests

The `high` and `xhigh` research tiers require enterprise access. If you get a 403, book a call at [cal.com/team/sixtyfour/discovery](https://cal.com/team/sixtyfour/discovery). The `micro`, `low`, and `medium` tiers work on all plans.

### Results are empty or incomplete

* Bump `tier` from `"low"` to `"medium"`. The default single-pass lookup misses people with limited online presence or common names.
* For people intelligence, pass as many identifiers as possible in `lead_info`: `full_name`, `company`, `linkedin_url`, and `email` all improve matching.

### Deep search appears stuck

Searches take 30–120+ seconds while the agent runs. The `poll_job.py` script prints progress messages like `Analyzing your query...` and `Found X profiles` as it goes. Don't kill it early. If it hangs past 10 minutes, re-run with a fresh `start-deep-search` call.

### Output file is CSV, not JSON

Deep search results download as CSV. Parse them with `csv.DictReader`, not `json.load`. Columns include `fullName`, `currentPosition`, `currentCompany`, `linkedinUrl`, `skills`, `locationName`, and others.

### Signed download URLs expire

After a search completes, the download URL expires in 15 minutes. If you wait too long, re-poll the status endpoint — it issues a fresh `resource_handle_id` you can use to get a new signed URL.