Menu
Manage secrets on a Covia venue — store API keys and credentials. Use when setting up LLM providers or other integrations that need secrets.
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.
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.
Set up and run a Covia venue — locally for development, on a VM for testing, or containerised for production. Covers build, config, deployment, and troubleshooting.
| name | secret |
| description | Manage secrets on a Covia venue — store API keys and credentials. Use when setting up LLM providers or other integrations that need secrets. |
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.
Manage encrypted secrets in the venue's per-user secret store.
set <name> — Store a secretAsk the user for the value, then:
secret_set name=<NAME> value=<value>
Secret values are encrypted at rest and redacted in job records.
list — List stored secretscovia_list path=s
Shows secret names (not values). Values cannot be read back via MCP — they are resolved internally at invocation time.
delete <name> — Remove a secretcovia_delete path=s/<NAME>
Removes the caller's own secret — whole records only (s/<NAME>; deeper paths are rejected). Idempotent: deleting a name that doesn't exist succeeds silently. To rotate a secret, just set it again — no delete needed.
| Secret Name | Used By | Required For |
|---|---|---|
OPENAI_API_KEY | langchain:openai | LLM agents using OpenAI (gpt-4o, etc.) |
DEEPSEEK_API_KEY | langchain:openai (with custom url) | DeepSeek models |
GEMINI_API_KEY | langchain:openai (with custom url) | Google Gemini models |
langchain:openai adapter resolves OPENAI_API_KEY automatically from the caller's secret storeurl parameter in the agent's config to point to the compatible endpoint