Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Auto Content
v1.0.2Full end-to-end SEO + GEO content creation pipeline for crypto/Web3 teams. Trigger this skill when the user wants to: write a blog post or article, research...
⭐ 2· 438·1 current·1 all-time
by@kaokray
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 to perform a full SEO/GEO and UGC mining pipeline, which explains the need for web searches and optional third‑party APIs. However SKILL.md repeatedly references local reference files (references/*.md) and tools (e.g., matplotlib, Google Trends, ubersuggest, Ahrefs/SEMrush) yet the package contains only SKILL.md and declares no installs or required credentials. That mismatch (instructions require resources not packaged or declared) is incoherent: either those files/tools must be provided or the skill can't reliably do what it promises.
Instruction Scope
The runtime instructions direct the agent to run web searches, fetch UGC pages and comments, mine and paraphrase user-generated content, and auto-run a 'X Trend Monitor' at the start of every session before any user input. Those steps are within the stated purpose, but they include proactive, session-start scraping and reading of external pages (including login-walled content fallback) and require network/browsing capabilities. The SKILL.md also references multiple local reference files for rubrics/blacklists/output templates that do not exist in the manifest — the instructions therefore assume resources that are not present, creating an operational and safety gap.
Install Mechanism
There is no install spec and no code files, which lowers direct supply-chain risk (nothing is downloaded or written to disk by the skill itself). However, the instructions implicitly expect external tooling and libraries (matplotlib, API clients) or platform browsing/network tools to be available; the skill does not declare or verify those dependencies.
Credentials
The skill declares no required environment variables or primary credential. It will optionally ask the user for Ahrefs/SEMrush API keys if available. That is proportionate in isolation, but the instructions also rely heavily on web searches and third-party services (Google Trends, ubersuggest, X/Twitter) without declaring how credentials, rate limits, or API access should be provided. The lack of declared credentials or config locations for expected external services is an inconsistency to watch.
Persistence & Privilege
The skill is not marked always:true, but SKILL.md instructs Stage 0 (X Trend Monitor) to 'auto-run on session start, propose hot keywords before the user asks.' This behavior (proactive scanning at session start) is a privilege/behavioral expectation not reflected in the manifest flags. Autonomous invocation is platform-default, so it could run without an explicit user trigger; users should be aware this skill is designed to act proactively and fetch external content unless you restrict or disable autonomous invocation.
What to consider before installing
What to consider before installing:
- Missing reference files: SKILL.md refers to references/*.md (rubrics, blacklists, templates) that are not included in the package. Ask the publisher where those files live or require them to be bundled before trusting outputs.
- Proactive scraping: The skill is written to auto-run a 'X Trend Monitor' at session start and to fetch external pages/comments. If you don't want an agent to actively search and scrape content without explicit consent every session, disable autonomous invocation or refuse to enable session-start triggers.
- External APIs and tooling: The skill expects Google Trends, ubersuggest, matplotlib, and optionally Ahrefs/SEMrush data, but declares no installs or credentials. Do not provide API keys unless you understand exactly how they’ll be used and stored. Prefer scoped, read-only keys with limited privileges if you must supply them.
- UGC handling risk: The skill will fetch and paraphrase user-generated content and instructs not to fabricate—but paraphrasing UGC or summarizing login-walled content can produce errors or inadvertently expose sensitive user data. Ask for explicit description of how paraphrases are sourced and disclosed.
- If you want to proceed: request that the skill author provide the referenced files, a clear list of external tools/APIs required, and a privacy/security statement explaining what data is fetched, where outputs are sent, and whether keys are persisted. Consider running it with autonomous invocation disabled and with test/spec inputs first.
Confidence note: Medium — the instructions broadly match the stated purpose, but multiple missing artifacts and the session-start auto-run instruction create notable inconsistencies that need author clarification before trusting this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk979rm46f4vf7w8f77w2wje4x581vfke
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
