Summary of "클로드 코드로 100% 자동화 마케팅 에이전트 팀을 만드는 방법 (서브에이전트+스킬+MCP 모두)"

Tech/Automation Concepts Covered

Claude Code setup for an automated marketing “agent team” (100% automation)
- The walkthrough covers building a multi-agent workflow that can generate campaign assets end-to-end—such as:
  - Newsletter / “cad news”
  - PPT decks
  - YouTube thumbnails
  - Social posts
- The workflow emphasizes keeping outputs consistent with brand guidelines.
High-quality output via upfront “Context + Templates + System doc”
- Create project folders:
  - /Context: brand guidelines, design style guide, business context
  - /Template: card news/newsletter/PPT/thumbnail templates
  - Skills installation/configuration (set up after folder structure is ready)
- Generate a claude.md file that acts as system documentation / SOP, ensuring consistent rules for the model and agents.
Skill-based document generation (consistency)
- Install official/curated Entropy / Claude Skills (e.g., document generation in consistent styles).
- Use skills to generate PPT/PDF-like assets, rather than letting the model freely design formats.
MCP integration for image generation
- Connect an image-generation MCP (referenced as “Nanobanana” / “Jemina” MCP).
- Use MCP to generate card news images according to brand rules and templates.
- The process is described as faster and more reliable than manually iterating layouts in code.
- API key security is emphasized:
  - Store keys in environment files
  - Never expose keys publicly
Buffer API for scheduled/automated social publishing
- Use Buffer and its Developer API (beta) to automate posting.
- Save the Buffer API key in environment variables (e.g., .env) and test scheduled posting from Claude Code.
- Verify scheduled posts in the Buffer dashboard.

Product Features / Workflow Steps (Tutorial Style)

Create a project folder in VS Code / Cursor (using the Claude Code extension).
Build Context docs (Markdown) in /Context
- Take a screenshot from the agency website and use it so Claude can generate:
  - Brand guidelines
  - Design style guide
  - Business context (target audience, positioning, pain points, service lines)
Build Template assets in /Template
- Include templates for:
  - Card news / newsletter
  - PPT
  - Thumbnail images
- Efficiency tip: convert PPT/image templates into a Markdown-reference template so Claude doesn’t repeatedly “read” large images (token efficiency).
Create claude.md (project system / SOP document)
- Claude scans the project structure and core context.
- Ensures consistent agent behavior and repeatable deliverable quality.
Install required skills
- Install “document skills” from the Entropy / Claude Skills marketplace.
- Scope skills to this project only using settings files (mentioned as settings.json).
Generate and test sub-agents
- Example agents include at least:
  - Research Agent
  - Design Agent
  - Review Agent
- Validate each agent individually, then test teamwork.
- Key principle: agents should be defined with explicit tools/models, and pipeline routing must be encoded as routing rules in claude.md (so tasks go to the right agent).
Create deliverables via the agent pipeline
- Pipeline outputs include:
  - Card news
  - PPT
  - Newsletter manuscripts
  - YouTube thumbnail variations
MCP image generation for card news
- Install MCP server; verify via MCP menu/listing.
- Configure the image API key:
  - Start with a free tier
  - Move to paid tier for higher quality
Buffer API scheduled posting
- Generate a Buffer API key (beta access).
- Store it in .env.
- Test scheduling (example: posting card news to a LinkedIn thread) and confirm the results in the Buffer dashboard.

Quality / Analysis Notes and Practical Tips

Setup emphasis: ~95% effort goes into setup (folders/context/templates + claude.md + agent routing), with only ~5% left for execution.
Narrow scope improves research quality:
- The research agent’s output is more usable when aligned closely with the company context.
SOP-like structure is essential:
- Work rules, routing rules, and agent guidelines are treated as required for consistency and repeatability.
Token efficiency:
- Avoid repeatedly importing PPT images; reference templates via generated Markdown instead.
Testing safeguards:
- The instructor repeatedly reminds viewers to ensure templates and context are reflected correctly during initial runs.
Security caution:
- Do not expose MCP/API keys or Buffer API keys publicly.
- A suggestion includes deleting keys after recording them.

Main Speakers / Sources

Primary speaker/instructor
- Creator demonstrating the setup
- Mentions operating an AX agency
- References a “Joshua/Josh” brand
- Requests viewers contact via the “Joshuhwa” website
Referenced external sources/tools
- Claude Code / Anthropic Claude Code
- Claude Mythos model release (mentioned as newly released during recording)
- Entropy / Claude Skills (skills marketplace)
- MCP author “Choi Su-min” (for the referenced MCP)
- Buffer (social scheduling + Developer API beta)