Back to Email Campaign Flow

Security Report

Email Campaign Flow

Pass
Version v1.2.0 Scanned 18 July 2026 at 16:46 Scanner v3.3.0

Summary

Detected

  • Services: llm-service
  • Permissions:
  • Data Handling: pii

Undeclared

All items declared

Warnings

No warnings

Findings (14)

Compliance

info GDPR declared
compliance-gdpr
RELEASE_NOTES.md:13

"GH#643 — declared GDPR + CAN-SPAM compliance. The skrpt generates marketing email copy and templates"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [gdpr]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info GDPR declared
compliance-gdpr
RELEASE_NOTES.md:13

"GH#643 — declared GDPR + CAN-SPAM compliance. The skrpt generates marketing email copy and templates"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [gdpr]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info GDPR declared
compliance-gdpr
RELEASE_NOTES.md:13

"GH#643 — declared GDPR + CAN-SPAM compliance. The skrpt generates marketing email copy and templates"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [gdpr]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info CAN-SPAM declared
compliance-can-spam
RELEASE_NOTES.md:13

"GH#643 — declared GDPR + CAN-SPAM compliance. The skrpt generates marketing email copy and templates"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [can-spam]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info CAN-SPAM declared
compliance-can-spam
RELEASE_NOTES.md:13

"GH#643 — declared GDPR + CAN-SPAM compliance. The skrpt generates marketing email copy and templates"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [can-spam]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info CAN-SPAM declared
compliance-can-spam
RELEASE_NOTES.md:13

"GH#643 — declared GDPR + CAN-SPAM compliance. The skrpt generates marketing email copy and templates"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [can-spam]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info CAN-SPAM declared
compliance-can-spam
RELEASE_NOTES.md:13

"GH#643 — declared GDPR + CAN-SPAM compliance. The skrpt generates marketing email copy and templates"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [can-spam]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info GDPR declared
compliance-gdpr
prompts/email-campaign-writer.md:30

"Write email campaign copy for the following audience segments and campaign objective. For each segme"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [gdpr]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info GDPR declared
compliance-gdpr
skills/email-campaign-composition.md:22

"Given the campaign brief, the audience segmentation, and the A/B-tested subject lines from upstream,"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [gdpr]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

info GDPR declared
compliance-gdpr
skills/email-campaign-composition.md:28

"3. **Compliance and readability:** Enforce brand voice, GDPR-compliant unsubscribe language, and mob"

This content references a regulatory or compliance framework. Informational only — no action needed unless the skrpt processes regulated data. If it does, declare it in requires.compliance (e.g. compliance: [gdpr]) so the declaration reads honestly. See https://github.com/skrptiq/skrptiq-hub/blob/main/docs/PUBLISHING-GUIDE.md#declaring-compliance-frameworks.

Services

info llm-service declared
frontmatter-service-connection
skills/a-b-test-analysis.md:1

"connection: llm-service (runs_on)"

This node depends on the "llm-service" service. Declare it in requires.services so users know what external services are needed.

info llm-service declared
frontmatter-service-connection
skills/email-campaign-composition.md:1

"connection: llm-service (runs_on)"

This node depends on the "llm-service" service. Declare it in requires.services so users know what external services are needed.

info llm-service declared
frontmatter-service-connection
workflows/email-campaign-flow.md:1

"connection: llm-service (runs_on)"

This node depends on the "llm-service" service. Declare it in requires.services so users know what external services are needed.

Data Handling

info pii declared
pii-data-reference
workflows/email-campaign-flow.md:83

"subscriber data"

This content handles personally identifiable information (names, emails, addresses). Declare pii in requires.data_handling so users are informed before import.

Send feedback

Sign in to send feedback — it lets us follow up and keeps the tracker free of spam.