Help Scout
v0.0.2CLI for the HelpScout API. Manage conversations, customers, mailboxes, knowledge base articles, and more from the terminal. Covers both Inbox and Docs APIs w...
⭐ 0· 243·0 current·0 all-time
byRoss Morsali@rmorse
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the declared requirement for the 'hs' CLI binary and the SKILL.md documents CLI commands for the Inbox and Docs APIs. The required binary (hs) and the brew install formula align with the stated purpose.
Instruction Scope
Instructions are focused on using the hs CLI and describe auth flows, config location (~/.config/hs/config.yaml), and operations (conversations, docs, uploads, webhooks, etc.). They do direct the agent to operate on local files when uploading attachments/assets and to read/store credentials in the OS keyring and config file. That is expected for a CLI but means the agent may access local files you point it at (attachments) and local secrets in the keyring/config.
Install Mechanism
Install uses a Homebrew formula (operator-kit/tap/hs) which is a package-managed install (lower risk than arbitrary downloads). However, the formula is from a third-party tap (operator-kit/tap) rather than the main homebrew/core; you should verify the tap/source before installing.
Credentials
The skill declares no required environment variables, which is consistent. The SKILL.md does rely on storing and using Help Scout credentials (OAuth client id/secret and Docs API key) in the OS keyring or config file; those are proportionate to a Help Scout CLI but are sensitive and will be read/written by the CLI as part of normal operation.
Persistence & Privilege
The skill does not request always:true or elevated platform privileges. It will install a binary and create/modify its own config and keyring entries (expected behavior for a CLI). The agent's ability to invoke the skill autonomously is the platform default and not by itself a red flag.
Assessment
Before installing: 1) Verify the Homebrew tap operator-kit/tap and inspect its formula/source on GitHub to ensure you trust the provider. 2) Understand that using the skill means the hs CLI will store and read Help Scout credentials from your OS keyring and the config file (~/.config/hs/config.yaml); treat those as sensitive. 3) Be cautious when running commands that upload local files or produce briefings containing conversation text (may include PII) — avoid pointing the CLI at sensitive files unless necessary. 4) If you prefer more control, install the CLI manually, review its binary/source, and perform interactive auth rather than providing credentials via automation. 5) If you have low tolerance for third-party packages, consider obtaining the client from an official Help Scout source or a vetted package repository.Like a lobster shell, security has layers — review code before you run it.
latestvk97eheb76s66vmr7xgzcr42gpn826dy1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📬 Clawdis
Binshs
Install
Install hs (brew)
Bins: hs
brew install operator-kit/tap/hs