Halo cli shared

Skill halo-dev/cli/skills/halo-cli-shared

CLI for Halo, Halo for Agents.

Install

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.3 KB, as published. Nobody here has run it

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:

$HALO_CLI_CONFIG_DIR/config.json if HALO_CLI_CONFIG_DIR is set
otherwise $XDG_CONFIG_HOME/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.