Automation Workflows Temp
PassAudited by ClawScan on May 1, 2026.
Overview
This is an instruction-only automation guide with no code or install step, but users should review third-party account access, data sharing, and the minor metadata mismatch before using it.
This skill appears safe as an instruction-only automation playbook. Before using its workflows, make sure you trust the automation providers, grant limited OAuth permissions, test carefully, and avoid automating public posts, invoices, payments, or customer communications without review.
Findings (4)
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 configured workflow could create incorrect records, send unintended emails, or perform repeated actions in connected services.
The skill teaches users to create automations that can write to business systems or send communications. This is purpose-aligned, but mistakes in setup could affect real accounts or customers.
ACTIONS: Step 1: Add lead to CRM ... Step 2: Send welcome email ... Step 3: Create task ...
Start with low-risk workflows, test with safe sample data when possible, keep actions narrow, and require manual review for public, financial, or customer-facing automations.
Connected automation platforms may be able to read or change data in the accounts the user authorizes.
The skill expects users to connect external accounts to automation platforms. OAuth access is normal for this purpose, but it delegates account authority to those tools.
Connect your account (authenticate via OAuth)
Grant only the scopes needed, connect the correct accounts, periodically review connected apps, and revoke access for workflows you no longer use.
Customer or lead data may be copied between services such as forms, CRMs, email tools, and project management tools.
The example workflow moves lead/customer information across multiple third-party tools. This is expected for automation work, but users should understand the data flow.
New form submission on website ... Add lead to CRM ... Send welcome email via email tool ... Create task in project management tool
Use trusted providers, avoid unnecessary fields, check privacy/compliance requirements, and document where customer data is sent.
The package metadata is inconsistent, which may make it harder to verify the exact publisher/version lineage.
The included _meta.json does not match the registry metadata shown for this evaluation, which lists a different owner ID, slug, and version. With no code or install step, this is a provenance note rather than a behavioral concern.
"ownerId": "kn732qfbv22he1jqm63xbwq6e980kn8s", "slug": "automation-workflows", "version": "0.1.0"
Confirm the skill source and publisher if provenance matters for your workspace before installing.