# Set up Wannalead

Wannalead gives your AI agent live LinkedIn capabilities — find who to contact,
understand why now, and send the message — from the user's own LinkedIn account,
over a workspace-scoped HTTPS API. Do this setup yourself; do not ask the user to
run terminal commands.

## 1. Install the CLI, agent skills and MCP

    curl -fsSL https://wannalead.co/launch.sh | bash -s -- --agent

This installs the `wannalead` CLI to `~/.local/bin`, adds the Wannalead skills to
Claude Code and Codex, and registers the MCP server. If `~/.local/bin` is not on
your PATH, add it.

## 2. Authenticate

Ask the user for their Wannalead API key (it starts with `wlk_`) and store it with
the CLI. Never print it, put it in a URL, or commit it to a repository.

    wannalead auth save -api-key wlk_...

No key yet? Send the user to https://wannalead.co/sign-in to create a workspace and
connect LinkedIn, then come back with the key shown at the end of onboarding.

## 3. Load the skills

Step 1 installed the Wannalead skills for Claude Code and Codex. Invoke the
core `wannalead` skill, then the `wannalead-onboarding` skill (Claude Code:
the Skill tool or `/wannalead-onboarding`; Codex: `$wannalead-onboarding`).
Onboarding is the non-bypassable first-use gate: it identifies the account and
builds the durable commercial context every later workflow relies on.

If those skills are not visible in this session (they were installed just now,
or your agent is neither Claude Code nor Codex), fetch them from the API and
follow them as if they were installed:

    wannalead skills get wannalead --full

This prints the core skill together with `wannalead-onboarding` and
`endpoints`. Without the CLI, read the skill URLs and the machine index listed
under Reference.

## 4. Run onboarding

The first authenticated call must be:

    wannalead me

Then follow `wannalead-onboarding`: inspect the workspace context it names for
the returned LinkedIn identifier, initialize or resume it, and only then move
on. Before any business call, inspect the endpoint catalogue and the exact
OpenAPI contract for the endpoint you plan to use.

## 5. Offer the six use cases

Once onboarding is complete, ask the user which one to start with (the core
skill carries the full menu and the skill to load for each):

1. Lookalikes with signals: describe the ICP, get every lookalike profile with
   the signals that matter (tools in use, posts, job changes).
2. Campaigns: from the user's context and writing style, draft the messages and
   run sends and follow-ups.
3. Dormant conversations: revisit LinkedIn threads left without a reply and
   follow up on leads that went quiet.
4. Dormant network: surface first-degree connections never contacted and
   propose an approach.
5. Saved post to ICP: the user saves a post whose engagers look like the
   target; pull them and keep those matching the ICP.
6. Messy list to contacts: reconcile a rough CSV of companies with LinkedIn and
   list the people to contact in each.

## Reference

- Core skill: https://wannalead.co/.well-known/skills/wannalead/SKILL.md
- Onboarding skill: https://wannalead.co/.well-known/skills/wannalead-onboarding/SKILL.md
- Endpoints skill: https://wannalead.co/.well-known/skills/endpoints/SKILL.md
- Endpoint catalogue: https://wannalead.co/v1/endpoints
- OpenAPI contract: https://wannalead.co/openapi.json
- Machine index: https://wannalead.co/llms.txt

## Safety

Every LinkedIn write runs on the user's own account and is hard-capped well under
LinkedIn's own thresholds. Never send invitations or messages without the user's
explicit approval.