skills.rest
ChronoAIProject
ChronoAIProjectOFFICIAL
Explore all skills by this author →
GitHub

aevatar-triage

Trace request paths and examine code to diagnose Aevatar workflow issues.

Updated May 4, 2026
Search Tags:#debugging#root cause#diagnostics#triage#github issue#aevatar#nyxid#ornn
One-click install
npx skills add https://github.com/ChronoAIProject/nyx-skills --skill aevatar-triage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aevatar-triage
Source: https://github.com/ChronoAIProject/nyx-skills/tree/main/aevatar-triage
Command: npx skills add https://github.com/ChronoAIProject/nyx-skills --skill aevatar-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The aevatar-triage skill addresses the challenge of diagnosing issues that arise when using Aevatar, ensuring users can quickly identify if the problem lies with Aevatar, NyxID, or Ornn, and then take appropriate action.

Core Features & Use Cases

  • Request Tracing: Attributes failure to the correct layer (Aevatar, NyxID, or Ornn) by tracing the request path.
  • Code-Based Root Cause: Pulls real public source code to identify a code-grounded root cause, citing file and line.
  • Issue Resolution: Offers guidance or files a GitHub issue for platform defects or provides explanations for usage mistakes.
  • Use Case: If a workflow fails or a scheduled run does not fire, use aevatar-triage to determine if the issue is with Aevatar, NyxID, or Ornn and then address it accordingly.

Quick Start

Use the aevatar-triage skill to investigate a workflow failure and determine the root cause.

Frequently Asked Questions about aevatar-triage

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

FAQPage Schema
How do I debug Aevatar workflow failures and identify the root cause?▼

Debug Aevatar workflow failures by tracing request paths across Aevatar, NyxID, and Ornn repositories to identify code-based root causes and cite specific files and lines for troubleshooting.

Why does my scheduled Aevatar workflow run fail to fire?▼

Scheduled Aevatar workflows may fail to fire due to defects in published contracts within Aevatar, NyxID, or Ornn; tracing the request path isolates the failing layer and code-level root cause.

What is the best way to diagnose Aevatar issues across multiple repositories?▼

Diagnose Aevatar issues across multiple repositories by pulling real public source code from Aevatar, NyxID, and Ornn to attribute failures to the correct architectural layer.

Can I file a GitHub issue directly when I find a platform defect in Aevatar?▼

Yes, after diagnosing a platform defect in Aevatar, NyxID, or Ornn, you can receive guidance or have a GitHub issue filed directly to address the code-based root cause.

How do I determine if a workflow failure is caused by NyxID or Ornn?▼

Determine if NyxID or Ornn caused a workflow failure by tracing the request path to attribute the failure to the correct layer before examining the source code for the specific defect.

Related Skills

Explore More Software Engineering Skills→
ChronoAIProjectChronoAIProject
36

aevatar-codex-exec-node-setup

Configure and verify Codex execution access for NyxID users.

Official
Advanced
KodingDevKodingDev
5

debug

Identify and resolve root causes of bugs and test failures.

Community
Advanced
anthropicsanthropics
23.4k

debug

Guide structured debugging to isolate root causes and propose fixes.

Official
Intermediate
ChronoAIProjectChronoAIProject

aevatar-scheduler

Automate Aevatar service execution with cron schedules and NyxID authentication.

Official
Advanced