skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
halo-dev/cli92 installs

halo-cli-shared

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.

How do I install this agent skill?

npx skills add https://github.com/halo-dev/cli --skill halo-cli-shared
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides instructions and routing for the Halo CLI tool. It includes installation steps for the official package from the npm registry and documents common command patterns for managing Halo CMS. No malicious behavior, obfuscation, or suspicious external references were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

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
  • shop — Halo Pro/Commercial shop management
  • 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.
  • Use halo-cli-shop for products, orders, customers, coupons, discounts, shop statistics, and shop configuration.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/halo-dev/cli/halo-cli-shared">View halo-cli-shared on skillZs</a>