personalization-subagent-pattern

Generates per-lead cold email personalization fields using parallel Claude Code Task sub-agents.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/Pinkycherry/newbusinessideas3 --skill personalization-subagent-pattern-pinkycherry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: personalization-subagent-pattern
Source: https://github.com/Pinkycherry/newbusinessideas3/tree/main/.claude/skills/personalization-subagent-pattern
Command: npx skills add https://github.com/Pinkycherry/newbusinessideas3 --skill personalization-subagent-pattern-pinkycherry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing personalized cold email lines for hundreds of leads by hand is slow and inconsistent, and running a single large prompt over a full lead list produces generic, low-quality output. This Skill defines a reusable approval-loop pattern that tunes a personalization prompt on small batches before scaling to the full list. ## Core Features & Use Cases - Approval loop before scaling: Shows one sample personalization, then batches of 10, collecting user edits until two consecutive rounds pass with zero corrections before locking the prompt. - Parallel Task sub-agent fan-out: Splits leads into batches of 10-20 and launches multiple Claude Code Task sub-agents (including A/B/C copy variants) that write JSON results to /tmp for merging by lead_id. - Schema and quality guardrails: Defines a strict output schema (situation_line, value_line, cta_soft), banned-word rules, no-fabrication rules, retry handling for malformed JSON, and skip flags for leads with thin data. - Use Case: Given 100 enriched leads with company descriptions, tune the prompt over two approval rounds, then fan out 10 parallel sub-agents to produce three personalization variants per lead, merged and mapped to Smartlead custom variables like {{situation_line_a}}. ## Quick Start Use the personalization sub-agent pattern to generate situation_line, value_line, and cta_soft fields for my lead list, starting with one sample lead for my approval before fanning out in parallel batches.

Frequently Asked Questions about personalization-subagent-pattern

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I personalize cold emails at scale with Claude Code?

Split your lead list into batches of 10-20 and launch parallel Task sub-agents, each running a tuned prompt that returns situation_line, value_line, and cta_soft as JSON. Tune the prompt first through an approval loop on small batches before scaling to the full list.

How does the approval loop for personalization prompts work?

Start with one sample lead, then run batches of 10 and show results in a table for user edits. When two consecutive rounds pass with zero corrections, the prompt is locked, saved to the profile directory, and fanned out across the remaining leads.

Does this pattern use the Anthropic API or an API key?

No. It runs entirely inside Claude Code via the Task tool, so there is no extra API spend or key management. Only at very large scale above 1,000 leads is shipping the tuned prompt to the Anthropic API suggested as an option.

What happens when a sub-agent returns malformed JSON or skips leads?

The orchestrator validates every response against the output schema, retries missing lead_ids once with a stricter prompt, and marks leads with thin data as personalization_status skipped so they receive static copy instead.

When should I not use sub-agent fan-out for personalization?

Skip fan-out for batches under 10-20 leads, where inline personalization in the main conversation is sufficient, and for static copy sent identically to every lead, where per-lead generation wastes tokens.