Agent Skill

Guide

Station ships with a Claude Code skill that teaches the AI assistant how to build with every Station package. Once installed, Claude knows how to create signals, broadcasts, beacons, schedules, Station Networks, adapters, subscribers, and dashboard configs without you having to explain the API.

What is a skill?

A Claude Code skill is a set of markdown files that get injected into Claude’s context when relevant. Skills contain API references, code patterns, and rules that guide the assistant’s output. The Station skill covers the framework packages, official adapters, Station Networks, and the REST API.

Install

npx skills add porkytheblack/station

The skill directory contains three files:

File	Description
`SKILL.md`	Main skill file. Contains critical rules, code patterns, builder workflows, network operations, and verification guidance. This concise file is what Claude reads first.
`api-reference.md`	Exhaustive package and v1 REST API reference, including signals, broadcasts, beacons, schedules, environment variables, expressions, Station Networks, adapters, station-kit, and station-tauri.
`examples.md`	Twenty-six complete examples covering signals, pipelines, beacons, runtime schedules, environment variables, all four adapter backends, deployment, and a Headquarters/worker topology.

Usage

Once installed, the skill activates automatically when you ask Claude about Station topics. You can also invoke it explicitly:

/station

Example prompts that trigger the skill:

“Create a signal that sends welcome emails with retry”
“Set up a broadcast DAG for my CI pipeline”
“Configure PostgreSQL adapters for signals and broadcasts”
“Scale this across a Headquarters and three GPU stations”
“Add a runner with SQLite persistence and graceful shutdown”
“Write a subscriber that posts failures to Slack”

What the skill knows

Topic	Coverage
Signals	Builder chain (`.input()`, `.output()`, `.timeout()`, `.retries()`, `.concurrency()`, `.placement()`, `.every()`, `.onComplete()`, `.run()`), multi-step pipelines (`.step()` + `.build()`), triggering, validation
Broadcasts	DAG builder (`.node()`, `.then()`), conditional nodes (`when`), failure policies, input/output mapping, fan-out and fan-in patterns
Adapters	SQLite, PostgreSQL, MySQL, and Redis for signals, broadcasts, beacons, schedules, environment variables, and network state. Constructor patterns, connection options, and subpath imports
Station Networks	Headquarters and station roles, shared storage, atomic run claims, fencing and recovery, per-station/fleet concurrency, placement, draining, inventory, and beacon HTTP proxying
Schedules	Editable interval and timezone-aware cron schedules, overlap and misfire policies, atomic occurrence claims, and timing semantics
Beacons	Supervised servers, pollers, and clients; restart policies, instances, placement, exposure, and graceful shutdown
Runners	`SignalRunner`, `BroadcastRunner`, and`BeaconRunner` setup, auto-discovery, manual registration, graceful shutdown, poll intervals
Subscribers	Lifecycle events for signal, broadcast, and beacon runners. Custom subscriber patterns for logging, metrics, and alerting
Remote triggers	`configure({ endpoint, apiKey })`, `HttpTriggerAdapter`, environment variables, Station REST API endpoints
Dashboard	`station.config.ts` options, CLI usage, auth configuration

Updating

Re-run the install command to pull the latest version:

npx skills add porkytheblack/station