From make-automation-specialist
Surface-level compliance risk assessment for Make.com scenarios. Checks GDPR, Quebec Law 25, PCI-DSS, and HIPAA. NOT legal advice — flags risks for human review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/make-automation-specialist:compliance-scannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Performs surface-level compliance risk assessment on Make.com scenarios.
Performs surface-level compliance risk assessment on Make.com scenarios. NOT legal advice. Flags risks for human review.
Applies when: scenario processes data from EU users or connects to EU-region services.
Check for:
Applies when: workspace owner or data subjects are in Quebec.
Check for:
Applies when: touches_payment_data: true from scenario-reader.
Check for:
Applies when: touches_health_data: true from scenario-reader.
Check for:
## Compliance Surface Assessment
**Frameworks assessed:** {list}
**Assessment date:** {timestamp}
**Status:** {risks-found | clean}
### Risks Found
#### [RISK TITLE]
**Framework:** {GDPR / Quebec Law 25 / PCI-DSS / HIPAA}
**Severity:** {Critical / High / Medium / Low}
**Scenario:** {scenario name}
**Description:** {plain-language risk description}
**Recommendation:** {specific action to take}
**References:** {relevant article/section}
### Clean Areas
{What was assessed and found compliant}
---
**Disclaimer:** This assessment is a surface-level automated scan, not legal advice.
Consult a qualified privacy lawyer before making compliance decisions.
In Quebec: contact Commission d'accès à l'information for guidance.
In the EU: contact your Data Protection Officer (DPO) or national supervisory authority.
Critical: Likely violation in progress. Stop and fix before next run. Example: Payment card numbers flowing through Make.com logs.
High: Probable violation if not addressed within 30 days. Example: Personal data transferred to US service without standard contractual clauses.
Medium: Risk area — review and document mitigation. Example: No documented legal basis for processing marketing email data.
Low: Best practice not followed — low immediate risk. Example: No explicit data retention policy defined for this automation's data.
Save to .make/compliance/{timestamp}-{scenario-id}-compliance.md.
Append summary to workspace-level compliance overview at .make/compliance/overview.md.
npx claudepluginhub cardinalconseils/make-automation-specialist --plugin make-automation-specialistGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.