Menú
Get full details for a single rounds error signature including diagnosis, recent events, and related signatures
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Assess telemetry data — identifies distinct transaction types from an explore query and launches sub-agents to analyze each for instrumentation quality, code efficiency, usage correctness, and skill improvement opportunities
Print available rounds skills, project directory layout, and a brief overview of what rounds does
Exploratory querying of telemetry data — search logs by keyword/metadata, search spans by metadata, and build full transaction trees from trace IDs using the rounds adapter interfaces
Investigate a distributed trace by ID — fetches the full trace, reads source files, and explains the end-to-end code flow
List error signatures in the rounds database, optionally filtered by status
Mute a rounds error signature to suppress further notifications
| name | rounds-details |
| description | Get full details for a single rounds error signature including diagnosis, recent events, and related signatures |
| user_invocable | true |
| args | ["signature_id"] |
Retrieve complete details for one error signature: status, occurrence history, LLM diagnosis, recent events, and related signatures.
/rounds-details SIGNATURE_ID
SIGNATURE_ID is a UUID string from the rounds database (visible in /rounds-list
output).
Substituting $ARGUMENTS for the signature ID:
cd /workspace/rounds && python -m rounds.main cli-run details '{"signature_id": "$ARGUMENTS"}'
The command outputs a JSON object. Parse it and present:
On success ("status": "success"), render data (a SignatureDetails object):
Identity
Status & History
Message Template
Diagnosis (if present in data.signature.diagnosis)
Recent Events (up to 5 from data.recent_events)
Related Signatures (up to 5 from data.related_signatures)
On error ("status": "error"):
Show the message field. If it mentions "not found", the signature ID may be wrong
— suggest running /rounds-list to see valid IDs.
/rounds-details 3f2a1b4c-8d9e-4f5a-b6c7-d8e9f0a1b2c3