english-to-dotfile

Name: english-to-dotfile
Availability: InStock
Author: danshapiro

Translates English software requirements into a runnable Kilroy Attractor DOT pipeline.

216|52|Updated Feb 6, 2026

Search Tags:#pipeline #nlp #graphviz #dotfile #Kilroy #Attractor

Ready to run

npx skills add https://github.com/danshapiro/kilroy --skill english-to-dotfile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: english-to-dotfile
Source: https://github.com/danshapiro/kilroy/tree/main/skills/english-to-dotfile
Command: npx skills add https://github.com/danshapiro/kilroy --skill english-to-dotfile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates natural-language software requirements into deterministic Kilroy Attractor DOT pipelines. It simplifies turning ambiguous specs into testable Graphviz graphs that Kilroy can ingest, validate, and execute.

Core Features & Use Cases

Convert English requirements into a valid .dot pipeline that Kilroy's Attractor can execute.
Support both concise requests and long specs; if input is vague, an expand_spec node bootstraps a detailed .ai/spec.md for later refinement.
Validate and run the generated pipeline with Kilroy's tooling; produce a plain .dot file suitable for CLI ingestion.

Quick Start

Provide English requirements to generate a .dot pipeline. The output will be raw .dot content starting with digraph and ending with }.

Frequently Asked Questions about english-to-dotfile

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

FAQPage Schema

How do I convert English software requirements into a Graphviz DOT pipeline?▼

To convert English requirements into a DOT pipeline, provide your natural-language software specs to generate a valid .dot file starting with digraph. The output is raw DOT content suitable for CLI ingestion and execution by Kilroy's Attractor tooling.

What happens if my natural-language spec is too vague to generate a valid DOT file?▼

When your natural-language spec is too vague, an expand_spec node bootstraps a detailed .ai/spec.md file. This provides a structured specification output for later refinement before generating the final executable DOT pipeline.

Can I use detailed multi-sentence specs to generate a Kilroy Attractor DOT pipeline?▼

Yes, you can use detailed multi-sentence specs to generate a Kilroy Attractor DOT pipeline. The translation process applies to both concise single-sentence requests and long, detailed software specifications to produce a valid graph.

Does the generated DOT pipeline include graph attributes required by Kilroy?▼

Yes, the generated DOT pipeline includes the required graph attributes for Kilroy. It writes a valid graph with necessary configurations and produces a status.json file for each run to track execution state.

What is the best way to validate and run a generated DOT pipeline with Kilroy tooling?▼

The best way to validate and run a DOT pipeline is to use Kilroy's integrated tooling to ingest the plain .dot file. The Skill produces a valid graph starting with digraph and ending with } for deterministic execution.