← Back to Skills Marketplace
dreamsarts

SEO Content Engine

by DreamsArts · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
123
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install openclaw-seo-content-engine
Description
Research competitors, analyze top-ranking content, and generate a fully SEO-optimized 2000+ word blog post with headings, FAQ, meta description, and internal...
Usage Guidance
This skill mostly does what its description says (scrape competitors and call Gemini to generate copy), but there are three things to consider before installing or running it: 1) GEMINI_API_KEY requirement: The code requires a Gemini API key but the registry metadata omitted any required env vars. Confirm where you should provide the API key and avoid placing other secrets in the same .env file. Prefer passing only the GEMINI_API_KEY via a secure, explicit mechanism rather than relying on a hard-coded file path. 2) Hard-coded .env path: engine.py loads /Users/edwin/.openclaw/workspace/dreams-arts/.env. That is a user-specific path and will pull any variables from that file into the process environment. Either change the code to accept a configurable path or ensure that file contains no secrets you don’t want the script to access. 3) Local Chrome CDP exposure: The script connects to Chrome on localhost:9222 to reuse an active Google session for scraping. This gives the script access to your browser context (open tabs, cookies, session state). Only run this in an environment where you consent to that access — ideally in a disposable or isolated profile/browser instance with no sensitive accounts logged in. Additional suggestions: review the rest of the script (generation calls truncated in provided file) to confirm it does not transmit scraped content or cookies to any unexpected remote endpoints beyond the Gemini API. If you need lower risk, run the research step separately in a controlled environment (or use skip-research) and keep the generation step limited to supplying only the minimal required inputs (keyword and a dedicated API key). If the author can update the skill to remove the hard-coded .env path and declare GEMINI_API_KEY in metadata, my concerns would be reduced.
Capability Analysis
Type: OpenClaw Skill Name: openclaw-seo-content-engine Version: 1.0.0 The skill is a functional SEO content engine that uses Playwright to scrape Google search results and competitor articles, then uses the Gemini API to generate blog posts. The code logic in engine.py is consistent with the stated purpose in SKILL.md and includes basic input sanitization for search queries. While it contains a hardcoded absolute path to a .env file (/Users/edwin/.openclaw/workspace/dreams-arts/.env) and requires an active Chrome session with remote debugging enabled (port 9222), these appear to be development artifacts or functional requirements rather than indicators of malicious intent.
Capability Assessment
Purpose & Capability
The code and SKILL.md implement SEO research (SERP scraping, PAA extraction, competitor heading analysis) and generation via Gemini, which matches the skill's stated purpose. However the skill's registry metadata declared no required env vars or credentials while both SKILL.md and engine.py require a GEMINI_API_KEY and a running Chrome with remote debugging. That registry omission is an inconsistency.
Instruction Scope
Runtime instructions and the script perform web scraping of Google and visit competitor pages (expected for research). But SKILL.md and engine.py point to a specific, hard-coded dotenv file path (/Users/edwin/.openclaw/workspace/dreams-arts/.env). engine.py calls load_dotenv on that path, which will load any environment variables contained there — not just GEMINI_API_KEY — and this is surprising and broad in scope. The script also connects to a local Chrome via CDP (localhost:9222), which exposes the full browser session to the tool; that can include cookies and logged-in sessions beyond what is necessary to fetch SERP results.
Install Mechanism
No install spec included; SKILL.md asks for standard Python packages (google-generativeai, playwright) and Chrome with remote debugging. These dependencies are proportionate to scraping + using Gemini. There are no external download URLs or archive extraction steps in the skill bundle.
Credentials
The skill requires GEMINI_API_KEY (used to configure google.generativeai) but the registry metadata does not list any required env vars — a discrepancy. More importantly, engine.py explicitly loads a hard-coded .env file from a specific user path, which could contain other secrets; even though the script only references GEMINI_API_KEY, loading that file has side effects (it populates the process environment) and is disproportionate and surprising. Requiring Chrome CDP access also broadens required privileges (access to browser session state).
Persistence & Privilege
The skill does not request persistent installation flags (always: false) and does not appear to modify other skills or system-wide configurations. It runs on-demand and needs no special platform privileges beyond network and local browser access.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install openclaw-seo-content-engine
  3. After installation, invoke the skill by name or use /openclaw-seo-content-engine
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the SEO Content Engine. - Generates fully SEO-optimized, ready-to-publish 2000+ word blog posts based on a target keyword. - Analyzes top-ranking competitor articles and structures via automated web research. - Outputs Markdown articles with frontmatter, FAQ, meta description, and suggested internal links. - Customizable writing style, word count, brand, location, and language options. - Built-in SEO best practices: keyword density, LSI integration, headings, and readability. - CLI and Python API support for flexible integration.
Metadata
Slug openclaw-seo-content-engine
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is SEO Content Engine?

Research competitors, analyze top-ranking content, and generate a fully SEO-optimized 2000+ word blog post with headings, FAQ, meta description, and internal... It is an AI Agent Skill for Claude Code / OpenClaw, with 123 downloads so far.

How do I install SEO Content Engine?

Run "/install openclaw-seo-content-engine" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is SEO Content Engine free?

Yes, SEO Content Engine is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does SEO Content Engine support?

SEO Content Engine is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created SEO Content Engine?

It is built and maintained by DreamsArts (@dreamsarts); the current version is v1.0.0.

💬 Comments