agentleFS
spiralcrew-ouspiralcrew-ou/profilespider-agent-skills/outreach-brief-generator/SKILL.md

outreach-brief-generator

Skill9 starsChanged 5 months agoMITView on GitHub

Converts structured prospect research into concise outreach preparation briefs. Use when the user provides prospect or account research and wants a brief with context, angles, and claims to verify. It generates a research brief and must not invent personalization or send outreach.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use only the supplied research and context.

    line 48
  2. Distinctive:

    Do not invent personalization, facts, or quotes.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Use only the supplied research and context.
  2. Do not invent personalization, facts, or quotes.
  3. Separate evidence from assumptions explicitly.
  4. List claims requiring verification.
  5. Produce a brief; never send outreach.

Process

  1. Parse the research and any offering context.
  2. Summarize the account and contact context.
  3. Derive evidence-based pain points and an angle.
  4. Cite supporting evidence.
  5. List claims requiring verification.

Output format

Return one brief per prospect with the following fields:

  • account_summary
  • relevant_contact_context
  • potential_pain_points
  • supporting_evidence
  • conversation_angle
  • claims_requiring_verification

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.