create-runfile

Automate Kilroy runfile authoring and DOT backend alignment.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/dcgrigsby/nexrad --skill create-runfile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-runfile
Source: https://github.com/dcgrigsby/nexrad/tree/main/.agents/skills/create-runfile
Command: npx skills add https://github.com/dcgrigsby/nexrad --skill create-runfile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates Kilroy runfile authoring and DOT backend alignment, ensuring consistent structure and reliable defaults across YAML/JSON run configs used by attractor workflows.

Core Features & Use Cases

  • Build a structured run config (version: 1) from a reference template like reference_run_template.yaml.
  • Align DOT graph providers with the correct backend settings and enforce explicit mode selection (real vs test_shim) for predictable execution.
  • Validate required fields (version, repo.path, cxdb, modeldb) and preserve template-driven configuration while keeping run-scoped paths explicit.

Quick Start

Create or repair a Kilroy runfile by starting from reference_run_template.yaml and filling the required fields (version, repo.path, cxdb settings, and provider backends) to align with your graph.

Frequently Asked Questions about create-runfile

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

FAQPage Schema
How do I create a Kilroy runfile for attractor workflows?

To create a Kilroy runfile, start from a reference template like reference_run_template.yaml and populate required fields including version, repo.path, cxdb, and modeldb to structure your attractor run configuration.

What required fields must be validated in a Kilroy run.yaml configuration?

A valid Kilroy run.yaml configuration must include the version, repo.path, cxdb, and modeldb fields to ensure proper template-driven structure and backend alignment for attractor execution.

How do I align DOT graph providers with backend settings in a runfile?

Aligning DOT graph providers involves configuring the correct backend settings and enforcing explicit mode selection between real and test_shim options to guarantee predictable execution behavior.

Can I use JSON instead of YAML for Kilroy attractor run configurations?

Yes, Kilroy supports both run.yaml and run.json formats for attractor runs across local, staging, and production contexts, allowing flexible configuration file authoring.

Why does my Kilroy runfile fail validation during attractor execution?

Kilroy runfile validation fails when required fields like version, repo.path, cxdb, or modeldb are missing, or when provider backends and supported keys do not match the expected template-driven structure.

What is explicit mode selection in Kilroy runfile backend configuration?

Explicit mode selection in Kilroy runfile backend configuration requires choosing between real and test_shim modes to ensure predictable and controlled execution of attractor workflows.