halo-dev/cli

halo-cli-shared

Use when a task involves Halo CLI, Halo CMS command-line operations, or terminal-based Halo management.

First seen Mar 20, 2026

Installation

$ npx skills add halo-dev/cli --skill halo-cli-shared

Summary

  • Use when a task involves Halo CLI, Halo CMS command-line operations, or terminal-based Halo management.
  • Also use when you need shared rules for profiles, JSON output, help discovery, config paths, and destructive actions.
  • Trigger this skill whenever the user mentions 'halo', 'Halo CLI', or terminal operations for Halo CMS, even if the specific command area is not yet clear.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from halo-dev/cli · top by installs.

npx skills add halo-dev/cli

Browse all from halo-dev/cli

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 29
License LICENSE
Default branch main
Open issues 2
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
Declared agents clawdbot
More metadata
openclaw
{"category":"developer-tools","requires":{"bins":["halo"]},"cliHelp":"halo --help"}

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,374 B
  • docs SUMMARY.md 399 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 79 installs

SKILL.md

Halo CLI Shared

Start here when the task says "use Halo CLI" but does not yet say whether it is auth, content, search, operations, or moderation.

Install And Verify

Install globally:

npm install -g @halo-dev/cli

Binary name:

halo

Check version and top-level help:

halo --version
halo --help

Top-Level Areas

  • auth
  • post
  • single-page
  • search
  • plugin
  • theme
  • attachment
  • backup
  • moment
  • comment
  • notification
  • completion <shell> — Generate shell completion script (bash, zsh, fish, powershell)

Shared Rules

  • Most command areas require an authenticated profile.
  • Use halo auth login to create a profile.
  • Use --profile <name> when more than one profile exists.
  • Use --json when output is meant for automation or follow-up parsing.
  • In non-interactive mode, dangerous commands usually require --force.
  • Read --help before guessing flags for a specific command.

Public vs Authenticated

Most areas require auth.

The main public workflow is halo search, which can use a direct site URL without login:

halo search --keyword "halo" --url https://www.halo.run

Config And Secrets

Profile metadata is stored in:

  • $HALOCLICONFIGDIR/config.json if HALOCLICONFIGDIR is set
  • otherwise $XDGCONFIGHOME/halo/config.json
  • otherwise ~/.config/halo/config.json

Credentials are stored in the system keyring.

Routing

  • Use halo-cli-auth for login, current profile, profile list/use/delete, and credential repair.
  • Use halo-cli-content for posts and single pages.
  • Use halo-cli-search for public site search.
  • Use halo-cli-operations for themes, plugins, attachments, backups, and moments.
  • Use halo-cli-moderation-notifications for comments, replies, and notifications.