Skip to content

quickstart.md

Latest commit

 

History

History
65 lines (42 loc) · 2.49 KB

quickstart.md

File metadata and controls

65 lines (42 loc) · 2.49 KB
Raw

Quickstart (live browser automation)

Day-to-day, the simplest flow is:

make browser
make cron

That will:

  • Start Chrome (if not already running) with a dedicated profile and CDP port.
  • Start the cron scheduler (connection sync + conversation planning sweeps).

install.sh starts Chrome and registers cron auto-start (launchd/systemd); after reboot, cron restarts at login automatically.

Then log into LinkedIn in the Chrome window (first time per profile) and use either:

  • Claude CLI (recommended for installation)
    • make claude-install — default: --scope user MCP + sync skills to ~/.claude/skills
    • make claude-install LOCAL=1 — --scope local MCP only; skills stay under outreach/skills/ in the repo
  • Claude + MCP tools for interactive outreach
  • Cron scheduler for unattended sync and follow-up planning

Live mode checklist

  1. Start Chrome with debugging (from the repo root):

    make browser

  2. Sign in to LinkedIn in that Chrome window.

  3. Start the scheduler (if not already running from install):

    make cron

  4. Use Claude with the MCP tools as usual.

If Chrome is not running with remote debugging, live tools will fail until make browser (or an equivalent launch) is used.

First-run profile setup

Before sending outreach, configure who the planner speaks as:

  1. In Claude Code, run /setup-outreach (or ask to “run setup-outreach”).
  2. The skill checks your browser session, **scrape_profile**s your signed-in LinkedIn profile, and drafts persona + organization.
  3. Review the draft, request edits, then approve — the skill persists via merge_conversation_planner_identity to outreach/config/persona.json.
  4. Optionally tune campaign goal/topic in the same wizard.

See Claude skills — setup-outreach and Conversation planner config.

Example usage

  1. /setup-outreach — configure operator profile (recommended first step).
  2. Connect to <linkedin-url>.
  3. Is <linkedin-url> my connection?
  4. Add Run conversation planner skill as a scheduled task.

Mock mode (optional, no browser)

The core MCP server (tools/server.py) is live-only. For scripted tests without a browser, use the mock-capable MCP server and fixtures under testing/: set OUTREACH_MOCK=1 and register testing/tools/server.py instead. See testing/README.md for the dev dashboard and regression suite.