Menu
Check Covia venue health — adapters, registered operations, active agents, workspace contents. Use for a quick overview of venue state.
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
Create, configure, and manage Covia agents. Handles config gotchas, system prompts, LLM backend setup, and lifecycle operations. Use when working with agents on a venue.
Demo cross-venue federated operations — invoke operations on remote venues, show distributed audit trails. Use for demonstrating Covia's federation capabilities.
Issue and manage UCAN capability tokens — delegate access to workspace, agents, secrets, and operations. Use for demonstrating or configuring Covia's authorisation model.
Set up and run the AP Invoice Audit Trail demo. Creates three agents (Alice, Bob, Carol) on a Covia venue, seeds reference data, and runs an invoice through the pipeline. Use when the user wants to demo or test the AP workflow.
Manage secrets on a Covia venue — store API keys and credentials. Use when setting up LLM providers or other integrations that need secrets.
Store, retrieve, list, and manage content-addressed assets on a Covia venue. Assets are immutable resources — operations, artifacts, agent definitions, orchestrations — identified by the SHA3-256 hash of their metadata. Use when working with any venue asset.
| name | venue-status |
| description | Check Covia venue health — adapters, registered operations, active agents, workspace contents. Use for a quick overview of venue state. |
Prerequisite: The venue must be running and connected as an MCP server (http://localhost:8080/mcp). If MCP tools are not available, tell the user to run /venue-setup local first.
Check the current state of the connected Covia venue. Run these in parallel:
covia_list path=v/info/adapters — list all registered adapters and operation countsagent_list — list all agents with statuscovia_list — describe the top-level namespace structurecovia_list path=v/ops — count operations available in the venue catalogPresent a clean summary:
Venue Status
============
Adapters: <count> registered (<names>)
Operations: <count> available
Agents: <count> (<statuses>)
Namespace: <top-level keys>
If agents exist, show a table with agent ID, status, timeline length, and pending task count.
If the workspace has data, show the top-level keys under w/.