Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Listenhub
v0.1.0Explain anything — turn ideas into podcasts, explainer videos, or voice narration. Use when the user wants to "make a podcast", "create an explainer video",...
⭐ 0· 355·0 current·0 all-time
by@0xfango
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill name/description align with the code: scripts call a media-generation API (api.marswave.ai / labnana). However the registry metadata declares no required environment variables while the scripts clearly require LISTENHUB_API_KEY and expect jq/curl. That mismatch (metadata says 'none' but the implementation requires an API key and common CLI tools) is an incoherence that should be resolved.
Instruction Scope
SKILL.md instructs the agent to only call the provided scripts (consistent with the implementation), but also mandates automatic behaviors (e.g., default to creating a single-speaker podcast when only a topic is given). The scripts read shell rc files to locate API keys and prompt to save API keys into shell rc files. They also perform network calls to external APIs. The combination of automatic generation decisions and reading/writing user config is broader scope than a simple 'format input -> call API' helper.
Install Mechanism
There is no formal install spec (the skill is delivered as scripts), which is low-level risk, but the scripts include code to auto-install missing dependencies via platform package managers (brew, apt-get, yum, pacman, choco, scoop) and will eval those install commands. Auto-installing system packages (possibly requiring sudo) is intrusive and increases risk compared to an instruction-only skill.
Credentials
The scripts require and use an API key (LISTENHUB_API_KEY) for the external service and read/write shell rc files to load/save that key; yet the registry metadata declared no required env vars. The scripts also parse and export API keys from users' ~/.zshrc or ~/.bashrc — accessing and modifying user config and environment variables is sensitive and should have been declared and justified in the metadata.
Persistence & Privilege
The skill does not set always:true (good), but scripts will attempt to persist the API key to shell rc files and can auto-install system packages. Writing to user shell rc files and invoking package-manager installs are persistent and privileged operations relative to a typical helper script; users should expect these side effects.
What to consider before installing
Things to consider before installing or running this skill:
- Metadata mismatch: the registry claims no required env vars, but the scripts require LISTENHUB_API_KEY (lh_sk_...) and expect jq and curl. Treat that as a red flag — confirm the author and update metadata before trusting automatic use.
- External network: the scripts call api.marswave.ai and api.labnana.com and fetch a remote VERSION from raw.githubusercontent.com. If you run them, network requests will be made to those domains.
- API key handling: scripts will try to read your ~/.zshrc ~/.bashrc to auto-load an API key and can append an export line if you paste a key during setup. If you are uncomfortable with that, set LISTENHUB_API_KEY yourself in a safe, limited-scope environment before running, or avoid letting the script auto-write your shell rc.
- Auto-install behavior: generate-image.sh can automatically run package-manager install commands (brew/apt/yum/pacman/choco/scoop). That can run sudo or require elevated privileges. Review and run install commands manually rather than allowing automatic installs.
- Least privilege: create and use a dedicated API key with minimal scope/quota for this skill, not your primary account key. Avoid sending sensitive or confidential text/URLs to the skill (SKILL.md itself warns against this).
- Review & sandbox: because the repo contains executable scripts that modify local configs and call remote APIs, review the script sources yourself and consider running them in an isolated environment (container, VM) first.
If you want to proceed: confirm/declare LISTENHUB_API_KEY in the skill metadata, inspect the scripts (especially the auto-install and shell-rc write paths), and either set up the API key manually or be prepared to paste it (knowing the script will persist it). If any of the above behaviors are unacceptable, do not install or run this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk970yvq5tchhteg3y6aqmxfmvd822ky5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
