Menu
Research a prospect then draft personalized outreach. Prefer Gmail, Drive, Sheets, and tagged files before web search, and create a Gmail draft when possible.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Plan, review, and then assemble a stakeholder-ready dashboard package from the current analysis run, with a native interactive canvas experience.
Data analysis skill hub. Routes to the right specialist subskill depending on the request — exploration, query writing, end-to-end analysis, visualization, validation, dashboard planning plus assembly, or recurring snapshot refresh.
End-to-end data analysis — from a quick metric lookup to a formal stakeholder report. Combines schema discovery, SQL execution, optional visualization, and an evidence-based summary. Use for general "analyze / what's happening with…" requests.
Create, edit, redline, comment on, and visually verify `.docx`, Word, and Google Docs-targeted document artifacts. Use for Word documents, `.docx` files, document creation, document edits, tracked changes, comments, render QA, and Google Docs-ready local DOCX generation.
Create stunning, animation-rich browser-native HTML presentations. Use only when the user explicitly wants an HTML/web presentation or animated interactive browser deck. Do not use for `.ppt`, `.pptx`, PowerPoint, Google Slides, native deck creation, native deck editing, deck templates, or PPTX conversion/export requests; use the `pptx` skill for those.
Work with PDF documents safely, including querying existing PDFs and creating simple image-based PDFs from workspace images.
| name | draft-outreach |
| description | Research a prospect then draft personalized outreach. Prefer Gmail, Drive, Sheets, and tagged files before web search, and create a Gmail draft when possible. |
Research first, then draft. This skill should never send generic outreach. Start with the seller's internal context, then enrich externally only where it improves the message.
| Connector | What It Adds |
|---|---|
| Gmail | Create a draft directly in the inbox and inspect prior threads |
| Drive | Reuse notes, decks, battlecards, or account plans |
| Sheets | Pull territory or account-tracker context |
| CRM | Prior relationship context, existing contacts |
| Enrichment | Verified email, phone, background details |
No connectors? The workflow still works. Return the email text and LinkedIn fallback.
+------------------------------------------------------------------+
| DRAFT OUTREACH |
| |
| Step 1: RESEARCH (always happens first) |
| - Gmail, Drive, Sheets, tagged files |
| - Google Search only after internal review |
| - CRM or enrichment if available |
| |
| Step 2: DRAFT |
| - Personalized opening from real context |
| - Relevant hook tied to priorities |
| - Clear proof and CTA |
| |
| Step 3: DELIVER |
| - Gmail draft if available |
| - Plain-text output always |
| - LinkedIn fallback if no email |
+------------------------------------------------------------------+
search_document and bounded inspect_document reads# Outreach Draft: [Person] @ [Company]
**Generated:** [Date] | **Research Sources:** [Gmail, Drive, Sheets, Web, CRM]
## Research Summary
**Target:** [Name], [Title] at [Company]
**Hook:** [Why reaching out now]
**Goal:** [Desired outcome]
## Outreach Brief
- Relationship status:
- Why now:
- Proof points to reference:
- Ask / CTA:
## Email Draft
**To:** [email if known]
**Subject:** [Personalized subject line]
[Email body]
## Subject Line Alternatives
1. [Option 2]
2. [Option 3]
## LinkedIn Message (if no email)
**Connection Request (<300 chars):**
[Short connection request]
**Follow-up Message:**
[Value-first message]
## Why This Approach
| Element | Based On |
|---|---|
| Opening | [Research finding that makes it personal] |
| Hook | [Their priority or pain point] |
| Proof | [Relevant customer story] |
| CTA | [Low-friction ask] |
Use Gmail first:
Use Drive and tagged files next:
Use Sheets if relevant:
Use Google Search after internal review:
Keep external research short and specific. Do not pad the message with generic facts.
Priority order:
Email structure
SUBJECT: [Personalized, short, non-spammy]
[Opening: personal hook]
[Interest: likely problem or opportunity]
[Desire: brief proof point]
[Action: clear CTA]
LinkedIn connection request
Hi [Name], [genuine context]. Would love to connect.
Subject: [Their initiative] + [your angle]
Hi [Name],
[Personal hook based on research].
[1 sentence on likely challenge].
[Brief proof point].
Worth a 15-min call to see if relevant?
Subject: Following up from [context]
Hi [Name],
[Reference to how you know them].
[Why reaching out now].
[Specific value you can offer].
[CTA]
Subject: [Short, curiosity-driven]
Hi [Name],
[Acknowledge time passed].
[New reason to reconnect].
[Simple question to reopen dialogue].
Subject: Great meeting you at [Event]
Hi [Name],
[Specific memory from conversation].
[Value-add or resource].
[Soft CTA for next conversation].
Stay outreach-first by default.
Escalate only when the ask clearly becomes a larger asset:
proposal-writing if the outreach is really a proposal or commercial follow-uppptx if the user needs a PowerPoint, Google Slides, native pitch deck, or editable presentation assetfrontend-slides only for explicit browser-native HTML/web presentationsWhen handing off, include:
If the seller says, "Write the follow-up and include a proposal next step," draft the outreach here first, then hand off the commercial document creation to proposal-writing.
If the seller says, "Draft outreach and make me a PowerPoint deck for the meeting," draft the message here, then pass the story, audience, and hook into pptx.