Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Deep Read
v1.0.0基于研究方法深度分析书籍，提炼核心观点、金句，生成实际应用指导和关联常青笔记。
⭐ 1· 100·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description match the code and SKILL.md: the skill analyzes books and emits insights/evergreen-note links. However, requirements.txt includes openai and obsidian-api even though the shipped code is a local placeholder and the skill does not declare or document required credentials or where Obsidian integration would connect. This is likely sloppy packaging rather than outright malicious, but it's an unexplained dependency.
Instruction Scope
SKILL.md describes inputs (book_title, optional book_file, user_notes) and outputs and does not instruct reading unrelated files, environment variables, or external endpoints. The runtime instructions explicitly say OpenAI or other model calls are a placeholder and should be replaced in the hosting environment.
Install Mechanism
There is no install spec (instruction-only behavior) which is low-risk. But a requirements.txt lists third-party packages (openai, pandas, markdown, obsidian-api). Installing those packages would pull code from PyPI; obsidian-api and openai are notable because they may enable network calls. The repository does not provide an install script or pin trusted release sources.
Credentials
The code imports openai (and requirements list openai) but the skill does not declare any required environment variables (e.g., OPENAI_API_KEY). If the placeholder were replaced with actual API calls, an API key would be needed — this mismatch is unexplained. Similarly, obsidian-api suggests possible integration with a user's Obsidian vault or service, but no config variables or paths are declared. Requesting secrets or vault access without documenting why is a proportionality concern.
Persistence & Privilege
Skill does not request always:true, requires no special config paths, and has no install script that modifies other skills or system-wide settings. It appears to be a normal, non-persistent skill.
What to consider before installing
This skill appears to do what it says (deep book analysis) and its code is a safe placeholder, but there are a few red flags to check before installing:
- The project lists openai and obsidian-api in requirements but does not declare any environment variables (e.g., OPENAI_API_KEY) or explain how Obsidian integration is configured. Ask the author or documentation how API keys or Obsidian credentials are expected to be provided.
- If you install dependencies, they will be fetched from PyPI; review those packages (especially obsidian-api) to ensure you trust them.
- If you must provide an API key (OpenAI or similar) or Obsidian credentials, limit the key permissions and avoid sharing highly privileged credentials.
- Prefer running this in a sandboxed environment and inspect/modify the code yourself to ensure it only calls the services you expect (or remove the unused dependencies if you won't use them).
If the author can confirm how API keys and Obsidian integration should be provided (or remove those dependencies if unused), the inconsistencies would be resolved and the skill would be reasonable to use.Like a lobster shell, security has layers — review code before you run it.
latestvk976ybd25p61923pdpf9bcgs3h83g06y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.