Skill flagged — suspicious patterns detected

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

Super Marketing Pro

v3.1.0

Full-stack B2B marketing execution skill equivalent to a 10-person agency team. Use for: building ICP and brand messaging, generating multi-platform content...

0· 189·0 current·0 all-time
byDa Wei@wd041216-bit

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for wd041216-bit/super-marketing-pro.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Super Marketing Pro" (wd041216-bit/super-marketing-pro) from ClawHub.
Skill page: https://clawhub.ai/wd041216-bit/super-marketing-pro
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install super-marketing-pro

ClawHub CLI

Package manager switcher

npx clawhub@latest install super-marketing-pro
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description align with included scripts and reference docs: the package legitimately implements ICP/strategy, content repurposing, email sequence, SEO and reporting. However the registry metadata claims 'instruction-only' / no required env vars while the shipped scripts clearly require the openai client and an OPENAI_API_KEY — a manifest mismatch that should have been declared.
!
Instruction Scope
SKILL.md and scripts instruct the agent to run the provided Python scripts (strategy_builder, content_repurposer, email generator, competitor monitor, etc.). Several scripts read user-supplied local files (source docs, batch lists) and pass their contents to an LLM call (via llm_utils.call_llm). That implies sending potentially sensitive content to an external model endpoint. The SKILL.md does not explicitly warn about external data transmission or specify which env var is required in the registry, reducing transparency.
Install Mechanism
No installer or remote download steps are declared; code is bundled with the skill (9 scripts + docs). The only external runtime dependency is the Python 'openai' package (installed via pip), which is expected for LLM-based scripts. There are no obscure download URLs or archive extractions in the manifest.
!
Credentials
The code (llm_utils.py referenced in SKILL.md) requires OPENAI_API_KEY and the SKILL.md/README instructs the user to set an OpenAI-compatible API key and install openai. Yet the registry lists no required env vars or primary credential. That omission is disproportionate and misleading: an API key is necessary for normal operation and will be used to transmit content to an external LLM service.
Persistence & Privilege
Skill is not always:true and is user-invocable; it does not request elevated platform privileges or modify other skill configs. It will be able to run autonomously only if the agent chooses to invoke it (default behavior), which is normal for skills.
What to consider before installing
This skill largely matches its stated marketing function, but exercise caution before installing: 1) The bundled Python scripts call an external LLM and require an OPENAI_API_KEY (and the openai package), but the registry manifest did not list any required env vars — treat that as a red flag and add the missing declaration or ask the author for clarity. 2) Any long-form source files you feed into content_repurposer or other scripts will be sent to the LLM provider; do not include PII, secrets, customer data, or proprietary documents you can't expose. 3) Inspect scripts/llm_utils.py to confirm which endpoint, model, and timeout/retry/logging behavior are used, and ensure API calls are not logged to disk or sent to additional endpoints. 4) Run the skill in an isolated environment first (no production keys) and monitor network calls to confirm only the expected LLM endpoints are used. 5) Prefer creating a scoped/test API key with limited quota and audit logs; if you accept the skill, ask the maintainer to update the manifest to declare OPENAI_API_KEY and other runtime requirements for transparency.

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

b2bvk971btkp6zm35sdg3bej2m257h833b9scontentvk971btkp6zm35sdg3bej2m257h833b9slatestvk971btkp6zm35sdg3bej2m257h833b9sllmvk971btkp6zm35sdg3bej2m257h833b9smanusvk971btkp6zm35sdg3bej2m257h833b9smarketingvk971btkp6zm35sdg3bej2m257h833b9sopenclawvk971btkp6zm35sdg3bej2m257h833b9sseovk971btkp6zm35sdg3bej2m257h833b9s
189downloads
0stars
1versions
Updated 23h ago
v3.1.0
MIT-0

Super Marketing Pro

Full-stack B2B marketing skill. Always run strategy_builder.py first to define ICP before generating any content.

Golden Rule: Strategy First

Never generate copy without an ICP. The workflow is always: ICP → Content → Repurpose → Distribute → Monitor → Report

Scripts

All scripts are in scripts/. Run with python3. Requires openai package (pip3 install openai).

ScriptFunctionKey Args
strategy_builder.pyGenerate ICP, messaging framework, elevator pitch--industry --product
content_repurposer.py1 long-form doc → multi-platform content matrix--source <file.md> --platforms
hashtag_generator.pyPlatform-specific hashtag matrix--content --platforms "linkedin,douyin,xiaohongshu"
content_calendar.pyWeekly/monthly publishing schedule--months --output <file.csv>
email_sequence_generator.py5-stage cold email sequence--target --stages
seo_analyzer.pyLLM-powered Topic Cluster strategy--seed-keyword --depth deep
competitor_monitor.pyBatch competitor battle cards--batch-list <file.txt> --export-format json
data_reporter.pyMulti-month cross-platform ROI report--type monthly --months 1,2,3
llm_utils.pyShared LLM utility (auto-imported)

llm_utils.py uses OPENAI_API_KEY env var. Default model: gemini-3.0-flash. Includes exponential backoff retry (3 attempts).

Execution Workflow

Stage 1 — Strategy: Run strategy_builder.py → get ICP, buyer personas, messaging pillars.

Stage 2 — Content Creation: Based on goal:

  • Awareness/SEO: Run seo_analyzer.py → write long-form pillar content.
  • Lead Gen: Read references/content_templates.md → write whitepaper or case study.
  • Outbound: Run email_sequence_generator.py.

Stage 3 — Repurpose: Run content_repurposer.py on any long-form asset → get LinkedIn post, X thread, TikTok/Douyin script, Xiaohongshu note.

Stage 4 — Distribute: Run hashtag_generator.py for tags, then content_calendar.py for scheduling.

Stage 5 — Convert: Run email_sequence_generator.py for lead nurturing sequences.

Stage 6 — Monitor & Report: Run competitor_monitor.py for battle cards, data_reporter.py for attribution reports.

Knowledge Base (References)

Load the relevant reference file before executing platform-specific tasks:

Strategy: abm_framework.md (ABM + sales alignment), messaging_icp_guide.md (ICP workshop), funnel_strategy.md (TOFU/MOFU/BOFU + attribution)

Channels: linkedin_guide.md, youtube_seo.md, douyin_algorithm.md, xiaohongshu_tips.md

Content: content_templates.md (whitepapers, case studies, emails), keyword_library.md (B2B keyword matrix)

Comments

Loading comments...