marketer

A curated Claude Code harness for Orama's marketing work. Brand-voice QA, content production, campaign orchestration, competitive intelligence, GTM enablement, and weekly measurement — all in one place.

Designed to live as a git submodule under oramasearch/amaro-bridge at modules/marketer/. Activate from the bridge with /marketer.

What's in here

• CLAUDE.md — operating instructions for the marketer agent
• style-guide.md — brand voice and visual identity, the source of truth for brand-voice skill
• .claude/skills/ — 8 Tier 1 skills (see the skill index)
• briefs/ — campaign briefs and editorial calendar
• tasks/ — persistent active task list + scheduled routine config
• assets/ — generated drafts (gitignored except for the index)
• .mcp.json — MCP servers for marketing tools (stubbed)
• .env.example — auth setup template

Activation

Two ways to use the harness:

• From the bridge: /marketer (bridge-level skill at amaro-bridge/.claude/skills/marketer/) loads this module's CLAUDE.md and lists available skills. /marketer <task> routes to the most appropriate sub-skill.
• Directly: cd modules/marketer && claude — operate inside the harness with the skills auto-discovered.

Skills (Tier 1)

Skill	Job
brand-voice	QA outgoing copy against style-guide.md
daily-briefing	Morning marketing briefing — what to ship today, what shifted overnight
content-draft	Channel-aware drafting (blog, social, email, landing)
content-repurpose	Turn one artifact into N channel variants
campaign-plan	Multi-channel launch orchestrator
competitor-scan	Periodic competitive sweep → battlecards + gap report
sales-enablement	Pitch decks, one-pagers, demo scripts, objection-handling
week-in-review	Friday performance recap (worked / didn't / changed)

Tier 2/3 skills (post-social, content-calendar, persona-refresh, landing-page-brief, lead-triage, launch-announcement, case-study, gtm-motion-design) are planned. See .claude/skills/README.md.

Setup

cp .env.example .env
# fill in keys for the tools you have access to

External integrations (all stubbed in v0 — turn on as keys land):

• Slack — posts to #marketer (general output) and #marketer-approve (anything needing human approval before sending)
• Salesforce — lead-gen and CRM context
• Postiz — social posting and scheduling
• GitHub — issue/PR context for marketing-adjacent engineering work

Scheduled routines

• daily-briefing runs weekday mornings (08:00 ET) and posts to #marketer
• week-in-review runs Fridays (16:00 ET) and posts to #marketer-approve

See tasks/scheduled.md for the cron specs and how to wire them via the bridge /schedule skill.

Owner

Nathanael Wolfe (@nathanaelwolfe). Engineering-side coordination via oramasearch/amaro-bridge.