Individual skill
assets
Locate, inspect, and read content-addressed workspace assets — search by filename/metadata, describe before reading bytes, then read bounded ranges. Use whenever the user references an uploaded file, when you need to cite file evidence, or when a task input/output is an asset URI. Executes via the `cloud asset` CLI and tools.
sdk/cloud/catalog/skills/assets/SKILL.md
Source commit f83b859a173802a73d978197e92328ab2bf57a6e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,364
- Repository last updated
- Oct 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-communication Repository topic
- agent-memory Repository topic
- ai-agents Repository topic
- claude Repository topic
- cursor Repository topic
- docker Repository topic
- knowledge-base Repository topic
- llm-tools Repository topic
- mcp Repository topic
- mcp-server Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Assets
Workspace assets are **content-addressed** (SHA-256). Each asset has a stable URI, MIME type, size, and metadata. Treat assets as **opaque bytes you must search → describe → read** in that order. Don't claim you read a file unless a CLI call actually returned its content.
## When to use
- The user references a file by name, path, or `prismer://...` URI and you need its content.
- A task description includes asset attachments — find them, inspect them, decide if you need to read bytes.
- You're answering a question that requires citing file evidence (extract text, quote a paragraph, summarize a doc).
- You need to find a file by hash, filename, or content keyword.
## CLI Reference
### Search