run402

Provision Postgres databases, deploy static sites, generate images, and build full-stack webapps on Run402 using x402 micropayments. Use when the user asks t...

Before installing or using this skill: (1) understand it instructs you to run `npm install -g run402` — inspect the npm package source (or use a sandboxed environment) before global install; (2) it will create and store a wallet at ~/.run402/wallet.json and project info at ~/.config/run402/projects.json — consider the privacy/security of storing keys on disk; (3) the manifest can include sensitive values (service_key, OPENAI_API_KEY). Never upload or store admin/service keys unless you trust the service and understand the privilege (service_key bypasses RLS); prefer using anon_key or scoped tokens; (4) the SKILL.md asks the agent to request or solicit on-chain payments from humans — be careful about social-engineering prompts and financial requests; (5) ask the skill author/maintainer for missing metadata (required binaries, exact npm package name and registry URL, where secrets are stored, and why env vars/credentials are not declared). If you proceed, use a disposable/test account, avoid putting production admin keys into manifests, and run the CLI in a contained environment.

Type: OpenClaw Skill Name: run402 Version: 3.0.1 The skill bundle facilitates the use of the 'Run402' platform, which involves high-risk activities such as managing a local crypto wallet (~/.run402/wallet.json), soliciting USDC funds from the user via provided social engineering scripts, and installing a global NPM package (run402). While these actions are aligned with the stated purpose of a micropayment-based hosting service, the combination of financial management, secret handling (e.g., OPENAI_API_KEY), and external CLI dependencies warrants a suspicious classification due to the potential for financial abuse or unauthorized system modifications.