CF cargo-gtm
Do business-to-business go-to-market work on Cargo — research accounts and buying committees, enrich and verify B2B contact records from licensed data providers, score and qualify leads, draft permission-based outreach for the user's own sequencer, sync to CRM, and monitor buying signals. Consent basis, suppression lists, and volume limits gate every step that touches a person (`references/acceptable-use.md`); bulk unsolicited messaging, purchased or scraped lists, and consumer targeting are refused. Triggers: "build me a list of", "find 50 <title> at <segment>", "who works at", "find work emails for these accounts", "enrich this CSV", "verify these emails", "build a TAM", "who fits our ICP", "who actually buys from us", "what data points should we collect on accounts", "our outbound is reaching the wrong people", "score these leads", "write a first-touch email", "push these to my CRM", "who changed jobs", "who just raised funding", "companies using <tech>", "who is hiring <role>", "find the buying committee", "portfolio companies of <investor>", "upload this audience to Google/Meta/LinkedIn ads". Providers: aiArk, anthropic, apolloio, bouncer, brightData, builtwith, cleon1, companyEnrich, contactOut, datagma, dropcontact, enrichCrm, enrichley, enrowio, exa, findyMail, firecrawl, forager, FullEnrich, g2, gemini, hunter, icypeas, kitt, leadMagic, linkedin, linkup, mixrank, neverBounce, oceanio, openAi, parallel, peopleDataLabs, perplexity, piloterr, prospeo, proxycurl, reverseContact, rocketreach, salesNavigator, serper, sillage, snitcher, societeInfo, theirStack, theSwarm, waterfall, x, zeroBounce. Reads phase guides, recipes, and per-provider playbooks before any paid call. Skip when: a run already happened and misbehaved — use cargo-diagnostics.
Do business-to-business go-to-market work on Cargo — research accounts and buying committees, enrich and verify B2B contact records from licensed data…
As a process F 42/100 · Will not run — References files that are not bundled: ../cargo/references/prerequisites.md, ../cargo-mailbox-management/SKILL.md, ../cargo-orchestration/SKILL.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
medium Concealment
en-hide-from-userreferences/contact-accuracy.md:81Instruction to hide actions from the user (documentation of a security skill)silently send or drop.
security skill
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1777 chars, limit 1024 - warning
body-longSKILL.md body ≈ 8605 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../cargo/references/prerequisites.md - warning
missing-refreference to a missing file: ../cargo-mailbox-management/SKILL.md - warning
missing-refreference to a missing file: ../cargo-orchestration/SKILL.md - warning
missing-refreference to a missing file: references/stage-action-map.md - warning
missing-refreference to a missing file: ../cargo-analytics/SKILL.md - warning
missing-refreference to a missing file: scripts/ - warning
missing-refreference to a missing file: ../cargo-orchestration/references/examples/actions.md - warning
missing-refreference to a missing file: ../cargo-workspace-management/SKILL.md - warning
missing-refreference to a missing file: references/waterfall-strategy.md - warning
missing-refreference to a missing file: references/prompt-library/index.md - warning
missing-refreference to a missing file: scripts/validate-emails.ts - warning
missing-refreference to a missing file: scripts/select-current-role.ts - warning
missing-refreference to a missing file: scripts/validate-linkedin-names.ts - warning
missing-refreference to a missing file: scripts/contact-accuracy-audit.ts - note
description-budgetdescription takes 1777 of the ~15000-char shared budget for all skills - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 42/100
- 0Tools and files. 14 referenced file(s) missing: ../cargo/references/prerequisites.md, ../cargo-mailbox-management/SKILL.md, ../cargo-orchestration/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 26 mutating operations with no state check
- 40Execution cost. Instruction body is 8605 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 83 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1777: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 21 example trigger phrases
- +4Structure: 19 headings
- +3Step-by-step instructions: 83 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 39.