How do I install the Helix Org CLI skill?

Run npx skillmds@latest add helixml/helix-org-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Helix Org CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Helix Org CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Helix Org CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Helix Org CLI?

helixml (@helixml) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Helix Org CLI by helixml — Agent Skill

Name: Helix Org CLI
Author: helixml

Helix Org CLI

Use the Helix CLI to operate helix-org (bots, topics, processors, chat) and raw REST via helix api. Use when listing/managing org bots, chatting with chief-of-staff or other bots, or calling any authenticated Helix API path.

helixml 98cc5a3 2.2 KB Updated Sep 17, 2026

File contents

Helix-org CLI

Auth (required):

export HELIX_URL=http://localhost:8080   # or your control plane
export HELIX_API_KEY=hl-…                # user API key (never the runner token)
export HELIX_ORG=unmanned-org            # optional default org (name or id)

Build (from repo root):

cd api && CGO_ENABLED=0 go build -o /tmp/helix-bin .

Org graph commands

# Bots
helix org bots list [--org NAME]
helix org bots get <bot-id> [--org NAME]
helix org bots start|stop|restart <bot-id> [--org NAME]
helix org bots chat <bot-id> "message…" [--org NAME] [--timeout 300] [--no-start] [--session ses_…]

# Topics / processors
helix org topics list [--org NAME]
helix org processors list [--org NAME]

bots chat resolves the bot’s project exploratory session (starts the agent if needed), sends the message to /sessions/{id}/chat, and prints the assistant reply.

Escape hatch — `helix api` (like `gh api`)

helix api /orgs/unmanned-org/bots
helix api -X POST /orgs/unmanned-org/bots/chief-of-staff/activate
helix api -X POST /orgs/unmanned-org/bots/b-mason/stop
helix api --input '{"…":…}' -X POST /sessions/chat
echo '{"message":"hi"}' | helix api -X POST /sessions/ses_…/chat --input -

Path may be /orgs/…, /api/v1/orgs/…, or a full URL. Always authenticated with HELIX_API_KEY.

Typical agent workflow

helix org bots list --org unmanned-org — see who is running.
helix org bots chat chief-of-staff --org unmanned-org "…" — talk to CoS.
If a first-class command is missing: helix api GET /orgs/unmanned-org/….

Notes

Prefer org name (unmanned-org) or full id (org_…); both resolve.
Do not use oh-hallo-insecure-token (runner token).
CoS tools (list_bot_repositories, etc.) are MCP tools the bot calls inside its session; the CLI chats with the bot session, it does not expose those MCP tools as CLI verbs (use helix api or chat the bot to invoke them).

---name: helix-org-clidescription: Use the Helix CLI to operate helix-org (bots, topics, processors, chat) and raw REST via helix api. Use when listing/managing org bots, chatting with chief-of-staff or other bots, or calling any authenticated Helix API path.---# Helix-org CLIAuth (required):```bashexport HELIX_URL=http://localhost:8080 # or your control planeexport HELIX_API_KEY=hl-… # user API key (never the runner token)export HELIX_ORG=unmanned-org # optional default org (name or id)```Build (from repo root):```bashcd api && CGO_ENABLED=0 go build -o /tmp/helix-bin .```## Org graph commands```bash# Botshelix org bots list [--org NAME]helix org bots get <bot-id> [--org NAME]helix org bots start|stop|restart <bot-id> [--org NAME]helix org bots chat <bot-id> "message…" [--org NAME] [--timeout 300] [--no-start] [--session ses_…]# Topics / processorshelix org topics list [--org NAME]helix org processors list [--org NAME]````bots chat` resolves the bot’s project exploratory session (starts the agent if needed), sends the message to `/sessions/{id}/chat`, and prints the assistant reply.## Escape hatch — `helix api` (like `gh api`)```bashhelix api /orgs/unmanned-org/botshelix api -X POST /orgs/unmanned-org/bots/chief-of-staff/activatehelix api -X POST /orgs/unmanned-org/bots/b-mason/stophelix api --input '{"…":…}' -X POST /sessions/chatecho '{"message":"hi"}' | helix api -X POST /sessions/ses_…/chat --input -```Path may be `/orgs/…`, `/api/v1/orgs/…`, or a full URL. Always authenticated with `HELIX_API_KEY`.## Typical agent workflow1. `helix org bots list --org unmanned-org` — see who is running.2. `helix org bots chat chief-of-staff --org unmanned-org "…"` — talk to CoS.3. If a first-class command is missing: `helix api GET /orgs/unmanned-org/…`.## Notes- Prefer org **name** (`unmanned-org`) or full id (`org_…`); both resolve.- Do **not** use `oh-hallo-insecure-token` (runner token).- CoS tools (`list_bot_repositories`, etc.) are MCP tools the bot calls inside its session; the CLI chats with the bot session, it does not expose those MCP tools as CLI verbs (use `helix api` or chat the bot to invoke them).

Frequently asked questions