PlugWiki

cargo-connection Skill for Claude Code: Connect Cargo to Your Tools

Lets Claude connect Cargo to tools like HubSpot, Salesforce and Slack, browse the integration catalog and find the connector and action a workflow needs.

Installs
11K
on skills.sh
Stars
21
on GitHub
Files
5
besides SKILL.md
Updated
Oct 2026
last repo commit

Claude uses cargo-ai connection commands to list connectors, create one, update its rate limit and cache, and remove it. It also browses the integration catalog by category or name, reads an integration's documentation, and looks up the connector UUID and action slug a workflow node needs.

An integration is the service type, such as HubSpot. A connector is your signed-in instance of it. Creating a connector with only an integration slug opens a hosted form in your browser. It needs the Cargo CLI and a Cargo sign-in.

Good for

  • RevOps and GTM engineers wiring a CRM or sequencer into Cargo
  • Admins fixing a connector that keeps asking for credentials
  • Developers registering a custom integration on their own server

Install cargo-connection

Claude Code

  1. 1

    Copy this prompt.

    Install the cargo-connection skill in Claude Code. Run this command:
    
    /plugin marketplace add getcargohq/cargo-skills
    /plugin install cargo@cargo-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Every Cargo skill drives the cargo-ai CLI, so install it and sign in first. A new account starts with 100 free credits and no card (README). Pick one channel, not two: the plugin and skills add both register the skills, so using both duplicates them. The whole bundle is the route the README documents; this skill's own files point to files in sibling skills such as ../cargo/references/prerequisites.md. The plugin needs Claude Code 2.1.154 or newer and adds hooks and two subagents; see the safety section.

From the project README. Source.

What's in the skill

When it loads

Connect Cargo to an external system and find out what it can do — authenticate connectors, browse the integration catalog, and resolve the `connectorUuid` and `actionSlug` a workflow node needs. Triggers: "connect my HubSpot", "is Salesforce connected", "what integrations do you support", "can Cargo talk to <tool>", "what actions does <provider> have", "I need the connector UUID", "set up the API key for", "it is asking for credentials again", "why is this connector failing auth", "list my connectors". Integrations: amplemarket, amplitude, attio, bigQuery, calendly, cargoSignals, closecom, contrast, csv, customerio, dbt, emailBison, expandi, googleAds, googleCalendar, googleSheets, heyReach, http, hubspot, hubspotMcp, instantly, instantlyV2, intercom, jira, kitt, lemlist, lgm, linkedinAds, linkedinMatchedAudience, livestorm, manus, marketo, metaAds, metabase, microsoftTeams, mixpanel, monaco, netsuite, netsuiteSoap, nooks, notionMcp, octave, onesignal, outreach, pipedrive, postgresql, redshift, resend, rift, salesforce, salesforceMcp, salesloft, Sendgrid, sillage, slack, smartlead, snowflake, sql, stripe, xAds, and 87 more. Skip when: choosing between enrichment providers for a GTM job — use cargo-gtm and its provider playbooks.

Sections in SKILL.md

  1. Bootstrap
  2. Key concepts
  3. Discover resources first
  4. Which action search?
  5. integration get vs native-integration get
  6. Quick reference
  7. Connectors
  8. Integrations
  9. Custom integrations
  10. Connector autocomplete — fetching available values for action fields
  11. How to detect autocomplete fields
  12. How to call connector autocomplete
  13. Autocomplete with parameters
  14. Response format
  15. Dynamic schemas — fields whose shape depends on another value
  16. End-to-end example: configuring a HubSpot action

Key facts

Version
1.7.1
Installs on skills.sh
10,977 (Nov 2, 2026)
GitHub stars
21 (Nov 2, 2026)
Last commit
Oct 31, 2026

What it includes

  • Lists connectors, optionally by integration slug, or reads one by UUID.

    Runs code · connector list / get

  • Opens a hosted form, or takes a --config JSON plus a slug and name.

    Runs code · connector create

  • Renames a connector and sets a rate limit and cache time.

    Runs code · connector update

  • Removes a connector by UUID.

    Delete · connector remove

  • Fetches allowed values for an action field and dynamic schemas.

    Runs code · connector autocomplete

  • Searches the catalog by category, name or slug and reads its documentation.

    Runs code · integration list / get

  • Shows Cargo built-in actions and extractors, not third-party ones.

    Runs code · native-integration get

  • Registers, lists, updates and removes an integration you host over HTTP.

    Delete · custom-integration

From the official docs

Permissions

Medium risk

It changes which outside accounts your Cargo workspace can reach. Use the hosted form for secrets and check the workspace before any remove.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can add and remove connections to outside accounts

    connector create, update and remove change what your workspace can reach in tools like HubSpot or Salesforce. Check the connector UUID and the workspace name before a remove. github.com

  • Claude runs the cargo-ai CLI as you

    The skill drives the cargo-ai CLI. Sign-in is saved to ~/.config/cargo-ai/credentials.json, and the docs say to confirm the workspace with cargo-ai whoami before any write. github.com

  • The plugin route adds hooks that run shell commands

    The plugin wires a PreToolUse hook on Bash that auto-approves safe cargo-ai calls, and a SessionStart hook that runs npm install -g @cargo-ai/cli at the pinned version. Login, token creation, report creation, project deploy and any remove or delete still prompt. github.com

  • The plugin sends a session summary to your Cargo workspace

    The SessionEnd hook passes the last 60,000 bytes of the transcript to claude -p to write a title and summary, then stores them in your Cargo workspace session record. Use the skills CLI route if you do not want that. github.com

  • Non-interactive create takes credentials as arguments

    The --config form puts integration settings in the command line. Prefer the hosted browser form when the integration needs a secret. github.com

  • Custom integrations point Cargo at your server

    A custom integration registers an HTTP server for actions, extractors and autocompletes. Only register servers you control. github.com

  • The plugin also adds two subagents

    cargo-execution-planner and cargo-list-builder run on the haiku model with Read, Grep, Glob and Bash tools. The planner is described as read-only and the list builder as executing only pre-approved slices. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Talks toapi.getcargo.io (Cargo API). registry.npmjs.org (CLI install). app.getcargo.io (token creation)
Sign-in and keysSign-in by emailed code, browser (OAuth) or an API token. Browser and email sign-in save a session to ~/.config/cargo-ai/credentials.json; API tokens are workspace-scoped and the README says to store them in a secrets manager.
Scopes
  • Creates, updates and removes Cargo connectors and custom integrations

  • Cargo workspace sign-in (saved in ~/.config/cargo-ai/credentials.json)

Questions

What does cargo-connection do?

It lets Claude manage the links between Cargo and your other tools. It lists and creates connectors, searches the integration catalog and finds the connector UUID and action slug that a workflow node needs.

What is the difference between an integration and a connector?

SKILL.md defines an integration as the service type, such as HubSpot, and a connector as an authenticated instance of it. One integration can have several connectors, such as two HubSpot accounts.

Where do my credentials go when I connect HubSpot?

By default connector create with an integration slug opens a hosted form in your browser. The non-interactive form takes a --config JSON whose shape depends on the integration. OAuth integrations finish with a separate complete-oauth step.

Can it remove a connector?

Yes, connector remove <uuid> removes it. The plugin's approval hook always prompts for remove and delete commands.

Can I add an integration that is not in the catalog?

Yes, as a custom integration: an HTTP server that speaks Cargo's integration protocol. The base URL must be publicly reachable, and SKILL.md says private and loopback addresses are refused, so a local server needs a tunnel.

How do I install it?

Use the install box above. Install the whole Cargo bundle, then the Cargo CLI and sign in. The README says to pick one channel, plugin or skills add, not both.

Is it official?

Yes. It sits in Cargo's own repo (getcargohq/cargo-skills), the LICENSE names Cargo as the copyright holder and the plugin manifest lists Cargo as the author.

Does it work in the Claude app, Codex or Cursor?

The README names Claude Code, Codex, Cursor, Windsurf, GitHub Copilot and Hermes Agent. For Claude Desktop it documents a Claude Cowork plugin route with network egress turned on. The skill drives a local CLI, so there is no plain Claude app skill upload here.

Is it safe to use?

It changes which outside accounts your Cargo workspace can reach. Connector commands create, update and remove connectors, and the non-interactive create takes credentials as a --config JSON. Our advice: use the hosted form for secrets and check connector UUIDs before a remove.

Information

updated Nov 2, 2026

Folder
cargo-connection

getcargohq/cargo-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 7
  1. cargo-skills README · github.com
  2. cargo prerequisites.md · github.com
  3. cargo-connection SKILL.md · github.com
  4. cargo-skills LICENSE · github.com
  5. cargo-skills plugin.json · github.com
  6. session-end.sh · github.com
  7. session-start.sh · github.com

Updated Nov 2, 2026.