Automation Workflows 0.1.0
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only guide for user-directed business automation, but users should be careful when connecting accounts or enabling workflows that can keep changing business data.
This skill appears safe to install as an instruction-only automation guide. Before following its recommendations, review each workflow's connected accounts, permissions, trigger conditions, and possible downstream effects, especially for customer messages, invoices, public posts, or synced business records.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A poorly designed automation could add wrong CRM data, send unintended emails, or create tasks without the user noticing immediately.
The skill describes workflows that can take actions in third-party business tools. This is purpose-aligned for automation, but incorrect configuration could create records or send communications unintentionally.
ACTIONS:\n Step 1: Add lead to CRM ...\n Step 2: Send welcome email ...\n Step 3: Create task in project management tool
Test each workflow with limited data first, add filters and error alerts, and require manual review for financial, public-facing, or customer-impacting actions.
Connected automation services may be able to read or change data in the linked accounts depending on the granted scopes.
The guide instructs users to connect accounts to automation services. OAuth access is expected for this purpose, but it can delegate permissions to third-party platforms.
**Connect your account** (authenticate via OAuth)
Use least-privilege OAuth scopes where possible, connect only necessary accounts, review connected-app permissions periodically, and revoke unused automations.
An error in one connected tool could spread incorrect or duplicate data to other business systems.
The guide encourages multi-tool data synchronization. This is central to the stated purpose, but bad trigger logic, duplicate events, or incorrect mappings can propagate errors across systems.
Sync data between tools (CRM ↔ email tool ↔ spreadsheet)
Add deduplication, validation, error notifications, and a clear rollback process before enabling multi-system syncs.