Security audit
Security checks for vulnerabilities and agentic risk
This is a plain guidance-only automation playbook with some sensitive business-data examples that users should configure carefully.
Before installing or using this skill, treat its example workflows as templates only: review OAuth scopes, minimize customer and payment data copied between services, confirm consent and compliance needs, test with safe data first, and keep workflow logs and error alerts enabled.
The trigger phrases are broad enough to match ordinary conversation such as 'save time' or 'automate,' which can cause the skill to activate outside narrowly intended contexts. Over-broad invocation increases the chance of inappropriate routing and accidental use of automation guidance in situations involving sensitive systems or data.
This skill gives detailed guidance for moving customer, payment, usage, and CRM data across external services but does not warn about data minimization, consent, credential scope, retention, or compliance obligations. In practice, users may implement automations that expose personal or financial data to unnecessary third parties or create insecure data flows without realizing the privacy implications.
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.