القائمة
Demo cross-venue federated operations — invoke operations on remote venues, show distributed audit trails. Use for demonstrating Covia's federation capabilities.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
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 | federation |
| description | Demo cross-venue federated operations — invoke operations on remote venues, show distributed audit trails. Use for demonstrating Covia's federation capabilities. |
Prerequisite: The local venue must be running and connected as an MCP server (http://localhost:8080/mcp). This skill also requires a second venue — either a deployed venue or a second local venue on a different port (see below). If MCP tools are not available, tell the user to run /venue-setup local first.
Demonstrate Covia's federated grid operations — invoking operations across venue boundaries.
grid:run — synchronous cross-venue operation (submit + wait for result)grid:invoke — asynchronous cross-venue operation (submit + return job ID)did:web:venue.example.com)This demo requires a second venue. Options:
Option A — Two local venues on different ports:
# Terminal 1: local venue on default port
java -jar venue/target/covia.jar
# Terminal 2: second venue on port 8081
java -jar venue/target/covia.jar second-venue-config.json
Where second-venue-config.json contains:
{
"venues": [{ "name": "Remote Venue", "port": 8081, "mcp": { "enabled": true } }]
}
The remote URL is then http://localhost:8081.
Option B — Use a deployed venue (e.g. https://venue.example.com). Ask the user for the URL.
demo — Run a federated demoAsk the user for the remote venue URL (or use http://localhost:8081 if running two local venues).
Echo test — verify connectivity:
grid_run operation=test:echo input={"hello": "federation"} venue=<remote-url>
Remote LLM call — invoke an LLM on the remote venue:
grid_run operation=langchain:openai venue=<remote-url>
input={ "messages": [{"role": "user", "content": "What venue are you running on?"}] }
Async invoke — submit and poll:
grid_invoke operation=test:echo input={"async": true} venue=<remote-url>
→ returns job ID
grid_jobStatus id=<job-id> venue=<remote-url>
grid_jobResult id=<job-id> venue=<remote-url>
invoke <venue-url> — Run a specific operation on a remote venueAsk the user which operation and input, then:
grid_run operation=<op> input=<input> venue=<venue-url>
ucans proof channel) for fine-grained authorisation; the relaying venue forwards the caller's tokens on cross-venue hopsatt, audienced to the target venue) — the target verifies the caller's own signature, trusting no relayvenue/relay capability to have it make the hop authenticated as itself, exercising the caller's delegation