Security audit
Security checks for vulnerabilities and agentic risk
This is a plain Markdown guide for designing no-code business automations, with no executable code or hidden install behavior.
Before installing, treat this as a general automation playbook. When following its examples, use least-privilege app permissions, test with non-sensitive data first, add duplicate/error checks, and manually review workflows that send emails, update CRMs, or touch invoices and payments.
The trigger list includes broad phrases such as "automate," "automation," and "save time," which can match many unrelated user requests and cause unintended invocation of this skill. Misrouting can lead the agent to suggest or initiate automation-oriented handling in contexts where the user did not intend it, increasing the chance of inappropriate actions or data-handling advice.
The skill provides detailed guidance for connecting forms, CRMs, email tools, payment systems, and customer data flows, but does not warn about privacy, consent, authentication scope, or data-integrity risks. In an automation context, missing warnings can cause users to create workflows that expose personal data, send incorrect communications, or silently corrupt records across systems.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
### Invoice and payment tracking
No suspicious patterns detected.