Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
HN Digest
v1.0.1Fetch and send Hacker News front-page posts on demand. Use when the user asks for HN, says 'hn', 'pull HN', 'hn 10', or specifies a topic like 'hn health', 'hn hacking', or 'hn tech'. Sends N (default 5) posts as individual messages with Title + Link. Exclude crypto.
⭐ 1· 2.9k·14 current·14 all-time
by@cpojer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims no required credentials or config, but its included code expects a Gemini API key (GEMINI_API_KEY) and also contains an alternate image routine that would use OPENAI_API_KEY. The skill's purpose (HN digest + mood image) can justify needing an image-generation key, but the SKILL.md/registry metadata do not declare any required env vars or explain where keys must come from.
Instruction Scope
SKILL.md tells the agent to run bundled node and shell scripts which: call the HN Algolia API (expected), create a local Python venv and pip-install packages, and run a Python image generator. One image generator (nano_banana_mood.py) will attempt to read ~/.openclaw/openclaw.json to extract a nano-banana-pro apiKey. Reading another skill/agent config file is out-of-scope for a simple HN digest and is not declared in the instructions.
Install Mechanism
No centralized install spec, but the runtime shell script creates ./tmp/hn-venv and pip-installs google-genai and pillow from PyPI. This is traceable (PyPI) and not an arbitrary HTTP download, but it will write files to disk and execute third-party packages — moderate risk and should be disclosed.
Credentials
The code checks for GEMINI_API_KEY (env) and, if absent, reads ~/.openclaw/openclaw.json to find nano-banana-pro.apiKey. That means the skill can access stored agent/skill config and potentially other skills' API keys. The repository also contains mood_image.py which would use OPENAI_API_KEY (not referenced by the main generate script) — the presence of multiple credential paths with no declaration is disproportionate and surprising.
Persistence & Privilege
The skill is not force-included (always: false) and does not request to modify other skills. However, it does read ~/.openclaw/openclaw.json, which leaks a higher-privilege config surface to the skill at runtime — this is a privilege elevation of read-access to agent config and should be considered when enabling the skill.
What to consider before installing
Before installing or enabling this skill, consider the following: (1) The SKILL.md and registry metadata do NOT declare that an image-generation key is required, but the scripts will look for GEMINI_API_KEY (and fall back to reading ~/.openclaw/openclaw.json for nano-banana-pro.apiKey). Decide whether you are comfortable exposing that key or allowing the skill to read your OpenClaw config. (2) The skill will create a local Python virtualenv and pip-install google-genai and pillow — review those packages and be prepared for code to run on your machine. (3) There is an extra image routine (mood_image.py) that would use OPENAI_API_KEY; confirm whether that is intended or dead/leftover code. (4) If you want to proceed, ask the author to: a) explicitly document required env vars and config access in SKILL.md, b) avoid reading ~/.openclaw/openclaw.json (require an explicit env var instead), or c) remove unused credential-using files. If unsure, run the skill in a sandboxed environment or inspect/execute the scripts locally with empty or test credentials first.Like a lobster shell, security has layers — review code before you run it.
latestvk97ckd5809vdyyckta9q39ydkh80db4p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.