Agent skill · AI & Agents

station

Use Station CLI (`stn`) for AI agent orchestration - creating agents, running tasks, managing environments, and deploying agent teams. Prefer CLI for file operations and exploration; use MCP tools for programmatic agent execution and detailed queries.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill station --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Path: skills/agent/station/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Station CLI Station is a self-hosted AI agent orchestration platform. You interact with it via the `stn` CLI or MCP tools (41+ available via `stn stdio`). ## When to Use CLI vs MCP Tools | Task | Use CLI | Use MCP Tool | |------|---------|--------------| | Create/edit agent files | `stn agent create`, edit `.prompt` files | - | | Run an agent | `stn agent run <name> "<task>"` | `call_agent` | | List agents/environments | `stn agent list`, `stn env list` | `list_agents`, `list_environments` | | Add MCP servers | `stn mcp add <name>` | `add_mcp_server_to_environment` | | Sync configurations | `stn sync <env>` | - | | Install bundles | `stn bundle install <url>` | - | | Inspect runs | `stn runs list` | `inspect_run`, `list_runs` | | Deploy | `stn deploy <env>` | - | | Start services | `stn serve`, `stn jaeger up` | - | **Rule of thumb**: CLI for setup, file operations, deployment. MCP tools for programmatic execution and queries within conversations. ## Quick Reference ### Initialization ```bash # Initialize Station with AI provider stn init --provider openai --ship # OpenAI with Ship filesystem tools stn init --provider anthropic --ship # Anthropic (requires OAuth: stn auth anthrop

What's inside
Steps it walks through
  1. When to Use CLI vs MCP Tools
  2. Quick Reference
  3. Initialization
  4. Agent Management
  5. Environment Management
  6. MCP Server Configuration
  7. Bundle Management
  8. Workflow Management
  9. Server & Deployment
  10. Benchmarking & Reports
  11. Runs History
  12. File Structure
  13. Agent File Format (dotprompt)
  14. Multi-Agent Hierarchy (Coordinator Pattern)
Ships with 1 file
  • metadata.json
Commands it runs
Initialize Station with AI provider
stn init --provider openai --ship       # OpenAI with Ship filesystem tools
stn init --provider anthropic --ship    # Anthropic (requires OAuth: stn auth anthropic login)
stn init --provider gemini --ship       # Google Gemini
Initialize in specific directory (git-backed workspace)
stn init --provider openai --config ./my-workspace
Start Jaeger for observability
stn jaeger up                           # View traces at http://localhost:16686
List agents
stn agent list                          # All agents in default environment
More from claude-skill-registry
All skills →
About this skill
What does the station skill do?

Use Station CLI (`stn`) for AI agent orchestration - creating agents, running tasks, managing environments, and deploying agent teams. Prefer CLI for file operations and exploration; use MCP tools for programmatic agent execution and detailed queries.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill station --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going