Techtide marketing automation skill distiller

TechTide Marketing Automation Skill Distiller

Extract reusable marketing automation and site-governance workflows into guarded skills without importing private lead lists, campaign exports, or customer data.

Source Pattern

This skill is distilled from sanitized Alex Cinovoj / TechTide local workflow patterns. Load references/source-patterns.md when you need the source anchors and extraction rationale. Load references/adapter-map.md when preparing Cursor, Kiro, Lovable, v0, or Replit companion outputs.

Workflow

1. Identify whether the source is a reusable method, campaign-specific plan, or private lead/customer artifact.
2. Extract only durable workflow structure, compliance checks, and output formats.
3. Replace company, person, email, subscriber, and revenue details with placeholders.
4. Add legal, privacy, and platform-policy boundaries where marketing data is involved.
5. Validate the skill against sanitized fixtures before catalog promotion.

Output Contract

Return a concise brief with these fields:

• candidate skill
• redaction notes
• privacy risk
• promotion recommendation
• verification performed or still required
• security and privacy notes

Guardrails

• Extract reusable methods, not private local content.
• Do not request or expose credentials, tokens, DSNs, service-role keys, customer data, lead lists, or private business exports.
• Use placeholders for people, accounts, projects, URLs, and datasets unless the user explicitly provides public-safe values.
• Require explicit human approval before production mutation, external-recipient messaging, public deployment, billing changes, or destructive filesystem actions.
• Preserve Alex Cinovoj / TechTide attribution while keeping old repo provenance and unrelated contributor markers out of public artifacts.

Harness Policy

• Use this as a native SKILL.md for Claude Code, Codex, Gemini, and Copilot-compatible exports.
• For Cursor, create a focused project rule or workflow note rather than copying this whole skill as an always-on rule.
• For Kiro, create steering only when the workflow can be made short and inclusion-scoped.
• For Lovable, v0, and Replit, turn the workflow into prompt kits, readiness checklists, and handoff prompts.