Add SEO and Video Optimization Marketing Agents

[Aditya-Ranjan1234]

What does this PR do?

Adds two new specialized marketing agents to the repository to expand the Marketing Division's capabilities:

1. SEO Optimization Expert: Focuses on deep technical SEO audits, advanced schema markup implementation, Core Web Vitals optimization, and organic traffic growth.
2. Video Optimization Specialist: Focuses on maximizing YouTube algorithm performance, audience retention tactics, strategic chaptering, and high-converting thumbnail concepts.

The README.md Marketing Division table was also updated to reflect the new additions.

Agent Information (if adding/modifying an agent)

• Agent Name: SEO Optimization Expert

• Category: Marketing Division

• Specialty: Technical SEO audits, schema markup, Core Web Vitals

• Agent Name: Video Optimization Specialist

• Category: Marketing Division

• Specialty: YouTube algorithm strategy, chaptering, thumbnail concepts

Checklist

• Follows the agent template structure from CONTRIBUTING.md
• Includes YAML frontmatter with name, description, color
• Has concrete code/template examples (for new agents)
• Tested in real scenarios
• Proofread and formatted correctly

[msitarzewski]

Thanks for these contributions! The Video Optimization Specialist is a great addition — unique role that fills a real gap.

Two issues with the other agents:

1. SEO Optimization Expert — We recently merged PR #89 which added marketing/marketing-seo-specialist.md covering the same ground (technical SEO audits, Core Web Vitals, schema markup, organic traffic growth). Having both would be confusing for users. Please remove this file.

2. Compliance Auditor — PR #56 was already merged adding specialized/compliance-auditor.md. The name collision would cause problems even though the approaches differ slightly. Please remove this file as well.

3. README.md — The README has changed since this PR was opened, so the updates will need to be rebased. Since we're only keeping the Video Optimization Specialist, the README change would just be adding that one entry to the Marketing Division table.

Could you update the PR to include only the Video Optimization Specialist agent + its README entry? Happy to merge once that's done.

[msitarzewski]

Thanks for the contribution @Aditya-Ranjan1234!

A few things to address before this can be merged:

1. SEO agent is a duplicate — we already have marketing/marketing-seo-specialist.md with comprehensive coverage. Please remove the SEO agent from this PR.

2. Video Optimization Specialist is genuinely new and we'd love to keep it! But it needs some work:

   • Add color, emoji, and vibe fields to the frontmatter
   • Add a "Workflow Process" section (step-by-step methodology)
   • Add a "Communication Style" section
   • Add at least 1-2 concrete template examples (e.g., a Video Audit Template)
   • Strengthen the personality/voice to match the depth of other agents

3. Remove pr_body.md — this file was accidentally committed and shouldn't be in the repo.

4. Update README changes to only reference the Video Optimization agent.

Happy to merge once these are addressed!

[Aditya-Ranjan1234]

Anything else to be added ?

[msitarzewski]

Hey @Aditya-Ranjan1234 — sorry for the delay on this! You've done great work addressing the feedback. The Video Optimization Specialist looks solid.

Two small things left:

1. Remove the tools field from frontmatter — we don't use that field in our agent template. Just keep name, description, color, emoji, and vibe.

2. Rebase onto main — the README has changed a lot since this was opened, so the diff has conflicts. After rebasing, make sure your README edit only adds the Video Optimization Specialist row to the Marketing Division table (the SEO row is already there from a previous merge).

Once those are in, this is good to go. Thanks for sticking with it!

[Aditya-Ranjan1234]

All done! I've removed the tools field from the frontmatter and rebased the branch onto the latest main to resolve the conflicts. The Video Optimization Specialist has also been correctly added to the Marketing Division table in the README.

Let me know if anything else is needed