Inputs
Provide these when prompted. The skill asks for anything missing before it runs.
Required
- Structured prospect or account research
Optional
- Your offering and value props
- The outreach channel
- A specific contact
Agent Skill
Outreach Brief Generator
Convert structured prospect research into concise outreach preparation briefs.
Version 1.0 Updated June 2026 SKILL.md MIT 6 min read
Overview
What this skill does
Reps either skip pre-call prep or spend too long on it, and the personalization that results is often guessed rather than grounded in research.
This skill turns existing research into a tight, factual outreach brief: an account summary, relevant contact context, likely pain points, the supporting evidence, a conversation angle, and a clear list of claims that still need verification — it prepares, it does not fabricate or send.
When to use it
Best used for
- Pre-call and pre-email preparation
- Turning research into a usable brief
- Grounding personalization in evidence
- Standardizing outreach prep across a team
Know the limits
When not to use this skill
- You have no underlying research yet
- You want messages sent automatically (this only prepares)
- You expect invented personalization (it will not guess)
Outputs
One brief per prospect with a consistent, inspectable schema.
account_summaryA concise factual account recap.
relevant_contact_contextThe contact's role and relevance.
potential_pain_pointsLikely problems, evidence-based.
supporting_evidenceThe research behind each point.
conversation_angleA grounded angle to open with.
claims_requiring_verificationAssumptions to confirm before use.
Example
Example
A brief from existing research.
Input
Research: Lumen Robotics, mid-market SaaS, hiring engineers, no observability tool mentioned. Contact: Director of Platform Eng.Output
account_summary: Mid-market industrial SaaS, scaling engineering
relevant_contact_context: Director of Platform Eng; owns infra decisions
potential_pain_points: Scaling reliability while hiring fast
supporting_evidence: Active engineering hiring; growth stage
conversation_angle: Reliability as the team scales
claims_requiring_verification: No current observability tool (assumed)The brief is concise and grounded, and it clearly separates the evidence-based angle from the assumption (no current tool) that the rep must verify.
Setup
How to use the skill
General steps first, then notes for specific clients where verified.
- 1Download the file using the button below, or copy the Markdown.
- 2Place it in a directory named after the skill (e.g. skill-name/).
- 3Make sure the filename stays exactly SKILL.md.
- 4Add any references or assets included with the package.
- 5Load the skill into a compatible agent and provide the required inputs.
Claude Code
- 1Create a folder for the skill and save SKILL.md inside it.
- 2Place the folder where your project's skills are discovered.
- 3Reference the skill when you want it applied to your data.
Other compatible clients
- 1Confirm the client supports the open Agent Skills format.
- 2Load the SKILL.md file as instructed by that client.
- 3If skills are not auto-loaded, paste the Markdown as instructions.
Source
Full SKILL.md source
Read the rendered skill or copy the complete Markdown. The download is generated from this exact source.
Version 1.0 SKILL.md ~2 KB MIT
Outreach Brief Generator
Purpose
Convert structured prospect research into concise outreach preparation briefs.
When to use this skill
- Pre-call and pre-email preparation
- Turning research into a usable brief
- Grounding personalization in evidence
- Standardizing outreach prep across a team
When not to use this skill
- You have no underlying research yet
- You want messages sent automatically (this only prepares)
- You expect invented personalization (it will not guess)
Required inputs
- Structured prospect or account research
Optional inputs
- Your offering and value props
- The outreach channel
- A specific contact
Rules
- Use only the supplied research and context.
- Do not invent personalization, facts, or quotes.
- Separate evidence from assumptions explicitly.
- List claims requiring verification.
- Produce a brief; never send outreach.
Process
- Parse the research and any offering context.
- Summarize the account and contact context.
- Derive evidence-based pain points and an angle.
- Cite supporting evidence.
- List claims requiring verification.
Output format
Return one brief per prospect with the following fields:
- account_summary
- relevantcontactcontext
- potentialpainpoints
- supporting_evidence
- conversation_angle
- claimsrequiringverification
Validation
- Confirm every point cites research evidence.
- Confirm assumptions are flagged for verification.
- Confirm nothing was fabricated.
Limitations
- Brief quality depends on the input research.
- Pain points are hypotheses to confirm, not facts.
Before you rely on it
Safety and limitations
- Brief quality depends on the input research.
- Pain points are hypotheses to confirm, not facts.
- Review the output before acting on it.
- Do not upload confidential datasets to an external model without authorization.
- Outputs depend on the model and the source data and are not guaranteed to be accurate.
History
Changelog
- v1.0June 2026
- Initial release.
Questions
Agent Skill FAQ
What research does it need as input?
Structured prospect or account research — role, company context, and relevant signals. It condenses that into a brief; the thinner the research, the thinner the brief.
Does it write or send the outreach message?
No. It produces a research brief to prepare outreach. It does not draft final copy automatically or send anything.
Do I need ProfileSpider to use this skill?
No. The skill works on any compatible data. ProfileSpider is one convenient way to produce that structured input.
Does running this skill send data to ProfileSpider?
No. Downloading or copying the file does not send any data to ProfileSpider. What happens afterward depends on the AI service you load it into.
Are Agent Skills the same as prompts?
No. A skill is a structured, reusable package — task, inputs, rules, process, and output format — so the workflow runs consistently and can be shared, versioned, and edited.