What problem does it solve? When adding new code to an OpenClaw project, developers must remember where each component type belongs, which naming convention applies, and what boilerplate structure is required. This Skill removes that guesswork by scaffolding skills, tools, pipes, crons, triggers, and agents in the right location with the right template. ## Core Features & Use Cases - Component Type Inference: Detects the intended component type from natural language descriptions (e.g., "run every day" maps to cron, "send a message" maps to tool). - Location & Naming Rules: Places files in the correct directory (skills/, tools/, pipes/, crons/, triggers/, agents/) following the {dominio}_{acao}.py naming convention, including subdirectory rules for domains with 3+ skills. - Mandatory Templates: Generates boilerplate with header docstrings (Função, Usar quando, ENV_VARS, DB_TABLES), standalone __main__ execution blocks, and no horizontal imports between same-layer components. - Use Case: Ask to create a component that fetches news daily and posts it to Telegram, and the Skill scaffolds the skill, pipe, and cron files with correct templates, then reminds you to update .env.example and add tests. ## Quick Start Ask the assistant to create a new OpenClaw component, for example: create a cron that runs the lead capture pipe every morning at 8am.