ClawHub

Halo Cli Shared

v0.1.1

Use when a task broadly involves Halo CLI and the correct command area is not yet clear, or when you need shared rules for profiles, JSON output, help discov...

⭐ 1· 183·0 current·0 all-time
byRyan Wang@ruibaby

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for ruibaby/halo-cli-shared.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Halo Cli Shared" (ruibaby/halo-cli-shared) from ClawHub.
Skill page: https://clawhub.ai/ruibaby/halo-cli-shared
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: halo
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install halo-cli-shared

ClawHub CLI

Package manager switcher

npx clawhub@latest install halo-cli-shared
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the content: the SKILL.md provides general guidance for using the Halo CLI, lists relevant command areas, and expects the 'halo' binary. There are no unrelated credential requests or unrelated binaries.
✓
Instruction Scope
Instructions stay within the stated purpose: they explain installing the CLI, checking version/help, which subcommands are relevant, config paths, and rules for profiles/JSON/force flags. The doc references config file locations and the system keyring for credentials but does not instruct reading or exfiltrating those files.
ℹ
Install Mechanism
The skill has no formal install spec (instruction-only). SKILL.md suggests running 'npm install -g @halo-dev/cli' which is a normal way to install a CLI but means the user would execute an external package install; users should verify the package name and source before installing globally, and avoid running such installs as root where unnecessary.
✓
Credentials
The skill does not declare or require any environment variables or credentials. It documents common config locations (HALO_CLI_CONFIG_DIR, XDG_CONFIG_HOME, ~/.config/halo) and notes credentials live in the system keyring; that documentation is proportional to a CLI helper and does not request unrelated secrets.
✓
Persistence & Privilege
always is false and there is no install-time code or persistent agent modification. The skill is instruction-only and does not request elevated or persistent privileges.
Assessment
This is an instruction-only helper for the Halo CLI and appears coherent. Before proceeding: (1) confirm you trust the npm package name '@halo-dev/cli' and install it from an official source (avoid arbitrary URLs); (2) avoid global installs as root if not necessary; (3) be aware the CLI stores config under XDG/~/ .config and uses your system keyring for credentials—do not share those files or keyring contents with third parties; (4) the skill does not request any secrets, but always verify any recommended commands before running them. If you want stronger assurance, check the '@halo-dev/cli' package homepage/repository and its release artifacts before installing.

Like a lobster shell, security has layers — review code before you run it.

Plugin bundle (nix)
Skill pack · CLI binary · Config
SKILL.mdCLIConfig
CLI help (from plugin)
halo --help

Runtime requirements

Binshalo
latestvk9727rgjt4qgbh64hjwgbp38gn83j96d
183downloads
1stars
2versions
Updated 1mo ago
v0.1.1
MIT-0
Ryan Wang@ruibaby
latest
Download

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

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.

Comments

Loading comments...