cargo-cdk
80Migrate 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 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.
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
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.에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
"cargo-context" 사용 중입니다. Summarize our current Cargo context without making changes.
예상 결과:
"cargo-context" 사용 중입니다. Draft a Head of RevOps persona from approved notes.
예상 결과:
"cargo-context" 사용 중입니다. Plan a bootstrap from our company domain.
예상 결과:
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.
이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.
버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.
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.
작성자
getcargohq라이선스
MIT
작성자 버전
v1.3.0
Skillstore 리비전
r1
참조
5447d31045d6a29e1c5e3f18100c791012c02a2c
유지보수 최신성
2026. 10. 13.
사용량
0 다운로드 · 0 조회
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.
Manage Cargo Workspaces as TypeScript Projects
Manual workspace changes are difficult to review and reproduce across environments. This skill guides TypeScript resource definitions, deployment previews, and state management with Cargo.
Connect Cargo MCP and Run Workspace Actions
Using Cargo through an AI client requires correct authentication, workspace selection, and action inputs. This skill guides hosted MCP connections, cost inspection, batch execution, and result reporting.
Markdown 아티클 포매팅
작성자 jimliu
초안에는 일관된 구조, frontmatter, 읽기 쉬운 타이포그래피가 부족한 경우가 많습니다. 이 스킬은 일반 텍스트나 거친 Markdown을 검토 준비가 된 체계적인 Markdown으로 변환합니다.
Maintain a Verified Codex Knowledge Wiki
작성자 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.
전문적인 Markdown 문서 작성
작성자 AutumnsGrove
팀에는 README 파일, 변경 로그, 기여 가이드 전반에서 일관성을 유지하는 명확한 프로젝트 문서가 필요합니다. Markdown Pro는 완성도 높은 기술 문서를 위한 템플릿, 구조, 보조 워크플로를 제공합니다.
Metabase 문서 작성
작성자 metabase
제품 문서는 종종 지나치게 격식적이거나 모호하거나 훑어보기 어렵게 됩니다. 이 스킬은 Claude, Codex, Claude Code가 명확하고 직접적이며 독자 중심적인 Metabase 스타일 문서를 작성하도록 돕습니다.
구조화된 작업 문서 만들기
작성자 0xhiroki
계획, 요구사항, 검증 단계가 흩어져 있으면 팀은 작업 맥락을 잃기 쉽습니다. 이 스킬은 저장소 맥락과 템플릿을 바탕으로 일관된 작업 문서를 만듭니다.
Markdown 문서 린트 및 수정
작성자 46ki75
Markdown 파일은 프로젝트 스타일 규칙에서 벗어나기 쉽고 유지 관리가 더 어려워질 수 있습니다. 이 스킬은 Claude, Codex, Claude Code가 markdownlint-cli2 검사, 수정, 명확한 보고를 수행하도록 안내합니다.