# 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.

## Install

```bash
npx skillstore add getcargohq/cargo-content
```

## Metadata

- Status: approved
- Slug: getcargohq-cargo-content
- Version: 1.0.1
- Author version: 1.0.1
- Skillstore revision: r1
- Version status: valid
- Tree hash: 15aa9f12b28964f451e38b5a25985bb277ab1f329dddc83c5ffaf942cef3e7a1
- Author: getcargohq
- GitHub username: getcargohq
- License: MIT
- Repository: https://github.com/getcargohq/cargo-skills/tree/92c825ad4ba1bbbbeff96ae85e62187279f3854d/cargo-content
- Ref: 077007320a82b1991f47e729817fc2936dbdd738
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/getcargohq-cargo-content
- Manifest: https://skillstore.pages.dev/api/skills/getcargohq-cargo-content/manifest

## Capabilities

- List and inspect Cargo knowledge files, including names, content types, sizes, and indexing indicators.
- Upload PDF, CSV, and text files to a Cargo workspace, optionally selecting a destination folder.
- Rename, move, and remove uploaded knowledge files using their Cargo identifiers.
- List and inspect native or connector-backed libraries, with filters for library kind and connector.
- Create connector-backed libraries using an existing connector, extractor, folder, and configuration.
- Update library names, remove libraries, and reference the documented upload, attachment, and deployment sequence.

## Use Cases

- Maintain Product Knowledge: Upload approved product documents, rename outdated labels, and organize files for later attachment to a support agent.
- Connect a Help Center: Create a knowledge library from an existing help-center connector and inspect the resulting library details.
- Review Workspace Content: Inspect file sizes, content types, and indexing indicators before planning agent knowledge updates.

## Prompt Templates

### List Knowledge Files

```
Confirm the active Cargo workspace, then list knowledge files with names, sizes, content types, and indexing indicators. Make no changes.
```

### Upload an Approved Document

```
Confirm my Cargo workspace, then upload ./product-docs.pdf as knowledge. Report the returned file identifier and explain whether agent attachment is still required.
```

### Organize Existing Files

```
List Cargo files and folders, then propose moving selected research documents into the Research folder. Ask for confirmation before changing names or locations.
```

### Prepare a Connector Library

```
Prepare a Cargo connector-backed library named Help Center. Request missing connector, extractor, folder, and configuration details; show the plan before creating anything.
```

## Limitations

- Requires the Cargo CLI, authenticated workspace access, and CLI version 1.0.19 or later for the documented content commands.
- Folder creation, connector setup, and agent release management belong to related skills.
- Uploading a file does not automatically attach it to an agent or guarantee retrieval readiness.
- The exact library response envelope is not specified; connector configuration depends on the selected extractor.

## Best Practices

- Confirm the active Cargo workspace and resource identifiers before uploading or modifying content.
- Upload only documents approved for the workspace, and confirm removal or deployment actions before execution.
- Inspect command responses and indexing indicators; use command help when connector configuration or response fields are unclear.

## Anti Patterns

- Assuming an uploaded document is automatically available to every agent.
- Using content uploads for batch-run input CSVs instead of the separate workspace-management upload surface.
- Guessing connector, folder, or file identifiers instead of discovering the correct workspace resources.

## Security Audit

- Audited at: 2026-10-12T17:15:15.98\+00:00
- Summary: All 61 static findings are false positives involving Markdown formatting, documentation links, Cargo resource identifiers, or legitimate workspace checks. No evidence found of prompt injection, unauthorized data transfer, or malicious execution in the reviewed files. The documented workflows require authenticated Cargo access and can upload, modify, or remove workspace content.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0