Landing Page Builder

Build premium static landing pages with the Stomme/PolyTrader design system. Glass morphism, CSS custom properties, separated copy, responsive, Cloudflare Pa...

This package appears coherent with its purpose, but review and adapt the included scripts before executing them: - Change the default site in references/validate-live-template.js from https://stomme.ai to your target URL so validations run against your deployment (otherwise the script will open headless browsers to an external domain). - The validate script uses Playwright (chromium) and Node — install playwright and add required Node deps in your dev environment and CI before running it. - The pre-push script will block git pushes on failing checks; read references/pre-push-check-template.sh and confirm its checks/grep patterns match your repo structure, and rename the theme/localStorage keys (it uses 'stomme-theme' by default). - Inspect the scripts for any external network calls you don't expect (the validation script intentionally makes HTTP requests to the target site). Run them in a controlled environment first. - Adding .githooks/pre-push and CI wiring modifies your repository — commit/push those changes only after verifying the scripts. If you are uncomfortable with automated hooks or running headless browser tests, skip or adapt those steps. If you want, I can point out exact lines to change (e.g., the SITE constant in validate-live-template.js and the KEY in the theme scripts) or produce an adapted copy configured for your domain and preferred localStorage key.

Type: OpenClaw Skill Name: stomme-landing-page-builder Version: 1.2.0 The skill bundle provides a comprehensive framework for building landing pages but includes instructions for the agent to generate and execute shell scripts (scripts/pre-push-check.sh) and run browser automation tests via Playwright (scripts/validate-live.js). While these capabilities are plausibly needed for the stated purpose of site validation and deployment readiness, the execution of agent-generated shell code and network-active browser testing are high-risk primitives that warrant caution, despite the lack of clear malicious intent in the provided templates.