{"id":42437,"plugin_id":"plugin_asdk_app_6a286d326c3c8191acfa27fdfcdc2841","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:05:04.333Z","digest":"1e24f5711acfd6d5d1faa3b5a7d413a0322b1636c0604a509b4bd432b7b61772","against":null,"payload":{"description":"Run AI marketing employee workflows for Brosh AI CRM: segment existing customers, write personalized marketing emails, send approved campaigns, and log campaign status. Use for customer marketing, not cold SDR outreach or support replies.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":246},{"relative_path":"references/brosh-marketing-crm-model.md","size_in_bytes":2734},{"relative_path":"references/marketing-workflows.md","size_in_bytes":3574},{"relative_path":"references/personalization-and-safety.md","size_in_bytes":2818}],"name":"brosh-ai-marketing","skill_md_contents":"---\nname: brosh-ai-marketing\ndescription: \"Run AI marketing employee workflows for Brosh AI CRM: segment existing customers, write personalized marketing emails, send approved campaigns, and log campaign status. Use for customer marketing, not cold SDR outreach or support replies.\"\n---\n\n# Brosh AI Marketing\n\nUse this skill when the user wants an AI marketing employee to create and send custom marketing emails to existing customers using Brosh AI CRM.\n\n## Core Workflow\n\n1. Confirm the campaign objective, audience, offer/message, product or feature being promoted, sender, and autonomy level before sending.\n2. Use Brosh CRM as the system of record for customers, contacts, accounts, campaigns, templates, and activity logs.\n3. Read [references/marketing-workflows.md](references/marketing-workflows.md) for campaign planning, segmentation, execution, and reporting.\n4. Read [references/brosh-marketing-crm-model.md](references/brosh-marketing-crm-model.md) when selecting or updating CRM records.\n5. Read [references/personalization-and-safety.md](references/personalization-and-safety.md) before drafting or sending marketing emails.\n\n## Autonomy Levels\n\n- `draft_only`: prepare campaign copy, audience recommendations, and CRM updates only.\n- `approval_required`: prepare campaign copy and audience details, then wait for approval before sending.\n- `autonomous_low_risk`: send only configured low-risk lifecycle/nurture messages to existing opted-in customers.\n- `skip_confirmations`: skip user approval for configured low-risk customer-marketing sends and CRM logging; still respect all safety gates.\n\n## Brosh Email Rules\n\n- Use `send_message_single` when each customer receives a fully personalized subject/body.\n- Use `send_email` with a `templateid` or direct `template` payload when the same approved template is sent to a segment.\n- Use sender options from the current Brosh CRM tool schema, such as `fromEmailSet` and `fromEmailSets`, when an approved sender is known. When the sender record from `email_settings` exposes an email address, put that sender email address in the outbound `cc` field unless the user explicitly gives a different CC rule.\n- Add the same `cc` value to the `task` payload when campaign sends should be logged to `activity`.\n- Brosh CRM email sends are direct execution calls in the current MCP flow. Do not use obsolete `previewOnly`, `confirm`, or `confirmationToken` parameters, and do not claim an email was sent until the tool confirms the send.\n- Never send to `email_opt_out=true`, unsubscribed, bounced, invalid, or uncertain-consent recipients.\n\n## Customer Marketing Boundaries\n\n- Target existing customers or clearly permissioned customer contacts. Do not use this skill for cold prospecting.\n- Personalize around customer value: usage, lifecycle stage, account context, industry, previous purchases, relevant features, renewals, upgrades, education, or retention.\n- Do not invent customer facts, product capabilities, pricing, discounts, deadlines, legal terms, security claims, or ROI numbers.\n- Escalate campaigns involving sensitive segmentation, high-value accounts, churn risk, legal/security claims, pricing changes, or unclear consent.\n\n## Output Expectations\n\nWhen reporting campaign work, include:\n\n- campaign objective and audience definition;\n- recipient count and exclusions;\n- draft subject/body variants or send outcome;\n- personalization logic used;\n- CRM records created or updated;\n- activity/campaign status;\n- sends completed, skipped, failed, and escalated.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}