cargo-content
The cargo-content skill provides commands for managing knowledge resources within a Cargo workspace. It enables users to upload, list, update, and remove files such as PDFs, CSVs, and text documents. It also supports the creation and management of native or connector-backed libraries for retrieval-augmented generation.
Is cargo-content safe to install?
Review the source first: our audit of cargo-content's source files found 16 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands via the cargo-ai CLI and interacts with local files for upload purposes.
How we audit skills: our security review methodology.
Who is this skill for?
Developers and users of the Cargo platform who need to manage knowledge bases and data sources for AI agent grounding.
What can you do with it?
- Upload local documents to a Cargo workspace for use in RAG.
- Organize uploaded files into libraries for agent reference.
- Sync external knowledge sources using connector-backed libraries.
- Update file metadata or library configurations.
- Remove obsolete knowledge files or libraries from the workspace.
How good is this skill?
Quality score: 5/10. The documentation is clear, provides specific command examples, and defines the scope of the content domain relative to other Cargo skills.
What does the skill file contain?
# Cargo CLI — Content Workspace **knowledge** management: upload and organize **files** (PDFs, CSVs, text) and group or sync them into **libraries**. These are the binary/grouped knowledge resources that ground agent responses (retrieval-augmented generation, RAG). > **New top-level domain (CLI ≥ 1.0.19).** Files and libraries moved out of the `ai` domain into the `content` domain — `cargo-ai content file …` and `cargo-ai content library …`. The old `cargo-ai ai file …` commands no longer exist; an `unknown command` error means you're on the old path. > For **attaching** a file or library t...
Frequently asked questions
How do I make uploaded files available to an agent?
You must attach the file or library UUID to the agent's draft release resources array using the cargo-ai skill and then deploy the draft.
Can I edit files directly in the workspace?
No. Uploaded files are read-only in the context runtime sandbox. You must use the content file commands to update or manage them.
What is the difference between a native and a connector library?
Native libraries consist of files uploaded directly to the workspace, while connector libraries sync data from external sources using an extractor slug.
Related skills
gws-workflow-email-to-task
17.9KUsers who manage tasks directly from their Gmail inbox via the command line
The gws-workflow-email-to-task skill converts a Gmail message into a Google Tasks entry using the gws CLI tool.
gws-workflow-meeting-prep
17.5KUsers who manage schedules and meeting preparation via the Google Workspace CLI
The gws-workflow-meeting-prep skill retrieves agenda, attendee, and document information for the next upcoming Google Calendar event.
wecomcli-meeting
10.7KUsers of the WeCom platform who need to manage their meeting schedules through an AI agent interface
The wecomcli-meeting skill provides management capabilities for WeCom meetings, including creating, listing, retrieving details, canceling, and updating meeting participants via the wecom-cli command-line tool.
apple-notes
2.3KmacOS users who want to manage Apple Notes via the terminal
The apple-notes skill provides an interface to manage Apple Notes on macOS using the memo CLI tool. It supports creating, viewing, editing, deleting, searching, moving, and exporting notes.