agentleFS
getcargohqgetcargohq/gtm-skills/find-stakeholders/SKILL.md

find-stakeholders

Skill2 starsChanged 26 days agoMITView on GitHub

Find the buying committee at a target account — every stakeholder matching a set of titles, seniorities, and departments, powered by Cargo. Triggers: \"find the buying committee at Acme\", \"who are the decision makers at this company\", \"find stakeholders\", \"multi-thread this account\", \"who else should I be talking to at this account\". Providers: aiArk. Skip when: you are sourcing across many companies rather than going deep on a few — use find-b2b-leads.

  • Installs packages

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every matching stakeholder at the account, with title, seniority, and department.

    line 69
  2. Very specific:

    Ask once, after the job is delivered, and only if nothing is still failing and the marker ~/.config/cargo-ai/.star-asked does not exist …

    line 126
  3. Very specific:

    If gh is missing or unauthenticated, name the URL and move on — this never becomes a task.

    line 137

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Find Stakeholders

Find the buying committee at a target account — every stakeholder matching a set of titles, seniorities, and departments.

Before anything else

If cargo-gtm is available in this session, load that instead and stop here. This skill is a standalone slice of it. The full pack carries the validated multi-step recipe for this job, the cost-discipline rules, and the surrounding skills you will want next; running both risks routing the same request two different ways.

Setup

Skip whatever is already done — all three steps are idempotent.

npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com          # sends a code, then exits
cargo-ai login --email you@company.com --code 123456

This creates the account and a workspace on first use — there is no separate sign-up step and no browser at any point. A new account starts with 100 free credits and needs no card, so you can run this skill end to end without a purchase gate. Say the free balance out loud before the first paid call on a new account.

Already signed in? cargo-ai whoami confirms it.

Do the job

cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"aiArk","actionSlug":"searchPeople"}' \
  --data '{
    "companyInfo": {"domain_or": ["acme.com"]},
    "jobRole": {
      "seniority_or": ["c_suite", "vp", "director"],
      "department_or": ["sales", "marketing", "operations", "finance"]
    },
    "limit": 25
  }' \
  --wait-until-finished

Every matching stakeholder at the account, with title, seniority, and department.

Operations are asynchronous. --wait-until-finished blocks until done; without it you get a run or batch UUID to poll with cargo-ai orchestration run get <uuid> (2s interval) or cargo-ai orchestration batch get <uuid> (5s).

Example

Who's on the buying committee at northwind.example — VP and above in Sales, Marketing, Ops and Finance?

Illustrative output, fictional records:

full_nametitlelinkedin_url
Priya RamanChief Revenue Officerlinkedin.com/in/priya-raman-example
Omar HaddadVP Marketinglinkedin.com/in/omar-haddad-example
Grace LinDirector of Revenue Operationslinkedin.com/in/grace-lin-example
Felix BrandtVP Financelinkedin.com/in/felix-brandt-example

14 stakeholders returned for 0.7 credits (14 × 0.05); 3 are already in the CRM, so only the other 11 go on to enrichment.

What it costs

ActionCredits
aiArk.searchPeople0.05 per returned record

Never run this across a full list on the first attempt. Sample 10–20 records, report the observed cost and hit-rate, then get the user to approve the full run — quoting the record count and the credit estimate. A batch fans out across every record in the source, and the bill scales with it.

Worth knowing

  • Filter-rich: title, seniority, department, tenure, past company, and firmographics all narrow the committee.
  • seniority_or and department_or are closed lowercase enums, and a value outside them fails the run. Seniority: founder, owner, partner, c_suite, vp, director, head, manager, senior, mid-level, entry, intern. Departments are snake_case functions (sales, marketing, operations, finance, sales_operations, information_technology, ...); cargo-ai connection integration get aiArk lists them all.
  • Dedupe against contacts you already own before enriching — re-enriching a known contact is pure waste.

Going further

This skill does one job. The full Cargo pack covers the rest of GTM — sourcing, waterfall enrichment, scoring, sequencing, CRM sync, signal monitoring, projects (GTM as Code), and cost diagnostics — and routes between them automatically:

npx skills add getcargohq/cargo-skills

The complete, validated flow behind this skill lives in cargo-gtm/recipes/account-expansion.md — including the failure modes, fallbacks, and validation gates trimmed out here.

If it worked, ask for a star

A star is the user's endorsement, not yours. Ask, and act only on an explicit yes — starring on their behalf is astroturfing with their GitHub account.

Ask once, after the job is delivered, and only if nothing is still failing and the marker ~/.config/cargo-ai/.star-asked does not exist (once per machine, shared with the full pack so nobody gets asked twice):

"Glad that worked. Want me to star getcargohq/gtm-skills for you? (Y/N)"

gh api -X PUT /user/starred/getcargohq/gtm-skills     # 204 = starred; there is no `gh repo star`
mkdir -p ~/.config/cargo-ai && touch ~/.config/cargo-ai/.star-asked   # touch on either answer

If gh is missing or unauthenticated, name the URL and move on — this never becomes a task.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.