Webflow
v1.0.0Build, launch, and optimize Webflow sites with responsive design, CMS architecture, and clean handoffs.
⭐ 0· 965·2 current·2 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name, description, and included docs (design, CMS, integrations, optimization) are consistent. The guidance and examples are appropriate for a Webflow-focused skill and do not request unrelated cloud credentials or unrelated system tools.
Instruction Scope
SKILL.md instructs the agent to 'Read on activation' and to create ~/webflow and ~/webflow/memory.md for user preferences. Those file reads/writes are not declared in the registry metadata (required config paths = none). The skill also contains code examples that reference API/TOKEN constants; while expected for CMS/API usage, the runtime instructions do not explicitly define how tokens are supplied or protected.
Install Mechanism
No install spec and no code files beyond documentation — lowest-risk deployment model. Nothing is downloaded or written by an installer.
Credentials
Registry metadata declares no required env vars, yet cms.md shows use of a Bearer token (TOKEN) for Webflow API and examples reference API/TOKEN variables. The skill also implicitly accesses a local config path (~/webflow/memory.md) without declaring it. This mismatch between declared vs. implied credentials/config access is disproportionate and should be clarified.
Persistence & Privilege
The skill persists a memory file under the user's home directory and will create ~/webflow on first use. It is not set to always:true and does not request system-wide config changes or other skills' secrets, but the local persistence is non-trivial and should be disclosed/approved by the user.
What to consider before installing
This skill appears to be legitimate Webflow documentation and guidance, but it will create and read a local preferences file at ~/webflow/memory.md even though the registry metadata doesn't declare that config path. Before installing or enabling the skill: (1) confirm you are comfortable with it creating ~/webflow and storing preferences there; (2) do not paste API keys or bearer tokens into chat — instead provide them through a secure, deliberate mechanism if the agent asks; (3) review any webhook/third-party endpoint instructions before wiring live endpoints (they can send user data externally); and (4) ask the skill author or registry for clarification / to declare the config path and any expected credential inputs. If you need higher assurance, run the skill in a restricted environment or request the author add explicit declarations of required env vars and config paths.Like a lobster shell, security has layers — review code before you run it.
latestvk97b3zzw8mneyqw82ytzbbeqy9816wxp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌐 Clawdis
OSLinux · macOS · Windows