npm - @opendirectory.dev/skills - Versions diffs - 0.1.50 → 0.1.52 - Mend

@opendirectory.dev/skills 0.1.50 → 0.1.52

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (18) hide show

package/skills/email-newsletter/templates/light-newsletter.html ADDED Viewed

@@ -0,0 +1,166 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <title>[SUBJECT]</title>
+  <link href="https://fonts.googleapis.com/css2?family=Instrument+Serif:ital@0;1&family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
+  <!--[if mso]>
+  <noscript><xml><o:OfficeDocumentSettings><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml></noscript>
+  <![endif]-->
+  <style>
+    @media only screen and (max-width: 600px) {
+      .container { width: 100% !important; }
+      .hero-h1   { font-size: 30px !important; }
+      .h2        { font-size: 28px !important; }
+      .pad       { padding-left: 24px !important; padding-right: 24px !important; }
+    }
+  </style>
+</head>
+<body style="margin:0;padding:0;background-color:#F0F0EE;-webkit-text-size-adjust:100%;-ms-text-size-adjust:100%;">
+  <!-- Preview text -->
+  <span style="display:none;max-height:0;overflow:hidden;opacity:0;font-size:1px;color:#F0F0EE;">[PREVIEW TEXT]</span>
+  <table width="100%" cellpadding="0" cellspacing="0" border="0" style="background-color:#F0F0EE;">
+    <tr>
+      <td align="center" style="padding:32px 16px;">
+        <table class="container" width="600" cellpadding="0" cellspacing="0" border="0" style="max-width:600px;width:100%;background-color:#FFFFFF;">
+          <!-- ══════════════════════════════════════════════════════
+               SECTION: HEADER
+          ═══════════════════════════════════════════════════════ -->
+          <tr>
+            <td bgcolor="#1A1A1A" style="background-color:#1A1A1A;padding:20px 40px;">
+              <table width="100%" cellpadding="0" cellspacing="0" border="0">
+                <tr>
+                  <td style="font-family:'Instrument Serif',Georgia,'Times New Roman',serif;font-size:20px;font-weight:400;color:#FFFFFF;letter-spacing:-0.01em;">[BRAND NAME]</td>
+                  <td align="right" style="font-family:Inter,Arial,Helvetica,sans-serif;font-size:11px;font-weight:500;color:#888888;letter-spacing:0.14em;text-transform:uppercase;white-space:nowrap;">Issue #[N] &nbsp;|&nbsp; [DATE]</td>
+                </tr>
+              </table>
+            </td>
+          </tr>
+          <!-- Brand strip -->
+          <tr>
+            <td bgcolor="[BRAND_COLOR]" style="background-color:[BRAND_COLOR];height:3px;font-size:1px;line-height:1px;">&nbsp;</td>
+          </tr>
+          <!-- ══════════════════════════════════════════════════════
+               SECTION: HERO (light — white bg)
+          ═══════════════════════════════════════════════════════ -->
+          <tr>
+            <td class="pad" bgcolor="#FFFFFF" style="background-color:#FFFFFF;padding:56px 40px 48px;">
+              <p style="margin:0 0 16px 0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:11px;font-weight:600;color:[BRAND_COLOR];letter-spacing:0.22em;text-transform:uppercase;">[CATEGORY LABEL]</p>
+              <h1 class="hero-h1" style="margin:0 0 20px 0;font-family:'Instrument Serif',Georgia,'Times New Roman',serif;font-size:46px;font-weight:400;line-height:1.05;color:#111111;letter-spacing:-0.02em;">[HERO HEADLINE]</h1>
+              <p style="margin:0 0 32px 0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:17px;line-height:1.6;color:#666666;">[HERO HOOK]</p>
+              <table cellpadding="0" cellspacing="0" border="0">
+                <tr>
+                  <td align="center" bgcolor="#111111" style="background-color:#111111;border-radius:8px;">
+                    <a href="[CTA_URL]" target="_blank" style="display:inline-block;padding:14px 32px;font-family:Inter,Arial,Helvetica,sans-serif;font-size:15px;font-weight:600;color:#FFFFFF;text-decoration:none;letter-spacing:0.01em;">[CTA BUTTON TEXT] &rarr;</a>
+                  </td>
+                </tr>
+              </table>
+            </td>
+          </tr>
+          <!-- ══════════════════════════════════════════════════════
+               SECTION: INTRO
+          ═══════════════════════════════════════════════════════ -->
+          <tr>
+            <td class="pad" bgcolor="#FFFFFF" style="background-color:#FFFFFF;padding:32px 40px 0;">
+              <p style="margin:0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:16px;line-height:1.7;color:#555555;">[INTRO TEXT]</p>
+            </td>
+          </tr>
+          <!-- DIVIDER -->
+          <tr>
+            <td bgcolor="#FFFFFF" style="background-color:#FFFFFF;padding:32px 40px 0;">
+              <hr style="border:none;border-top:1px solid #EEEEEE;margin:0;">
+            </td>
+          </tr>
+          <!-- ══════════════════════════════════════════════════════
+               SECTION: MAIN CONTENT
+          ═══════════════════════════════════════════════════════ -->
+          <tr>
+            <td class="pad" bgcolor="#FFFFFF" style="background-color:#FFFFFF;padding:32px 40px 8px;">
+              <p style="margin:0 0 18px 0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:15px;line-height:1.75;color:#444444;"><strong style="color:#111111;font-weight:700;">[BOLD CALLOUT]</strong> [paragraph]</p>
+              <p style="margin:0 0 18px 0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:15px;line-height:1.75;color:#444444;"><strong style="color:#111111;font-weight:700;">[BOLD CALLOUT]</strong> [paragraph]</p>
+              <p style="margin:0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:15px;line-height:1.75;color:#444444;"><strong style="color:#111111;font-weight:700;">[BOLD CALLOUT]</strong> [paragraph]</p>
+            </td>
+          </tr>
+          <!-- ══════════════════════════════════════════════════════
+               SECTION: STAT CALLOUT (light version)
+          ═══════════════════════════════════════════════════════ -->
+          <tr>
+            <td class="pad" bgcolor="#FFFFFF" style="background-color:#FFFFFF;padding:24px 40px;">
+              <table width="100%" cellpadding="0" cellspacing="0" border="0">
+                <tr>
+                  <td bgcolor="#F8F8F6" style="background-color:#F8F8F6;border-left:3px solid [BRAND_COLOR];padding:22px 24px;border-radius:0 6px 6px 0;">
+                    <p style="margin:0 0 8px 0;font-family:'Instrument Serif',Georgia,'Times New Roman',serif;font-size:22px;font-weight:400;line-height:1.3;color:#111111;">"[STAT OR QUOTE]"</p>
+                    <p style="margin:0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:12px;color:#999999;">[SOURCE]</p>
+                  </td>
+                </tr>
+              </table>
+            </td>
+          </tr>
+          <!-- ══════════════════════════════════════════════════════
+               SECTION: CTA CALLOUT CARD (light — dark card)
+          ═══════════════════════════════════════════════════════ -->
+          <tr>
+            <td class="pad" bgcolor="#FFFFFF" style="background-color:#FFFFFF;padding:8px 32px 48px;">
+              <table width="100%" cellpadding="0" cellspacing="0" border="0">
+                <tr>
+                  <td bgcolor="#111111" style="background-color:#111111;border-radius:12px;padding:48px 40px;text-align:center;">
+                    <h2 style="margin:0 0 12px 0;font-family:'Instrument Serif',Georgia,'Times New Roman',serif;font-size:36px;font-weight:400;line-height:1.05;color:#F2F2F2;letter-spacing:-0.02em;">[CTA CALLOUT HEADLINE]</h2>
+                    <p style="margin:0 0 28px 0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:16px;line-height:1.55;color:#AAAAAA;">[CTA CALLOUT BODY]</p>
+                    <table cellpadding="0" cellspacing="0" border="0" style="margin:0 auto;">
+                      <tr>
+                        <td align="center" bgcolor="[BRAND_COLOR]" style="background-color:[BRAND_COLOR];border-radius:8px;">
+                          <a href="[CTA_URL]" target="_blank" style="display:inline-block;padding:14px 32px;font-family:Inter,Arial,Helvetica,sans-serif;font-size:15px;font-weight:700;color:#0A0A0A;text-decoration:none;">[CTA BUTTON TEXT]</a>
+                        </td>
+                      </tr>
+                    </table>
+                  </td>
+                </tr>
+              </table>
+            </td>
+          </tr>
+          <!-- ══════════════════════════════════════════════════════
+               SECTION: FOOTER (light)
+          ═══════════════════════════════════════════════════════ -->
+          <tr>
+            <td bgcolor="#F8F8F6" style="background-color:#F8F8F6;border-top:1px solid #EEEEEE;padding:36px 40px 44px;">
+              <p style="margin:0 0 6px 0;font-family:'Instrument Serif',Georgia,'Times New Roman',serif;font-size:18px;font-weight:400;color:#111111;text-align:center;">[BRAND NAME]</p>
+              <p style="margin:0 0 24px 0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:12px;line-height:1.5;color:#AAAAAA;text-align:center;">[COMPANY NAME] &nbsp;&middot;&nbsp; [CITY, COUNTRY]</p>
+              <hr style="border:none;border-top:1px solid #E8E8E8;margin:0 auto 24px;width:96px;">
+              <p style="margin:0;font-family:Inter,Arial,Helvetica,sans-serif;font-size:12px;line-height:1.5;color:#BBBBBB;text-align:center;">
+                <a href="[UNSUBSCRIBE_URL]" style="color:#AAAAAA;text-decoration:underline;">Unsubscribe</a>
+                &nbsp;&nbsp;|&nbsp;&nbsp;
+                <a href="[PREFERENCES_URL]" style="color:#AAAAAA;text-decoration:underline;">Manage preferences</a>
+              </p>
+            </td>
+          </tr>
+        </table>
+      </td>
+    </tr>
+  </table>
+</body>
+</html>

package/skills/linkedin-job-post-to-buyer-pain-map/.env.example ADDED Viewed

@@ -0,0 +1,7 @@
+# linkedin-job-post-to-buyer-pain-map — Environment Variables
+# ============================================================
+# An LLM is required for pain map analysis and scoring.
+# Required: Gemini API key for signal analysis and pain inference
+# Get it: aistudio.google.com, Get API key
+GEMINI_API_KEY=your_gemini_api_key_here

package/skills/linkedin-job-post-to-buyer-pain-map/README.md ADDED Viewed

@@ -0,0 +1,144 @@
+# linkedin-job-post-to-buyer-pain-map
+<img src="cover.png" width="100%" alt="LinkedIn Job Post to Buyer Pain Map — Signal Decoder for GTM Teams" />
+Turn LinkedIn job posts into an actionable buyer pain map with signal strength, urgency, and outreach angles for each account.
+## What It Does
+- Parses 1–15 pasted job descriptions and groups them by company
+- Extracts team, seniority, responsibility emphasis, requirement language, and tool/stack hints from each post
+- Infers primary and secondary operational pains with cited evidence from the job text
+- Scores each account on 3 dimensions: signal strength (1–10), urgency (1–10), ICP fit (1–10)
+- Computes an overall priority score (10–100) using a transparent weighted formula
+- Determines buy-vs-build posture and company stage from hiring language
+- Generates 1–3 actionable outreach angles per account with talk-track bullets
+- Produces a structured handoff object ready for `outreach-sequence-builder` consumption
+## Requirements
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Gemini API key | Signal analysis, scoring, and pain inference | aistudio.google.com → Get API key |
+## Setup
+```bash
+cp .env.example .env
+```
+Fill in `GEMINI_API_KEY` (required).
+No other dependencies. The skill runs entirely through agent instructions and Gemini API calls.
+## How to Use
+Analyze a single job post:
+```
+"Analyze this job post for buyer pain. My product is [X]. ICP: [Y]. Here's the post: [paste job description]"
+```
+Batch analysis of multiple posts:
+```
+"Build a pain map from these 5 job posts. Product: [X]. ICP: [Y]. Posts: [paste all posts]"
+```
+Focus on positioning angles:
+```
+"Decode these hiring descriptions for positioning angles. Focus on positioning. Product: [X]. ICP: [Y]. Posts: [paste posts]"
+```
+Handoff to outreach:
+```
+"Analyze these job posts and give me a handoff I can pass to outreach-sequence-builder"
+```
+## Input Format
+Each job post should include at minimum:
+- **Company name** and **job title** (required)
+- **Job description text** — the full pasted content (required)
+- Location, seniority, team/function, URL (optional — inferred if missing)
+Posts can be pasted as plain text, numbered lists, or structured JSON objects.
+## Output
+For each company analyzed, the skill produces:
+1. **Summary** — headline, overall score, score breakdown with explanations, stage guess, buy-vs-build posture
+2. **Buyer Pain Map** — primary and secondary pains, each with label, description, and cited evidence
+3. **Outreach Angles** — 1–3 angles with narrative and talk-track bullets
+4. **Handoff** — structured block for outreach-sequence-builder (account summary, key pain, personas, tone)
+Reports are saved to `docs/pain-maps/` as dated markdown files.
+## Scoring Model
+| Dimension | Weight | Measures |
+|-----------|--------|----------|
+| Signal Strength | 40% | Density and specificity of relevant hiring signals |
+| Urgency | 30% | Time-sensitivity indicators in the job text |
+| ICP Fit | 30% | Company profile match to user's ICP description |
+**Overall Score** = `round((0.4 × signal + 0.3 × urgency + 0.3 × icp_fit) × 10)` → 10–100 scale.
+See `references/scoring-rubric.md` for full scoring rules and modifiers.
+## Plays Well With
+| Skill | How |
+|-------|-----|
+| `outreach-sequence-builder` | Feed the handoff block as input context to generate a multi-channel outreach sequence |
+| `noise-to-linkedin-carousel` | Use primary pains and evidence quotes as content source material |
+| `reddit-icp-monitor` | Cross-reference pain themes from job posts with Reddit discussions |
+## When NOT to Use
+- Need to **find** companies hiring → use `linkedin-hiring-intent-scanner` or `yc-intent-radar-skill`
+- Need to **write** outreach messages → use `outreach-sequence-builder`
+- Need to **monitor** platforms for signals → use `reddit-icp-monitor` or `twitter-GTM-find-skill`
+- Need contact data or email enrichment → this skill does not provide that
+## Project Structure
+```
+linkedin-job-post-to-buyer-pain-map/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── cover.png
+├── evals/
+│   └── evals.json
+└── references/
+    ├── scoring-rubric.md
+    └── examples.md
+```
+## License
+MIT
+## Installation in Claude Desktop App
+### Video Tutorial
+Watch this quick video to see how it's done:
+https://github.com/user-attachments/assets/ee98a1b5-ebc4-452f-bbfb-c434f2935067
+### Step 1: Download the skill from GitHub
+1. Copy the URL of this specific skill folder from your browser's address bar.
+2. Go to [download-directory.github.io](https://download-directory.github.io/).
+3. Paste the URL and click **Enter** to download.
+### Step 2: Install the Skill in Claude
+1. Open your **Claude desktop app**.
+2. Go to the sidebar on the left side and click on the **Customize** section.
+3. Click on the **Skills** tab, then click on the **+** (plus) icon button to create a new skill.
+4. Choose the option to **Upload a skill**, and drag and drop the `.zip` file (or you can extract it and drop the folder, both work).
+> **Note:** Always make sure you are uploading the specific folder that contains the `SKILL.md` file!

package/skills/linkedin-job-post-to-buyer-pain-map/SKILL.md ADDED Viewed

@@ -0,0 +1,301 @@
+---
+name: linkedin-job-post-to-buyer-pain-map
+description: Takes pasted LinkedIn job posts or hiring descriptions and converts them into a structured buyer pain map with inferred pains, capability gaps, buy-vs-build signal, account priority scores, and suggested outreach angles. Use when asked to analyze hiring posts, decode job descriptions for buyer intent, build a pain map from job listings, extract GTM signals from hiring activity, or prioritize accounts based on hiring data. Trigger when a user says "analyze these job posts", "what pain does this hiring signal", "build a pain map from these listings", "decode this job description", or "score these accounts from their hiring".
+author: ajaycodesitbetter
+version: 1.0.0
+---
+# LinkedIn Job Post to Buyer Pain Map
+Take LinkedIn job posts. Decode them into a structured buyer pain map with scores, pains, and outreach angles.
+---
+**Critical rule:** Every inferred pain must cite specific language from the job description that supports it. Never hallucinate pains that are not grounded in the text. If a post is too generic to infer pain, say so explicitly and assign a low signal strength score.
+**Ethical rule:** Do not infer personal attributes or protected characteristics about candidates. Focus strictly on company-level operational pain and organizational needs.
+---
+## Step 1: Setup Check
+Confirm required env vars:
+```bash
+echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"
+```
+**If GEMINI_API_KEY is missing:**
+Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file."
+---
+## Step 2: Collect Inputs
+The skill needs 3 required inputs. Collect them before proceeding.
+### 2a: Product Brief
+Ask: "Describe your product in 2-5 sentences. What do you do, what is your core value prop, and who do you target?"
+**If the user already included this in their prompt:** Extract it. Confirm: "Product brief captured: [summary]."
+### 2b: ICP Description
+Ask: "Describe your ideal customer profile in 2-6 bullets: industries, company sizes, roles you sell to, tech stack hints."
+**If the user already included this in their prompt:** Extract it. Confirm: "ICP captured: [summary]."
+### 2c: Hiring Posts
+Ask: "Paste the job descriptions you want analyzed. For each post, include the company name, job title, and the full description text. You can paste 1-15 posts."
+**Accepted formats:**
+- Raw pasted text with company name and job title clearly labeled
+- Structured JSON objects with fields: `company_name`, `job_title`, `location` (optional), `seniority` (optional), `team_or_function` (optional), `job_description_text`, `job_url` (optional)
+- Multiple posts separated by clear delimiters (--- or numbered)
+**If any field is missing:** Infer what you can from the description text. If company_name or job_description_text is missing, ask for it before proceeding.
+### 2d: Optional Inputs
+If the user provides any of these, capture them:
+- `account_notes`: additional context per company (funding, tech stack, known tools, contacts)
+- `focus_dimension`: "pipeline" (bias toward scoring and prioritization), "positioning" (bias toward messaging angles), or "both" (default)
+---
+## Step 3: Extract Signals
+For each job post, parse and extract:
+1. **Team / function:** Which team is this role on? (GTM, Product, Infra, Data, RevOps, CS, Engineering, etc.)
+2. **Seniority:** IC, Senior IC, Manager, Director, VP, C-level
+3. **Responsibilities emphasis:** Classify the dominant mode:
+   - Fire-fighting: "stabilize", "fix", "reduce downtime", "unblock"
+   - Building new: "build from scratch", "0→1", "greenfield", "design and implement"
+   - Optimizing: "scale", "optimize", "improve efficiency", "automate"
+   - Replacing: "replace legacy", "migrate from", "modernize"
+4. **Requirement language:** Note keywords that signal intent: "first X hire", "critical role", "immediate", "must have"
+5. **Tool / stack hints:** Any references to specific tools, platforms, or technology categories that overlap with the user's product area
+**Group by company.** If multiple posts come from the same company, group their signals together.
+State: "Extracted signals from X posts across Y companies."
+---
+## Step 4: Score with the LLM
+Read `references/scoring-rubric.md` for the full scoring model.
+Build the LLM request:
+```bash
+cat > /tmp/pain-map-score-request.json << 'ENDJSON'
+{
+  "system_instruction": {
+    "parts": [{
+      "text": "You are a GTM analyst who specializes in decoding hiring signals into buyer intent. For each account provided, you will score three dimensions and infer company context. Rules: (1) Every score must include a one-sentence plain-text explanation. (2) signal_strength measures how many and how specific the hiring signals are relative to the user's product area. (3) urgency measures how time-sensitive the hiring need appears. (4) icp_fit measures how closely the company matches the user's ICP description. (5) Each score is 1-10. (6) overall_score = round((0.4 * signal_strength + 0.3 * urgency + 0.3 * icp_fit) * 10). (7) Infer buy_vs_build from job language. Use EXACTLY one of these labels: 'Leaning build', 'Leaning buy', 'Hybrid (buy-and-build)', 'Unknown'. (8) Infer stage_guess from company clues: funding stage, employee count, company type. (9) Output valid JSON only."
+    }]
+  },
+  "contents": [{
+    "parts": [{
+      "text": "SCORING_CONTEXT_HERE"
+    }]
+  }],
+  "generationConfig": {
+    "temperature": 0.2,
+    "maxOutputTokens": 4096
+  }
+}
+ENDJSON
+curl -s -X POST \
+  "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash:generateContent?key=$GEMINI_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d @/tmp/pain-map-score-request.json \
+  | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['candidates'][0]['content']['parts'][0]['text'])"
+```
+Replace `SCORING_CONTEXT_HERE` with:
+- The product brief and ICP description from Step 2
+- The extracted signals per company from Step 3
+- The scoring rubric rules from `references/scoring-rubric.md`
+- Instructions to output JSON with: `company_name`, `headline`, `overall_score`, `score_breakdown` (signal_strength, urgency, icp_fit — each with score and explanation), `stage_guess`, `buy_vs_build_guess`
+---
+## Step 5: Build Pain Map
+For each account, use the extracted signals and LLM scoring context to build the buyer pain map.
+```bash
+cat > /tmp/pain-map-analysis-request.json << 'ENDJSON'
+{
+  "system_instruction": {
+    "parts": [{
+      "text": "You are a B2B pain analyst who reads job descriptions and identifies the operational pains a company is experiencing. Rules: (1) Every pain must have a short label, a 1-3 sentence description, and specific phrases quoted from the job post as supporting evidence. (2) Classify pains as primary (directly relevant to the user's product) or secondary (real pain but tangential to the product). (3) If a post is too generic to infer specific pain, state that explicitly — do not hallucinate. (4) For each account, also generate 1-3 recommended outreach angles. Each angle has: angle_name (short), narrative (1-2 sentences on how to lead), and talk_track_bullets (2-4 concrete talking points). (5) Outreach angles must reference specific pains and evidence, not generic value props. No banned words: synergy, leverage, innovative, cutting-edge, best-in-class, world-class, game-changing, disruptive, seamless, robust, comprehensive, revolutionize, transform, streamline. (6) Output valid JSON only."
+    }]
+  },
+  "contents": [{
+    "parts": [{
+      "text": "ANALYSIS_CONTEXT_HERE"
+    }]
+  }],
+  "generationConfig": {
+    "temperature": 0.4,
+    "maxOutputTokens": 8192
+  }
+}
+ENDJSON
+curl -s -X POST \
+  "https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash:generateContent?key=$GEMINI_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d @/tmp/pain-map-analysis-request.json \
+  | python3 -c "import sys,json; d=json.load(sys.stdin); print(d['candidates'][0]['content']['parts'][0]['text'])"
+```
+Replace `ANALYSIS_CONTEXT_HERE` with:
+- The product brief and ICP description
+- Each company's job posts (full text)
+- The scores and context from Step 4
+- Account notes if provided
+- The focus_dimension preference (pipeline / positioning / both)
+- Instructions to output per-account: `buyer_pain_map` (primary_pains, secondary_pains) and `recommended_outreach_angles`
+Read `references/examples.md` to calibrate the expected output quality and depth.
+---
+## Step 6: Build Handoff Object
+For each account, generate a structured handoff block that `outreach-sequence-builder` can consume directly:
+```
+handoff:
+  for_outreach_sequence_builder:
+    account_summary: 2-3 sentence recap of the company's situation and hiring context
+    key_pain: The single most actionable pain in one sentence
+    suggested_personas: 2-4 job titles of the people most likely to own this pain
+    tone: One sentence describing the recommended outreach tone
+```
+The handoff must be concrete enough that someone could paste it into outreach-sequence-builder's prompt and get a usable sequence without re-researching the account.
+---
+## Step 7: Self-QA
+Run every check and fix violations before presenting:
+- [ ] Every inferred pain cites at least one specific phrase from the job description
+- [ ] No pains hallucinated for generic/low-signal posts (check posts with signal_strength ≤ 3)
+- [ ] All three scores (signal_strength, urgency, icp_fit) have a one-sentence explanation
+- [ ] Overall score matches the formula: `round((0.4 × signal + 0.3 × urgency + 0.3 × icp_fit) × 10)`
+- [ ] Buy-vs-build label is one of: "Leaning build", "Leaning buy", "Hybrid (buy-and-build)", "Unknown"
+- [ ] No banned words in outreach angles: synergy, leverage, innovative, cutting-edge, best-in-class, world-class, game-changing, disruptive, seamless, robust, comprehensive, revolutionize, transform, streamline
+- [ ] Each outreach angle has 2-4 talk track bullets, not generic value statements
+- [ ] Out-of-ICP accounts are flagged with a clear recommendation to deprioritize
+- [ ] Handoff objects are complete with all 4 fields (account_summary, key_pain, suggested_personas, tone)
+- [ ] No personal attributes or protected characteristics inferred about candidates
+- [ ] Posts grouped by company when multiple posts are from the same company
+Fix any violation before presenting.
+---
+## Step 8: Output and Save
+### Human-readable output
+Present the full analysis in this format:
+```
+## Buyer Pain Map — [YYYY-MM-DD]
+**Product:** [product name from brief]
+**Posts analyzed:** X posts across Y companies
+**Focus:** [pipeline / positioning / both]
+---
+### [Company Name] — Score: [N]/100
+**Headline:** [one-line summary of what the hiring reveals]
+| Dimension | Score | Explanation |
+|-----------|-------|-------------|
+| Signal Strength | N/10 | [one sentence] |
+| Urgency | N/10 | [one sentence] |
+| ICP Fit | N/10 | [one sentence] |
+**Stage:** [stage guess] | **Buy-vs-Build:** [posture label]
+#### Primary Pains
+- **[Pain label]:** [1-3 sentence description]
+  - Evidence: "[quoted phrase from job post]"
+#### Secondary Pains
+- **[Pain label]:** [1-3 sentence description]
+  - Evidence: "[quoted phrase from job post]"
+#### Recommended Outreach Angles
+1. **[Angle name]:** [narrative]
+   - [bullet 1]
+   - [bullet 2]
+   - [bullet 3]
+#### Handoff → outreach-sequence-builder
+> **Summary:** [2-3 sentences]
+> **Key pain:** [one sentence]
+> **Suggested personas:** [list]
+> **Tone:** [one sentence]
+---
+[repeat for each company, ordered by overall_score descending]
+```
+### Save to file
+```bash
+mkdir -p docs/pain-maps
+OUTFILE="docs/pain-maps/$(date +%Y-%m-%d).md"
+cat > "$OUTFILE" << 'EOF'
+REPORT_CONTENT_HERE
+EOF
+echo "Pain map saved to $OUTFILE"
+```
+If multiple companies are analyzed, also save individual files using slugified company names (lowercase, replace spaces and special characters with hyphens, strip trailing hyphens):
+e.g., "ACME, Inc." → `acme-inc.md`, "CoolStartup Inc" → `coolstartup-inc.md`
+```bash
+SLUG=$(echo "COMPANY_NAME" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/-$//')
+cat > "docs/pain-maps/${SLUG}.md" << 'EOF'
+INDIVIDUAL_ACCOUNT_CONTENT_HERE
+EOF
+```
+---
+## When to Use
+- You have 1-15 pasted job descriptions and want to know what pain each company is feeling
+- You are planning account-based outreach and need structured pain analysis before writing sequences
+- You want to prioritize which hiring-signal accounts to pursue first
+- A PMM wants real-world pain language from job posts to refine positioning
+## When NOT to Use
+- You need to **find** companies that are hiring (use `linkedin-hiring-intent-scanner` or `yc-intent-radar-skill` instead)
+- You need to **write outreach messages** (use `outreach-sequence-builder` instead — feed it the handoff from this skill)
+- You want to **monitor** a platform for signals over time (use `reddit-icp-monitor` or `twitter-GTM-find-skill` instead)
+- You need contact information or email enrichment (this skill does not provide that)
+## Plays Well With
+- **outreach-sequence-builder**: Pass the `handoff.for_outreach_sequence_builder` block directly as context when building a sequence.
+- **noise-to-linkedin-carousel**: Use the primary pains and evidence quotes as source material for a carousel about buyer problems.
+- **reddit-icp-monitor**: Cross-reference pain themes from job posts with pain themes showing up in Reddit discussions.

package/skills/linkedin-job-post-to-buyer-pain-map/cover.png ADDED Viewed

Binary file