@opendirectory.dev/skills 0.1.50 → 0.1.51

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opendirectory.dev/skills",
-  "version": "0.1.50",
+  "version": "0.1.51",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "bin": {

package/registry.json

@@ -135,6 +135,16 @@
     "version": "1.0.0",
     "path": "skills/kill-the-standup"
   },
+  {
+    "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...",
+    "tags": [
+      "Social Media"
+    ],
+    "author": "ajaycodesitbetter",
+    "version": "1.0.0",
+    "path": "skills/linkedin-job-post-to-buyer-pain-map"
+  },
   {
     "name": "linkedin-post-generator",
     "description": "Converts any content, blog post URL, pasted article, GitHub PR description, or a description of something built, into a formatted LinkedIn post wit...",

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

@@ -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

@@ -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

@@ -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/evals/evals.json

@@ -0,0 +1,36 @@
+{
+  "skill_name": "linkedin-job-post-to-buyer-pain-map",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Analyze this job post for buyer pain. My product is Metabase, an open-source BI tool for non-technical teams. ICP: B2B SaaS, 50-500 employees, Series A-C, modern data stack. Job post: Acme Analytics (Series B, 120 employees) is hiring a Senior Data Platform Engineer to build a self-serve analytics layer for product managers and business leads. Responsibilities include owning ETL and dbt transformations, optimizing query performance for BI tools, and partnering with 6+ internal teams. Requirements: 5+ years with Snowflake, dbt, Airflow.",
+      "expected_output": "Agent checks GEMINI_API_KEY (set). Captures product brief (Metabase, open-source BI), ICP (B2B SaaS, 50-500, Series A-C, modern data stack), and job post. Extracts signals: team=Data Platform, seniority=Senior IC, emphasis=building new (self-serve analytics layer), stack hints=Snowflake, dbt, Airflow. Scores with the LLM: signal_strength 8-9 (explicit analytics pain, modern data stack match), urgency 7-8 (6+ teams partnering, scaling rapidly), icp_fit 8-9 (Series B, 120 employees, dbt+Snowflake). Overall score 80-90. Buy-vs-build: Hybrid (buy-and-build). Stage: Scaling post-PMF. Primary pain: data team bottleneck for business teams needing metrics access. Evidence cites 'self-serve analytics layer' and 'without pinging the data team'. Outreach angle references self-serve analytics build-out. Handoff block includes suggested personas (Head of Data, VP Product). Saves to docs/pain-maps/acme-analytics.md.",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Decode this job description for GTM signals. Product: Ramp, a sales onboarding platform. ICP: B2B SaaS, 100-1000 employees, 10+ sales reps, Series B+. Job post: CoolStartup Inc is hiring a Full Stack Engineer. 'We're looking for a rockstar full-stack engineer who loves building cool things. React, Node.js, PostgreSQL. Must be a team player in a fast-paced startup. We offer equity, unlimited PTO, and weekly team lunches.'",
+      "expected_output": "Agent checks GEMINI_API_KEY (set). Captures inputs. Extracts signals: team=Engineering, seniority=Mid-level IC, emphasis=generic (no clear pain), stack hints=React/Node/PostgreSQL (unrelated to sales onboarding). Scores: signal_strength 1-2 (no sales, onboarding, or GTM signals), urgency 1-2 (no urgency language, exploratory tone), icp_fit 1-2 (no company size, no sales team indicators). Overall score 10-20. Buy-vs-build: Unknown. Stage: Unknown. No primary pains inferred — agent explicitly states post is too generic to extract meaningful pain signals. Does not hallucinate pains. Recommends skipping this account. No outreach angles generated because signal strength is too low.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Build a pain map from this hiring post. Product: Datadog, monitoring and observability for cloud-native apps. ICP: cloud-native tech companies, 200+ engineers, Kubernetes, multi-cloud, Series C+ or public. Job post: MedSecure Health Systems (2,000 employees, healthcare technology) is hiring a Director of Cloud Infrastructure to lead cloud migration of 200+ on-premise applications to AWS, build container orchestration capabilities, and establish monitoring and observability practices from scratch. Requirements: AWS, Terraform, Kubernetes, HIPAA compliance.",
+      "expected_output": "Agent checks GEMINI_API_KEY (set). Captures inputs. Extracts signals: team=IT Infrastructure, seniority=Director/Leadership, emphasis=building new (from scratch) and replacing (migrating on-prem), stack hints=AWS/Terraform/Kubernetes. Scores: signal_strength 7-9 (Director-level, building observability from scratch, Kubernetes), urgency 7-8 (200+ app migration, leadership hire), icp_fit 2-4 (healthcare not cloud-native tech, on-prem migrating not cloud-native). Overall score 45-60. Stage: Mature/Enterprise. Buy-vs-build: Leaning buy. Primary pain: no observability stack exists, migrating 200+ apps blind. Evidence cites 'establish monitoring and observability practices from scratch'. Agent flags account as OUTSIDE CORE ICP with recommendation to deprioritize unless healthcare is an expansion segment. Still provides outreach angle in case user wants to pursue.",
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Analyze these job posts for buyer pain signals.",
+      "expected_output": "Agent detects GEMINI_API_KEY is missing from environment. Stops at Step 1. Tells the user: 'GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file.' Does not proceed to collect inputs or generate any analysis.",
+      "files": [],
+      "setup": "GEMINI_API_KEY not set in environment"
+    },
+    {
+      "id": 5,
+      "prompt": "Analyze these 3 job posts from the same company. Product: Gong, revenue intelligence platform. ICP: B2B SaaS, 200+ employees, 20+ sales reps, Series B+. Company: RapidScale (Series C, 450 employees). Post 1: VP of Sales — build and scale the outbound sales org from 15 to 50 reps over 18 months, establish sales methodology and playbooks, own pipeline generation strategy. Post 2: Revenue Operations Manager — implement and manage CRM workflows, build forecasting models, reduce manual pipeline reporting, first RevOps hire. Post 3: Senior Customer Success Manager — manage 40+ enterprise accounts, reduce churn in enterprise segment, build QBR process from scratch.",
+      "expected_output": "Agent checks GEMINI_API_KEY (set). Captures inputs. Groups all 3 posts under RapidScale. Extracts signals: Post 1 (GTM/Sales leadership, scaling 15→50 reps, building playbooks), Post 2 (RevOps, first hire, CRM + forecasting, manual pipeline reporting), Post 3 (CS, enterprise churn, QBR process). Identifies dominant theme: GTM infrastructure buildout across Sales + RevOps + CS. Scores: signal_strength 9-10 (multiple related hires, explicit GTM pain, VP-level), urgency 8-9 (scaling 15→50, first RevOps hire, enterprise churn), icp_fit 8-9 (Series C, 450 employees, 20+ reps). Overall score 85-95. Stage: Scaling post-PMF. Buy-vs-build: Hybrid (buy-and-build). Primary pains: (1) No sales methodology or playbooks for scaling team, (2) Manual pipeline reporting with no RevOps function, (3) Enterprise churn with no structured QBR process. Multiple outreach angles generated. Handoff block targets VP Sales and RevOps Manager as personas. Report groups all 3 signals under one company entry.",
+      "files": []
+    }
+  ]
+}

package/skills/linkedin-job-post-to-buyer-pain-map/references/examples.md

@@ -0,0 +1,122 @@
+# Worked Examples
+
+This file provides 3 worked examples showing how the skill interprets different types of job posts. The agent reads this file to calibrate its analysis quality.
+
+---
+
+## Example 1: High Signal, High ICP Fit
+
+### Input
+
+**Product brief:** "Metabase — open-source BI tool that lets non-technical teams query data and build dashboards without SQL. Target: Series A–C startups with growing data teams."
+
+**ICP description:** "B2B SaaS companies, 50–500 employees, Series A–C, have at least 2 data engineers, use modern data stack (dbt, Snowflake, BigQuery), need self-serve analytics for business teams."
+
+**Job post:**
+```json
+{
+  "company_name": "Acme Analytics",
+  "job_title": "Senior Data Platform Engineer",
+  "location": "Remote, US",
+  "seniority": "Senior / IC",
+  "team_or_function": "Data Platform / Infra",
+  "job_description_text": "We're looking for a Senior Data Platform Engineer to own our analytics infrastructure. You'll build a self-serve analytics layer so product managers and business leads can access metrics without pinging the data team. Responsibilities: own ETL pipelines and dbt transformations, optimize query performance for our BI tools, partner with 6+ internal teams to define metrics, and ensure data reliability for executive dashboards. Requirements: 5+ years with modern data stack (Snowflake, dbt, Airflow), experience building self-serve data products, strong SQL. We are a Series B company with 120 employees scaling rapidly."
+}
+```
+
+### Expected Output
+
+**Summary:**
+- Headline: "Staffing data infra to unblock self-serve analytics for non-technical teams"
+- Overall score: 87
+- Signal strength: 9 (explicit analytics pain + modern data stack + building self-serve layer)
+- Urgency: 8 (partnering with 6+ teams suggests backlog, "scaling rapidly")
+- ICP fit: 9 (Series B, 120 employees, dbt + Snowflake, self-serve analytics need)
+- Stage guess: Scaling post-PMF
+- Buy-vs-build: Hybrid (buy-and-build)
+  - _Reasoning: building infrastructure + likely to buy BI tooling_
+
+**Primary pain:** "Data team is a bottleneck for business teams needing metrics access. PMs and leads are blocked by ad-hoc data requests."
+
+**Evidence cited:** "product managers and business leads can access metrics without pinging the data team", "partner with 6+ internal teams"
+
+**Outreach angle:** "Reduce ad-hoc data fire drills — lead with how Metabase gives PMs self-serve dashboards so the data team stops being a ticket queue."
+
+---
+
+## Example 2: Low Signal, Generic Post
+
+### Input
+
+**Product brief:** "Ramp — sales onboarding platform for B2B SaaS. Helps VP Sales cut new-rep ramp time."
+
+**ICP description:** "B2B SaaS, 100–1000 employees, at least 10 sales reps, hiring SDRs/AEs, series B+."
+
+**Job post:**
+```json
+{
+  "company_name": "CoolStartup Inc",
+  "job_title": "Full Stack Engineer",
+  "location": "San Francisco, CA",
+  "seniority": "Mid-level / IC",
+  "team_or_function": "Engineering",
+  "job_description_text": "We're looking for a rockstar full-stack engineer who loves building cool things. You'll work on our product using React, Node.js, and PostgreSQL. Must be a team player who thrives in a fast-paced startup environment. We offer competitive salary, equity, unlimited PTO, and weekly team lunches. Come join our amazing culture!"
+}
+```
+
+### Expected Output
+
+**Summary:**
+- Headline: "Generic engineering hire with no relevant GTM or sales signals"
+- Overall score: 16
+- Signal strength: 1 (no sales, onboarding, or GTM signals; engineering role unrelated to product area)
+- Urgency: 2 (no urgency language, exploratory tone)
+- ICP fit: 2 (no company size, no sales team indicators, no relevant function)
+- Stage guess: Unknown (no indicators)
+- Buy-vs-build: Unknown
+
+**Primary pain:** None identified. Post is too generic to infer operational pain relevant to sales onboarding.
+
+**Note to user:** "This post contains minimal signal for your ICP. The role is a general engineering hire with no references to sales operations, onboarding, or GTM infrastructure. Recommend skipping."
+
+---
+
+## Example 3: Decent Pain, Out-of-ICP
+
+### Input
+
+**Product brief:** "Datadog — monitoring and observability platform for cloud-native applications. Target: tech companies running Kubernetes in production."
+
+**ICP description:** "Cloud-native tech companies, 200+ engineers, running Kubernetes/containers, multi-cloud, Series C+ or public."
+
+**Job post:**
+```json
+{
+  "company_name": "MedSecure Health Systems",
+  "job_title": "Director of Cloud Infrastructure",
+  "location": "Chicago, IL",
+  "seniority": "Director / Leadership",
+  "team_or_function": "IT Infrastructure",
+  "job_description_text": "MedSecure Health Systems is seeking a Director of Cloud Infrastructure to lead our cloud migration initiative. You will oversee the transition of 200+ on-premise applications to AWS, build container orchestration capabilities, and establish monitoring and observability practices from scratch. Manage a team of 8 infrastructure engineers. Requirements: 10+ years in infrastructure, experience with AWS, Terraform, container orchestration (Kubernetes preferred), HIPAA compliance expertise required. We are a 2,000-employee healthcare technology company."
+}
+```
+
+### Expected Output
+
+**Summary:**
+- Headline: "Healthcare company building cloud infra and observability from scratch"
+- Overall score: 62
+- Signal strength: 8 (Director-level, building observability from scratch, Kubernetes, AWS migration)
+- Urgency: 7 (200+ app migration, building from scratch, leadership hire)
+- ICP fit: 3 (healthcare, not cloud-native tech company; on-prem migrating to cloud, not cloud-native)
+- Stage guess: Mature / Enterprise
+- Buy-vs-build: Leaning buy
+  - _Reasoning: "establish monitoring and observability practices from scratch" suggests they need to adopt tooling_
+
+**Primary pain:** "No monitoring or observability stack exists. Migrating 200+ on-prem apps to AWS with zero cloud-native visibility."
+
+**Evidence cited:** "establish monitoring and observability practices from scratch", "transition of 200+ on-premise applications to AWS"
+
+**ICP flag:** ⚠️ Outside core ICP — healthcare vertical, on-prem migrating (not cloud-native). Pain is real and product-relevant, but company profile does not match ideal customer profile. Consider deprioritizing unless healthcare is an expansion segment.
+
+**Outreach angle:** "If pursued: lead with migration observability — reference the 200-app migration and offer a proof-of-value on the first 10 apps moved to AWS."

package/skills/linkedin-job-post-to-buyer-pain-map/references/scoring-rubric.md

@@ -0,0 +1,120 @@
+# Scoring Rubric
+
+This file defines the scoring model used by the linkedin-job-post-to-buyer-pain-map skill. The agent reads this file during Step 4 to evaluate each account.
+
+---
+
+## Three Scoring Dimensions
+
+### Signal Strength (1–10)
+
+Measures how many and how specific the hiring signals are that relate to the user's product area.
+
+**Scoring rules:**
+
+| Condition | Modifier |
+|-----------|----------|
+| Multiple related hires on the same team or problem area | +3 |
+| Explicit language about a pain area the user's product addresses | +2 |
+| Senior role (Head / Director / VP) in a relevant function | +1 |
+| Role responsibilities reference building, replacing, or fixing a system in the product's category | +1 |
+| "First X hire" or "0→1" language indicating new team formation | +1 |
+| Generic "nice-to-have" requirements with no clear pain signal | −1 |
+| Job post is mostly a list of perks and culture statements with minimal responsibilities | −2 |
+
+**Floor:** 1. **Ceiling:** 10. Clamp after summing.
+
+**Base:** Start at 3 for any post that mentions a function relevant to the user's ICP.
+
+---
+
+### Urgency (1–10)
+
+Measures how time-sensitive the hiring need appears from the text.
+
+**Scoring rules:**
+
+| Condition | Modifier |
+|-----------|----------|
+| Explicit urgency language: "immediate", "ASAP", "critical hire", "backfill" | +3 |
+| Multiple open roles in the same function at the same company | +2 |
+| Language suggesting firefighting: "stabilize", "fix", "unblock", "reduce downtime" | +2 |
+| Role described as replacement for a departing leader | +1 |
+| "Nice to have" tone, exploratory language ("we're thinking about...") | −2 |
+| No urgency indicators at all | −1 |
+
+**Floor:** 1. **Ceiling:** 10. Clamp after summing.
+
+**Base:** Start at 4 for any role at IC-Senior or higher that has a defined scope.
+
+---
+
+### ICP Fit (1–10)
+
+Measures how closely the company profile in the job post matches the user's `icp_description`.
+
+**Scoring rules:**
+
+| Condition | Modifier |
+|-----------|----------|
+| Industry matches ICP exactly | +3 |
+| Company size indicators match (headcount, "Series X", "enterprise") | +2 |
+| Tech stack or tool references overlap with ICP tech stack | +2 |
+| Role function matches ICP target persona function | +1 |
+| Industry is adjacent but not exact match | +1 |
+| Industry is clearly outside ICP (e.g., government when ICP is B2B SaaS) | −3 |
+| Company size indicators suggest a segment the user does not serve | −2 |
+
+**Floor:** 1. **Ceiling:** 10. Clamp after summing.
+
+**Base:** Start at 3 for any post where industry cannot be determined.
+
+---
+
+## Overall Score (10–100)
+
+```
+overall = round((0.4 × signal_strength + 0.3 × urgency + 0.3 × icp_fit) × 10)
+```
+
+Each dimension is 1–10, so the raw weighted sum ranges from 1.0 to 10.0. Multiply by 10 to get 10–100 scale.
+
+**Interpretation guide:**
+
+| Range | Label | Recommendation |
+|-------|-------|---------------|
+| 80–100 | Strong signal | Prioritize immediately. Build pain map and outreach angles. |
+| 60–79 | Moderate signal | Worth analyzing. Pain map likely has actionable pains. |
+| 40–59 | Weak signal | Low priority. Limited pain signal. |
+| 1–39 | Noise | Skip or deprioritize. Post is too generic or outside ICP. |
+
+---
+
+## Buy-vs-Build Inference
+
+The skill infers the company's likely posture toward buying vs building based on language patterns in the job description.
+
+| Language Pattern | Inferred Posture |
+|-----------------|-----------------|
+| "Build from scratch", "0→1", "greenfield", "design and implement new" | **Leaning build** |
+| "Evaluate and implement", "select vendor", "integrate third-party" | **Leaning buy** |
+| "Replace legacy", "migrate from", "modernize" | **Leaning buy** (replacing existing) |
+| "Own end-to-end", "build and maintain" + "integrate tools" | **Hybrid (buy-and-build)** |
+| "Scale existing", "optimize current" | **Hybrid** — already built, may buy to augment |
+| No clear signals | **Unknown** — do not guess |
+
+Output as a text label, not a numeric score.
+
+---
+
+## Stage Guess
+
+Inferred from company context clues in the job description.
+
+| Clue | Stage Guess |
+|------|------------|
+| "Series A", "seed", "early stage", < 50 employees | Pre-PMF or Early |
+| "Series B/C", "scaling", "hypergrowth", 50–500 employees | Scaling post-PMF |
+| "Enterprise", "Fortune 500", "publicly traded", > 500 employees | Mature / Enterprise |
+| "First [role] hire", "founding team" | Very early |
+| No clues available | "Unknown" |