Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
AI Labs Builder
v1.0.0AI Labs Builder - Create modern websites, AI applications, dashboards, and automated workflows. Unified system for building production-ready projects with Ne...
⭐ 0· 769·3 current·3 all-time
by@slemo54
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's stated purpose is to scaffold websites, AI apps, dashboards and workflows — which explains the included Bash/Node scripts and npm installs. However, metadata declares no required environment variables or credentials while the code and SKILL.md clearly expect provider API keys (OpenAI/Anthropic/Claude, Pinecone, etc.). This mismatch (no declared env requirements but many references in code) is incoherent and increases risk.
Instruction Scope
SKILL.md and the provided scripts instruct the agent to run shell scripts that create projects, call npx/create-next-app and npm install packages, and write many files into the current working directory. Instructions allow Read/Write/Edit/Bash/Node tools (broad file and command access). The instructions do not attempt obvious exfiltration, but they do instruct network operations (npm installs, possible API calls) and create an MCP stdio server in workflow code. Also, some referenced commands/files (deploy.sh, integrate.sh) are invoked by the CLI but are absent from the manifest — a functional inconsistency.
Install Mechanism
No formal install spec is declared (instruction-only), but the included scripts perform live package installs via npm and run npx. That means the skill will pull many packages from public registries at runtime (moderate risk). There are no downloads from unknown URLs in the manifest, but running npm install will fetch third-party packages (traceable but should be reviewed).
Credentials
Although the registry metadata declares no required env vars, the code and SKILL.md reference multiple secrets: OPENAI_API_KEY, CLAUDE_API_KEY / ANTHROPIC_API_KEY (inconsistent naming), PINECONE_API_KEY, and NEXT_PUBLIC_* vars. Requiring these without declaring them is disproportionate and confusing. The skill will encourage use of provider credentials to enable AI features; the user should not provide high-privilege keys without audit or scoping.
Persistence & Privilege
always:false (normal). The skill will write many files and create project directories in the current working directory (expected for a scaffolder). The SKILL.md metadata references a state dir ".ailabs" (stateDirs) — this indicates it may store per-project state. There is no evidence it modifies other skills or system-wide agent settings, but because allowed-tools include Bash and Node, the agent could execute arbitrary shell commands if invoked — that capability is expected here but increases blast radius.
What to consider before installing
Summary of what to consider before installing/running this skill:
- Missing/undeclared secrets: The manifest lists no required environment variables, but the scripts and code expect provider API keys (OpenAI, Anthropic/Claude, Pinecone). Do not set or expose high-privilege API keys to this skill until you audit the code and understand where keys are used and stored.
- Inconsistent env names: The code uses different variable names for the same provider (e.g., ANTHROPIC_API_KEY vs CLAUDE_API_KEY). Verify and standardize names to avoid confusion and unintended key leakage.
- Network and package installs: The scripts run npx/create-next-app and npm install many packages. Running the skill will cause network activity and install third-party packages — review package lists and consider running in an isolated environment (container, VM) or offline audit first.
- Missing referenced scripts: The main CLI references deploy.sh and integrate.sh, but those files are not present in the provided manifest. That could break functionality or be a sign the package is incomplete; request the missing files or avoid running commands that call them.
- File-system and command execution scope: The skill's purpose requires writing files and running Node/npm commands. If you allow the agent to run Bash/Node, understand it can execute arbitrary commands on the host. Prefer to run the CLI inside a disposable container or sandbox.
- MCP/stdio server: The workflow generator builds an MCP server that listens on stdio. Understand what exposes and how workflows/tools are registered before enabling network or production use.
Immediate recommendations:
- Inspect the full package (missing files) locally and review package.json and the actual list of npm dependencies before running npm install.
- Run the tool in a sandbox (container/VM) rather than on a sensitive machine.
- Provide least-privilege API keys (scoped tokens) if you want to test AI features; rotate keys after testing.
- Ask the skill author for the missing deploy/integrate scripts and clarification about env var names and what state is saved under .ailabs.
If you want, I can: (1) list the exact locations where environment variables are referenced, (2) extract the npm dependency lists from the scripts, or (3) produce a short checklist and a safe command sequence to run the scaffolder inside a container.Like a lobster shell, security has layers — review code before you run it.
Plugin bundle (nix)
Skill pack · CLI binary · Config
SKILL.mdCLIConfig
Config requirements
State dirs.ailabs
latestvk97216jrh03x4crscx3q081yvx81gtnf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🚀 Clawdis