AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Halo Cli Shared

skill-halo-dev-cli-halo-cli-shared · by halo-dev

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.

↗ Website ↗ Repository
— No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-halo-dev-cli-halo-cli-shared

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Halo Cli Shared? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 — 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 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

  • Author: halo-dev
  • Source: halo-dev/cli
  • License: MIT
  • Homepage: https://www.npmjs.com/package/@halo-dev/cli

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills