Agent skill

Homerail Dag Ops

by xiaotianfotos in xiaotianfotos/homerail

Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access.

MITAuto-check passedBackend & APIs

Install Homerail Dag Ops

skills CLI
$ npx skills add xiaotianfotos/homerail --skill homerail-dag-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install xiaotianfotos/homerail homerail-dag-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/xiaotianfotos/homerail.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/homerail-dag-ops .claude/skills/homerail-dag-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
homerail-dag-ops
GitHub stars
994
Token cost
~1.5k tokens
SKILL.md length
729 words
Files
15 (incl. scripts, references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access.

  • Works in 5 steps: Establish the output, source… → Resolve the existing CLI and Manager… → Use hr --json templates list, or inspect… → …
  • Project work delegated to a DAG
  • SKILL.md covers Choose the next action, Start once and Wait, decide, and finish
  • Runs Python and JavaScript scripts from its folder; calls node

What it does

Homerail Dag Ops is an agent skill from xiaotianfotos/homerail. Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access. Use for project work delegated to a DAG, workflow patterns, existing-run results, approval/Actor follow-ups, live panels, and background event callbacks. Handles the full run lifecycle with event-driven waiting instead of repeated model polling.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/acceptance.md` and `references/architecture.md`).

It sits in Backend & APIs, covering Event-driven systems. The repository describes itself as: Voice-first local agent orchestration runtime for auditable DAG workflows. The licence is MIT.

When your agent uses it

  • Project work delegated to a DAG
  • Workflow patterns
  • Existing-run results
  • Approval/Actor follow-ups

Example prompts

  • “/homerail-dag-ops”

Requirements

  • Python 3
  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Establish the output, source revision/inputs, permitted changes, budget, and
  2. Resolve the existing CLI and Manager origin. Use hr doctor for readiness;
  3. Use hr --json templates list, or inspect a known database workflow. Read
  4. Give Workers reachable inputs. Container Workers do not automatically see
  5. For a new/changed workflow, inspect hr dag schema, validate with `hr --json

What it can do on your machine

Read from SKILL.md and the folder at commit 916e343. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 5 files in scripts/ (Python and JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Homerail Dag Ops loads about 1.5k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 729 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from xiaotianfotos/homerail at commit 916e343, republished under its MIT licence (© xiaotianfotos). 729 words, ~1,533 tokens.

Download SKILL.mdSave it as .claude/skills/homerail-dag-ops/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
homerail-dag-ops
description
Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access. Use for project work delegated to a DAG, workflow patterns, existing-run results, approval/Actor follow-ups, live panels, and background event callbacks. Handles the full run lifecycle with event-driven waiting instead of repeated model polling.

HomeRail DAG

Use one workflow: define outputs → choose/validate a DAG → start once → wait outside the model → handle decisions → verify evidence. Running and supervising are stages of the same task. Load only the reference needed for the current stage; do not load every HomeRail skill before starting.

Choose the next action

Request or current stateAction
New project workUse the start path below; reuse a workflow/profile.
New topology or a reusable patternRead patterns.md; inspect the live schema/catalog.
Active run requiring event-driven waitingRead supervision.md; use the current host’s blocking event tool or a verified optional adapter.
[homerail-dag-event ...] callback, including the former supervision skill nameFollow event consumption in supervision.md.
Requested status, results, or diagnosisRead inspection.md; inspect only relevant evidence.
Live Actor panels or a later per-Actor commandRead multi-actor-surfaces.md.

The old homerail-dag-patterns entry remains for compatibility. Its content lives in this skill's references; it is not a prerequisite skill to load.

Start once

  1. Establish the output, source revision/inputs, permitted changes, budget, and acceptance evidence. If unattended supervision is needed, confirm the host can await a tool/event or receive a callback before starting the run. If a run ID already exists, inspect that run first.
  2. Resolve the existing CLI and Manager origin. Use hr doctor for readiness; use hr runtime status if diagnosis is needed. If hr is absent but HOMERAIL_CLI_ENTRYPOINT is set, use node "$HOMERAIL_CLI_ENTRYPOINT". Do not rebuild or restart a ready installation for an ordinary DAG run. Use homerail-install-ops only for an actual installation/service task.
  3. Use hr --json templates list, or inspect a known database workflow. Read its input contract. Resolve template files from the verified HomeRail source or Manager catalog; assets/... is not relative to an arbitrary project.
  4. Give Workers reachable inputs. Container Workers do not automatically see host paths: supply a cloneable repository URL and pinned revision, or the workflow's supported workspace/input mechanism. Keep input identity shared across nodes and verify access from the executing environment.
  5. For a new/changed workflow, inspect hr dag schema, validate with hr --json dag validate <file>, then sync. Bind database LLM settings through a runtime profile; keep provider/model credentials out of workflow YAML.
bash
# Existing database workflow and runtime profile
hr run --workflow <workflow-id> --profile <profile-id> --prompt "<task and inputs>"

# Alternatively: a concrete template with its actual input contract
hr run <verified-template-path> --prompt "<task and inputs>"

Template-embedded profiles and database profiles differ: use --workflow for a DB profile or the documented sync flow. Check local help for unfamiliar flags. Record the returned run ID, workflow revision/hash, inputs and acceptance criteria in a private receipt. If submission has an unknown outcome, reconcile existing runs; do not blindly create a replacement.

In the Manager Agent, available tools such as list_orchestrations, create_and_run, invoke_run, get_run_status, get_dag_schema, and validate_dag_workflow are shortcuts for covered operations. Use structured CLI output for the rest. Any agent may use these CLI/HTTP contracts; no particular supervisor model, SDK or harness is required. Do not launch another agent or model merely to subscribe to or consume events.

Show full SKILL.md (261 more words)Show less

Wait, decide, and finish

The default bundled path is register → wait → handle the returned event → ack. Registration persists identity; wait blocks in ordinary code and returns one actionable JSON event. Let the host await that tool instead of repeatedly invoking the model. Registration alone does not start a background observer.

If the host provides native event subscriptions, use its equivalent mechanism. An optional callback adapter can deliver the same JSON into a persistent host session. End the model turn after registration only when that continuing event path is verified. A plain skill cannot force a host to suspend, steer or resume an agent. If the host lacks event/tool continuation, explain that limitation; do not claim automatic wakeup or substitute a Codex executor.

Routine progress stays quiet. hr dag watch/supervise remain optional foreground inspection tools, not a model polling loop. A requested snapshot needs no new watcher.

On a callback, verify the single event and current run identity, handle the current condition, record the finding/action intent, and acknowledge consumption. An ACK does not approve a proposal or end a waiting DAG. Let the human decide approval nodes. Reconcile ambiguous mutation outcomes before retrying.

Check terminal status and relevant artifacts/handoffs against the original acceptance criteria. A completed pipeline or passing advisory scorecard alone is not proof of useful output. See inspection.md. End the turn when nothing actionable remains.

Keep secrets in existing Manager configuration/encrypted storage, never in prompts, templates, receipts or commits. Keep deployment and disruptive runtime changes within the user's authorized scope. For HomeRail self-development read architecture.md; for skill changes read acceptance.md.

© xiaotianfotos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files (scripts, references) in skills/homerail-dag-ops of xiaotianfotos/homerail.

  • SKILL.md
  • .gitignore
  • agents/openai.yaml
  • references/acceptance.md
  • references/architecture.md
  • references/inspection.md
  • references/listener.md
  • references/multi-actor-surfaces.md
  • references/patterns.md
  • references/supervision.md
  • scripts/check_integration.py
  • scripts/dag_subscription.py
  • scripts/manager_fixture.mjs
  • scripts/storage.py
  • scripts/test_dag_subscription.py

Open the folder on GitHubat commit 916e343

Compare with similar skills

Homerail Dag Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Homerail Dag Ops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Homerail Dag Ops this skillxiaotianfotos/homerail994—~1.5kAutomated safety check: PassMIT
Stripe Projectsfossasia/eventyay1.7k5 repos~2kAutomated safety check: NotesApache-2.0
MQTTX CLIemqx/MQTTX5.1k—~1.9kAutomated safety check: PassApache-2.0
AWS Serverless Edazxkane/aws-skills3674 repos~3.2kAutomated safety check: PassMIT
Windmill Trigger Type Checklistwindmill-labs/windmill18k—~4.7kAutomated safety check: PassCustom licence
FoundatioFoundatioFx/Foundatio2.1k—~3.9kAutomated safety check: PassApache-2.0

Similar skills

  • Stripe Projects

    fossasia/eventyay

    A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.

    1.7k GitHub starsUsed in 5 repos~2k tokens
    Backend & APIsAuto-check: notes
  • MQTTX CLI

    emqx/MQTTX

    Operates the `mqttx` command line client to connect, publish, subscribe, benchmark and simulate data against an MQTT broker, with TLS and MQTT 5 support.

    5.1k GitHub stars~1.9k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • AWS Serverless Eda

    zxkane/aws-skills

    AWS serverless and event-driven architecture expert based on Well-Architected Framework.

    367 GitHub starsUsed in 4 repos~3.2k tokens
    Backend & APIsAuto-check passed
  • Windmill Trigger Type Checklist

    windmill-labs/windmill

    Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.

    18k GitHub stars~4.7k tokensUpdated today
    Backend & APIsAuto-check passed
  • Foundatio

    FoundatioFx/Foundatio

    A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.

    2.1k GitHub stars~3.9k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Dynamic Consistency Boundaries

    AxonIQ/AxonFramework

    Explain and reason about Dynamic Consistency Boundaries (DCB) and how Axon Framework 5 and Axon Server implement them.

    3.6k GitHub stars~1.9k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from xiaotianfotos/homerail

All 11 skills in this repo
  • Voice Generative UI

    xiaotianfotos/homerail

    Design and maintain truthful HomeRail generative UI for voice or text.

    994 GitHub stars~3.8k tokensUpdated 15 days ago
    Auto-check passed
  • Homerail CLI

    xiaotianfotos/homerail

    HomeRail CLI syntax, flags, configuration, and command reference.

    994 GitHub stars~3.4k tokensUpdated 15 days ago
    Auto-check passed
  • Homerail Install Ops

    xiaotianfotos/homerail

    Install, configure, start, verify, update, and troubleshoot a local-source HomeRail deployment for AI-agent use.

    994 GitHub stars~2k tokensUpdated 15 days ago
    Auto-check passed
  • Homerail PR Review

    xiaotianfotos/homerail

    Run HomeRail's built-in read-only pull request review DAG. An agent skill from xiaotianfotos/homerail.

    994 GitHub stars~670 tokensUpdated 15 days ago
    Auto-check passed
  • Homerail Shared

    xiaotianfotos/homerail

    Shared HomeRail rules for AI agents operating the local-source release candidate: service roles, environment variables, secrets, provider boundaries, Docker callback networking, update expectations…

    994 GitHub stars~1.5k tokensUpdated 15 days ago
    Auto-check passed
  • Dag Best Practices

    xiaotianfotos/homerail

    HomeRail DAG review and execution best practices. An agent skill from xiaotianfotos/homerail.

    994 GitHub stars~419 tokensUpdated 15 days ago
    Auto-check passed

Categories

Questions about Homerail Dag Ops

What does Homerail Dag Ops do?

Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access. Homerail Dag Ops is an agent skill from xiaotianfotos/homerail. Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access.

When should I use Homerail Dag Ops?

Homerail Dag Ops fits situations like: project work delegated to a DAG; workflow patterns; existing-run results; approval/Actor follow-ups.

How do I install Homerail Dag Ops in Claude Code?

Run `npx skills add xiaotianfotos/homerail --skill homerail-dag-ops -a claude-code`. Or copy the skill folder (skills/homerail-dag-ops in xiaotianfotos/homerail) into .claude/skills/homerail-dag-ops in your project. Claude Code loads it when a task matches its description.

How do I install Homerail Dag Ops in Codex?

Run `npx skills add xiaotianfotos/homerail --skill homerail-dag-ops -a codex`. Or copy the skill folder (skills/homerail-dag-ops in xiaotianfotos/homerail) into .agents/skills/homerail-dag-ops in your project. Codex loads it when a task matches its description.

Can I use Homerail Dag Ops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add xiaotianfotos/homerail --skill homerail-dag-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/homerail-dag-ops, .gemini/skills/homerail-dag-ops, .github/skills/homerail-dag-ops and .opencode/skills/homerail-dag-ops in your project.

What does Homerail Dag Ops need to run?

Going by SKILL.md and its folder, Homerail Dag Ops needs Python and JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Python 3; Node.js.

Does Homerail Dag Ops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Homerail Dag Ops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Homerail Dag Ops use?

Homerail Dag Ops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Homerail Dag Ops use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Homerail Dag Ops?

Skills that share tags, products or a category with Homerail Dag Ops: Stripe Projects (fossasia/eventyay, 1.7k stars), MQTTX CLI (emqx/MQTTX, 5.1k stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and Windmill Trigger Type Checklist (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Homerail Dag Ops?

xiaotianfotos (a GitHub user) maintains it in xiaotianfotos/homerail, which has 994 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 25, 2026.

Source: xiaotianfotos/homerail on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.