Automation Workflows
v1.0.1Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building wor...
⭐ 0· 224·0 current·0 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/description match the SKILL.md content: it teaches how to identify automation opportunities, select tools (Zapier, Make, n8n), design, test, and maintain workflows. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
The instructions stick to workflow design and implementation steps and testing. They do not instruct the agent to read local files, environment variables, or send data to unexpected endpoints. The playbook explicitly expects you to authenticate with third-party automation platforms (OAuth) — which is appropriate for this purpose.
Install Mechanism
There is no install spec and no code files; this is instruction-only, so nothing is written to disk or fetched during install. This minimizes risk and is proportionate to the skill's purpose.
Credentials
The skill itself requires no environment variables or credentials. However, actual use of the workflows will require connecting external services (Zapier/Make/n8n, email providers, CRMs) via OAuth or API keys — that is expected but you should apply least-privilege when authorizing these services.
Persistence & Privilege
always:false and no special permissions are requested. The skill does not request persistent system-wide configuration or access to other skills' credentials.
Assessment
This skill appears coherent and instruction-only, but before installing: 1) note a metadata inconsistency in the package (owner ID and version differ between registry metadata and _meta.json) — verify the publisher if you care about provenance; 2) when you connect automation platforms (Zapier/Make/n8n) only grant the minimal OAuth scopes needed and test automations with dummy data; 3) prefer self-hosted n8n if you plan to handle sensitive data, and keep audit logs and ability to revoke tokens; 4) review and test error handling and edge cases before relying on automations that touch payments or private customer data.Like a lobster shell, security has layers — review code before you run it.
latestvk9769nz62g797pf1nzrr8s62k982zpwf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.