Automation Workflows 0.1.0
v1.0.0Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building workflows across tools, setting up triggers and actions, or optimizing existing automations. Covers automation opportunity identification, workflow design, tool selection (Zapier, Make, n8n), testing, and maintenance. Trigger on "automate", "automation", "workflow automation", "save time", "reduce manual work", "automate my business", "no-code automation".
⭐ 12· 6.1k·120 current·129 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md content: a playbook for identifying, designing, and testing automations (Zapier, Make, n8n). The skill requires no binaries, env vars, or installs, which is proportionate for a guidance-only skill. Minor metadata mismatch: the _meta.json ownerId differs from the registry owner id, which is a packaging/metadata inconsistency but does not affect runtime behavior.
Instruction Scope
SKILL.md stays within expected boundaries (identify tasks, choose tools, design test/check workflows). It instructs connecting third-party services via their normal auth flows (OAuth) and testing with real data — expected for automation guidance. There is no instruction to read local files, system credentials, or to send data to unknown endpoints in the visible content. Note: the SKILL.md was truncated in the provided excerpt; review the full file for any steps that might request reading local secrets or sending data to non-standard endpoints.
Install Mechanism
No install spec and no code files — lowest-risk model for a skill. Nothing will be written to disk or executed by the platform based on an installer.
Credentials
The skill declares no required environment variables, credentials, or config paths. The guidance expects users to authenticate to external automation platforms (Zapier/Make/n8n) via their normal OAuth/API mechanisms — this is appropriate and proportional for the stated purpose.
Persistence & Privilege
Flags show always:false and normal model invocation is allowed (default). There is no request for permanent presence or self-modifying behavior. Autonomous invocation is platform-default and combined with this skill's benign footprint does not raise special concern.
Assessment
This skill is a guidance-only playbook and appears internally consistent, but before relying on it: (1) review the full SKILL.md (it was truncated in the excerpt) to ensure no steps ask the agent to read local files or export sensitive data; (2) when connecting third-party services (Zapier, Make, n8n) use least-privilege accounts, test with dummy data or limited-permission accounts, and revoke tokens you don’t need; (3) verify the skill source/owner if provenance matters (registry ownerId and _meta.json ownerId differ), and avoid sharing real customer PII until you’ve validated your automation in a safe test environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97bhhhbqmgb4h9fn42qxz4njh80pg4m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.