ClawHub

Poe Usage

v0.5.0

Monitor Poe API point balance and usage history from the terminal using poeusage CLI.

⭐ 1· 75·0 current·0 all-time
byGreg Stephens@rgstephens
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description, required binary (poeusage), and required env var (POE_API_KEY) align with a CLI tool that queries the Poe API for usage and balance information.
✓
Instruction Scope
SKILL.md is instruction-only and confines actions to installing/running the poeusage CLI, reading its config (~/.config/poeusage/config.toml) and using POE_API_KEY. It does not instruct the agent to read unrelated files, exfiltrate data to unknown endpoints, or access unrelated credentials.
ℹ
Install Mechanism
Install uses a Homebrew tap (rgstephens/tap) and formula 'poeusage'. Homebrew installs are common, but this is a third‑party tap (not an official central formula), so you should inspect the tap/formula and upstream repo before trusting the binary.
✓
Credentials
Only POE_API_KEY (and ordinary opt-in envs like NO_COLOR/timeout/page_size) are referenced. Requesting the Poe API key is proportionate to the stated function. The SKILL.md notes storing api_key in ~/.config/poeusage/config.toml is possible but 'not recommended'.
✓
Persistence & Privilege
Skill does not request always:true, does not modify other skills or system-wide settings, and relies on a standalone CLI binary. No elevated persistence or cross-skill privileges are requested.
Assessment
This skill appears to do what it claims: run the poeusage CLI using your POE_API_KEY to report Poe usage. Before installing: (1) review the Homebrew tap and formula (rgstephens/tap) and the upstream repo to confirm the binary's source and build steps; (2) avoid storing your API key in plaintext config files if possible — prefer passing POE_API_KEY at runtime or using a secure credential store; (3) verify the installed poeusage binary (checksums/signature) if provided; and (4) limit the API key's scope/rotate it if you stop using the tool. If you cannot inspect the tap or binary, treat the install as higher risk.

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

costvk97ccxmenkyk79mb7any0gf59d83mzw9latestvk97ccxmenkyk79mb7any0gf59d83mzw9poevk97ccxmenkyk79mb7any0gf59d83mzw9tokenvk97ccxmenkyk79mb7any0gf59d83mzw9usagevk97ccxmenkyk79mb7any0gf59d83mzw9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📊 Clawdis
Binspoeusage
EnvPOE_API_KEY

Install

Homebrew
Bins: poeusage
brew install rgstephens/tap/poeusage

Comments