Menu
Inspect, snapshot, publish, and fork Prismer long-running agents through the cloud agent lifecycle API.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | agent-meta |
| description | Inspect, snapshot, publish, and fork Prismer long-running agents through the cloud agent lifecycle API. |
| allowed-tools | cloud.agent.spec cloud.agent.snapshot cloud.agent.snapshots cloud.agent.restore cloud.agent.publish cloud.agent.packs cloud.agent.fork prismer.agent.snapshot prismer.agent.publish prismer.agent.fork |
| metadata | {"prismer":{"category":"workflow-core","version":"1.0.0"}} |
Use this skill when the user asks you to inspect, save, restore, publish, or fork a Prismer long-running agent.
Inspect your 4-tuple spec:
cloud agent spec <agent-id>
Save a private owner snapshot:
cloud agent snapshot <agent-id> --label "<label>"
Save a snapshot with memory reference:
cloud agent snapshot <agent-id> --include-memory --label "<label>"
List snapshots:
cloud agent snapshots <agent-id>
Restore from a snapshot:
cloud agent restore <agent-id> <snapshot-id>
Publish an agent pack without memory:
cloud agent publish <agent-id> --slug <pack-slug> --version 1.0.0 --license proprietary
List public agent packs:
cloud agent packs
Fork a pack into a workspace:
cloud agent fork <pack-id-or-slug> --workspace-id <workspace-id> --display-name "<name>"
The runtime CLI has the same operational verbs for daemon environments:
prismer agent snapshot <agent-id>prismer agent publish <agent-id> --slug <pack-slug>prismer agent fork <pack-id-or-slug> --workspace-id <workspace-id>Find other agents, list participants in a conversation, send routed messages, attach files, and recover earlier conversation context (history / resolve a fuzzy reference / read a quoted message / read compressed summaries). Use whenever you need to delegate to another agent, address a peer in a multi-agent conversation, send a message that carries a file, or pull context that scrolled out of your prompt window. Executes via `cloud discover`, `cloud im conversations`, `cloud send`, `cloud file send`, `cloud conversation history|resolve-identifier|summary`, and `cloud quote read` CLIs.
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.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Orchestrator skill for resolving multi-daemon binding contention. Use when you (the orchestrator) detect an `agent.binding.contested` sync event indicating two daemons are racing for the same agent โ explicitly rebind ownership to a chosen target daemon so subsequent dispatches route deterministically. Implements Gap G-2-โค on top of the Wave 2-B2 `/api/im/agent-bindings/:agentImUserId/rebind` endpoint.
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 โ 4.6, 4.6 โ 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project. SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action โ submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs / generating files / summarising chats / answering questions / explaining concepts / read-only tool calls) โ those are pre-authorized; just produce the output. The 5-minute-rollback litmus test applies: if the wrong outcome can be undone in <5 minutes by editing or deleting, it is NOT approval-eligible. Routine misuse (intro/explain/summarise/file-generation) burns the user's attention budget and is a contract violation. Executes via `cloud approval` CLI.