skills.rest
dcgrigsby
dcgrigsbyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

investigating-kilroy-runs

Diagnose Kilroy Attractor run status from manifest.json, live.json, and progress.ndjson artifacts.

1|Updated Mar 12, 2026
Search Tags:#debugging#logs#diagnostics#kilroy#attractor#cxdb#run-troubleshooting
One-click install
npx skills add https://github.com/dcgrigsby/nexrad --skill investigating-kilroy-runs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigating-kilroy-runs
Source: https://github.com/dcgrigsby/nexrad/tree/main/.agents/skills/investigating-kilroy-runs
Command: npx skills add https://github.com/dcgrigsby/nexrad --skill investigating-kilroy-runs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses Kilroy Attractor runs by collecting and interpreting run artifacts (manifest.json, live.json, checkpoint.json, final.json, progress.ndjson) to determine status.

Core Features & Use Cases

  • Resolve Run Root: locate the most recent Kilroy run from logs and determine RUN_ROOT for diagnostics.
  • CXDB Launch, UI, and Query: provide steps to start CXDB, access the UI, and query turns for run context.
  • Read Canonical Files: inspect graph, manifest, live, checkpoint, and final artifacts to assess run state.
  • Determine Current State: classify as Running, Finished, or Likely stalled and provide quick validations.

Quick Start

Query the latest Kilroy Attractor run status with the status command and review manifest.json, live.json, and progress.ndjson to identify current state and failures.

Frequently Asked Questions about investigating-kilroy-runs

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

FAQPage Schema
What is the best way to diagnose a failed Kilroy Attractor run?▼

Diagnose a failed Kilroy Attractor run by collecting run artifacts like final.json and progress.ndjson to determine status. Querying CXDB provides context-turn tracing and model routing analysis to pinpoint the failure.

Why does my Kilroy Attractor run show no progress in the logs?▼

Your Kilroy Attractor run shows no progress because it is likely stalled. Cross-reference live.json with checkpoint.json and query CXDB to validate the current state and identify where the execution graph halted.

Why does my Kilroy Attractor run show no progress in the logs?▼

Your Kilroy Attractor run shows no progress because it is likely stalled. Cross-reference live.json with checkpoint.json and query CXDB to validate the current state and identify where the execution graph halted.

How do I query Kilroy run context in CXDB?▼

Query Kilroy run context in CXDB by launching the database, accessing the UI, and executing queries to trace context turns. This consolidates run diagnostics into a comprehensive report for active or failed environments.

Can I use CXDB to analyze model routing for a stalled run?▼

Yes, you can use CXDB to analyze model routing for a stalled run. Launching CXDB and querying the UI enables context-turn tracing and model/provider routing analysis to resolve execution issues across environments.

Related Skills

Explore More Software Engineering Skills→
danshapirodanshapiro
216

using-kilroy

Convert English requirements into Kilroy Attractor pipelines via the Kilroy CLI.

Community
Advanced
GenproMMGenproMM

gsd-forensics

Analyze git history, artifacts, and state to diagnose failed GSD workflows.

Official
Advanced
eaglhuangeaglhuang
3

best-mode

Route (best) prompts through context-budget-guard before task-specific logic.

Community
Advanced
Wike-CHIWike-CHI
2

MCP管理器

Manage MCP servers and tools via the mcporter CLI.

Community
Intermediate