Agent skill

Homerail Shared

by xiaotianfotos in 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…

MITAuto-check passedDevOps & Cloud

Install Homerail Shared

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

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

GitHub CLI
$ gh skill install xiaotianfotos/homerail homerail-shared --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-shared .claude/skills/homerail-shared && 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-shared
GitHub stars
994
Token cost
~1.5k tokens
SKILL.md length
727 words
Files
2
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

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

  • Troubleshooting
  • SKILL.md covers Core Rules, Provider Boundaries, Local Source Layout and Anti-Patterns (Don'ts), plus 1 more section
  • Calls npm
  • Running HomeRail through other HomeRail skills

What it does

Homerail Shared is an agent skill from 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, and safe command behavior. Use whenever installing, configuring, upgrading, troubleshooting, or running HomeRail through other HomeRail skills.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in DevOps & Cloud, covering Containers and Secrets management. It works with Docker. The repository describes itself as: Voice-first local agent orchestration runtime for auditable DAG workflows. The licence is MIT.

When your agent uses it

  • Troubleshooting
  • Running HomeRail through other HomeRail skills

Example prompts

  • “/homerail-shared”

Requirements

  • Docker

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

    Shell commands in SKILL.md call:

    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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 Shared loads about 1.5k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 727 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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); files beside SKILL.md are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/homerail-shared/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
homerail-shared
description
Shared HomeRail rules for AI agents operating the local-source release candidate: service roles, environment variables, secrets, provider boundaries, Docker callback networking, update expectations, and safe command behavior. Use whenever installing, configuring, upgrading, troubleshooting, or running HomeRail through other HomeRail skills.

HomeRail Shared

Core Rules

Use these rules with all HomeRail skills.

  • Treat this release as a local-source install. Do not assume npm packages or public GitHub URLs exist yet.

  • Prefer placeholders such as <local-homerail-repo> and /path/to/HomeRail in user-facing instructions.

  • Keep provider and integration secrets in the Manager encrypted secret store through CLI/UI configuration; never write API keys, tokens, or passwords into repo files, skill files, DAG templates, commits, or issue text.

  • Use one shared HOMERAIL_HOME for Manager and Node. Default is $HOME/.homerail.

  • Prefer hr config for local runtime settings and hr start to start Manager and Node together.

  • Manager and Node run as local services. Manager is not expected to run inside the Worker Docker image.

  • Node provisions Worker containers. Workers for one run should share ${HOMERAIL_HOME}/workspace/<run_id>.

  • Local service ports (use this table and the CLI before falling back to low-level process probes):

    PortRoleDefault URLNotes
    19191Manager (HTTP + WS, what DAGs and the CLI talk to)http://localhost:19191This is the only port a DAG run / CLI hits. Bind via HOMERAIL_MANAGER_HOST / manager.host / hr start --host; public access via HOMERAIL_MANAGER_PUBLIC_URL / hr start --public-url.
    19192Agent UI (HTTPS, browser)https://localhost:19192Browser-only. Do NOT send DAG/CLI traffic here. Config via HOMERAIL_UI_HOST / HOMERAIL_UI_PORT / ui.host / ui.port.
    19193Agent UI HTTP fallbackhttp://localhost:19193Fallback when HTTPS port is taken. Config via HOMERAIL_UI_HTTP_PORT / ui.httpPort.

    The Manager port is 19191, not 19192. 19192 is the Agent UI. Mixing these up is the most common startup mistake.

  • For hr start --ui --public without explicit public URLs, Agent UI should bind and advertise the detected machine IP with HTTPS, and the browser should use same-origin Manager API/WS proxying for the HTTPS UI. Use HOMERAIL_PUBLIC_HOST only when automatic machine IP detection picks the wrong interface.

  • For reverse-proxied public access, prefer explicit HTTPS/WSS public URLs through HOMERAIL_MANAGER_PUBLIC_URL / HOMERAIL_UI_PUBLIC_URL or --public-url / --ui-public-url.

  • Do not hardcode Docker bridge addresses. Use Docker host.docker.internal / host-gateway support or explicit operator-provided callback settings.

Provider Boundaries

For Coding Plan / Agent Plan accounts:

  • Never use direct-llm or Chat Completions as the worker runtime path.
  • Kimi plans should use the Kimi Code CLI harness (kimi_code / kimi-code).
  • Other provider plans should use the Claude Code compatible harness (claude-sdk) with an Anthropic-compatible endpoint.
  • If a plan does not expose an Anthropic-compatible endpoint, fail explicitly instead of falling back to the Chat Completions URL.

For MiMo:

  • DAG worker LLM access uses the MiMo token-plan Anthropic-compatible endpoint.
  • MiMo ASR/API-billing endpoints are a separate voice path and must not be mixed into DAG worker model configuration.
  • If a user provides a provider key, configure it with hr model configure --api-key-stdin or the interactive CLI/UI flow so Manager stores it encrypted. Plaintext env files are legacy import fallbacks only.
Show full SKILL.md (283 more words)Show less

Local Source Layout

Expected source checkout:

text
<local-homerail-repo>/
  homerail_manager/
  homerail_node/
  homerail_worker/
  homerail_protocol/
  homerail_cli/
  agent-ui/
  assets/
  skills/

Use homerail_cli for the TypeScript CLI. Do not refer to the old homerail_cli_ts name.

Anti-Patterns (Don'ts)

These cause wasted investigation rounds during normal operation. The CLI already exposes everything below.

  • Do not start service diagnosis with raw process probes or source spelunking. Run hr doctor (readiness) and hr runtime status (live state) first; they report manager/node/worker/model state. Use ps, lsof, direct curl, logs, or source reading only after the CLI output is insufficient or the user explicitly asks for low-level debugging.
  • Do not start a fixed host Worker process. DAG Workers are provisioned on demand by a Node into Docker containers; there is no standing worker to launch. Starting a bare homerail_worker node process manually will not register correctly and bypasses the isolated-workspace contract every DAG depends on.
  • Do not hand-craft WebSocket URLs or reverse-engineer the worker connection protocol. hr start handles Manager↔Node↔Worker wiring. If a Worker cannot reach the Manager, set the Manager worker-WS callback host (see homerail-install-ops troubleshooting), do not hardcode Docker bridge IPs.
  • Do not rebuild packages before every DAG run. install:all / build / typecheck / test are only needed after changing source or on first install. A ready runtime runs DAGs directly via hr run.
  • Do not read dag_runs/dag_handoffs tables via sqlite3 to get run output. Use hr dag handoffs <run_id> (with --content-limit 0 for untruncated content). The CLI is the supported read path.
  • Do not treat an idle or running snapshot as success. Terminal status (completed/failed/cancelled) plus non-empty handoffs is the only success signal.

Validation Ladder

When validating a local install or change, prefer this order:

bash
npm run install:all
npm run build
npm run typecheck
npm test
npm run ci

For end-to-end readiness, also run hr config, hr start, hr doctor, and one public smoke DAG through homerail-install-ops.

© 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 1 other file in skills/homerail-shared of xiaotianfotos/homerail.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 916e343

Compare with similar skills

Homerail Shared 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 Shared compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Homerail Shared this skillxiaotianfotos/homerail994—~1.5kAutomated safety check: PassMIT
Iron Proxy Gateway for NanoClawnanocoai/nanoclaw31k—~4.6kAutomated safety check: NotesMIT
LangBot Deployment Guidelangbot-app/LangBot18k—~1.5kAutomated safety check: NotesApache-2.0
Add Config Env Varbaserow/baserow6.1k—~1.1kAutomated safety check: PassCustom licence
Monstermq Broker Configvogler75/monster-mq143—~2.2kAutomated safety check: PassGPL-3.0
Deploymentmatrixorigin/memoria610—~1.6kAutomated safety check: NotesApache-2.0

Similar skills

  • Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.

    31k GitHub stars~4.6k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Add Config Env Var

    baserow/baserow

    Add a Baserow configuration environment variable for the backend, frontend, or both, and propagate it through settings, Nuxt runtime config, Docker Compose, documentation, consumers, and tests as…

    6.1k GitHub stars~1.1k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Monstermq Broker Config

    vogler75/monster-mq

    Guide for configuring, deploying, and operating the MonsterMQ broker.

    143 GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Deployment

    matrixorigin/memoria

    Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.

    610 GitHub stars~1.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Practical Docker and Docker Compose patterns for local development: stacks, override files, networking, volumes, container hardening and debugging.

    277k GitHub starsUsed in 4 repos~2.1k tokens
    DevOps & CloudAuto-check: notes

More from xiaotianfotos/homerail

All 11 skills in this repo
  • Homerail Dag Ops

    xiaotianfotos/homerail

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

    994 GitHub stars~1.5k tokensUpdated 15 days ago
    Auto-check passed
  • 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
  • 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

Works with

Categories

Questions about Homerail Shared

What does Homerail Shared do?

Shared HomeRail rules for AI agents operating the local-source release candidate: service roles, environment variables, secrets, provider boundaries, Docker callback networking, update expectations…. Homerail Shared is an agent skill from 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, and safe command behavior.

When should I use Homerail Shared?

Homerail Shared fits situations like: troubleshooting; running HomeRail through other HomeRail skills.

How do I install Homerail Shared in Claude Code?

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

How do I install Homerail Shared in Codex?

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

Can I use Homerail Shared 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-shared -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-shared, .gemini/skills/homerail-shared, .github/skills/homerail-shared and .opencode/skills/homerail-shared in your project.

What does Homerail Shared need to run?

Going by SKILL.md and its folder, Homerail Shared needs the command-line tools its instructions call (npm). Our summary lists: Docker.

Does Homerail Shared access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Homerail Shared 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. Review the folder before installing.

What licence does Homerail Shared use?

Homerail Shared 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 Shared use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Homerail Shared?

Skills that share tags, products or a category with Homerail Shared: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Add Config Env Var (baserow/baserow, 6.1k stars) and Monstermq Broker Config (vogler75/monster-mq, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Homerail Shared?

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.