Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

SvelteKit WebApp

v1.1.1

Scaffold and configure a production-ready SvelteKit PWA with opinionated defaults. Use when: creating a new web application, setting up a SvelteKit project,...

0· 1.4k·2 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name and description (scaffold a SvelteKit PWA) align with the runtime instructions (scaffold, add addons, configure PWA, deploy). However, the manifest metadata declares no required binaries or config paths while the SKILL.md explicitly requires/uses CLIs (sv/pnpx, pnpm, gh, vercel, optional turso) and reads a user config (~/.openclaw/workspace/SKILL-CONFIG.json). That mismatch between declared requirements and actual instructions is an incoherence worth flagging.
!
Instruction Scope
The SKILL.md instructs the agent to run shell commands (git init/branch, pnpx sv create, pnpm install, gh repo create, vercel link, push to remote), to read and append project files (prd.json, progress.txt), and to check a user config at ~/.openclaw/workspace/SKILL-CONFIG.json. Most of these actions are within the stated purpose, but reading a file in the user's home directory is not declared, and the skill's autonomous-agent prompt (Ralph) directs repeated file reads/writes and commits. The skill claims commands will only run with user approval, but the instructions give the agent broad latitude to modify the repo and push to remote services once approved.
Install Mechanism
This is an instruction-only skill with no install spec or downloaded code. That is the lowest install risk: nothing is written to disk by an installer. The runtime will rely on local CLIs being present, per SKILL.md.
Credentials
The skill requests no environment variables or credentials in its registry metadata, which is plausible because most actions use the user's local CLI authentication (gh/vercel) or interactive token flows. However SKILL.md references environment variables and .env.example (for the generated app) and commands (gh, vercel) that implicitly rely on authenticated CLI sessions. The skill also references checking Vercel/GH/Turso auth but does not declare any required secrets or config paths—this implicit reliance should be made explicit to users before granting permissions.
Persistence & Privilege
always is false (no forced persistent inclusion). The skill asks for exec, Write, Edit and browser tools (in SKILL.md), and includes an autonomous-agent prompt (Ralph) that directs iterative code changes, tests, commits, and pushes. Autonomous invocation is allowed by the platform default, which increases blast radius if the agent is given exec/write privileges; combined with the instruction to create/push repos, this is a capability users should explicitly review, but it is not automatically a policy violation.
What to consider before installing
This skill appears to be a realistic scaffolding and deployment helper for SvelteKit, but it has a few mismatches you should be aware of before installing or granting tools: - The SKILL.md expects local CLIs (pnpm/pnpx sv, gh, vercel) and will run shell commands to create repos, commit, and push — ensure you want an agent to run those commands and that your CLI is authenticated the way you intend. - The skill will read a user config at ~/.openclaw/workspace/SKILL-CONFIG.json (not declared in metadata). If that file contains sensitive data, review it first or remove it. - The 'Ralph' autonomous prompt instructs the agent to append to files, run tests, and commit/push. Confirm you will approve each action (the doc says commands require approval) and that you will review PRD/progress.txt changes before allowing pushes. Recommendations: - Review the full SKILL.md (especially the PRD and Ralph prompt) and verify you are comfortable with an agent creating repos and pushing code. - Keep backups of any repositories the skill might modify and run the scaffold locally yourself first if unsure. - If you want tighter controls, require the skill to declare required tools/paths explicitly or run the scaffolding steps manually following the generated PRD. If you want, I can highlight the exact lines in SKILL.md that reference the home config, the CLI checks, and the autonomous agent prompt so you can review them before proceeding.

Like a lobster shell, security has layers — review code before you run it.

latestvk972cxq3vm8xaesm37r3tppv3n81b5g4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments