SEO + GEO Content Engine

Use when the user wants to write an SEO article, generate a blog post, create content for a keyword, run the full SEO pipeline, or check available keywords....

This skill appears to implement a legitimate SEO/GEO pipeline, but there are several packaging/metadata mismatches you should clear up before installing: 1) Confirm whether SERPAPI_API_KEY and GOOGLE_SHEETS_TRACKER_URL are truly required or optional (SKILL.md says required, manifest calls them optional, registry summary said none). 2) Don't provide a private Google Sheets URL unless you trust the skill author — prefer a read-only/public tracker or paste CSV exports. 3) If you supply SERPAPI_API_KEY, ensure the key has appropriate limits and is revocable; consider using an account with minimal quota. 4) The repository/license metadata is inconsistent (README shows MIT badge while manifest lists Apache-2.0) and the published source/owner identity is not clearly verifiable — prefer skills with a known GitHub org or author. 5) If you still want to try it, run it in a restricted/test environment, monitor requests (to ensure it uses the declared APIs only), and avoid giving access to production secrets until you verify behavior. If possible, ask the publisher to correct the manifest/registry metadata so required vs optional env vars and the license are explicit.

Type: OpenClaw Skill Name: seo-geo-content-engine Version: 1.0.4 The skill bundle defines a legitimate 5-step programmatic SEO and GEO content generation pipeline. It utilizes standard external integrations like SerpAPI and Google Sheets for keyword tracking and SERP analysis, with explicit instructions in SKILL.md to handle missing environment variables by requesting manual user input rather than attempting unauthorized access. No evidence of malicious intent, data exfiltration, or suspicious execution logic was found across the code or documentation.