Fills three sender-defined bullet slots with company-specific details to build a three-idea cold email, without picking topics or writing extra bullets.
Use this Skill when you need to fill three fixed idea slots in a "few ideas for you" cold email with details specific to each company, producing evidence-backed bullets you can trust on a follow-up call. Avoid using it for emails with a single personalized line, event-triggered hooks, or campaigns where you cannot name three concrete idea slots yourself.
What it delivers
You get three evidence-backed bullets per company plus a rendered email block ready to drop into a sequence, and a run summary showing how many rows qualified versus were excluded. The Skill routes any row missing a bullet to a separate campaign, so it never sends a three-bullet email with fewer than three ideas.
SKILL.md preview
# SKILL.md
The full Skill file is available after sign-in.
This is an illustrative preview, not the source.
## Inputs and setup
Required inputs and setup details appear here.
Sign in to read the complete instructions.
## Workflow instructions
The Skill's execution steps appear here.
This placeholder contains no actual Skill content.
## Outputs and examples
The full file includes its source documentation.
Sign in to view and copy the original file.
## Notes and requirements
Additional source details appear after sign-in.
The actual SKILL.md is not loaded in this preview.
Illustrative preview. Sign in for the actual file.
How someone would prompt this
I want a three-bullet 'I had a few ideas for you' email for my leads list, where bullet 1 covers production scheduling, bullet 2 covers quality and compliance, and bullet 3 covers supplier planning, using our company evidence data and never mentioning competitors or dollar figures.
Inputs & outputs
What someone provides before the Skill runs, and the reviewable artifacts it returns.
Inputs
01Lead listA table, CSV, or audience with company name and domain for each row to process
02Bullet slot definitions
The three subjects each bullet must cover, in your own words
the specific prospect detail each slot needs
anything that must never appear, like competitors or dollar figures
03Hand-written examplesThree complete bullet sets you write yourself for three real companies, used to guide the model's output
04Evidence and routing setup
Where the company-description evidence comes from
a short client suffix so field names don't collide across clients
the campaign to send rows with a missing bullet to instead
05Model choiceThe AI model configured in your workspace that fills the bullet slots
Outputs
01Three bullets per companyA table listing up to three idea bullets per company, each paired with the exact evidence quote the model used to write it.
02Rendered email blockA ready-to-use email block combining the three bullets, with any row missing a bullet marked as excluded.
03Run summary reportA report showing how many rows had all three bullets, how many rows the Skill excluded and why, and the overall blank rate.
Representative output
The three bullets, one company
bullet
evidence_N (must be a real substring of the input)
1
a production scheduler that plans injection molding runs against cleanroom capacity
"injection molding in a class 8 cleanroom"
2
batch records that stay audit-ready without anyone rekeying them from the floor
"ISO 13485 certified"
3
resin lead times visible before a run is committed, not after
"medical-grade resins sourced from three suppliers"
The rendered block, and a row that was excluded
- a production scheduler that plans injection molding runs against cleanroom capacity
- batch records that stay audit-ready without anyone rekeying them from the floor
- resin lead times visible before a run is committed, not after
EXCLUDED harborline.example
bullet 1 ok "contract manufacturing for orthopedics"
bullet 2 ok "FDA registered facility"
bullet 3 "" nothing in the evidence about materials or suppliers
-> routed to the non-ideas campaign. two bullets is a different email, not a worse one.
The run summary
32 real production rows, seven live campaigns
27 usable (84%) <- out of sample, at volume, different senders
5 not usable
blank rate 16% (healthy band: 5-30%. under 5% means the prompt was loosened)
read the 3 thinnest rows by hand: all 3 correctly abstained
evidence-quote verification: 96 quotes asserted, 2 blanked for not appearing in the input
rows excluded for an empty bullet: 5 -> routed to <the non-ideas campaign>
fields pushed: creative_idea_1_<client> .. _3_<client> (namespaced)
model: mini-class in-platform, named in the column description
How the Skill runs
Follow the steps in order. Each row includes the full instruction.
StepWorkflowType
01
Confirm the table and workspace
The skill checks that your workspace and target table are reachable, states which columns it will add, and stops if the check fails.
Step
02
Interview you and get hand-written examples
The skill asks what each bullet slot is about, what detail must appear, and what must never appear, then requires you to hand-write three full bullet sets before any model runs; the run stops here so you can confirm everything read back is correct.
Step
03
Gather company evidence
The skill works through several evidence sources in order until it finds a paragraph long enough to support a specific bullet, skipping any that are too short even if not empty.
Step
04
Generate and verify bullets
The model fills each slot with a detail from the evidence, checks every quote actually appears in the source text, and blanks any bullet whose quote it cannot verify.
Output
05
Review the thinnest results
The skill shows 10 rendered examples and highlights the three companies with the least evidence for manual review; the run stops here so you can check quality before continuing.
Step
06
Route exclusions and report
Rows missing any bullet are sent to a separate non-ideas campaign, and a final report lists completed rows, excluded rows, blanked bullets, and the overall blank rate.
Action
Connections required
No connections listed.
Install Clay and run it
Sign in once, install the Skill, then run the prompt.
1Install ClayUse the connector or official plugin in your coding-agent environment.
2Sign up or log inAuthorize Clay access and return when the connection is ready.
3Install the SkillRun the one-line install command from the Add this Skill card.
4Run the SkillPaste the example prompt and review the result.
