create-dotfile

Generate and repair DOT graphs from reference_template.dot for Kilroy Attractor pipelines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables template-first DOT graph authoring and repair for Kilroy Attractor pipelines, ensuring topology, routing guardrails, and validator-clean output are consistently produced from requirements and DoD evidence.

Core Features & Use Cases

  • Enforces a validated, template-based topology using reference_template.dot to minimize ad-hoc graph design.
  • Manages node prompts, routing, model assignments, and validation behavior to ensure deterministic and recoverable DOT graphs.
  • Leverages defaults from preferences.yaml while respecting explicit user constraints, guardrails, and validator requirements.
  • Provides clear separation of concerns: topology definition, model resolution, and verification/validation workflows within the Attractor pipeline.
  • Out of scope: run config authoring and backend policy details; use create-runfile for those aspects.

Quick Start

Edit the reference_template.dot to define topology, then run kilroy attractor validate to produce a ready DOT graph.

Frequently Asked Questions about create-dotfile

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

FAQPage Schema
How do I generate DOT graphs reliably for Kilroy Attractor pipelines?

Generate DOT graphs by editing the reference_template.dot to define topology and running kilroy attractor validate. This template-first approach ensures deterministic routing, model assignments, and validator-clean output.

What is the best way to repair invalid DOT graph topology in an Attractor pipeline?

Repair invalid DOT topology by applying template-based guardrails and defaults from preferences.yaml during generation. This enforces routing constraints and integrates analysis and merge nodes for recoverable graph behavior.

Can I manage model assignments and validation behavior directly within a DOT graph?

Manage model assignments and validation behavior by configuring the model_stylesheet with semicolon-terminated declarations. This enforces guardrails and ensures deterministic validator-clean output for Attractor pipelines.

Do I need a separate skill to author run configuration and backend policies for Attractor?

Use create-runfile to author run config and backend policy details. This skill focuses exclusively on DOT graph topology, routing, model assignments, and validation behavior, leaving run configuration out of scope.

Why does my DOT graph validation fail despite explicit user constraints?

DOT graph validation fails if topology deviates from the reference_template.dot or violates guardrails. Ensure defaults from preferences.yaml are respected and model_stylesheet declarations are properly semicolon-terminated.