seo-suite
v1.1.0Comprehensive SEO suite combining audit, content planning, and strategic optimization. Diagnose SEO issues, create content strategies, plan topic clusters, a...
⭐ 0· 787·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the content of SKILL.md: it describes an SEO audit and content-planning workflow. The skill does not declare unrelated binaries, credentials, or config paths that would be out of scope for an SEO suite.
Instruction Scope
The runtime instructions are an SEO framework, scope gate questions, and auditing checklist. It asks whether the user can provide access to Google Search Console / Analytics (as context questions) but does not instruct the agent to read arbitrary system files or exfiltrate data.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes disk/network install risk and is appropriate for a documentation-style skill.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The SKILL.md only asks about data access as user-provided context (e.g., GSC/Analytics), which is appropriate for its purpose.
Persistence & Privilege
always is false and model invocation is allowed (the platform default). The skill does not request persistent installation or system-wide changes in the provided content.
Assessment
This appears to be a coherent, instruction-only SEO skill. Before installing or using it, confirm the full SKILL.md (the provided snippet shows truncation) and be cautious about granting any account access: if you give Google Search Console or Analytics access, prefer read-only or delegated/OAuth access rather than sharing full account credentials. If later versions add install scripts or request environment variables/keys, reevaluate — those would change the risk profile. If you plan to let the agent act autonomously with account access, consider limiting its permissions and reviewing activity logs.Like a lobster shell, security has layers — review code before you run it.
latestvk972byda6tjbywak48pwyfwbyh81cktb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
