category-page-generator
v1.0.1When the user wants to create, optimize, or audit e-commerce category pages or listing pages. Also use when the user mentions "category page," "product categ...
⭐ 0· 89·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (category page generation and optimization) match the SKILL.md content: hierarchy, URL structure, faceted navigation, on-page content, SEO markup, and an audit checklist. Nothing in the instructions requires unrelated capabilities.
Instruction Scope
The runtime instructions are prose-only guidance and stay on-topic. They do direct the agent to read local files if present (.claude/project-context.md or .cursor/project-context.md) to gather product catalog/site structure context — which is reasonable for this skill but means the agent will access repository-local project context files when available. The instructions do not request other files, environment variables, or external endpoints.
Install Mechanism
No install spec or code files are present; this is an instruction-only skill, so nothing is downloaded or written to disk during install.
Credentials
The skill declares no environment variables, credentials, or config paths. The single file-read behavior (project-context files) is proportionate to the stated purpose of tailoring recommendations to a site/catalog.
Persistence & Privilege
always is false and the skill does not request permanent presence or system-wide changes. It does not modify other skills' configs or request elevated privileges.
Assessment
This skill is instruction-only and internally consistent with its purpose, so risk is low. Before enabling it, check whether your repository's .claude/project-context.md or .cursor/project-context.md contain any sensitive data (API keys, passwords, or private endpoints); if they do, remove or sanitize those secrets because the skill explicitly reads those files when present. Also treat the quantitative claims (e.g., "3x more revenue") as guidance rather than guarantees, and review any generated changes (canonical tags, robots rules, redirects) on a staging site before deploying to production.Like a lobster shell, security has layers — review code before you run it.
latestvk975t6n3hxhbtmk24nmbs0e1w183yqjj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
