Package SEO
v1.0.0Implements SEO best practices for npm packages, GitHub repos, and AI skills to improve discoverability using keyword-rich descriptions and metadata.
⭐ 1· 1.6k·0 current·0 all-time
byNext Frontier AI@nextfrontierbuilds
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name and the SKILL.md both target SEO/publishing guidance for packages/repos/skills. There are no unrelated env vars, binaries, or install steps requested — everything requested (nothing) is proportional to the stated purpose.
Instruction Scope
Instructions are limited to copy/content/metadata guidance (package.json, README, topics, tags, badges, checklist). It suggests checking external trends (X/Twitter) and adding 'Works With' compatibility claims — these are marketing actions rather than privileged system operations. Minor caution: the guide encourages many keywords and compatibility claims, which can encourage misleading or trademark-heavy listings if not validated.
Install Mechanism
No install spec and no code files — instruction-only skills are lowest-risk for disk writes or arbitrary downloads.
Credentials
The skill requires no environment variables, credentials, or config paths. Nothing disproportionate is requested for the documented goal.
Persistence & Privilege
always:false and disable-model-invocation:false (default) — no elevated persistence. The skill does not request system-wide configuration changes or access to other skills' secrets.
Assessment
This skill is an offline/style checklist and does not request keys or install code, so it is low-risk from a security perspective. Before using: (1) review and adapt the suggested keywords/tags to avoid trademark misuse or false compatibility claims (don’t assert support for services you haven’t tested), (2) avoid keyword stuffing that may violate marketplace policies, and (3) when following badge links (shields.io, npm, GitHub), ensure you publish to the real locations before linking. If you want stronger safety guarantees, ask the author for provenance or examples of published packages that used this exact checklist.Like a lobster shell, security has layers — review code before you run it.
aivk97e13ayk5w24fc0m46k3k75ex80c02aclawdbotvk97e13ayk5w24fc0m46k3k75ex80c02agithubvk97e13ayk5w24fc0m46k3k75ex80c02alatestvk97e13ayk5w24fc0m46k3k75ex80c02amarketingvk97e13ayk5w24fc0m46k3k75ex80c02anpmvk97e13ayk5w24fc0m46k3k75ex80c02apublishingvk97e13ayk5w24fc0m46k3k75ex80c02aseovk97e13ayk5w24fc0m46k3k75ex80c02a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.