cargo-ai login --email (emailed code, no browser), --oauth, or an API token\nhomepage: https://github.com/getcargohq/cargo-skills\nmetadata:\nauthor: getcargo\nopenclaw:\nrequires:\nbins:\n- cargo-ai\ninstall:\n- kind: node\npackage: \"@cargo-ai/cli@latest\"\nbins:\n- cargo-ai\nhomepage: https://github.com/getcargohq/cargo-skillsOne guided demo: pull ~25 fresh leads matching a buyer persona the user picks, show the cost receipt, then save the pull as a recurring play. The point is not the list — it's that in minute 3 the user owns a running system, not a one-off result.
\nA new account starts with 100 free credits — no card. This demo spends about 0.5 of them. Say that out loud before the first paid call (\"this costs about half a credit of your 100 free ones\"): it converts the moment from a purchase decision into a look around, which is the whole job of a quickstart. Never let a new user think the demo is why they'd run out.
\nAlready signed in (cargo-ai whoami returns a workspace)? Skip to the next section.
npm install -g @cargo-ai/cli # no global install? prefix every command with `npx @cargo-ai/cli`\ncargo-ai login --email you@company.com # emailed code, no browser; creates the account on first use\n # alternatives: --oauth (browser) · --token <api-token> (CI)\ncargo-ai whoami # confirm the active workspace before any write\nEvery command prints JSON to stdout; failures exit non-zero with {\"errorMessage\": \"...\"}. Anything that creates a run or a batch is async — pass --wait-until-finished or poll the matching get. When the full skill bundle is installed, ../cargo/references/prerequisites.md adds the CLI version pin, token scopes, and the admin-only surface.
Ask exactly one question before doing anything:
\n\n\n\"Who do you sell to?\" (a persona in a few words — e.g. \"Heads of RevOps at mid-market SaaS\")
\n
Everything else — provider, filters, limits — you decide. Don't ask about output format, volume, or providers; defaults below.
\nThe demo has a two-minute budget from answer to deliverable. On the fast path:
\ncargo-ai --version, cargo-ai whoami, connection connector list, or any exploratory command first. Auth problems will surface as errors on the first real call — handle them then.salesNavigator.searchLeads, 0.02/record → 25 records ≈ 0.5 credits). Nothing else paid runs without asking.Translate the persona into a searchLeads filter (quote the exact title phrase in keywords; a bare keyword matches loosely and pollutes the page) and run:
# 1. Execute — returns a run object; note run.uuid and run.workflowUuid.\n# searchLeads returns a 25-row page minimum (limit below 25 still bills 25 × 0.02 = 0.5 credits).\ncargo-ai orchestration action execute \\\n --action '{\"kind\":\"connector\",\"integrationSlug\":\"salesNavigator\",\"actionSlug\":\"searchLeads\",\"config\":{}}' \\\n --data '{\"keywords\": \"\\\"<persona title phrase>\\\"\", \"limit\": 25}' \\\n --wait-until-finished > /tmp/quickstart-run.json\n\n# 2. Fetch the output data (NOT in the execute stdout) — signed URL, then filter to THIS run\nRUN_UUID=$(jq -r '.run.uuid' /tmp/quickstart-run.json)\nWF_UUID=$(jq -r '.run.workflowUuid' /tmp/quickstart-run.json)\ncurl -s \"$(cargo-ai orchestration run download-outputs \\\n --workflow-uuid \"$WF_UUID\" --output-node-slug action --format json | jq -r '.url')\" \\\n > /tmp/quickstart-outputs.json\n\n# 3. Show the table (the file holds ALL of the workflow's runs — filter by _uuid;\n# each row's .output is the leads array directly, fields are snake_case)\njq -r --arg u \"$RUN_UUID\" \\\n '[.[] | select(._uuid==$u)][0].output[] | [.full_name, .job_title, .company_name, (.recently_hired // false)] | @tsv' \\\n /tmp/quickstart-outputs.json | head -25\nShow the table (name · title · company · recently-hired), not the raw JSON. recently_hired: true rows are the demo's headline — lead with them (\"6 of these 25 just started the job — the exact moment to reach out\").
salesNavigator.searchLeads (0.02/record) — primary.theirStack.searchJobs (0.5) — reframe as \"companies hiring your persona right now\" (job postings for the persona's title). Same wow, different angle.waterfall.searchProspects (3/record) — exceeds the ~1-credit demo cap, so this rung asks first: \"The two cheap sources aren't connected; I can pull 5 matches via waterfall for ~15 credits instead — run it, or connect Sales Navigator first (free)?\" Run only on an explicit yes, with limit capped at 5.cargo-ai connection integration list | head, show what could be wired, and offer to connect one (browser auth) — the demo resumes after.The demo is itself the pilot from ../cargo-gtm/references/cost-discipline.md. Close it with a receipt:
cargo-ai billing subscription get — remaining = subscriptionAvailableCreditsCount − subscriptionCreditsUsedCount). For a brand-new account, frame it against the 100 free starting credits rather than as a bare number — \"0.5 spent, 99.5 of your 100 free credits left\" lands very differently from \"99.5 credits remaining\".Immediately offer to make the pull recurring — this is the step that shows what Cargo is:
\n\n\n\"Want this to run by itself? I can save this exact search as a play that runs weekly and writes new matches into a model — new
\n<persona>leads land without you asking.\"
On yes, follow ../cargo-gtm/recipes/save-as-play.md with the demo's action + filter as the workflow body and a weekly cron.
Propose 2–3 next steps grounded in the rows just pulled, per the next-step spec in ../cargo-gtm/SKILL.md (§4): e.g. \"enrich these 25 with firmographics (~0.5 cr each)\", \"find + verify emails for the best 10 (~1.4 cr each)\", or something else entirely. From here, real GTM work belongs to cargo-gtm — read it before anything beyond the demo.