skills.rest
OmerFarukOruc
OmerFarukOrucCOMMUNITY
Explore all skills by this author →
Website𝕏@orcsriseGitHub

symphony-logs

Inspect Symphony orchestrator runs and live state via local API endpoints.

2|Updated Mar 16, 2026
Search Tags:#debugging#logs#api#runtime#archive#inspection#symphony
One-click install
npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill symphony-logs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: symphony-logs
Source: https://github.com/OmerFarukOruc/symphony-orchestrator/tree/main/skills/symphony-logs
Command: npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill symphony-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect Symphony orchestrator runtime history and live local state using the repo-root ./symphony-logs helper, archived .symphony/ attempt data, and local http://127.0.0.1:4000/api/v1/* endpoints. Use this for Symphony-specific run inspection requests like "check NIN-6", "show retry history", "why did it fail", "inspect attempt abc123", or "is the worker still running", and not for generic repository debugging, generic application logs, or non-Symphony services.

Core Features & Use Cases

  • Inspect the latest attempt for a given issue, summarize status and timeline, and surface relevant events
  • Compare retry history across attempts and verify live worker state via the local API
  • Provide explicit provenance by naming the exact source used (helper, archive, or API) for conclusions

Quick Start

Run the latest issue check using the symphony-logs helper for an issue like NIN-6.

Frequently Asked Questions about symphony-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect a Symphony orchestrator run to check its latest attempt status?▼

To inspect a Symphony orchestrator run, use this Skill to query the repo-root ./symphony-logs helper and archived .symphony/ data. It summarizes the latest attempt status, timeline, and relevant events for a given issue.

Why did my Symphony runtime fail and how can I view the retry history?▼

To diagnose why a Symphony runtime failed, this Skill compares retry history across attempts using archived .symphony/ data. It surfaces failure events and timeline details to help pinpoint the exact cause.

Can I check if the Symphony worker is still running via the local API?▼

Yes, you can check if the Symphony worker is still running by querying the local http://127.0.0.1:4000/api/v1/* endpoints. This Skill verifies live worker state directly through those local API endpoints.

Does this tool work for generic application logs or non-Symphony services?▼

No, this tool does not work for generic application logs or non-Symphony services. It is specifically designed for Symphony-specific run inspection tasks using the ./symphony-logs helper and local API endpoints.

What sources do I need to diagnose Symphony runtime failures?▼

To diagnose Symphony runtime failures, you need access to the repo-root ./symphony-logs helper, archived .symphony/ attempt data, and local /api/v1 endpoints. The Skill uses these exact sources to provide explicit provenance in its conclusions.

Related Skills

Explore More Software Engineering Skills→
OmerFarukOrucOmerFarukOruc
2

visual-verify

Visually verify Symphony dashboard and logs UI with automated browser checks.

Community
Advanced
RHEcosystemAppEngRHEcosystemAppEng
48

job-failure-analyzer

Classify AAP job failures and reconstruct timelines from job events and host summaries.

Official
Advanced
dseirz-rgbdseirz-rgb

multi-service-debug

Correlate logs and traces to diagnose cross-service failures between Vercel and Cloud Run.

Community
Advanced
LuminairPrimeLuminairPrime

debug

Trace Symphony and Codex logs to resolve stuck runs and execution failures.

Community
Intermediate