Manage Your Cargo GTM Knowledge Base
Scattered buyer knowledge makes positioning and sales guidance difficult to maintain. This skill organizes Cargo workspace documents and connects personas, plays, objections, and evidence.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "cargo-context" from https://skillstore.io/skills/getcargohq-cargo-context.md and its manifest at https://skillstore.io/api/skills/getcargohq-cargo-context/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "cargo-context". Summarize our current Cargo context without making changes.
Expected outcome:
Using "cargo-context". Draft a Head of RevOps persona from approved notes.
Expected outcome:
Using "cargo-context". Plan a bootstrap from our company domain.
Expected outcome:
Documentation links, Markdown backticks, quoted heredocs, and workspace identity checks account for most alerts; no evidence found of malicious injection or exfiltration. Twelve temporary-file findings retain conditional overwrite, disclosure, or tampering risks on shared hosts. The bootstrap recipe also lacks per-file checks to enforce its promise not to overwrite existing knowledge.
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/getcargohq-cargo-context/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/getcargohq-cargo-context?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/getcargohq-cargo-context?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/getcargohq-cargo-context/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/getcargohq-cargo-context.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>getcargohq. (2026). cargo-context security audit report (audit version 1) [Author version 1.3.0]. Skillstore. https://skillstore.io/skills/getcargohq-cargo-context/audits/1@techreport{getcargohq-getcargohq-cargo-context-2026,
author = {getcargohq},
title = {cargo-context security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/getcargohq-cargo-context/audits/1},
note = {Author version 1.3.0}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cargo-context security audit report (audit version 1)"
version: "1.3.0"
type: report
authors:
- name: "getcargohq"
date-released: "2026-10-12"
url: "https://skillstore.io/skills/getcargohq-cargo-context/audits/1"
identifiers:
- type: other
value: "skillstore:getcargohq-cargo-context:audit:1"
description: "Skillstore immutable audit report identifier"
Document buyer roles, pains, preferred channels, and supporting objections using consistent templates and source links.
Review call-derived claims individually, propose evidence-backed updates, and check related plays for missing proof.
Confirm the client workspace, research its public domain, and draft missing company context before approved repository writes.
Browse my Cargo context and summarize existing personas, positioning, and plays. Do not change any files.
Read the persona template and draft a persona for [role] using [approved notes]. Confirm the workspace and request approval before writing.
Inspect the knowledge graph for unresolved references and plays without proof. Verify the response shape and propose fixes without editing files.
Prepare a bootstrap plan for [domain]. Confirm the workspace, estimate integration credits, cite sources, and skip existing paths. Request approval before writes.
Author
getcargohqLicense
MIT
Author version
v1.3.0
Skillstore revision
r1
Ref
5447d31045d6a29e1c5e3f18100c791012c02a2c
Maintenance freshness
10/13/2026
Usage
0 downloads · 0 views
File structure
Migrate cargo-cdk References to cargo-project
Existing cargo-cdk installations can retain an outdated skill name after a rename. This migration pointer identifies cargo-project as the replacement and documents the CLI naming change.
Manage Cargo Knowledge Files and Libraries
Scattered documents make workspace knowledge difficult to maintain. This skill guides Cargo CLI workflows to upload, organize, and manage knowledge files and connector-backed libraries.
Build and Configure AI Agents in Cargo
Configuring agents requires coordinating prompts, models, knowledge, tools, and releases. This skill guides Cargo configuration through documented CLI workflows and examples.
Format Markdown for Clearer Reading
by jimliu
Turn plain text or uneven Markdown into a structured document that readers can scan quickly. Preserve the author's content while improving headings, emphasis, lists, frontmatter, and typography.
Maintain a Verified Codex Knowledge Wiki
by phelan164
Codex guidance becomes stale, duplicated, and difficult to trace. This skill maintains a review-first wiki with source provenance, explicit knowledge states, safe paths, and deterministic linting.
Create Professional Markdown Documentation
by AutumnsGrove
Inconsistent project documentation makes installation, use, and contribution difficult. This skill supplies structured templates, formatting guidance, and local tools for maintainable Markdown.
Write Clear Metabase Documentation
by metabase
Technical documentation often becomes formal, vague, or difficult to scan. This skill helps Claude, Codex, and Claude Code write clear Metabase documentation with focused steps.
Create Structured Task Documentation
by 0xhiroki
Teams often lose task context when plans, requirements, and validation steps are scattered. This skill creates consistent task documents from repository context and templates.
Lint and Fix Markdown Documents
by 46ki75
Markdown files often drift from project style rules and become harder to maintain. This skill guides Claude, Codex, and Claude Code through markdownlint-cli2 checks, fixes, and clear reporting.