Brand Awareness Crew — Social Posting and Email Outreach Team

A 15-agent outreach team for building brand and business awareness across social platforms and email. Curated for the TalentDelta catalogue from The Agency — the roster is that project's own Multi-Channel Marketing Campaign runbook team plus its Email Marketing Strategist, so the agents are designed to work together, not just sit side by side.

• Upstream: msitarzewski/agency-agents — pinned at commit f99f6aa910a4 (2026-10-07)
• Licence: MIT — the upstream LICENSE ships unchanged in this pack
• Format: one Markdown agent per file, with YAML frontmatter (name, description, color, emoji, vibe) — the shape Claude Code, OpenCode, Gemini CLI, Codex, Kimi, Cursor and the other supported runtimes read as an agent definition

Who is in the crew

Agent	File	What it does
Social Media Strategist (campaign lead)	marketing/marketing-social-media-strategist.md	Cross-platform campaign strategy, community building, real-time engagement, thought-leadership positioning
Email Marketing Strategist	marketing/marketing-email-strategist.md	Segment architecture, lifecycle sequences (welcome → nurture → win-back → referral), deliverability (SPF/DKIM/DMARC), post-MPP measurement
Content Creator	marketing/marketing-content-creator.md	Editorial calendars and channel-adapted copy across every format, including email sequences and landing copy
Brand Guardian	design/design-brand-guardian.md	Brand identity, messaging framework, tone-of-voice rules and consistency review for every asset
Twitter Engager	marketing/marketing-twitter-engager.md	X/Twitter execution: real-time engagement, threads, community growth
TikTok Strategist	marketing/marketing-tiktok-strategist.md	Short-video content, platform culture and algorithm fit for brand growth
Instagram Curator	marketing/marketing-instagram-curator.md	Visual storytelling, multi-format posts, aesthetic development, engagement
Reddit Community Builder	marketing/marketing-reddit-community-builder.md	Authentic community participation and long-horizon relationship building
App Store Optimizer	marketing/marketing-app-store-optimizer.md	Store listing presence and discoverability (when the business is mobile)
Growth Hacker	marketing/marketing-growth-hacker.md	Acquisition experiments, funnel optimisation, viral loops
Trend Researcher	product/product-trend-researcher.md	Market timing, trend signals, competitor campaign analysis
Experiment Tracker	project-management/project-management-experiment-tracker.md	A/B and holdout tracking so campaign variants are measured, not guessed
Analytics Reporter	support/support-analytics-reporter.md	Performance tracking and reporting across channels
Executive Summary Generator	support/support-executive-summary-generator.md	Turns campaign results into a decision-ready summary
Legal Compliance Checker	support/support-legal-compliance-checker.md	Ad disclosure, platform ad policies and regulatory constraints

Operational plan: strategy/runbooks/scenario-marketing-campaign.md — the upstream runbook for a 2–4 week multi-channel campaign, with the week-by-week execution plan and each agent's hand-off artefacts.

Quick start

1. Put the agents where your runtime looks for them. Each file is a self-contained agent definition, so copying is the whole install:

   mkdir -p ~/.claude/agents
   cp marketing/*.md design/*.md support/*.md product/*.md project-management/*.md ~/.claude/agents/
   

   Other runtimes read the same source files through upstream's converter (scripts/convert.sh then scripts/install.sh --tool <claude-code|codex|gemini-cli|opencode|cursor|copilot|openclaw|hermes|…>). That installer belongs to the upstream project and is not bundled here — see the pinned repo if you want the full 380-agent roster instead of this crew.

2. Run the campaign. Activate the campaign lead and give it the brief — "act as the Social Media Strategist and plan a 4-week brand-awareness campaign for " — then follow strategy/runbooks/scenario-marketing-campaign.md, which routes work to the channel specialists, brand review, analytics and compliance.

3. Connect the channels you actually use. The email strategist works against an ESP and CRM (upstream names Brevo, Mailchimp, MailerLite, ActiveCampaign, SendGrid, and HubSpot/Pipedrive as CRM); the social specialists work against your platform accounts or your scheduling tool. No credentials ship in this pack: every service is prompted for at authentication time.

What this crew does and does not do

• Does: strategy, calendars, copy and sequences, per-platform adaptation, brand review, experiment design, measurement, reporting and compliance checks — the full planning and drafting loop for awareness outreach.
• Does not: publish or send on its own. Going live happens in your platform accounts, ESP or scheduler, under your credentials and consent rules. Upstream's own auto-publishing agents (carousel growth engine, Chinese multi-platform publisher) are deliberately not part of this crew.

Selection scope

This pack is a curated subset: 15 of the 382 files in the pinned commit. Not included are the rest of the repository's agents (engineering, finance, sales, design, and so on), the other 28 marketing agents (China-platform, e-commerce and SEO specialists), the repository's own README.md and desktop app, and its scripts/ installer and integrations/ output. Every shipped file is byte-identical to the pinned commit; nothing was edited, renamed or removed. See the provenance record below for the licence and safety detail.

MIT © the upstream authors. This pack is a redistribution, not a fork, and is not affiliated with or endorsed by the upstream project.

---

TalentDelta provenance record (added at packaging)

• Packaged for: TalentDelta catalogue (draft; gated by review)
• Upstream: https://github.com/msitarzewski/agency-agents
• Pinned commit: f99f6aa910a442b0197b768ce0ea7751e35e2060 (2026-10-07)
• Licence: MIT - the upstream LICENSE ships unchanged in this pack
• Upstream author credit: The Agency contributors (msitarzewski/agency-agents)
• Runtime: any runtime that reads Markdown agent definitions with YAML frontmatter (Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Kimi, OpenClaw, and upstream's Hermes plugin)
• Changes made at packaging: this section was appended to README.md. No upstream path is excluded. Added at packaging, not present in the pinned commit: README.md, LICENSE (the pack README (written for this crew) and the repository's LICENSE, so the MIT terms travel with the bytes). Every other file is byte-identical to the pinned commit.
• Safety read of the packaged archive (packaging time, 2026-10-08): scanned before packaging (leak_scan.py over 18 text files): no credential-shaped values, no personal data, no host paths; the only email-shaped strings are the illustrative dpo@company.com (in the compliance agent's example privacy notice, and quoted in this note)

Packaging notes (TalentDelta)

• Scouting basis: owner asked for an outreach agent that posts to social media and sends email to raise brand/business awareness. This crew covers both sides - per-platform social execution and lifecycle email - with identity, behaviour (per-agent missions, rules, deliverables, success metrics) and usage docs present in every agent file, so it meets the catalogue's full-agent bar.
• Maturity at the pin: 382 files, ~50 divisions, active CI (5 workflows incl. a Hermes config-rewrite check), tests, i18n and an installer that targets 10+ runtimes; the project was pushed within a day of the pin.
• Roster provenance: the crew is upstream's own 'Multi-Channel Marketing Campaign' runbook roster (marketing-, design- and support-division agents) plus the Email Marketing Strategist, so the agents are designed to hand off to one another. The runbook ships at strategy/runbooks/scenario-marketing-campaign.md.
• Reach: the crew plans, drafts, adapts, reviews and measures; it does not publish or send on its own - posting and sending happen in the operator's platform accounts and ESP under their credentials, which matches the catalogue's no-send stance. Upstream's auto-publishing agents (carousel growth engine, Chinese multi-platform publisher) are excluded.