Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

political-struggle-history

v1.0.0

解说中国和西欧历史上的政治斗争事件。涵盖中国从先秦到清末、西欧从古罗马到19世纪的宫廷政变、党争、权臣专权、宗教冲突、革命等重大政治斗争,并支持中西对比分析。当用户询问历史政治斗争、宫廷政变、权力斗争时自动触发。

0· 583·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name/description (explain Chinese and Western political struggles) matches the bundled reference files and the SKILL.md instructions. Minor mismatch: SKILL.md uses the internal name 'chinese-political-struggles' while registry lists 'political-struggle-history' — not harmful but inconsistent. Including a script that performs web searches is coherent with the advertised '--search' feature.
!
Instruction Scope
SKILL.md instructs the agent to run a local Python script to perform web searches and to use Read and Bash. The instructions explicitly tell the agent to run: python "$(dirname "$SKILL_PATH")/scripts/search_views.py" ... and provide a fallback absolute path (/Users/hazelnut/Documents/Skills/...). That fallback reveals a developer-local path and is brittle; it may prompt the agent to attempt reading/writing beyond the skill folder in some environments. The instructions also direct fetching and presenting external search results and links (expected for --search), and to run Bash to debug script errors — running arbitrary Python + Bash is powerful and should be allowed only with user consent.
Install Mechanism
There is no install spec (instruction-only), which reduces disk-write risk, but the included script imports a third-party package ('tavily' / tavily-python). The skill does not declare that dependency, so runtime execution will fail unless the environment has that package installed or the agent installs it dynamically (pip). Lack of an install/installation-offer increases the chance of runtime surprises if the agent attempts to pip install packages.
!
Credentials
The SKILL.md and scripts require the environment variable TAVILY_API_KEY to perform searches, but the skill metadata lists no required env vars. This is an inconsistency: the skill will request a secret (API key) at runtime that wasn't declared in registry metadata. The Tavily key would allow the script to send user queries to an external service (expected for search), so the user should know that queries will be transmitted to Tavily when using --search. No other unrelated credentials are requested.
Persistence & Privilege
The skill is not force-included (always:false) and does not request system-wide config or permanent presence. It does run code only when invoked (or when the agent autonomously decides to call it under normal skill invocation rules). No indications it modifies other skills or agent configs.
What to consider before installing
This skill looks like a legitimate historical explainer, but it has a few practical and privacy-related mismatches you should consider before installing or enabling it: (1) SKILL.md and scripts require a TAVILY_API_KEY (an external API key) but the skill metadata does not declare this — providing that key will let the script send search queries and results (including the user's query text) to Tavily; (2) the bundled search script depends on the third‑party Python package 'tavily' (tavily-python). The package isn't declared in an install spec, so running the skill may fail or cause the agent to pip install packages at runtime; verify the package's provenance before allowing installs; (3) SKILL.md contains an absolute developer path (/Users/hazelnut/...) as a fallback — harmless by itself but a sign the author used a local dev environment and the fallback could cause the agent to attempt reading unexpected local paths in some setups; (4) the skill runs a Python script via Bash when --search is used, so only use the search feature if you trust sending queries to an external service and are comfortable the environment has the proper dependency. Recommendations: (A) if you will use the skill without networked search, disable or ignore the --search option; (B) if you want the search feature, obtain and review the tavily-python client and Tavily's privacy policy, and provide a dedicated API key with minimal scope (or test in an isolated environment); (C) ask the publisher for an explicit dependency/installation spec and a reason for the absolute-path fallback or for them to remove it; (D) if unsure, run the skill in a sandboxed/isolated environment or decline to install until the env var and dependency are declared in the registry metadata.

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

latestvk979krypv6p57gwqdnmyjkycp9816pv7

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments